clearMDM - Installation Guide v1.6

clearMDM®isaregisteredtrademarkofAudit9LtdacompanyregisteredintheUnitedKingdomwithcompanynumber08088394. 1

clearMDM–InstallationGuidev1.6(productversion2.9)Date:9thSeptember2017Productsupportcanbecontacteddirectly([email protected])forspecificquestionsnotaddressedbycontentofthisdocumentorforadditionalinformationorfeedback.

TableofContents

clearMDM–InstallationGuidev1.6(productversion2.9).................................................1ProductIntroduction..................................................................................................................2KeyConcepts..............................................................................................................................3Pre-requisites.............................................................................................................................5

Permissions....................................................................................................................................5MDMFields....................................................................................................................................5

Step1-InstalltheclearMDMmanagedpackage........................................................................6Step2-ProductActivation........................................................................................................7Step3-TargetObjects...............................................................................................................8

3.1NormalisationSettings............................................................................................................93.3MatchingSettings..................................................................................................................113.4MatchingRules......................................................................................................................123.5MergeSettings.......................................................................................................................133.6SynchronisationSettings.......................................................................................................13

Step4-DataSources................................................................................................................144.1DataSourceSettings..............................................................................................................154.2MatchingSettings..................................................................................................................164.3MergeSettings.......................................................................................................................174.4FieldSettings..........................................................................................................................174.5ChildObjectRelationships.....................................................................................................18

Step5-ValidateMatchingSettings..........................................................................................195.1MatchingTestStep1(Search)...............................................................................................195.2MatchingTestStep2(Compare)...........................................................................................205.3FindMatches(Optional)........................................................................................................21

Step6-RunBatchJobs............................................................................................................226.1JobChaining...........................................................................................................................236.2CustomActionSupport..........................................................................................................23

ReferenceMaterials.................................................................................................................24


ProductIntroductionTheclearMDMproductisanativeapplicationprovidedasamanagedpackagedthatdeliversamasterdatamanagementsolutionfortheSalesforceplatform.Therearenooff-platformcomponentstothesolutionanddataisnottransitedoff-platformforprocessingbyexternalservices.TheproductUIisLightningReadyandsupportsSalesforce1formobileaccess.TheclearMDMproductsupportstheMDMoperationsoutlinedbelowintheirlogicalsequence.FurtherdetailsforeachMDMoperationisprovidedintheproductQuickStartdocumentation.(BT)Normalisation.StandardisationoffieldvaluesusinglistCustomSettinglookups(Countrycodes,Root FirstNames etc.) or predefined transformation formats (email domain,URL, Title case etc.).NormalisationgeneratesBlockingKeys(ormatchkeys)usedasthefirstpassinrecordmatching.(BTU)Matching.Cross-objectmatchingofrecordsusingkey,deterministicandprobabilistic(fuzzy)matchingrules.(B)InternalMatching.Singleobjectlargedatavolumematchingoperation.(BU)Merge. Custommerge functionality compatible with Standard and Custom objects and alsoportal enabled accounts, person accounts and contacts. There is no dependency on the standardplatformmergecapability.(B)Synchronisation.MasterRecordsareupdateddirectlytoreflectfieldmodificationsontheirSourceRecord. Synchronisation adds efficiency as the 2-stepmatch andmerge cycle is avoided; existingSourceRecordtoMasterRecordrelationshipsareutilised.(B)Conversion.MasterRecordcreationonaone-to-onebasisforunmatchedrecordsorexternaldatawhere matching is not required. Once paired Master Records updated directly to reflect fieldmodificationsontheirSourceRecords.(B)Re-parenting.ChildRecordsrelatedtoaSourceRecordcanbere-parentedtotherelatedMasterRecordvialookuprelationship.(B)CustomRollups.Numeric fieldsonChildRecordscanbeaggregated to theMasterRecord (vialookuprelationship).Prefixesindicateentrypoints:B=Batch(ScheduledJoborCustomAction–RESTAPI/ProcessBuilder)T=ApexTriggerU=UserInterface/Manual


KeyConceptsConcept DefinitionTargetObjects AcompatibleobjectthatisdefinedasthetargetforMatchingoperations

andwhereMasterRecordswillbecreatedorupdated.Account,Contact,LeadStandardObjectsaretypicallyconfiguredasTargetObjects,whereduplicaterecordsmayexistdirectlyintheobjectorindirectlyinaseparateobject.AbroadrangeofStandardObjects(includingPersonAccounts)aresupportedasbothTargetObjectsandDataSources.CustomObjectsarealsosupported.

DataSources AcompatibleobjectthatprovidesdatatoMDMoperations.EachDataSourcehasaSourceObjectandaTargetObjectsetting.InternalDataSourcesexposedataheldintheTargetObject.DataSource(Account)>TargetObject(Account)ExternalDataSourcesexposedataheldinadifferentobject.DataSource(ERPCompanies)>TargetObject(Account)Partition Data Sources enable a single object to support multiple DataSourceswith distinct settings. Partition Data Sources are typically used togrouprecordsrelatingtoanexternalsystem(e.g.SAP,SageX3)ortoisolaterecordsatdifferentqualitygrades(e.g.High,MediumandLow).MasterRecordDataSourcesallowMasterRecordstobeexposedtoMDMoperations via a distinct Data Source with appropriate settings such aselevated merge field priorities. A Master Record Partition data source isimplemented as a partition data source that references the record MDMstatusvalue.Check-onlyDataSources support cross-objectmatchingbetween standardobjects. The primary use case for Check Only Data Sources is duplicatecheckingacrossLeads,Contactsand/orPersonAccounts.Forexample,Leadcreation (file import, UI data entry etc.) can be blocked where the LeadmatchestoanexistingContact.

