Siebel Business Process Designer Administration Guide > Workflow Policies > About Creating Workflow Policies >

Creating Workflow Policies

After creating your workflow policy actions and workflow policy groups, you are ready to go to the Workflow Policies view to complete your workflow policy creation.

You create a new workflow policy after you create the policy action and the policy group.

The Workflow Policies view is made up of four applets:

• Policies List applet. Where you enter and view information about the workflow policy. The entry applet toggles with a list applet so that you can quickly move between working on an individual policy and viewing information about several policies or groups of policies. See About the Policies List Applet.
• Conditions applet. Where you define or change the conditions for the workflow policy. You can define as many conditions as necessary. All the conditions for the policy must be met to trigger the workflow policy action. If you want the policy to be triggered when one or another condition is true, you must create a separate workflow policy for each condition. See About the Conditions Applet.
• Actions applet. Where you enter the name of the previously defined workflow policy action you want to take place when the conditions of the workflow policy are met. See About the Actions Applet.
• Arguments applet. Where you can review the workflow policy action arguments.

To create a Workflow policy

1. From the application-level menu, choose Navigate > Site Map > Administration - Business Process > Policies.
2. In the Policies List applet, select New Record from the applet-level menu, create a policy name and fill in the other applet fields.
3. Fill in the fields in the Conditions applet.
4. Fill in the name of the action you created in the Workflow Policies Actions view and, if necessary, check the Consolidate field.

NOTE:  Workflow policies can not be based on the table S_DOCK_TXN_LOG. The unique index for this table is TXN_ID, rather than ROW_ID for other standard Siebel tables. Because Workflow uses ROW_ID to do the comparison and execute actions, it will error out if used against S_DOCK_TXN_LOG.

NOTE:  You cannot execute a Business Service from a Workflow Policy.

Examples of Workflow Policies

The following are examples of workflow policies for specific situations. You can use these examples as the basis for creating your own workflow policy actions.

• Example of a Workflow Policy: Creating a Send Page Workflow Policy
• Example of a Workflow Policy: Creating a Send Email Workflow Policy

NOTE:  Workflow policies update the database fields directly through the Data Layer, and do not go through the Business Object Layer; therefore, any Workflow Processes that include Business Component events related to the updated fields are not executed.

Using Batch Mode with Workflow Policies

You can create Workflow policies as batch policies by checking the Batch check box in the Policies applet. When you start Workflow Monitor in batch mode, it checks for policies with the Batch check box marked. Each policy causes an SQL statement to be issued to identify the specific records that meet the policy conditions. The records identified are then processed in turn and the appropriate actions are carried out.

You can use the batch function to consolidate email messages for a designated recipient by checking the Batch field in the Actions applet in the Workflow Policies Policies view.

If you consolidate email messages, the recipient would receive one email with the information of multiple actions rather than multiple emails. For example, you can create a workflow policy that sends an email to the director of sales each time a quote is submitted with a discount over 30%. If 20 sales representatives submit quotes with the 30% discount and the Batch field is checked, the director of sales receives one email listing the 20 quotes. If the Batch field is not checked, the director of sales will receive 20 email messages.

NOTE:  When creating a batch type workflow policy, the comparison operators IS ADDED, IS UPDATED, or IS DELETED must be used in conjunction with regular conditions. These comparison operators are considered special conditions intended for Dynamic mode when triggering rows to look up regular conditions.