Why Workflow Policy Action is not Executed after First Action Execution and Records Removed from S_ESCL_REQ
(Doc ID 476637.1)
Last updated on OCTOBER 29, 2019
Applies to:Siebel Workflow - Version 7.5.3  and later
Information in this document applies to any platform.
Checked for Relevance on 13-Jan-2012
This document was previously published as Siebel FAQ 1595.
*** Checked for Currency: July 25, 2018 ***
When the workflow policy is executed, the first execution is successful: subsequent ones never trigger any action.
At the same time, records from S_ESCL_REQ table are deleted.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Workflow Policy Action Monitored by the Action Interval Parameter|
|Flow of Records between S_ESCL_REQ, S_ESCL_LOG, and S_ESCL_STATE Tables|