MasterRecords TheMasterRecordistheoutputofMDMprocessingandisoptionallyrelatedtotheunderlyingSourceRecords(orduplicates)viarelationshipfieldorsimplythroughtheconcatenationofrecordidentifiersintoafieldontheMasterRecord.MosttypicallyaMasterRecordisade-duplicatedAccount,PersonAccount,ContactorLeadrecordenrichedwithdatafromitsrelatedSourceRecords.WhereSourceRecords(orduplicates)arenotremoved,itistypicaltousetheSalesforcesharingmodeltopresentSalesforceend-userswithaccesstoMasterRecordsonly–therebyremovingthevisibilityofduplicates.


SourceRecords SourceRecordsaretheinputtoMDMoperationsandmayberelatedtoa

MasterRecord.SourceRecordscanberetainedordeleted.SourceRecordscanbeconsideredastheunderlyingduplicatesthatareoftenhiddenfromviewforSalesforceend-usersordeletedentirelyonceprocessed.

MasterRecordUpdateLogic-AttributeGroup

AttributeGroupsarecollectionsoffieldsonaTargetObjectthatmustbemergedtogetherfromasingleSourceRecordonly.IndetermininghowtheMasterRecordfields(intheAttributeGroup)arepopulatedeachrelatedSourceRecordisevaluatedforvalidity(typicallycompleteness)andpriority.AttributeGroupprioritycanbedefinedonaNewest,OldestorDynamicPrioritybasisallowingcustombusinessrulestodirectwhichSourceRecordthefieldvaluesaretakenfrom.AttributeGroupprocessingperformsafullre-evaluationofallSourceRecordsforagivenMasterRecordwheneveraneworexistingSourceRecordmodificationisidentified.MergeandSynchronisationMDMoperationsperformAttributeGroupprocessing.

MasterRecordUpdateLogic–FieldPriority

FieldsthatarenotmappedtoanAttributeGroupareprocessedusingDataSourcespecificMergePriorities.MasterRecordsretainamemoryoftheSourceRecord(andDataSource)thatlastupdatedeachfield.SubsequentMergeandSynchronisationoperationswillonlyupdatefieldsfromaSourceRecordwithahighermergepriorityforthefield,orwheretherecordismorerecentlyupdatedshouldtheprioritybeequal.Manualupdates,whereMasterRecordfieldsaredirectlyupdatedviatheSalesforceUIorAPIs,areassignedamergeprioritythatcanbeusedintherelativescaleevaluationappliedtoeachfield.ThisallowsmanualupdatestoberetainedirrespectiveoftheoccurrenceofSourceRecordupdatesonaper-fieldselectivebasis.


Pre-requisitesPermissionsTheclearMDMpackageinstallswithdefaultpermissionsfortwodistinctuserroles;DataStewardandMDMUser. The default permissions serve as starting point fromwhich the required permissionsstructurecanbedefinedbyaSalesforceAdministrator.TheDataStewardroleisintendedforusersthatareresponsiblefordatamanagementgenerallyandMDMprocessingspecifically.DataStewardswilltakeadministrativeownershipoftheclearMDMproduct,defineandimplementrequisiterecordlifecycles, steward candidate matches and generally take responsibility for the applicationconfiguration of the clearMDM product and the outcomes achieved. The objective of the DataSteward should be to implement optimal data management processes, supported by MDMoperations,thatabstractdataduplicationfromend-usersanddeliveraclear360-degreeviewforallmasterrecords.TheMDMUserroleis intendedforanySalesforceuserthatmaycreaterecordsorbenefitfromviewingdynamichierarchyvisualisationsrelatedtorecordstowhichtheyhaveaccess.Thedefaultpermissions,forthetworolesdescribedabove,arepackagedasProfilePermissionsandPermission Sets. In the former case the installation process allows the Profile Permissions to beoverlayedontoselectedprofileswithinthesubscriberorg.InthelattercaseuserscanbeassignedtoPermissionSetsasrequired,withnoimpactontheircurrentUserProfileassignment.TherecommendedbestpracticeapproachtopermissionsisassignmentviaPermissionSet.MDMFieldsTheclearMDMproductrequiresthateachobjectdefinedasaTargetObjectand/orDataSource isconfiguredwith a set of custom fields that complywith theMDMFields requirement outlined inAppendix A. The complete set ofMDM Fields for Account, Contact and Lead are installed by thepackagebydefault. Foradditionalobjects, theMDMfieldsmustbeconfigureddirectlywithin thesubscriberorg.


Step1-InstalltheclearMDMmanagedpackage

