Siebel Sub-Workflow Overrides Parent Workflow BO Context
Last updated on DECEMBER 24, 2016
Applies to:Siebel Workflow - Version 126.96.36.199.3 [IP2014] and later
Information in this document applies to any platform.
A parent Workflow Process that operates on the HLS Case BO. It queries related Contacts and loops through each Contact, invoking a Sub Workflow.
However, the Sub Workflow is also based on the HLS Case BO - it queries a different Case record, based on information passed in from the parent Workflow Process, in order to perform additional processing.
Invoking the Sub Process, the HLS Case query context of the parent Workflow Process is broken. its Observed in two ways:
The "NextRecord" operation step never returns "true" in the "NoMoreRecords" output property, thereby resulting in an infinite loop
The same record is always returned by "NextRecord", meaning the cursor on the query context never progresses through the recordset
How do we force the parent Workflow Process to maintain it's query context, when calling Sub Workflows that use the same BO.
WHAT IS THE DESIRED BEHAVIOR?
Parent Workflow should maintain it's query context when Sub Workflow also use the same BO.
WHAT IS THE ACTUAL OR UNEXPECTED BEHAVIOR?
Parent Workflow is loosing it's query context when Sub Workflow use the same BO and queries the same BC Context which is already queried in Parent Workflow.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms