Data Director User Guide

10.3

Back Next

Example of a Review Process for Edits

The staff in the Finance department use

Data Director

to keep supplier banking information up to date. A supplier representative contacts a Finance staff member and requests a change to the supplier's banking information.

In the Finance department, each

Data Director

user credential includes one of the following user roles:

User. Staff members have permission to add and change records, but the changes must go through a review process before the master data is updated.

Manager. A manager is a type of business user with additional permissions. A manager reviews changes, but cannot approve changes. If a manager agrees with a change, he escalates it to a senior manager.

SrManger. A senior manager is a type of manger with additional permissions. A senior manager reviews changes and has the authority to approve them.

A staff member edits the supplier data as requested by the supplier representative. The following steps describe what happens during the review process.

A staff member changes the banking information of the supplier and saves the change. In the MDM Hub Store, the state of the supplier records changes from active to pending. The proposed edit is saved in a cross-reference record. The save action initiates the review process.

An instance of a review process starts and begins executing activities.

When the review process reaches the first people activity, it generates a task notification for managers. For example, in the default review process, the first people activity is Review No Approve. All managers with the role of Manager receive a task notification in the task inbox with the task type of Review No Approve.

A manager claims the task. The task is assigned to the manager and the task disappears from the task inboxes of the other managers.

The manager opens the supplier record, reviews the edit, and agrees with the edit. The manager resolves the task by clicking Escalate.

The review process marks the task as complete, and follows the Escalate flow to the next activity.

When the review process reaches the next people activity, the process generates a task notification for senior managers. For example, in the default review process, the second people activity is Final Review. All senior managers with the role of SrManager receive a task notification in the task inbox with the task type of Final Review.

A senior manager claims the task. The task is assigned to the senior manager and the task disappears from the task inboxes of the other senior managers.

The senior manager opens the supplier record, reviews the edit, and agrees with the edit. The senior manager resolves the task by clicking Approve.

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 banking information in the supplier banking record. The supplier records change to the active state.

Rename Saved Search

Table of Contents

Data Director User Guide

Data Director User Guide

Example of a Review Process for Edits

Example of a Review Process for Edits