For both 'match and merge' and match and link' solutions, merging two existing golden records – which can happen when updating information on one record results in both records being the same real-world object – one of the records must survive and the other must be deactivated. The default is to allow the record with the oldest STEP revision to persist and to deactivate the youngest record. This behavior can be overridden by adding a Merge Keep First Handler.
The supplied golden records are retrieved by the STEP manager with the context and workspace defined by the matching algorithm. Even if the Approved workspace is selected, the Main workspace is used since changes are not allowed in the Approved workspace.
- Merge Keep First Handler - Create a business condition to determine which golden record survives when two golden records are being merged. Write the business condition to evaluate 'True' to keep the first golden record and evaluate 'False' to keep the second golden record. If this handler is not used, the default behavior keeps the golden record that was created first.
-
The surviving golden record is bound to the 'Current Object' parameter. Refer to the Current Object Bind topic in the online help Resource Materials documentation here.
-
The golden record to be deactivated / deleted is bound to the 'Secondary Object' parameter. Refer to the Secondary Object Bind topic in the online help Resource Materials documentation here.
For information about other handlers, refer to the Creating Merge Golden Record Match Action Handlers topic here.