What are the survivorship rules for parties with custom objects and attributes?
This topic describes how to define survivorship rules for merging parties having custom objects and attributes.
For example, you can define a survivorship rule of the type Set Master Record to select the party with the maximum number of custom objects or the party with a specific attribute as the master. You can also define a survivorship rule of the type Set Attribute Value to select the smallest value for a specific attribute.
Custom Objects and Attributes
You can use Oracle Application Composer to configure and extend Oracle CX Sales and Fusion Service applications. The Application composer provides you the ability to extend an Oracle CX Sales and Fusion Service application's object model. You can configure CX Sales and Fusion Service objects by adding new fields (custom fields or custom attributes) to an existing object (standard objects). Or you create entirely new objects (custom objects) and related fields (custom attributes).
Custom Objects and Attributes in Survivorship Rules
The following table describes the basic merge operations that can be performed on standard or custom objects.
|
Object |
Examples |
Can be merged |
Can be transferred |
Can be removed |
|---|---|---|---|---|
|
Standard Top-Level Object |
Account/Organization Contact/Person |
Yes |
Not applicable for top-level objects |
Not applicable for top-level objects |
|
Standard Child Object |
Address Phone |
Yes (by reviewing in the Data Steward UI) |
Yes (by default if not merged or removed) |
Yes (by reviewing in the Data Steward UI) |
|
Standard Child Object |
Lead Opportunity |
No |
Yes (always) |
No |
|
Custom Top-Level Object |
Not applicable (implementation specific) |
No |
Not applicable for top-level objects |
Not applicable for top-level object |
|
Custom Child Object |
Not applicable (implementation specific) |
No |
Yes (always) |
No |
The following table describes whether or not these objects and attributes can be used while defining conditions, clauses, and actions for survivorship rules of the type Set Master Record and Set Attribute Value.
|
Object |
Examples |
Can be used in Set Master Record rule conditions |
Can be used in Set Master Record rule actions |
Can be used in Set Attribute Value rule conditions |
Can be used in Set Attribute Value rule actions |
Can be used for Attribute Override in Data Steward UI |
|---|---|---|---|---|---|---|
|
Standard Top-Level Object |
Account/Organization Contact/Person |
Yes (standard and custom attributes) |
Yes (standard record ID attribute) |
Yes (standard and custom attributes) |
Yes (standard and custom attributes) |
Yes (standard and custom attributes) |
|
Standard Child Object |
Address Phone |
Yes (standard and custom attributes) |
No, survivorship not supported for child objects |
No, survivorship not supported for child objects |
No, survivorship not supported for child objects |
No, attribute override not supported for child objects |
|
Standard Child Object |
Lead Opportunity |
Yes (standard and custom attributes) |
Not applicable if you can't merge the records |
No |
Not applicable if you can't merge the records |
Not applicable if you can't merge the records |
|
Custom Top-Level Object |
Not applicable (implementation specific) |
No |
Not applicable if you can't merge the records |
No |
Not applicable if you can't merge the records |
Not applicable if you can't merge the records |
|
Custom Child Object |
Not applicable (implementation specific) |
Yes (all attributes are custom) |
Not applicable if you can't merge the records |
No |
Not applicable if you can't merge the records |
Not applicable if you can't merge the records |