Release Notes

Use this URL to install the package into any organization:
https://login.salesforce.com/packaging/installPackage.apexp?p0=04t4w000000Mwtm

Note: If you are installing into a sandbox organization you must replace the initial portion of the URL with http://test.salesforce.com

Please refer to the terms of service before installation.

(clearMDM App > Settings Tab)

Manual Merge Settings.
[Allow When Batch Jobs In Progress?]

This new setting allows manual merges (during Data Stewarding) whilst MDM batch jobs are in-progress. The key use case is where batch jobs are scheduled throughout the business day (hourly matching etc.)

Real-time MDM Settings (Blocking Key Process Settings).
[Is Merge Activated Masters?]

Where Master Records are activated for MDM processing, clearMDM can either synchronise the group or execute a merge operation (where additional matches may be found).

• 6.33 API version update to 58.0.
• Control the activation state of MDM triggers by user or profile.

Configuration: Custom Setting = MDM Settings.

• Normalisation – Blank Target Fields if the Source Field is blank.

Configuration: Target Object Normalisation Settings.

• Matching – Match to Single Master Record Only? Use where records should join the first matching group.

Configuration: Data Source Matching Settings.

• Real-time MDM – Abort pending requests after X minutes. Default is 30 minutes.

Configuration: App Settings > Blocking Key Process Settings.

The following new attributes have been added to clearMDM Reparenting Rules:

• Is Clone?
• Is Clone Prevent Delete?

Child Records can now be cloned (and parented to the Master Record) instead of updated. By default the original records are deleted, unless the “Is Clone Prevent Delete?” flag is set, in which case the original records are retained in addition to the new cloned records.

• Is Delete Failed Records?
• Delete Failed Records Keyphrase.

Where errors are encountered during Child Record update, the Reparenting Engine can now delete the failing Child Records. The primary use case here is where a unique constraint prevents the reparenting update and the retention of the original records causes record sharing issues. The keyphrase field can be used to specify a particular error condition to target for deletion.

The Remove Normalisation Rule Type can be used to remove all instances found of specified text tokens listed in a referenced Custom Setting. For example, the ” AND ” can be removed from Company Names to improve matching quality.

The clearMDM package now installs a Remove Values Custom Setting which can be populated and used as a reference for normalisation rules.

Scheduled data service processing can now be limited to specific data services. For example, Low priority data services can run daily and Medium priority data services hourly.

Note, real-time data service processing is unaffected by this enhancement.

The ISO Country Code list now provides a “Target Remove Start” attribute which can be populated with a list of prefixes to be removed from phone numbers before the international prefix is added.

For example with a Target Remove Start of 44 for UK.

44-0207990990, normalises to +44207990990 instead of +4444207990990.

The previously internal list of standard SObjectTypes supported for reparenting can now be managed via the MDM Home page (Manage Child SObject Types component).