Siebel Business Process Framework: Workflow Guide > Using Predefined Workflow Policies > About Workflow Policies >

Sequence That a Workflow Policy Uses

Figure 22 illustrates the sequence that a typical workflow policy uses.

Figure 22. Sequence That a Workflow Policy Uses

Explanation of Callouts

A typical workflow policy does the following work:

1. Detect End-User Activity or Server Process. An end-user activity or server process occurs.
2. Create Triggers. To enforce workflow policies, Siebel CRM uses database triggers at the data layer. If the conditions for a workflow policy are met, then these database triggers capture the database event and provide this information to the Workflow Policy Manager server component.
3. Fire Triggers. Siebel CRM queues the S_ESCL_REQ table.
4. Read Records. The Workflow Monitor Agent reads records in the S_ESCL_REQ table. To process requests, it then runs the actions that are defined for the workflow policy. The Workflow Monitor Agent is a component of the Workflow Policy Manager.
5. Start. In some situations, an action can start the Workflow Process Manager.

   The Workflow Policy Manager uses the Workflow Action Agent to make sure Siebel CRM can scale. This agent can run on a different application server in the Siebel Enterprise.

For more information about:

• Workflow Action Agent, see Running a Workflow Policy with the Workflow Action Agent
• Generate Triggers, Workflow Process Manager and Workflow Monitor Agent, see Run-Time Architecture That Siebel Workflow Uses.
• The S_ESCL_REQ table, see Fixing Problems in the S_ESCL_REQ Table