The November 2025 release of Data Governance and Catalog includes the following new features and enhancements.
Watch the following What's New video to learn about the new features and enhancements in the November 2025 release:
Usage analytics for governance
Usage analytics help you track and report the impact of governance on data and data users. You can monitor analytics for various user and asset trends on dashboards for Assets and User Adoption. The dashboards have various widgets that show data on several predefined metrics across user adoption and engagement, and data curation and management.
In Metadata Command Center, administrators can enable usage analytics from the Configure page. Enabling usage analytics starts collecting metric data and also activates usage analytics dashboards in Data Governance and Catalog.
In Data Governance and Catalog, administrators can share usage analytics dashboards to users and groups. You can perform various activities on the dashboards such as customize dashboards, add widgets, and share dashboards.
The following image shows a system-generated User Adoption dashboard with various preconfigured widgets:
This release integrates data profiling capabilities into Data Governance and Catalog, enabling you to create and run data profiles on data elements using rules and view detailed profile results.
Use data profiling to perform deep analysis on technical assets to assess data quality across sources, and gain insights into the accuracy, completeness, conformity, and consistency of data. You can run data profiling on a large number of data elements and compare results between historical profile runs to perform a time series analysis. The profile results also help you perform what-if analyses of data quality assets such as rule specification, cleanse, parse, and verifier.
You can assign an unclaimed task or reassign a task that is already claimed by a user. Find the assignment options in the Assign Tasks dialog box on the Tasks Inbox page.
The following image shows the Assign Task dialog box:
You can use the following new and enhanced features for data access management:
•You can reverse the effect of a data de-identification technique on your data and return the data to its original state. To unmask the data, configure an Access Policy transformation in a mapping in Data Integration and run the mapping.
•You can use the constant value data de-identification technique to mask decimal and integer values with a constant value when you create or edit a data protection.
For more information about the constant value data de-identification technique, see Constant value.
Data quality remediation
If you are the stakeholder of a data quality rule occurrence and you opt for notifications, you receive in-app and email notifications when the data quality score in the rule occurrence changes between two consecutive runs. Your organization administrator can enable automatic creation of tickets if the data quality score goes below the threshold that you specify in the rule occurrence. The administrator can set the Data Quality Remediation option in the Data Quality section of the catalog source configuration to Yes and enable the Data Quality Failure Ticket option. The Data Quality Remediation option is disabled by default.
The administrator can define downward and upward score thresholds based on the criticality of the rule occurrence for which you receive notifications in Metadata Command Center.
The following image shows the Notifications tab in the Configure page in Metadata Command Center:
When the administrator enables the Data Quality Remediation option, you can select a flat file connection in Metadata Command Center, and specify a location where the failed rows are written during each rule occurrence execution. If you want to preview all failed rows and download them for further remediation action, you can copy the file path link from the rule occurrence and navigate to the location that you specified.
The following image shows the Data Quality Remediation and the Create Data Quality Failure Ticket options in Metadata Command Center:
For more information about data quality score change notifications, see Notifications.
You can filter data entities and observe the entities for freshness and volume by configuring the Asset filters panel on the Data Observability tab of a catalog source in Metadata Command Center. You don't need to manually enable the Metadata Extraction or Data Profiling options to observe your data.
The following image shows the new data observability filters in Metadata Command Center:
If you modify the stakeholders on an asset, the newly added stakeholders will receive notifications for the active workflow tasks that are associated with the asset. Data Governance and Catalog will send only new task notifications to the newly added stakeholders. Notifications sent before their addition will not be reissued to the new stakeholders.
For more information about notifications, see Notifications.
Enhanced notifications for technical asset updates
Metadata Command Center notifies stakeholders of a catalog source when a technical asset in the source system changes.
Metadata Command Center sends a notification for the following types of change to a technical asset in the source system:
•Updates to the attributes of an asset. For example, a technical asset is renamed and its description is updated.
•Updates to asset structure. For example, the data type of the asset is changed or a child asset is removed from the asset.
•Discovery of new assets. New assets are discovered when the source system is scanned.
If a catalog source is assigned more than one stakeholder, all the stakeholders receive the notification. Stakeholders receive an email notification and a notification within the Data Governance and Catalog interface that summarizes all asset changes within the source. To manage these notifications, you can use the Technical Asset Changes subcategory on the Asset Changes tab of the Notification Settings page.
For more information about notifications, see Notifications.
URL as a custom attribute
You can add a URL or a hyperlinked label as a custom attribute for asset types. Select the URL Field data type in Metadata Command Center to add a URL as an attribute.
Then in Data Governance and Catalog, you can modify the URL on associated asset pages or through bulk import and export operations.
The following image shows a business term with a custom attribute of the URL field data type:
For more information about the bulk import process, see Bulk import process.
Updates to Save options for search results
When you save your search, you can save the sorting order along with the search query and any filters you applied.
For catalog sources that extract XML objects, you can view the attribute Repeatable. In an XML schema, the attribute indicates if a node can repeat under the parent node. If the value for Repeatable is yes, then the node can repeat multiple times under the parent node. If the value for Repeatable is no, then the node does not repeat under the parent node.
The following image shows the attribute Repeatable for an XML object:
The QuickLook browser extension introduces the Data Marketplace filter that enables you to discover Data Governance and Catalog assets that are added by stakeholders to data collections in Data Marketplace. You can also view the data collections that are associated with these assets and open the data collections in Data Marketplace.
The following image shows the Data Marketplace filter in the Informatica QuickLook browser extension:
You can extract metadata from source systems hosted on Google Cloud Dataproc clusters using non-Kerberos authentication and on Cloudera Data Platform (CDP) version 7.3.1.
When you extract metadata from Databricks notebooks, you can use the Notebooks Preload Paths property to specify the paths to the Databricks notebooks that you want to preload.
- You can extract metadata from pipelines that connect to SAP HANA source systems.
- You can perform connection assignment to view lineage between an SAP HANA Database source system and a Microsoft Azure Synapse Analytics source system.
- You can extract metadata from Salesforce datasets that use Salesforce Object Query Language (SOQL) queries.
- You can run metadata extraction jobs with the SAP Datasphere Command Line Interface. You can choose the metadata extraction method when you configure metadata extraction.
- You can perform connection assignment to view lineage between the following source systems and an SAP Datasphere source system:
▪ SAP Enterprise Resource Planning
▪ SAP Business Warehouse
▪ SAP HANA
▪ SAP BW/4HANA
▪ SAP S/4HANA
▪ SAP Analytics Cloud
For more information about catalog sources, see SAP Datasphere.
SAP SuccessFactors
You can use OAuth 2.0 authentication to connect to an SAP SuccessFactors source system.
You can configure the following additional data capabilities on catalog sources:
•Glossary association, data classification, and relationship discovery capabilities on Greenplum.
•Glossary association and data classification capabilities on the following catalog sources:
- SAP Datasphere
- Workday
•Profiling and data quality capabilities on SAP SuccessFactors.
For more information about catalog sources, see the corresponding catalog source help.
Incremental metadata extraction
You can now run incremental metadata extraction jobs on the following catalog sources:
•Databricks
Applicable only to Databricks Unity Catalog.
Applies to the following Databricks Unity Catalog objects:
- Table
- View
•Google BigQuery
•Google Cloud Storage
•Microsoft Sharepoint Online
•Workday
A full metadata extraction extracts all objects from the source to the catalog. An incremental metadata extraction considers only the changed and new objects since the last successful catalog source job run. Incremental metadata extraction doesn’t remove deleted objects from the catalog and doesn’t extract metadata of code-based objects.
For more information about catalog sources, see the corresponding catalog source help.
Technical Description extraction
You can now view the technical description after you run a metadata extraction job on pipelines and activities with the following catalog sources:
•Microsoft Azure Synapse Analytics
•Microsoft Azure Data Factory
For more information about catalog sources, see the corresponding catalog source help.
Metadata extraction from partitioned JSON files
You can extract metadata from partitioned JSON files with the following catalog sources:
•Amazon S3
•File System
•Google Cloud Storage
•Hadoop Distributed File System
•Microsoft Azure Blob Storage
•Microsoft Azure Data Lake Storage Gen2
•Microsoft Fabric OneLake
•Microsoft OneDrive
•Microsoft SharePoint Online
•Oracle Cloud Object Storage
•SFTP File System
For more information about catalog sources, see the corresponding catalog source help.
Configure partition detection for JSON and XML files
You can enable partition detection for JSON and XML files in the following catalog sources:
•Amazon S3
•File System
•Google Cloud Storage
•Hadoop Distributed File System
•Microsoft Azure Blob Storage
•Microsoft Azure Data Lake Storage Gen2
•Microsoft Fabric OneLake
•Microsoft OneDrive
•Microsoft Sharepoint Online
•Oracle Cloud Object Storage
•SFTP File System
For more information about catalog sources, see the corresponding catalog source help.
Deprecate objects deleted from a source system
When you configure or run a catalog source, you can choose to deprecate objects that are deleted from a source system using the Metadata Change Option. If you delete objects from the source or make changes to the filter, the objects imported into the catalog before the change move to the "Obsolete" lifecycle in the catalog.
You can purge such obsolete objects from a catalog source. This permanently deletes all objects with the "Obsolete" lifecycle status, along with associated enrichments, from the catalog.
For more information about catalog sources, see the corresponding catalog source help.
Modify assigned connections
You can modify connection assignments to endpoint catalog source objects. After you modify connections, the connection assignment job starts. When the job completes, the old connections are unassigned, new connections are assigned, and Metadata Command Center creates links between matching objects in the connected catalog sources.
Export lists of matched and unmatched objects after assigning connections
After you assign connections to endpoint catalog source objects, there can be both matched and unmatched objects in the catalog. Matched objects are objects that directly match the assigned endpoint objects. Unmatched objects are objects that don't directly match the assigned endpoint objects and are not found in the source system.
After assigning connections, you can export a list of matched and unmatched objects to a Microsoft Excel file. You can use these lists for remediation or for reference.
When you define filters for metadata extraction, you can include or exclude metadata from a folder or file path. You can either enter the path as the filter value or select a path from a list of folders and files available in the source system.
You can filter based on a folder, file, or path when you configure the following catalog sources:
•Amazon S3
•File System
•Google Cloud Storage
•Hadoop Distributed File System
•Microsoft Azure Blob Storage
•Microsoft Azure Data Lake Storage Gen2
•Microsoft Fabric OneLake
•Microsoft OneDrive
•Microsoft SharePoint Online
•Oracle Cloud Object Storage
•SFTP File System
For more information about catalog sources, see the corresponding catalog source help.
Generate lineage for file system based catalog sources
When you link catalog sources to generate lineage, you can select file system based catalog sources as the source and target catalog sources.
You can choose any of the following file system based catalog sources when you link catalog sources:
Generating JSON Web Token (JWT) to authenticate REST API requests
To authenticate users to REST API endpoints, organization administrators can choose the JSON Web Token-based authentication method in Administrator. This method allows you to generate JWT tokens without a session ID.
With this method, you can authenticate to REST API endpoints with only the JWT token. However, generating the JWT token from a session ID remains the default.
You can use the parallel gateway component to design workflows that require multiple tasks to run concurrently.
For example, when you create a workflow for processing a loan application, you can add multiple tasks that can run in parallel to speed up the process. Customer credit risk validation, KYC collection, asset details, and legal inputs are tasks that users can perform concurrently.
For more information about how you can design a workflow, see Designing a workflow.
Modify published workflows
You can now edit an existing workflow that is already published.
For more information about how you can modify a workflow, see Update a workflow.
Custom layouts for the Browse page
Administrators can configure custom layouts for the Browse page. The configuration options are similar to the custom layout options for the Asset page.
Metadata Command Center now sends email notifications about organization upgrades to the latest versions of Metadata Command Center, Data Governance and Catalog, and Data Marketplace.
As an administrator, you receive notifications for the following events:
