Siebel Business Process Framework: Workflow Guide > Defining Custom Workflow Policies > Process of Defining a Workflow Policy >

Defining a Workflow Policy

This task is a step in Process of Defining a Workflow Policy.

You use the Workflow Policies view to define a workflow policy. For more information, see Examples of Configuring a Workflow Policy.

To define a workflow policy

1. In the Siebel client, navigate to the Administration-Business Process screen, and then the Policies view.
2. In the list for the Policies List, choose New Record from the applet level menu, and then define fields using values from the following table.

   Field	Description	Explanation
   Name	Define the workflow policy name.	Not applicable
   Workflow Object	Define the workflow policy object for which the workflow policy is defined.	For example, choose Service Request, Activity, or Accounts. This field is required.
   Policy Group	Define the workflow policy group to which the workflow policy belongs.	You must assign each workflow policy to a workflow policy group. For more information, see Moving a Workflow Policy to a Different Group.
   Activation	Define the date and time when Siebel CRM must activate the workflow policy.	If this field is empty, then Siebel CRM activates the workflow policy immediately.
   Expiration	Define the date and time when Siebel CRM must expire the workflow policy.	If this field is empty, then the workflow policy remains active indefinitely.
   Duration	Define the duration fields in days, hours, or minutes that the workflow policy conditions must be true in order for Siebel CRM to run the workflow policy.	If the workflow policy runs in batch, then Siebel CRM ignores this field.
   Qty	Define the number of records that must meet the workflow policy conditions before Siebel CRM runs the workflow policy action.	If you do not define a value in the Qty field, then Siebel Workflow assumes a quantity of 1. Qty allows you to define a workflow policy condition according to the number of records that meet the condition determines. For example, you can define a policy that sends a broadcast message if 20 or more critical service requests are open.
   Batch Mode	If the Batch Mode field contains a check mark, then this workflow policy evaluates records that meet the workflow policy conditions.	The Workflow Monitor Agent uses the workflow policy conditions to identify records to process. If the Batch Mode field contains a check mark, then you must run the Workflow Monitor Agent with the Batch Mode field set to TRUE.

3. In the Conditions list, choose New Record from the applet level menu, and then define fields using values from the following table.

   Field	Usage	Example
   Condition Field	Define the workflow policy component column in the workflow policy object that the workflow policy condition references. Values that Siebel CRM displays in the Condition Field are context sensitive, depending on the value you choose for the Workflow Object in Step 2. To allow Siebel CRM to call a workflow policy that contains a Condition Field that is not equal to [Value n], a value must be defined in this field that is different than the value that the workflow policy condition contains. If Condition Field contains no value, then Siebel CRM does not call the workflow policy and it uses the IS NULL operator.	Choose Service Request Area from the drop-down list.
   Operation	Define the comparison that Siebel CRM must make between the value of the column for a workflow policy agent and the value you define. Choose the comparison from the drop-down list for the field. For more information, see Examples of Configuring Workflow Policies.	Choose equals (=) from the drop-down list.
   Value	Define the value that Siebel CRM compares to the value that exists in the column of the workflow policy instance. If the Comparison field does not contain one of the following values, then the Value field is a required: Is Null Is Not Null Is Updated Is Deleted Is Added For more information, see Examples of Configuring Workflow Policies, and Using Date Calculations in the Conditions List.	Choose Printer from the drop-down list.

4. In the Actions list, choose New Record from the applet level menu, and then define fields using values from the following table.

   Field	Usage
   Action	Pick the action that Siebel CRM runs with this workflow policy.
   Sequence	Define the sequence of the action relative to other actions.
   Consolidate	If more than one record meets the workflow policy conditions during the same action interval, then you can consolidate the action to one instance. To consolidate an action, make sure the consolidate field contains a check mark. The consolidate field is not available with an action that sends a page.

5. Optional. Repeat Step 4 to add more actions, as necessary.

Restrictions with Defining a Workflow Policy

If you define a workflow process, then note the following restrictions:

• A workflow policy cannot reference the S_DOCK_TXN_LOG table. The unique index for this table is TXN_ID rather than the ROW_ID that other Siebel tables use. Siebel Workflow uses ROW_ID to do the comparison and run actions. If it makes comparisons to the S_DOCK_TXN_LOG table, then Siebel CRM creates an error.
• You cannot run a business service from a workflow policy.
• A workflow policy updates a database field directly through the data layer. It does not update a field through the business object layer. Siebel CRM can run a workflow process that includes a business component event that is related to the updated field.