To properly manage data, an MDM system provides support for Information Governance functionality such as policy evaluation, creation, and collaboration, as well as policy change management and impact analysis.
To meet these needs, the following functionality is available for use in STEP:
-
Policies that monitor data and data streams
-
Notifications in the UI and via email that inform users of deviations in the data quality
-
Metrics to define data quality
-
Sufficiencies that determine product data quality and completeness
Additionally, Configuration Governance involves capturing data that explains how your system works and how to use it. This could include metadata that documents, for example, the purpose of an attribute or integration endpoint, the owner of an LOV, or the process to request a change to a workflow. For STEP, the wiki (also known as Data Catalog Connector) provides a way to capture configuration governance metadata on many system setup objects, and displays it via a 'Go to Wiki' link. For more information, refer to the Wiki Metadata (Data Catalog Connector) topic in the System Setup documentation here.
Initial Data Policies Configuration
To set up Data Policies, on a Customer MDM-supported system, in the workbench, objects must be created with permissions added for the associated users. For information on configuring the workbench, refer to the Configuring Workbench to Create Data Policies section in the Data Policies topic here.
Configuring a Data Policy
For general guidelines on Data Policies, refer to the Data Policies topic in this documentation here.
To begin, configure a completeness metric, value metric, or function metric. For more information, refer to the following topics in the System Setup documentation: