After An Error Executing A Step From A Sub Workflow The Workflow Output Properties Are Not Set When Returning To Parent Workflow
(Doc ID 2820576.1)
Last updated on OCTOBER 28, 2022
Applies to:Siebel CRM - Version 17.0 [IP2017] to 21.10 [Release V17]
Information in this document applies to any platform.
When executing a workflow that calls a sub workflow and the parent workflow has a error exception connector to handle any error during sub workflow execution, any workflow process property set in a sub workflow is not updating the output properties of the sub workflow and consequently the parent workflow will not have any output process property set too.
Here is an example using standard eMail Response main workflow eMail Response - Process message, verify the highligheted steps and connector in yellow that should be trigger in case of sub workflow eMail Response- Create Activity fails.
Standard Sub workflow eMail Response - Create Activity, in this particular case if fails in Add Attachments steps, so AFTER the Create Activity steps where the Activity Id workflow process property has been set:
On this particular workflow scenario, the Add Attachments failed and the Error Exception connector is trigger in main workflow, but as the Activity Id has not been set it failed on step "Delete Record on Exception" as indicated on Document Duplicate Inbound eMails Got Created From Single .error File in Queued Folder (Doc ID 2818065.1)
The behavior could also be reproduced on previous Siebel Innovation Pack 2016 Patch Set 19.
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