How the Workflow Monitor Agent Runs Workflow Policies

The Workflow Monitor Agent runs several server processes that monitor the Siebel database. In summary, the Workflow Monitor Agent does the following:

• Examines the S_ESCL_REQ table to determine when the Workflow Policy conditions are met.

• Monitors Workflow Policies in a single group. You can run only one process of the Workflow Monitor Agent on one group at one time. If you run two processes on the same group, then a deadlock can occur. You can run multiple processes at the same time but you must run each process on a different group.

• If the Action Agent parameter is True, then Workflow Monitor Agent creates requests for the Workflow Action Agent in the S_ESCL_ACTN_REQ table.

• Purges requests from the S_ESCL_REQ table after processing finishes. If Siebel CRM activates a database trigger because a Workflow Policy condition is met, then it inserts a record in the S_ESCL_REQ table. The Workflow Monitor Agent evaluates the request on the rules that the policies in the Workflow Policy group establish.

The Workflow Monitor Agent handles a request in one of the following ways:

• Scenario 1: The Action Agent is True and the request in the S_ESCL_REQ table does not include a duration in the Workflow Policy. The Workflow Monitor Agent logs an entry in the S_ESCL_LOG table and sends the request to the S_ESCL_ACTN_REQ table.

• Scenario 2: The Action Agent is True and the request in the S_ESCL_REQ table does not include a duration in the Workflow Policy. The request remains in the S_ESCL_STATE table until the duration is met or until Siebel CRM removes the request because the Workflow Policy conditions are no longer met. Workflow Monitor Agent evaluates each request that remains in the S_ESCL_STATE table for a duration or to determine if the condition still matches values in the S_ESCL_STATE table. As each match occurs, Workflow Monitor Agent logs an entry in the S_ESCL_LOG table or sends it to the S_ESCL_ACTN_REQ table.