How Generate Triggers Works with a Workflow Policy That Contains Multiple Conditions

If a Workflow Policy includes two or more Workflow Policy conditions, then Generate Triggers uses OR logic instead of AND logic. The following table shows some example Workflow Policy conditions that Siebel CRM uses to create a Workflow Policy that references the Account object.

Property Condition 1 Condition 2

Condition Field

Account Modification Num

Account Last Update By

Operation

> (greater than)

<> (not equal to)

Value

0

0-1

Siebel CRM can use multiple database triggers for multiple Workflow Policy conditions in one Workflow Policy. This configuration keeps Generate Triggers functionality and Workflow Monitor Agent functionality separate:

  • Generate Triggers monitors changes that Siebel CRM makes to database records and inserts records in tables that are specific to a Workflow Policy.

  • Workflow Monitor Agent evaluates conditions, determines if the conditions that are associated with the rule are met, and runs the actions that are associated with the Workflow Policy.