TIBCO MDM Customization Guide - TIBCO Product Documentation

218 Chapter 10 Setting up Data Quality Process|record already exists in the application using the MatchRecord activity. If youfound the exact match for this new record, you can directly merge the sourcerecord with the target record. For example, consider the following recordhierarchy:Figure 10 Merge Record : InDocument modeIn this case, a new record - John Roe has two related records: Address record PaloAlto, 94304 and BankAccount record Bank of California Acct Number11223344 and the existing record - John Doe has one related ResidenceAddressrecord Palo Alto, 94304 , which is found matching. However,SavingsBankAccount relationship does not exist. Hence, while merging therecords, the following records are merged:• Primary Person record is merged.• Attributes of the matching ResidenceAddress repository are merged.• By default, true value is specified for ImplicitRelationshipMergeparameter, therefore non-matching SavingsBankAccount relationship is alsomerged.ImplicitRelationshipMerge works only for Direct merge. Implicit RelationshipMerge allows you to merge non-matching relationship records. You can select notto merge such non-matching relationships implicitly by specifying the falsevalue for the ImplicitRelationshipMerge parameter of the MergeRecordactivity.Legacy ModeThe Legacy mode is supported only with the release version 8.2 or later. Legacymode uses the MergeRecordUsingLegacyProcess parameter of the MergeRecordactivity. If you found a source record matching with the existing record, you candirectly process it for merge or you can pass source and target records directly tothe merge without evaluating MatchRecord activity.The MatchRecord activity is optional for the Legacy mode.TIBCO MDM Customization Guide