Figure1.1–AppExchangeListingTheclearMDMmanagedpackageisinstalledfromtheSalesforceAppExchangeviathe“GetItNow”link on the product listing page. The standard package installation process prompts for usercredentials (either sandbox or production) for the target Salesforce org. The first step of theinstallationprocess enablespackagedprofile settings tobeoverlayedontoexistingprofiles in thesubscriber org. Note, it is a best practice to install the package with the default settings; userpermissionsshouldbeprovidedthroughuserassignmenttothepackagedpermissionsets.Itisnotrecommendedtoinstallthepackagewiththe“installthisappforeveryuser”option.clearMDM licensing isappliedat theorg-level,notper-individualuser.Thepackage installswithadefaulttriallicensewhichexpires5daysafterinstallation.Pleasecontactusathello@clearmdm.comtopurchaseanannualsubscriptionlicense,ortodiscussspecificimplementationrequirements.PleasecontactclearMDMbeforeimplementationinaproductionSalesforceorg.Pleasenote;theproducteditionlinkedtotheAppExchangelistingistheBasicEdition.ForMidandEnterpriseeditionpackageinstallationlinkspleasecontactsupport@clearmdm.com.


Allsubsequentstepsrequirealoginuserthathasbeenassignedthe[MDMDataSteward]permissionset,orhasaprofilethatwasassignedthe[MDMDataSteward]permissionsduringinstallation.Note,thestandardpermission(CustomizeApplication)isalsorequired.Pleasenote; the“Get ItNow” linkreferencedaboveallows installationofclearMDMBasicEdition to a selected sandbox or production org with a 5-day trial license. It is notrecommendedthataproductionorgisused.Thetrialperiodcanbeextendeduponrequest.TocreateanewdedicatedtrialorgwithclearMDMEnterpriseEditionpre-configuredandasampledata-set,pleasevisittheTrialpageontheclearMDMwebsite.Step2-ProductActivationTheclearMDMmanagedpackageinstallsinaninactivestateandmustbeexplicitlyactivatedbeforechanges aremade to the application configuration. The screenshot below shows the Settings tabwhichcanbeaccessedviatheMDMcustomapplication.The[IsActive?]checkboxmustbecheckedandtheSavebuttonclickedtoactivatethepackagefunctionality.Upondoingso,additionalsubtabs,withintheSettingstab,willappeartoenableconfigurationoftheclearMDMpackagefunctionality.

Figure2.1–ApplicationSettingsTab


Step3-TargetObjectsATargetObjectisthedirecttargetforallMDMoperations.Dataisnormalised,matchedandmergedorsynchronisedintoexistingornewMasterRecordsheldinaTargetObject.ATargetObjectcouldbeacompatiblestandardobjectoracustomobject.Forexample,theMatchingMDMoperationrunsforaspecificTargetObject;SourceRecordsaregatheredacrossallDataSourcesthatreferencetheTargetObjectandmatchedasacombineddataset.AllobjectsforwhichDataSourceswillbedefinedmustbeconfiguredasaTargetObjectwithNormalisationSettings.ThisisnecessaryastheNormalisationMDMoperationpopulatestheBlockingKeyfieldvaluesrequiredbytheMatchingMDMOperation.

Figure3.1–TargetObjectSettingsNote,onlyactiveandconfiguredMDMOperationsarelistedontheJobspagewhenaTargetObjectisselected.


Note,forobjectsnotlistedontheTargetObjectstab(Settingspage)thefollowingstepsmustbecompleted.

ü ClicktheAddbutton.ü SelecttheTargetObjectfromthelist.ü ConfiguretheTargetObjectsettingsasdescribedbelow.

3.1NormalisationSettingsTheNormalisationMDMoperationstandardisesfieldvaluesandpopulatesblockingkeyvalueswhichsupporttheinitialblocking(ormatching)passesappliedbytheMatchingMDMoperation.SettingArea UsageAutoNormalisation TheNormalisationMDMoperationcanbeappliedtoallSourceRecords

heldwithintheTargetObject[AutoNormaliseRecords?]=True,oronaselectivebasiswherethe[IsNormalisedFieldName?]fieldisemployed.WhenAutoNormalisationisactiveitispossibletolimittherecordprocessedtothosethathavebeenmodifiedsincethepreviousdayonaninclusivebasisviathe[AutoNormaliseRecentlyModified?]setting.WhenAutoNormalisationisnotactive,SourceRecordsprocessedbytheNormalisationMDMOperationhavethe[IsNormalisedFieldName?]fieldsettoTrue.clearMDMcandetectwhenfieldchangesoccurthatinvalidatetheNormalisationstateandsetthe[IsNormalisedFieldName?]fieldtoFalsetoensurethatthenextNormalisationMDMoperationwillre-normalisetherecord.Thisbehaviourissetviathe[CheckNormalisationStateonSave?]setting.

BlockingKeyOutputFields TheNormalisationMDMoperationpopulatesthespecified[BlockingKeyGroupFieldName]and[BlockingKeyFieldName]fieldswithmatchingtokensusedinthefirstmatching(orblocking)passesappliedbytheMatchingMDMOperation.Normalisationalsosetsthe[IsBlockingKeyComplete?]fieldtoTruewhereacompleteblockingkeycouldbegeneratedfromthefieldspopulatedontheSourceRecord.SourceRecordswithoutthisflagsetareexcludedfromtheMatchingMDMoperation.

