Workflow Changes Deliverd To MAIN Is Not Executed On Batch Component Such As WfProcMgr In DR And RR Unless Component Is Restarted
(Doc ID 2764093.1)
Last updated on MARCH 26, 2021
Applies to:Siebel CRM - Version 20.7 and later
Information in this document applies to any platform.
The behavior is observed after update Siebel CRM to Siebel CRM 20.7 or later using the new Workflow in Workspaces engine.
Workflow is been executed in a batch component such as Workflow Process Manager and the component parameter User Name is set to a Siebel User ID that is not the current creator of the workspace been used.
The batch components by default has User Name = SADMIN and Workspace Branch Name = MAIN
In case the batch component parameter User Name is changed to another Siebel User ID it will differ from the usual creator of MAIN workspace (SADMIN) and the following behavior can be observed:
1) Execute workflow "A Dummy WF Single Step" on a batch component, for example WfProcMgr component. The WfProcMgr component parameter can be changed to another Siebel User ID or you can trigger the workflow from Server Manager Command Line with command:
7) Here the results is that old cache"A Dummy WF Single Step" was executed and the changes delivered to MAIN/13 are not executed.
8) Only way to WfProcMgr using Siebel User ID TEST01 execute the changes on the workflow and not used the cached one in step 1) is restart the batch component.
The same similar behavior can be observed when executing a Incremental Migration and the batch component parameter User Name on the target environment is using a Siebel User ID different of the workspaces creator. The only way to refresh the cache on the target component after Incremental Migration on this scenario is to restart the batch component.
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