Processing critical data changes
Updates to critical data can be updated and any party suspects identified in realtime, or those changes can be held until a data steward accepts or rejects the change.
InfoSphere® MDM provides various transactions to update party information in real-time, such as updateParty, updatePersonName, and others. When the transactions involve updating the party's critical data—such as name and address—the critical data is updated, party suspects are re-identified based on the presence of critical data change, and notification is generated indicating critical data has changed. All this processing can happen in real-time.
InfoSphere MDM also provides a feature for suspending critical data change in real-time. Instead, the critical data change remains pending until such time when a data steward either accepts or rejects the change. When a change is rejected, the existing party information is unchanged. When a change is accepted, the existing party information is updated with the critical data. Subsequently, party suspects are re-identified and notification is generated.
Suspending critical data change in real-time is called Critical Data Change processing.
An example where Critical Data Change processing would be used is when a customer representative uses the updateParty transaction to change the party's information. If Critical Data Change processing is configured on, and the change contains critical data, the critical data change is held as pending. A data steward then verifies the validity of the data, and uses the updatePartyPendingCDCRequest transaction to accept the pending critical data change. The party's information is then updated.
Definitions of terms used when discussing Critical Data Changes
Terms that are used when discussing Critical Data Changes are:
- Critical Data Change
- Changes that are made to the critical data of a party. In the context of Critical Data Change processing, a critical data change is encapsulated at a business object level. For example, changes to the person's last name and first name are contained in a single TCRMPersonNameBObj object.
- Critical Data Change Request
- An update transaction can produce one or more critical data changes. For example, an updatePersonName transaction may produce one critical data change of the party's name information. An updateParty transaction may produce several critical data changes, such as the party's name, address, and identification. A party's Critical Data Change request must be either accepted or rejected before another Critical Data Change request can be made for that party.
Data model for Critical Data Changes
The following data map illustrates how Critical Data Changes works.