BlockingKeyInputFields Upto3inputfieldscanbeselectedfortheblockingkeypopulation;foreachfieldaninputlengthcanbespecified.Determinationofanappropriateblockingkeystrategy,groundedinthecharacteristicsofthespecificdataset,isimperativetosuccessfulrecordmatching.BlockingKeyInput1ismandatory,2and3areoptional.StrictBlockingKeyPopulation.InStrictmodeblockingkeysarepopulatedonlywhereeachinputisofsufficientlengthtomatchtherequiredinputlength.Thisfeatureavoidsunusableblockingkeysbeingcreatedandenablesearlyreporting.BlockingKeyPadding.Whereablockingkeyinputhasavaluethatisnotofthespecifiedinputlength–paddingcanbeappliedtoallowconstructionofacompleteblockingkey.ItistypicalforinputfieldstobeselectedthataretheTargetFieldsspecifiedinNormalisationRules.


3.2NormalisationRulesNormalisationRulesstandardisefieldvaluesusingtemplateruletypesorcustomreferencedata.RuleType OutputLookup CustomSettingvaluescanbereferencedtomatchaninputfieldvalue

againstaMatchListheldagainstaStandardisedValue.Forexample,theCountryCodessettingholdsISOCountryCodevaluesagainstcommonlyusedcountrynamesandabbreviations.TheclearMDMpackageinstallsanumberofexemplarsettingswithexamplevaluepopulations.AdditionalCustomSettingscanbeaddedtothesubscriberorgandreferencedinNormalisationRulestoapplylookupnormalisationagainstanylistofdata.

RemoveEnd TheRemoveEndruletypereferencesaCustomSettingforcommonsuffixes,anymatchesfoundinthesettingareremovedfromtheendoftheinputfieldvalue.Thisruletypeisintendedtoremovecommonsuffixesappliedtocompanynamesorsurnames.ExemplarCustomSettingsareprovidedwithexamplevaluepopulations;suchsettingsshouldbefullypopulatedbeforeuse.AswiththelookupruletypeadditionalCustomSettingscanbeaddedtothesubscriberorg.

EmailDomain Iftheinputfieldvaluematchesanemailaddressformat,[email protected]=>hotmail.com

URL Iftheinputfieldvaluematchesawebaddress(orURL)formatthentheprotocolprefix(httporhttps)isremoved.

Format Allwhitespaceisremovedandandtheinputfieldvalueisconvertedtouppercase.

Title EachwordintheinputfieldvalueissettoTitlecase.

TitleHyphen EachwordintheinputfieldvalueissettoTitlecaseandspacesarereplacedbyhyphencharacters.


3.3MatchingSettingsTheMatchingMDMoperationgroupsSourceRecordsbyBlockingKeyValuesandappliesconfiguredmatchingrules.IdentifiedrecordmatchesarerecordedintheMatchedRecordPairobject.SettingArea UsageMatchingThresholds The[BlockingKeyMatchLength]settingenablesspecificationofhow

manycharactersfromtheblockingkeyareusedinmatching;alowervaluecansignificantlyincreaseprocessingtime.Thisfieldenablesexperimentationwithblockingkeylengthswithoutthenecessitytore-normaliserecords.BlockingKeyAuto-adjustment.Withlargerdatasetsitispossibleforblockingkeymatchvaluestocoverlargevolumesofrecords.TheMatchingMDMoperationcanbeconfiguredtodynamicallyadjustthelengthoftheoverallblockingkeyusedincreatingmatchinggroups.Thisfine-tuningpreventsblockingkeymatchvaluesbeingskippedduetothesizeofrecords(MaxRecordsperGroupsetting).Animplementationbestpracticeistoaimforablockingkeylengthof10charactersandtouseashortermatchlengthvalue.Thisapproachprovidesflexibilitytoaccommodatelargermatchinggroups.TheFuzzyMatchthresholdspecifiesthescore%abovewhicharecordpairisconsideredacandidatematch.

AutoAccept The[AutoAcceptMatches?]settingenablesDataStewardstospecifyascore%abovewhichrecordpairsareconsideredadefinitematchandstewardingwillnotberequired;thestatuswillbesettoAcceptedautomatically.Candidaterecordpairswithascore%betweenthematchthresholdandautoacceptthresholdwillrequirestewardingandwillretaintheCandidatestatus.AnimplementationbestpracticeistoimplementreportingnotificationsthatproactivelynotifyDataStewardsthatcandidatematchesexistforstewarding.

MatchingCheckOverride Wherethe[CheckforMatchesonRecordCreation?]flagisset,clearMDMappliesastrictMatchingCheckthatpreventsrecordcreationwherematchesarefound.The[MatchingCheckOverrideFieldName]settingallowsacheckboxformulafieldtobespecifiedthatoverridesthisbehaviourbasedonrecord-levelconditions.SuchconditionscanincludeProfileorUserreferencesandfieldvalueconditions.Forexampleitmaybenecessarytobypasscheckingforauserthatrepresentsanexternalsystemintegration,oraparticularcategorisationofrecord.

MatchingManagerApexClass clearMDMimplementstheLevenshteindistance(oreditdistance)fuzzymatchingalgorithmbydefault.TheclearMDMproductexposesaprogrammaticinterfacethatenablesadditionalmatchingalgorithmstobeencodedinanApexclasswithinthesubscriberorgandconfiguredwithintheMatchingsettings.


