Siebel Administration >  Workflow execution explained


Workflow Policy not having a duration specified -


1. When the workflow policy columns are violated, a new row gets inserted into S_ESCL_REQ table by database Triggers.


2. Workflow monitor agent verifies the record in S_ESCL_REQ table and compares if the violated record and matches the Policy Condition.


3. If the conditions are not met, then it moves the record to S_ESCL_LOG from S_ESCL_REQ without processing it.


4. If the conditions are met, then Workflow Monitor Agent checks in S_ESCL_LOG table if this row already had been violated by the policy during the Action Interval period of Monitor Agent.


5. If the record had not been in prior violation, and if no duration was specified in Policy, and if ‘Use Action Agent’ parameter (This is monitor agent parameter – used to invoke Workflow Action Agent if set to TRUE) was set to ‘False’, then the ‘Workflow Monitor Agent’ invokes the Policy Action by submitting the request to SR Broker.


6. SR Broker looks for the right component in all the Siebel Servers and dispatches the request to that Component. (Let’s say if the Policy Action is a Workflow Process, then it will submit the request to Workflow Process Manager Component).


7. It waits till that Component returns a Success, else it assumes that request has error out and retries equal to [Number of Retries] parameter in Workflow Monitor Agent.


8. If the record fails to process, it is not removed from S_ESCL_REQ; it lies there till it processes successfully.


9. Hence, once the action is performed successfully, the Workflow Monitor Agent logs the information into S_ESCL_LOG table for the row that had been violated by the policy.


10. Finally, Workflow Monitor Agent deletes the row from S_ESCL_REQ table.