Siebel Business Process Framework: Workflow Guide > About Workflow Policies > About the Workflow Policies Module >

Functional Description of a Typical Workflow Policy

A functional processing of a typical workflow policy is illustrated in Figure 20.

Figure 20. Functional Processing of a Typical Workflow Policy

Processing for a typical workflow policy includes:

1. Detect End-User Activity or Server Process. An end-user activity or server process occurs.
2. Create Triggers. Workflow Policies enforce policies at the data layer through database triggers. When a particular policy's conditions are met, underlying database triggers capture the database event into a Workflow Policy Manager.
3. Fire Triggers. The S_ESCL_REQ table is queued.
4. Read Records. The Workflow Monitor Agent, which is a Workflow Policy Manager component, reads records in the S_ESCL_REQ table then processes requests by taking the actions defined.
5. Invoke Workflow Process Manager. In some cases, an action defined can invoke the Workflow Process Manager.

Workflow Policy Manager provides scalability by using an additional component called Workflow Action Agent. Workflow Action Agent can be executed on a different application server within the Siebel Enterprise. For more information, see Executing a Workflow Policy with Workflow Action Agent.

For more information about Generate Triggers, Workflow Process Manager and Workflow Monitor Agent, see Workflow Run-Time Architecture.

For more information about the S_ESCL_REQ table, see About the S_ESCL_REQ Table.