The July 2025 release of Data Governance and Catalog includes the following changed behaviors.
Updated feature privileges for Metadata Command Center and Data Governance and Catalog
You can now view the following updated feature privileges for Metadata Command Center as well as a new feature privilege for Data Governance and Catalog:
Current privilege name
New privilege name
Description
Manage Reference Data
Manage Lookup Tables
Allows users to import and publish lookup tables that can be used in data classification.
View Reference Data
View Lookup Tables
Allows users to view lookup tables.
View Reference Data
Allows users to view data on the Reference Data tab for business terms, metrics, manual data elements, and data elements.
Data quality modifications
This release includes the following modifications to data quality:
•You will now need to associate a Data Quality Failure ticket with a workflow.
Previously, you could create Data Quality Failure tickets without workflows to notify the stakeholders of an asset about data quality failure issues or low data quality scores.
Note: Data Quality Failure tickets that were previously created will be automatically resolved or cancelled.
•You can now execute upto ten profiling runs for anomaly detection while configuring data observability for a catalog source in Metadata Command Center.
Previously, you could execute upto five profiling runs.
•The Data Quality Automation parameter in the Data Profiling and Quality tab of a catalog source is renamed to Data Quality Rule Automation.
•If you're a stakeholder of a data quality rule occurrence, you'll receive notifications and email alerts if the score of the rule occurrence improves.
Previously, you received notifications and alerts only when the data quality score status deteriorated.
•You can now select rule specifications with multiple inputs in the Technical Rule Reference field of a Data Quality Rule Occurrence or a Data Quality Rule Template asset.
•In a data quality rule occurrence, you will now see more accurate data quality score percentage based on the validity of the records.
Preeviously, you saw a 100% score even if a very small number of records were invalid.
•In a rule occurrence generated from a scorecard, all affected columns are now highlighted when you view the preview of failed and valid rows under the Preview of Valid Rows and Preview of Failed Rows options when the rule has multiple inputs.
•When you upload a data quality score through API, a data quality score propagation job is triggered in Metadata Command Center.
Previously, the score propagation job was triggered only when you updated the score through UI or bulk import.
•You can view the open events for your asset based on metric and severity in a single widget.
Search queries show only accepted associations
Search results strictly show associations between business terms and data sets that are in the accepted state.
Previously, search results would show pending and declined associations.
Separate descriptions for catalog sources in Metadata Command Center and Data Governance and Catalog
A catalog source can have different descriptions in Metadata Command Center and Data Governance and Catalog. When you update the description of a catalog source in Metadata Command Center, the update doesn’t appear in Data Governance and Catalog, and when you update the description in Data Governance and Catalog, it doesn’t appear in Metadata Command Center.
Previously, when you modified the description in one service, it updated in both.