Worklfow Policy Action is Not Executed

7/19/2012 No Comment

Why Workflow Policy Action is Not Executed after First Action Execution and Records Removed from S_ESCL_REQ.

When the workflow policy is executed, the first execution is successful and the subsequent ones never triggers any action, at the same time why the records from S_ESCL_REQ table gets deleted.

Workflow policy conditions can monitor changes in the Siebel application database tables or columns. If the conditions are met, the specified workflow policy action will be executed. Workflow policy violations are monitored by the Workflow Monitor Agent server task and its parameter values. Depending on the value of the Action Interval parameter for Workflow Monitor Agent, the action is taken.

Workflow Policy Action Monitored by the Action Interval Parameter
The Action Interval parameter of Workflow Monitor Agent controls how often the action should be executed. The default value is 3600 seconds. The default value of 3600 seconds means that if the action is executed once for the violated record, then no actions will be executed in the next 3600 seconds even if violations may occur during this period. The minimum value that can be set for Action Interval is 1 second.

NOTE: The default value of the Action Interval parameter for Siebel 6.x, 7.x, and 8.0 are all 60 minutes. However, the unit of measurement has changed between the versions as shown in the following table:

Siebel Version
Default Value
Minimum Value
Unit of Measurement
Siebel version 6.x
Siebel version 7.x and 8.0

Setting the Action Interval = 0 is not recommended by Siebel Systems because the following behaviors have been observed to occur with this setting:
  • Actions performed for rows in S_ESCL_REQ without checking if conditions are met or not. 
  • Actions do not get executed at all at times. 
  • Duplicate actions occur for the same record. 
  • Performance issues occur because this setting causes Workflow Monitor Agent to be busy all the time. Thus, Workflow can cause resource crunch in terms of CPU utilization and memory, etc.
Once Workflow Monitor Agent performs an action on the record in violation, an entry is logged into the S_ESCL_LOG table. If the same record comes into violation again within the Action Interval time, the Workflow Monitor Agent will not perform the action again on the same record. It will only remove the row from S_ESCL_REQ table. As a result, it is possible that Workflow Monitor Agent clears many records from the S_ESCL_REQ table for which no actions have been performed.

Flow of Records between S_ESCL_REQ, S_ESCL_LOG, and S_ESCL_STATE Tables

Workflow policy without duration value
When the workflow policy columns are violated, a new row gets inserted into S_ESCL_REQ table. Workflow monitor agent verifies the record in S_ESCL_REQ table and compares if the violated record matches the policy condition. If the condition is 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. If the record had not been in prior violation, and if no duration was specified, and if ‘Use Action Agent’ parameter was set to ‘False’, then the ‘Workflow Monitor Agent’ invokes the policy action. Once the action is performed, the Workflow Monitor Agent logs the information into S_ESCL_LOG table that the row had been violated by the policy. Finally, ‘workflow monitor agent’ deletes the row from S_ESCL_REQ table.

Workflow policy with duration value specified.
If duration is specified in the policy, Workflow Monitor Agent inserts a new record into the S_ESCL_STATE table and removes the row from S_ESCL_REQ table. Depending on the sleep time parameter, Workflow Monitor Agent wakes up and verifies the S_ESCL_STATE table to check whether the row had reached its expiration time in the END_TM column.

Once the record completes the duration period, Workflow Monitor Agent verifies if the record is still in violation and removes the row from the S_ESCL_STATE table.

NOTE: Executing Workflow Action Agent as a separate task is not recommended. This means that the Use Action Agent parameter should be used only for the consolidate email feature. If this feature is not needed, it is recommended to run Workflow Monitor Agent with the Use Action Agent parameter’s default value set as False.

If the above suggestion does not help, log a service request to Siebel Technical Support providing details of the policy and Workflow Monitor Agent log file.
Related Posts

No comments :


Aired | The content is copyrighted and may not be reproduced on other websites. | Copyright © 2009-2016 | All Rights Reserved 2016

Contact Us | About Us | Privacy Policy and Disclaimer