3.4MatchingRulesSourceRecordsareinitiallygroupedbyblockingkeyvalues;thenextstepsappliedbytheMatchingMDMoperationistoprocesstheconfiguredfield-levelrulesacrosstherecordscontainedwithineachrecordgroup.RuleType(inorder) LogicKey AKeymatchruleindicatesthatifthe2SourceRecordsbeingcompared

havethesamefieldvaluethenthematchscoreis100%(i.e.anExactMatch)andnofurthermatchinglogicisapplied.Thisruletypeisintendedforuniqueidentifiersandwillmatchindividualvalueswithinapipedelimitedtextfieldvalue.Keymatchingisthemostefficientmatchingruletype;formulafieldscanbeusedtoreturncustommatchingtokensthatenablehighlyefficientmatchingprocesses;i.e.EmailplusMobilePhonecombination=ExactMatch.

Deterministic ADeterministicruleindicatesthatifthe2SourceRecordsbeingcompareddonothavethesamefieldvaluethenano-matchoutcomeisrecordedandnofuzzymatchinglogicisapplied.

Exact ExactmatchingisappliedwhereKeyruleshavefailedandDeterministicruleshavepassed.ForeachconfiguredExactmatchingfield,themaxfieldscoreisaddedtotherecordlevelmatchingscoreifthefieldvaluesarenotblankandmatchexactly.Ifoneormorefieldvalueisblankthenullfieldscoreisadded,otherwiseazerovalueisapplied.

Fuzzy FuzzymatchingisappliedwhereKeyruleshavefailedandDeterministicruleshavepassed.ForeachconfiguredFuzzymatchingfield,ascoreiscalculatedandanoverallmatchscorereturned.Thefieldscoreequatestotheactualeditdistanceasapercentageofthemaximumpossibleeditdistancethenappliedtothemaxfieldscore.Ifeitherfieldvalueisblankthenthenullfieldscoreisapplied.

Ignore TheIgnorematchingtypeindicatesthatthefieldisrequiredfortheMergeMDMOperation(andthereforeamappingisrequiredacrossdatasources)buttheMatchingMDMOperationwillignorethefield.TheIgnoretypeisnotmandatoryforallDataSourcesandisthereforeusefulforcopyingDataSourcespecificfieldvaluestotheMasterRecord.

RulePrecedence MatchingRulesareprocessedintheorderbelow.1-Key2-Deterministic3-Exact4-Fuzzy


3.5MergeSettingsMatched RecordGroups produced by theMatchingMDMoperation are processed by theMergeMDMoperation intoMaster Record create or update events. TheMatched Record Pair object iswherematchinggroupsarecreated,the[RecordGroupId]fieldindicatesthegroupingofrecords.SettingArea UsageMasterFieldMap ACustomFieldof[LongText,5000size]canbespecifiedtoholdthefield

mappingforaMasterRecord.Thefieldmappingrecordsthepopulationlogicforeach(MDMactive)field.Theinformationrecordedincludesthesourcerecordthevaluecamefrom,thedatasourceforthesourcerecord(oraManualUpdateflag)andalastupdatedtimestamp.ThefieldmapisusedbytheMergeandSynchronisationMDMoperationswhenevaluatingwhethertoupdatefieldsonaMasterRecordinresponsetoSourceRecordupdates.

IgnorePartialGroups ThissettingenablesMatchedRecordGroupsthatcontainrecordsatboththeAcceptedandCandidatestatustobeskipped.Instricttermsonlygroupsthatarefullyaccepted,eitherviaauto-acceptlogicorviadatastewarding,shouldbemerged.

MergeDefaults MergeOverrideValuescanbeaddedperfield(thatisactiveformatching)andenabledefaultvaluestobespecifiedincaseswherethemasterrecordfieldvaluewouldotherwisebeblank.

3.6SynchronisationSettingsIn cases where Source Record to Master Record relationships do not require full re-evaluationwhenever the Source Record is updated, the Synchronisation MDM operation can be used tosynchronisechange(selectivelyappliedbasedonAttributeGroupsorfieldpriorityrules)totheMasterRecordinone-step.Synchronisation is enabled at the Target Object and Data Source level and requires that MasterRecordshaveavalidblockingkeyandaresetwiththe“MergeMaster”MDMStatus.SourceRecordsmustbesetfor[IsActiveforMatching?]=Trueattherecord-level–SynchronisationdoesnotworkwithAutoMatching.The Synchronisation MDM operation provides a highly efficient mechanism for the controlledpromotionofSourceRecordchangestotheMasterRecordwithoutincurringtheseparatestepsofmatchandmerge.A typical implementationapproach is to synchronise recordupdatesandapplymatchandmergetonewrecords.


Step4-DataSourcesA Data Source is configured to expose Source Records to the Matching and Conversion MDMoperations.EachDataSourcehasdistinct configuration that includesadefinedSourceObjectandTarget Object. Where the objects are different (i.e. an External Data Source) a field mapping isrequiredtoenablecross-objectprocessing.MultipleDataSourcescanbeconfiguredforbothSourceObjectsandTargetObjects.

Figure4.1–DataSourceSettingsNote,MatchingrequiresthataTargetObjectwithNormalisationsettingsisconfiguredforallobjectsexposedviaDataSources.Note,forDataSourcesnotlistedontheDataSourcestab(Settingspage)thefollowingstepsmustbecompleted.

