Siebel Business Process Framework: Workflow Guide > Reference Materials for Siebel Workflow > Predefined Workflow Policies >

Identifying the Source Table When Modifying an Existing Workflow Policy

When defining the types of workflow policies you must operate for your business, you might find that the predefined workflow policy objects do not contain the policy components you need. Use the procedures in this topic as a general guideline for identifying the source database table and column when modifying an existing workflow policy object.

Tasks you should perform before modifying a workflow policy object include:

• Identify the names of the workflow policy object's database table and column. If you are going to add or modify a component, you must know the relationship between the component and the primary workflow policy component.
• Make sure you do not have other records referencing this object that can be affected by your change. For example, before inactivating a component column, confirm that no policy conditions are referencing the component column.

The procedures in this topic are presented in the context of Account objects.

To identify the database table

1. In the Siebel client, navigate to the appropriate workflow policy object view. This is the view that contains the business data you need to monitor.

   For example, if you must modify the workflow for an account activity, you navigate to Accounts > Accounts List > Activities.

2. Choose Help > About View.

   About View identifies the Business object, Business components, and applets this view uses.

   In the example of the Account Activities view, the dialog box identifies Action as the business component used by the Activities applet.

3. In Siebel Tools, navigate to the Business Components OBLE, then locate the business component object definition named Action.

   Note the value in the Table property. In this example, the table name is S_EVT_ACT. You use this table name when you create a workflow policy component.

Next, determine the relationship between a business component and the primary workflow policy component.

To determine the relationship between the business component and the primary workflow policy component

1. Navigate to the Business Objects OBLE, then choose the object definition for the business object.

   In this example, choose the Account business object.

2. With the business object still chosen, navigate to the Business Object Components OBLE, choose the object definition with Action in the Bus Comp property, then click the hyperlink in the Link Property.
3. Note that the Source Field property is empty and the Destination Field property contains Account Id.

   The value in the Link property identifies the link that defines the relationship between the Account and the Action business components.

   This Link defines the relationship between the parent Business Component and the child Business Component through the Source field and Destination field.

   An empty Source Field property indicates that the join is using the ROW_ID column of the table defined in the Table property of the parent business component.

   The Destination Field property defines the field within the child business component that is a foreign key to the Business Component.

4. Click the hyperlink in the Child Business Component property.

   Clicking the hyperlink in the Child Business Component property navigates you to the object definition in the OBLE for the Action business component.

5. In the Object Explorer, expand the Business Component object type to expose the Field object type.
6. Choose the Account Id field, then note the value in the Column property.

   The Column property contains TARGET_OU_ID, which is the column in the table the Account Id field references. You use this information when you define the workflow policy component.