Difference In Behavior In Resolution Request From UI And Api
(Doc ID 2725573.1)
Last updated on DECEMBER 02, 2020
Applies to:Oracle Fusion CX Sales Cloud Service - Version 11.13.20.04.0 and later
Information in this document applies to any platform.
We have few queries related to the Duplicate resolution.
1) We are using the resolutionRequests REST Api to create resolution requests and we have set the ZCH_USER_MERGE_REQUESTS: “Allow Processing without Approval” so requests are automatically processed and completed without any manual intervention.
However the same thing when we try to do from UI the Request goes to New from Pending and we have to manually submit and process the request. We want to know why this difference in behavior. Can we achieve the same feature from UI as well?
2) When we merge few records if there are multiple slaves , what we have observed is that if master has few fields with no values, then after Merge the value is picked from the last record in the slave which has some value in that particular field. Can this be controlled through some way? Or is this an OOTB feature which can not be changed? We know we can write custom Attribute level survivor ship rules to pick and choose values from fields of slave records. But we would like to know the OOTB behavior
3) Additionaly since we have an integration with Custom UI so the duplicate identification request and duplicate resolution request will be triggered through APIs. For Duplicate resolution Request we have an API but we dont see any Api for Duplicate Identification request. Can you please let us know if it is in plan anytime soon?
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