Table of Contents

Search

  1. Preface
  2. Introduction to Informatica MDM - Customer 360
  3. Getting Started
  4. Adding Records
  5. Finding Records
  6. Editing Records
  7. Working with Drafts
  8. Participating in Review Processes
  9. Importing Data
  10. Resolving Duplicates
  11. Investigating Data Changes
  12. Investigating Hierarchies and Relationships
  13. Viewing the Relationship Graph

Example of a Review Process for Edits

Example of a Review Process for Edits

The staff in the Despatch department use
Customer 360
to keep customer address information up to date.
In the Despatch department, each user credential includes one of the following user roles:
  • Sales Operation Analyst. The user have permission to add and change records, but the changes must go through a review process before the master data is updated.
  • Sales Operation Manager. A Sales Operation Manager is a type of manager with additional permissions. A Sales Operation Manager reviews changes and has the authority to approve them.
A Sales Operation Analyst edits the customer data as requested by the customer representative. The following steps describe what happens during the review process.
  1. A Sales Operation Analyst changes the address information of the customer and saves the change. In the MDM Hub Store, the state of the customer records changes from active to pending. The proposed edit is saved in a cross-reference record. The save action initiates the review process.
  2. An instance of a review process starts and begins executing activities.
  3. When the review process reaches the first people activity, it generates a task for managers. All users with the role of Sales Operation Manager receive a task notification in the task inbox with the task type of Approve.
  4. A Sales Operation Manager claims the task. The task is assigned to the manager.
  5. The Sales Operation Manager opens the customer record, reviews the edit, and agrees with the edit. The manager resolves the task by clicking Approve.
  6. The review process marks the task as complete, and follows the Approve flow. The review process notifies the MDM Hub that the change is approved, and then the review process ends. The MDM Hub changes the address information in the customer record. The customer records change to the active state. The creator of the record receives a notification, when a record is approved or rejected.