Siebel Business Process Framework: Workflow Guide > Using Predefined Workflow Policies > About Workflow Policies >

Overview of Workflow Policy Objects

A workflow policy object provides the context in which Workflow Policies operate. The workflow policy object, through the policy components of the workflow process, defines the set of tables and columns that a workflow policy monitors and how each table in the workflow policy object relates to the other tables. This collection of columns and the relations between the tables of the workflow policy object represent the entity in Siebel Tools that you must monitor.

Siebel Tools allows you to access predefined workflow policy objects for common business requirements, such as opportunities, service requests, or contacts. You can modify some predefined workflow policy objects through administrative screens in the Siebel client. To define a custom workflow policy object, you can use Siebel Tools.

Relationships Between Objects of a Workflow Policy

Figure 19 illustrates the relationships that exist between workflow policy objects, workflow policy columns, and workflow policy programs.

Figure 19. Relationships That Exist Between Workflow Policy Objects, Programs, and Columns

Explanation of Callouts

The following relationships exist between workflow policy objects:

1. Workflow Policy Object. A workflow policy object is a collection of workflow policy components. It is a parent to the workflow policy components and the workflow policy component columns.
2. Workflow Policy Component. A workflow policy component is a logical mapping to a database table in the Siebel database. It defines the relations between the primary workflow policy component and other workflow policy components of a workflow policy object. Except for the primary workflow policy component, each workflow policy component defines a relation to another workflow policy component. To create this relation, Siebel CRM defines a source policy column and a target policy column. These source and target columns of a workflow policy component identify foreign key relations between the tables.

   A primary workflow policy component is a workflow policy component to which other workflow policy components are directly or indirectly related. Siebel CRM can define the workflow policy columns that are available for monitoring in the workflow policy from these workflow policy components. Each workflow policy object contains only one primary workflow policy component. The other workflow policy components of a workflow policy object are directly or indirectly related to the primary workflow policy component.

3. Workflow Policy Component Column. A workflow policy component column defines the columns in the Siebel database table that Siebel CRM can monitor. You can allow Siebel CRM to monitor these columns when you define workflow policy conditions for a workflow policy. For more information, see How Siebel Tools Indicates the Primary Workflow Policy Component.

To define a workflow policy object and the components of a workflow process, it is recommended that you familiarize yourself with the Siebel Data Model. For more information, see Siebel Data Model Reference on My Oracle Support.

Viewing the Hierarchy That Exists Between Workflow Policy Objects

Each workflow policy component can expose a number of workflow policy component columns. In the Object Explorer, a workflow policy component column is the child object of a workflow policy component, which is itself a child object of a workflow policy object. To view this hierarchy, see Hierarchy of Workflow Policy Objects.

Example of an Entity Relationship Diagram for a Workflow Policy

Figure 20 displays the entity relationship diagram of four workflow policy components for a service request. It illustrates each of the components, their relations to one another, and the columns that are of interest. Service request is the primary workflow policy component. Siebel CRM joins the other three components to the primary directly or indirectly.

Figure 20. Example of an Entity Relationship Diagram for a Workflow Policy

Using a Workflow Policy to Monitor Tables

A workflow policy can monitor only Siebel database tables. You cannot use a workflow policy to monitor a database table that is external to Siebel CRM.

CAUTION:  Do not monitor the S_DOCK_TXN_LOG table or table columns of Enterprise Integration Manager (EIM). Siebel CRM prefixes the name of an EIM table with EIM_ or ends it with _IF. Siebel CRM can monitor most tables except S_DOCK_TXN_LOG and EIM tables.