Last updated on MARCH 02, 2017
Applies to:Siebel Workflow - Version 188.8.131.52.15 [IP2013] and later
Information in this document applies to any platform.
On : 184.108.40.206.15 [IP2013] version, Siebel Workflow
Trying to run Generate Triggers for a Workflow Policy that uses an 'IS DELETED' condition, it fails with the error SBL-ESC-00201.
On one policy that we set up some months back it works fine. On a second policy that we just created it fails each time.
The second policy's condition is based on workflow policy object 'CCCI_Google_Activity', here is the condition:
Activity IS DELETED
It is from 'CCCI Google Activity' workflow policy component and is considered as a child workflow policy component of 'CCCI Google Archive' workflow policy component.
The policy we set up months ago has a similar condition that is based on another workflow policy object 'CCCI_GR_Person', the delete trigger is created successfully, here is the condition:
Contact IS DELETED
It is Contact workflow policy component and is considered as a child workflow policy component of 'Global Registry IDs' workflow policy component.
I don't see any significant differences between the two Workflow Policies or the associated Workflow Policy Objects.
SBL-ESC-00201: Error creating triggers
In WorkMon log, the following errors:
SQLStatementOptions Free Statement Details 5 0004936755ce0eec:0 2015-12-15 10:53:49 (SQLFreeStmt) Option: SQL_RESET_PARAMS
GenericLog GenericError 1 0004936755ce0eec:0 2015-12-15 10:53:49 Message: GEN-11,
Additional Message: no trigger type
ProcReq GenericFatal 0 0004936755ce0eec:0 2015-12-15 10:53:49 Failed to load trigger condition information in LoadConditions
GenericLog GenericError 1 0004936755ce0eec:0 2015-12-15 10:53:49 Message: GEN-10,
Additional Message: Calling Function: LoadConditions; Called Function: Failed to load trigger condition information
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms