How To Avoid After An Incremental Migration With Workflows Changes Delivered A Componet Restart? For example for EAIObjMgr and CommInboundRcvr Requires a Component Restart.
(Doc ID 2804404.1)
Last updated on SEPTEMBER 03, 2021
Applies to:Siebel CRM - Version 20.7 and later
Information in this document applies to any platform.
After workflow changes were push from Development (DR) to Production (RR) environments, in order for the EAIObjMgr and CommInboundRcvr components start using the new objects pushed, such as workflows, it is required to restart the component.
Is this expected behavior? In which circumstances the Siebel Repository object changes migrated through Incremental Migration take effect?
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