Generating Database Triggers with Specialized and Standard Operators

Siebel CRM implies an OR between specialized operators, where one or more of the Workflow Policy conditions must be met before the action occurs. For example, a service representative can receive an email if Siebel CRM adds an activity to an open service request. The following conditions in the policy implement this example:

• Service Request Status = 'Open'

• Service Request Activity Component IS ADDED

If a Workflow Policy condition is IS ADDED or IS UPDATED, then the database triggers that Siebel CRM creates do not represent every condition defined in the policy. The policy ignores any database triggers that are not represented. For details, you can examine the entries in the trigger.sql file that Siebel CRM creates as a result of doing the comparison. This behavior is expected.

If you modify a condition, then you must run Generate Triggers so that Siebel CRM implements this condition. For more information, see Overview of Creating Database Triggers.

If you use a Workflow Policy condition with a standard operator, then the database triggers that Siebel CRM creates encompass the condition. If you use a specialized operator, then Workflow Monitor Agent evaluates this condition at runtime.