ü ClicktheAddbutton.ü ConfiguretheDataSourcesettingsasdescribedbelow.


4.1DataSourceSettings.SettingArea UsageInternal/ExternalDataSources

The[IsExternal?]settingisusedtospecifyanExternalDataSource,whereaSourceObjectmustbespecified.InternalDataSourcesarethosewheretheSourceRecordsareexposedfromtheTargetObjectdirectly.AnExternalDataSourcemustspecifyfieldmappingsfromtheSourceObjectdatastructuretothefieldsmarkedasactiveformatchinginTargetObjectsettingdefinition.

PartitionDataSources PartitionDataSourcesenableasingleSourceObjecttobehorizontallypartitionedthroughvaluesinasinglepartitionfield.Allpartitionsforthesameobjectmustshareacommondesignatedfieldandprovideadistinctpartitionvalue.Beforepartitionscanbecreatedanon-partitionDataSourcemustbeconfigured;thisDataSourcecoversallrecordsoutsideofthefieldvalueconditionsspecifiedinpartitions.The[IsPartition?],[PartitionField]and[PartitionValue]fieldsareusedtoconfigureaPartitionDataSource.PartitionDataSourceusecasesincludepartitionsthatprovideahigh-levelgroupingofrecordsforcontrolledmatchingandpartitionsthatrepresentdifferentqualitygradestowhichspecificconfigurationsareapplied.

CheckOnlyDataSources Check-onlyDataSourcessupportcross-objectmatchingbetweenstandardobjects.TheprimaryusecaseforCheckOnlyDataSourcesisduplicatecheckingacrossLeads,Contactsand/orPersonAccounts.Forexample,Leadcreation(fileimport,UIdataentryetc.)canbeblockedwheretheLeadmatchestoanexistingContact.


4.2MatchingSettingsTheMatchingMDMoperationprocessesSourceRecordsexposedbyDataSourcesviaauto-matchorselectivematchingconfigurations.SettingArea UsageAutoMatching TheMatchingMDMoperationcanbeappliedtoallSourceRecords

exposedbytheDataSource[AutoMatchRecords?]=True,oronaselectivebasiswhererecord-level[IsActiveforMatchingFieldName?]fieldisemployed.WhereSourceRecordmodificationsareintegratedfromanexternalsource,fine-grainedcontrolcanbeachievedbyusingtheETLprocesstosetthe[IsActiveforMatchingFieldName?]fieldtoTrueformodifiedrecords.Insuchamodelthe[MasterRecordsActiveforMatching?]flagshouldbesettoTruetoensurethatnew/changedSourceRecordsarematchedagainstexistingMasterRecords.The[ResetSourceRecordMatching?]flaginstructstheMatchingMDMoperationtosettherecord-levelflagtofalsepost-processing.Itisimperativethatthissettingisappliedforincrementalprocessingtoavoidcontinualre-matchingofSourceRecords.clearMDMcandetectwhenfieldchangesoccurthatinvalidatetherecordmatchedstateandsetthe[IsActiveforMatchingFieldName?]fieldtoTruetoensurethatthenextMatchingorSynchronisationMDMoperationwillprocesstherecord.Thisbehaviourissetviathe[CheckMatchingStateonSave?]setting.

MasterRecordInclusion MasterRecordinclusionallowsMasterRecordstobeselectivelyexposedtotheMatchingMDMoperationforblockingkeysfoundwithintheSourceRecorddataset.MatchesbetweenMasterRecordsexposedbythislogicareprevented;onlySourceRecordtoMasterRecordmatchingpathsaresupported.ThedeterminationofwhichrecordsaredeemedtobeMasterRecordscanbestatusbased(MergeMaster,ConversionMaster)orcontrolledbyanominatedCheckboxformulafieldwhichevaluatestoTrueonlyonMasterRecords.ThislatterapproachenablesstandalonerecordstobehandledasMasterRecordsinrespecttoSourceRecordmatching.MasterRecordinclusionisconfigurableforInternal-typeDataSourcesonly,wherethesourceobjectisthesameasthetargetobject.


4.3MergeSettingsTheMergeMDMoperationmergesmatchesSourceRecordswith flexible configurationoptions inrespecttotraceabilitybetweenSourceRecordsandMasterRecords.SettingArea UsageTransientMode The[IsTransientModeEnabled?]flagenablesSourceRecords,thatare

notdesignatedMasterRecordstatus,tobeautomaticallydeletedbytheMergeMDMoperation.ThismodeissupportedbytheMergeUIonly.

IdentifierCopy The[MasterRecordIdSourceFieldName]settingcanbeusedtospecifyalookupfieldontheSourceObjectthatreferencestheTargetObject.TheMergeMDMoperationwillpopulatethislookupfieldonSourceRecordswithareferencetotheMasterRecord,therebyestablishingapersistent,traversableparent-childrelationship.SourceRecordrelatedlistscanthereforebeaddedtoMasterRecordpagelayouts.The[IdentifierSourceFieldName]settingcanbeusedtospecifyafieldontheSourceObjectforwhichvalueswillbepopulatedonthespecified[IdentifierTargetFieldName]fieldontheTargetObject.Identifiersareconcatenatedintoapipecharacterdelimitedstring.IdentifiercopyenablesSourceRecordstobedeleted,withidentifiertraceabilitymaintainedattheMasterRecordlevel.

