How you Configure Merges Using Groovy Scripts

A merge request consists of configuring logic to:

• Determine which record from a set of identified duplicates should be designated as the master record. You can set this up by configuring Set Master Record Rules.

• Determine which attribute value instances from across the set of duplicates the master record should contain. You can set this up by configuring Set Attribute Value Rules. The Set Master Record Rules and Set Attribute Value Rules are collectively called Survivorship Rules.

• Determine whether the merge is violating any of the conditions under which a merge should be prohibited. You can set this up by configuring Agreement Rules.

The linked records are treated as unique records in the data registry, and have their own unique identifiers. Merging involves combining duplicate records into one new master record.

You can setup duplicate resolution using Groovy scripts by configuring a couple of profile options discussed in the topic Duplicate Resolution Simplified Profile Options and specify the scripts in the Application Composer.

You can easily setup survivorship and agreement rules using Groovy Script in Application Composer. If you already have defined survivorship and agreement rules without using the Groovy Scripts, you can migrate them to Groovy Script incrementally. For example, you could continue to use your existing agreement rules while also using Groovy Script for your set master rules.