You can use ActiveVOS to ensure that updated entity data goes through a change-approval workflow before the updated records contribute to 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

integrate with the ActiveVOS Server. Predefined MDM workflows, task types, and roles enable the components to synchronize with one another. You can configure your MDM implementation to work with the embedded ActiveVOS server. Alternatively, you can run a standalone instance of ActiveVOS in your environment.

Embedded ActiveVOS authenticates requests from

Data Director

and the MDM Hub by a specific principal that is trusted by both MDM and ActiveVOS. This principal is called the trusted user. The system administrator creates the credentials and roles for the trusted user in the application server.

The ActiveVOS server must run on the same application server as the MDM Hub. For more information, see the

Multidomain MDM Configuration Guide

.