Vanilla UCM Workflow Sending Cached Values to UCM
Last updated on MARCH 20, 2017
Applies to:Siebel Communications - Version 16.4 [IP2016] and later
Information in this document applies to any platform.
Why Vanilla UCM workflow from a new WF Polilcy (when a contact is getting updated) is not sending the latest information of the BC instance? Instead it is sending the old values to UCM.
Ex: If a new contact is getting added to the Account, the New policy is getting triggered because of the change in the contact BC. But the UCM workflow is not sending the newly crated contact to the UCM system.
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