1. Business Process Framework: Workflow Guide
  2. Configuring Batch Mode to Ensure Siebel CRM Calls a Workflow Policy Correctly

Configuring Batch Mode to Ensure Siebel CRM Calls a Workflow Policy Correctly

You can configure batch mode to make sure Siebel CRM calls a Workflow Policy correctly.

To configure batch mode to ensure Siebel CRM calls a Workflow Policy correctly

  1. Make sure the Batch Mode field is checked for the Workflow Policy.

  2. Set the Batch Mode parameter to TRUE for the Workflow Monitor Agent.

Example of Configuring Batch Mode to Ensure Siebel CRM Calls a Workflow Policy Correctly

The example configuration shown in the following table demonstrate why a previously existing record that meets the Workflow Policy conditions does not call the Workflow Policy.

Field Value

Workflow Policy Name

Account Active

Workflow Object

Account

Group

Test

Using this example, to monitor a field, Siebel CRM starts a Workflow Policy that references a business object when the following situations occur:

  • Workflow Condition, Account Status is Active.

  • Workflow Action, Action: Send Email to Employee.

  • Remove and create database triggers, and then start a Workflow Monitor Agent server task for the Test Workflow Policy group.

Note the following:

  • If a user adds a new account that meets these requirements, then Siebel CRM calls the Workflow Policy.

  • If a user updates an existing account in such a way that these requirements are met, then Siebel CRM calls the Workflow Policy.

If an account existed in the Siebel database before you created the Workflow Policy, and if the account meets the requirements that you define for this Workflow Policy, then this Workflow Policy does not start a Workflow Process for this account.

If Siebel CRM creates database triggers for this Workflow Policy, then the Workflow Monitor Agent evaluates a record only if the user updates it or if the user creates a new record. Old records are not affected.

To evaluate an account record that existed before you created the Workflow Policy, make sure the Batch Mode field is checked for the Workflow Policy, and that the Workflow Monitor Agent runs with Batch Mode set to TRUE.