4.4FieldSettingsSettingArea UsageFieldMappings ExternalDataSourceswheretheSourceObjectisnotthesameobjectas

theTargetObjectrequireaFieldMappingtobedefined.ForeachTargetObjectfieldthatisactiveformatchingaSourceObjectfieldofthesamedatatypemustbespecified.Cross-objectMDMoperationsapplydynamicfieldtranslationsinordertomatchorconvertrecordswithdifferentdatastructures.

MergePriorities ForeachDataSourcearelativemergeprioritycanbespecifiedperfieldtoenablefine-grainedcontroloverthefieldpopulationoftheMasterRecord.Onaper-fieldbasistheMergeMDMoperationwillpopulatetheMasterRecordusingtheSourceRecordvaluethathasthehighestrelativepriority;takenfromtheDataSourcetowhichtheSourceRecordisassociated.Note,thelogicaboveisskippedwherefieldsareprocessedbytheMergeorSynchronisationMDMoperationsduringAttributeGroupevaluation.


4.5ChildObjectRelationshipsTheRe-parentingMDMoperation re-parentsChildRecordsusingsettingvaluesspecifiedperDataSource.SettingArea UsageInternalDataSources ForInternalDataSources(wheretheSourceobjectandTargetobjectare

thesame)compatibleChildRelationshipscanbere-parentedbyselectingtheRe-parentoption.ThisapproachupdatestheparentfieldontheChildRecordreplacingtheSourceRecordIdwiththeMasterRecordId.

ExternalDataSources ForExternalDataSources(wheretheSourceobjectandTargetobjectarenotthesame)compatibleChildRelationshipscanbere-parentedbyspecifyingalookupfieldontheChildObjectthatreferencestheTargetObject.ThisapproachdoesnotimpactontheexistingparentfieldontheChildRecordthatreferencestheSourceRecord;theonlyactiontakenistoupdatethespecifiedlookupfieldwiththerelevantMasterRecordId.

