System trigger tasks
There are two system trigger tasks: HasShadow and PreMerge. These tasks are used primarily by the Message Brokers to trigger an internal system action.
Users reviewing records and tasks typically do not see these two types in MDM client applications
When tasks are created, users can modify data through the Inspector data stewardship application to resolve the issue. If task resolution required that member attribute data be modified, that attribute is assigned a status of S for shadow.
After the shadow status is assigned, a trigger is sent to the outbound broker component. The outbound broker then creates a message that contains the attribute change and sends it to the appropriate source system. When the client system is updated with the change, a confirmation message is returned to the MDM operational server by the inbound broker. When the confirmation is received, the attribute status changes from Shadow to Active.
When a suspected duplicate task is created, resolution requires that one record is made obsolete and one is made the survivor. After the workflow status is set, the records are in a “premerge” state. The outbound broker triggers on a premerge condition and sends a message to the appropriate source system. When the merge is made in the source system, a confirmation message is returned to the MDM operational server and the task is closed.