Siebel Business Process Designer Administration Guide > Creating Workflow Policies > Working with Workflow Policies >

Understanding the Policies List Applet

Table 61 defines the Policies List applet fields.

Table 61. Policies Applet Fields
Policy Name
The name of the workflow policy.
Workflow Object
The workflow policy object for which the policy was created, for example, Service Request, Activity, or Accounts. This field is required.
The workflow policy group to which the policy belongs. Each policy must be assigned to a workflow policy group.
See the note following this table for information about changing workflow policy groups.
Any comments about the purpose or use of the policy.
Activation Date/Time
The date and time that the policy was or will be activated. If this field is null, the policy is activated immediately.
Expiration Date/Time
The date and time that the policy expires. If this field is null, the policy is active indefinitely.
The duration fields specify how long in days, hours, or minutes all conditions must be true for the workflow policy to be executed.
This field is ignored if the policy is run in batch mode.
Created By
The login name of the person who created the workflow policy. The information in this field is automatically filled. Read-Only.
Created On
The date and time the workflow policy was created. The information in this field is supplied for you. Read-Only.
The number of records that meet the policy conditions before the policy action executes. If you do not specify a quantity, Siebel Workflow assumes a quantity of 1. Quantity allows policy administrators to create conditions that are based on a number of records that meet the policy conditions. For example, an administrator may create a workflow policy that sends a message broadcast when 20 or more critical service requests are open.
When Batch is checked, this indicates that this policy should evaluate all records that potentially meet the conditions of the policy. The Workflow Monitor Agent scans all records using the conditions of the policy to find the matches.
When this field is checked, run Workflow Monitor Agent with the Batch Mode flag set to TRUE.
The default is unchecked.

NOTE:  Before you can move a Workflow Policy from one group to another group, all requests associated with that Workflow Policy must complete. If a Workflow Policy's group is changed while associated requests are pending, the Workflow Monitor Agent will fail with the error Rule Not Found. If this occurs, restore the Workflow Policy to its original group, wait for the requests to complete, and then proceed with the change.

 Siebel Business Process Designer Administration Guide 
 Published: 29 May 2003