Note,ChildRecordsthatarenotincompliancewiththecurrentsetofValidationRulesappliedtotheobjectcannotbere-parented(thedataintegrityissuemustbecorrectedmanuallybeforeupdatescanbeappliedirrespectiveofsource(UI,APIetc.).TomitigatethisscenarioaclausecanbeaddedtotheValidation Rule logic to allow updates to occur where the parent field is changing only (e.g.IF(ISCHANGED(parentField),FALSE,[logichere]).


Step5-ValidateMatchingSettingsTheMatchingTestfunction,accessedviaatabaccessibleintheMDMcustomapplication,enablestheapplicationconfiguration(TargetObjectsandDataSources)tobevalidatedandmatchingrulestoberefinedthroughexploratorytesting.

Figure5.1–MatchingTest-Search5.1MatchingTestStep1(Search)Step1requiresasearchtobeperformedacrossSourceRecordsusingasimplefilterorcompoundfilter conditions applied with and/or logic. The search performed does not apply the configuredmatchingrules, insteadatext-basedsearchisemployedtogatherrecordswithcommonattributesthatmaynot otherwisematch.As the screenshot above shows, records are returned across datasources. The filter fieldoptions are limited to thosedefinedas active formatching for the TargetObject; as Data Sourcesmust provide fieldmappings filter conditions can be applied consistentlyacrossobjects.Thedefaultsearchfieldcanbesetviathe“Default?”optionwithintheTargetObjectSettingsFieldssection.


Onceasearchhasreturnedresults,exactly2recordsshouldbeselectedforcomparison.Selectiontakesplace via theSelect checkbox in the leftmost column.Once2 recordsare selected theNextbuttonwillbepresented;thisbuttontakestheusertoMatchingTestStep2(Compare).

Figure5.2–MatchingTest–Compare5.2MatchingTestStep2(Compare)Step2enablescomparisonof2candidatesourcerecordsusingthematchinglogicconfiguredfortheTargetObject(PersonAccountintheexampleabove).Foreachrecordtheactualfieldvaluesforeachmatchingactivefieldisdisplayednexttotheconfiguredmatchingsettingsforthefield.TheComparebutton invokes amatching operationwhich calculates thematching score for the 2 records. Theprimarypurposeofthisfunctionistoenableexperimentationwiththeconfiguredfield-levelmatchingsettings.OnceasatisfactoryresultisachievedtheApplytoSettingsbuttoncanbeusedtoupdatetheTargetObjectmatchingsettingsbasedonthecurrentsettingvalues.Note,the2recordsselectedforcomparisoncanalsobedirectlymergedviathe“Merge”button,thiscapabilityallowsduplicaterecordsthatmaynotshareablockingkeytobematchedandmergedonanad-hocbasis.


5.3FindMatches(Optional)TheFindMatchesfeatureisaccessiblefromacustombuttonaddedtothepackagedpagelayouts.Forcustom objects (or standard objects without packaged layouts) a custom button can be createddirectlywithinthesubscribedorgusingtheformatbelow./apex/clearmdm__FindMatches?id=[Merge Expression for Record Id – REPLACEME]

TheFindMatchesfeatureenablesreal-timematchingforanindividualrecord.“Find”:MatchesarereturnedfortherecordBlockingKey,thatrelatetotheSourceRecordonly.“FindAll”:MatchesarereturnedfortherecordBlockingKey,thatmaynotrelatetotheSourceRecord.

Figure5.3–FindMatchesNote,theApplicationSetting[SelectiveUIMatchingEnabled?]allowsSourceRecordstobeexposedtoUIfunctionssuchas“FindMatches”withouttherequirementthattherecordis[IsActiveforMatching?]=True.


Step6-RunBatchJobsTheBatchJobManagementfunction,accessedviaatabaccessibleintheMDMcustomapplication,enablesMDMoperationstobeinvokedimmediatelyoronascheduledbasis.AJobisaninstanceofaMDMoperationforaspecifiedTargetObject,i.e.MatchingforAccount.Theobjectsthatarelistedforselectionforanoperationarelimitedtothosethatareconfiguredandactiveforthatoperation.

Figure6.1–JobsPageNote,Jobswillnotrunconcurrentlyforthesametargetobject.AsthescreenshotaboveshowsaJobcanbescheduledonarecurringbasistoaspecifiedrecurrencepattern;Daily,Weeklyetc.ItisalsopossibletofiltertheDataSourcesreferencedbyanindividualjob;this option allows selective processing to be applied across larger data sets thatmay have beenpartitionedusingPartitionDataSources.


6.1JobChainingMDM operations have a logical sequence of application; normalisation precedes matching andmatching precedes merge for example. To enable efficient automation of MDM processing it ispossible to chain jobs together in a seamlessmanner. Job chaining is specified via Target Objectsettings;thesupportedjobrelationshipsarelistedbelow.ChildJob ParentJob(s)Synchronisation NormalisationMatching Normalisation,SynchronisationMerge MatchingConversion Matching,MergeRe-parenting Conversion,MergeCustomRollup Re-parenting

6.2CustomActionSupportMDMOperationscanbeinvokedviaProcessBuilderortheRESTAPI. IntheformercaseaProcessmust be declaratively defined with an Apex action that references the class[clearmdm__BatchJobRunAction];theMDMOperationandTargetObjectparametersarerequired,theDataSourcesandProcessCountparametersareoptional.CustomActionsupportenablesMDMprocessing to be incorporated into any process automation logic implemented through ProcessBuilder. The same Custom Action referenced above is exposed via the REST API enabling MDMprocessingtobeinvokedbyoff-platformprocessing.AtypicalusecaseforthiscapabilityiswheredataintegrationtasksrequireamechanismtoinitiateMDMprocessingoncompletion.ForexampleonceanETLtoolhasfinishedloadingrecordsintoSalesforceobjectstheNormalisationMDMoperationcanbeinvoked,whichmaybechainedtotheMatchingMDMoperationtodeliverfullyautomatedend-to-enddataprocessing.


ReferenceMaterialsReference ContextImplementationModel1-ExternalDataConsolidation

[email protected]

ImplementationModel2-InternalDataManagement

Inproduction

QuickStartGuides Availableatclearmdm.com/resourcesOverviewNormalisationMatchingMergeDataConsolidationDataQuality


AppendixA–MDMFieldsLabel(illustrative) APIName(illustrative) Type(mandatory) AreaBlockingKey BlockingKey__c Text(100)(External

ID)Normalisation

BlockingKeyGroup BlockingKeyGroup__c Text(10)(ExternalID)

Normalisation

IsActiveForConversion? IsActiveForConversion__c Checkbox ConversionIsActiveForMatching? IsActiveForMatching__c Checkbox MatchingIsActiveforReparenting? IsActiveForReparenting__c Checkbox Re-parentingIsBlockingKeyComplete? IsBlockingKeyComplete__c Checkbox NormalisationIsConversionMaster? IsConversionMaster__c Checkbox ConversionIsNormalised? IsNormalised__c Checkbox NormalisationLastConversionDate LastConversionDate__c Date/Time ConversionLastMatchingDate LastMatchingDate__c Date/Time MatchingLastMergedDate LastMergedDate__c Date/Time MergeLastNormalisedDate LastNormalisedDate__c Date/Time NormalisationLastSynchronisationDate LastSynchronisationDate__c Date/Time SynchronisationMatchingonSave? MatchingOnSave__c Checkbox MatchingMDMStatus MDMStatus__c Text(25) AllNormaliseonSave? NormaliseOnSave__c Checkbox NormalisationMasterFieldMap SystemMasterFieldMap__c LongText(5000) Merge

Synchronisation TargetObjectOnly DataSourceObjectOnlyOtherTypesofFields:MasterRecordLookups RelationshipfieldsthatenableSourceRecordstoberelatedtotheMaster

Record–e.g.MasterContact.NormalisationOutputFields CustomfieldsaddedasthetargetforNormalisationRules.

Examples;[NormalisedCompanyName],[ISOCountryCode],[EmailDomain].

Re-parentingRelationshipFields

LookuprelationshipfieldsaddedtoChildObjectstoenablere-parentingtoaMasterRecord.

IdentifierTargetFields TextfieldsaddedtoTargetObjectsthatarepopulatedwithaconcatenatedlistofSourceRecordidentifiers.

clearMDM - Installation Guide v1.6

Documents