Table of Contents

Search

  1. Preface
  2. MDM and Embedded ActiveVOS
  3. Configuring Workflow Tasks and Triggers
  4. Running the Migration Script
  5. Frequently Asked Questions

MDM and ActiveVOS Overview

MDM and ActiveVOS Overview

You can ensure that updated entity data goes through a change-approval workflow before the updated records contribute the Best Version of the Truth (BVT) records. For example, a business process might require that a senior manager review and approve updates to customer data before it becomes master data.
To support a change-approval workflow, the
MDM Hub
and
Data Director
(IDD) integrate with the ActiveVOS
®
Server. Predefined MDM workflows, task types, and roles enable the components to synchronize with one another.
The components support a change-approval workflow in the following ways:
  • The
    MDM Hub
    manages a state on the records in the base object tables that have state management enabled. Unapproved records have a pending state, while approved records have an active state.
  • In IDD applications, authorized business users change entity data and can send updates for approval.
  • The
    ActiveVOS Server
    runs activities within the MDM workflows and creates tasks for business managers and data stewards.

0 COMMENTS

We’d like to hear from you!