The April 2025 release of Data Governance and Catalog includes the following new features and enhancements.
Associate reference data from Reference 360 with glossary assets
You can now view and associate reference data from Reference 360 with business terms and metrics in Data Governance and Catalog.
You can view a sample list of the first 50 code values in Data Governance and Catalog, and then navigate to Reference 360 to view more reference data.
You can also use the bulk import process to associate reference data with business terms and metrics. To associate reference data, use the new Reference Data column in the import file. When you export business terms and metrics, the exported file contains the associated reference data details.
The following image shows the reference data of a Business Term asset:
Associate reference data from Reference 360 with data elements
You can now associate reference data from Reference 360 with both technical and manual data elements and view reference data for data sets. For data elements, you can link reference data associated with the glossary or associate new reference data from Reference 360. If multiple glossaries have associated reference data, you can choose which glossary to link. For data sets, you can view the reference data associated with their corresponding data elements.
You can also use the bulk import process to associate reference data with technical and manual data elements. To associate reference data with data elements, use the new Reference Data column in the import file or use the new Referenced Glossary column to associate reference data linked to the glossary. When you export technical and manual data elements, the exported file contains the associated reference data details.
The following image shows the reference data of a data element:
This release of Data Governance and Catalog introduces the Tasks Inbox, which allows you to view the tasks for workflows created using the new workflow engine implemented in the latest release of Metadata Command Center.
To maintain business continuity, you can continue to access the tasks for your existing workflows in the current Workflow Inbox from the Home page. Tasks related to workflows created using the Application Integration process will continue to appear in the Workflow Inbox until the next major upgrade for Data Governance and Catalog.
The following image shows the Tasks Inbox page:
Note: To streamline your ticket management experience, the Tasks Inbox will fully replace the Workflow Inbox in the next major upgrade for Data Governance and Catalog. Before the next major upgrade, ensure that you complete all tasks pertaining to workflows created through Application Integration. After the upgrade, any open tasks from these legacy workflows will expire, and the associated tickets will be cancelled.
Use CLAIRE to generate description and enrich assets
When you create a new glossary asset or curate technical assets with business context, Data Governance and Catalog now provides you the option to harness the power of CLAIRE to assist you in your journey.
The following image shows the Description section of a technical asset:
You can leverage CLAIRE to perform the following tasks:
•Generate a description when you are creating or modifying a glossary asset.
•Generate a business name and description for a technical asset.
As a part of this change, the user experience to enrich technical assets with business context has been updated. To explore the new experience, open the Contains tab of a data set or data element. On the Contains tab, use the Action menu next to the data element for which you want to curate data classifications to open the Curate Glossaries and Data Classifications dialog box.
The following image shows the Contains tab of a table:
If you expand a search-based widget, you can export assets of the corresponding search results using the Export button. On the Export Dashboard Widget dialog box, you can apply additional filters to the selected assets to export its child assets, relationships, custom attributes and other details.
The following image shows the Export Dashboard Widget dialog box:
You can use the following new public REST APIs to interact with the assets in Data Governance and Catalog:
•Use the Audit API to export the audit history of single or multiple assets.
•Use the following REST APIs to interact with data access assets:
- Data access control API. Use this API to view, create, modify, and delete data access control policies and data access control rules.
- Data de-identification API. Use this API to view, create, modify, and delete data de-identification policies and data de-identification rules.
- Data filter API. Use this API to view, create, modify, and delete data filter policies and data filter rules.
- Data protection API. Use this API to view, create, modify, and delete data protections.
- Precedence tier API. Use this API to view, create, modify, and delete precedence tiers.
- Publish assets API. Use this API to publish the draft version of an asset.
For more information about these REST APIs, see API Reference.
Data Access Management enhancements
This release includes the following enhancements to Data Access Management:
•You can use cell-level conditions to explicitly protect selected cells of data based on the values of one or more other fields. For example, based on the value in a country code field, you can protect the postal code where the country is U.S. differently than where the country is U.K. or France.
•You can push down data access control policies into the Microsoft Power BI cloud data platform to grant specific user groups read, write, or delete access to selected workspaces and datasets.
On the Lineage tab, you can now view catalog source level and system level lineage for assets. Catalog sources show the highest lineage level without underlying data sets or data elements. You can navigate across various lineage levels seamlessly with lineage at higher levels aggregating relevant information from lower levels.
The following image shows the catalog source level lineage for a sample technical data set:
The following image shows the system level lineage for a sample Microsoft Power BI Report:
For more information about data lineage, see Data lineage.
Notifications
Notifications have the following enhancements:
•In the notifications tray, related notifications are now grouped and collapsed under the first item. You can expand a group to view all notifications.
•Users with the privilege Manage user notifications can configure whether users in their organization receive email notifications. They can set the default behavior for new users and override the setting for all users. The Admin role has this privilege by default.
For more information about notification settings, see Organization Administration. For more information about roles and privileges, see User Administration.
•The product filtering option in the notifications tray no longer appears in services where filtering isn't available.
For more information about the notifications tray, see User Administration.
Receive notifications for pending tasks
Data Governance and Catalog now sends you a notification on the the Notifications page if a workflow task on an asset for which you are responsible, is approaching or past its due date.
For more information about notifications, see Notifications.
Data quality enhancements
This release includes the following enhancements to data quality:
•View aggregate and individual data quality scores for Geography and Project assets on the Data Quality tab of these asset pages.
The following image shows the data quality scores for Geography asset:
The following image shows the data quality scores for Project asset:
For more information about the Geography and the Project assets, see Geography and Project respectively.
•You can now view and download the data preview, including the preview of failed rows, for rule occurrences generated through data profiling scorecards. See the Data Preview pane in the Score tab of the rule occurrence.
The following image shows the Data Preview pane in a rule occurrence generated through data profiling scorecard:
The following image shows the download option for valid rows in a Data Preview pane:
The following image shows the download option for failed rows in a Data Preview pane:
This release includes the following enhancements to data observability:
•You can now specify the maximum number of anomaly events to generate for each catalog source run in Metadata Command Center. The minimum value should be 10.
If the detected anomalies in the catalog source exceed the limit you defined in Metadata Command Center, you can see a single event instead of individual events. The single event shows aggregated information on the detected anomalies.
The following image shows the new data observability configuration options:
•If an anomaly is detected in the catalog source and if you are a stakeholder of the catalog source, you can choose to receive email notifications for the anomalies. The email summarizes the data observability task job that was run.
•If anomalies are detected in a failed, skipped, or a partially-complete data observability job, you will not receive any email notification.
This release includes the following enhancements to customization:
•Switch between Standard and Compact modes to set the layout density from the user Settings page in Data Governance and Catalog and Metadata Command Center. The Compact mode optimizes screen space to display the interface layout in a dense format.
The following image shows the new display options on the user Settings page:
•The Browse page, the Contains tab, and the Hierarchy tab now have the following enhancements:
- Additional asset-specific columns, such as columns for custom attributes.
- New filters for specific assets, such as a system type filter for system assets.
- Additional sorting options.
Additionally, the Contains tab shows indicators if it has primary and foreign keys.
The following image shows asset-specific columns:
The following image shows asset-specific filter for the process asset:
The following image shows primary key and foreign key indicators for a table:
This release includes the following enhancements to bulk export and import:
•When you create or update a data quality rule template or a data quality rule occurrence using bulk import, you can now specify the output port names of the primary data element of the data quality rule. The bulk import templates and the exported files for data quality rule template and rule occurrence contain a new column called Output Port Name.
•You can now see the Threshold Result column extracted in the export sheet of a data quality rule occurrence.
•In the bulk import file for data quality rule template, the Enable Automation column now supports automatic triggering of data quality rule occurrences. The function triggers rule occurrences based on the number of data elements associated with the Glossary assets that are linked to the rule template.
If you set the value to True, the rule template automatically triggers rule occurrences when the data quality rule template is executed. After the bulk import job, Data Governance and Catalog initiates a job to create schedules for the Catalog Source. The rule occurrences are created as per the schedule each time the data quality job runs. The frequency of the data quality rule execution depends on the frequency set in the Frequency column of the rule template file.
If set to False, no automated rule occurrences are generated. You can manually run the data quality rule for the associated data elements.
If automation was previously enabled on a rule template, then you cannot use a bulk import template to modify the value from True to False
You can perform connection assignment to view the lineage between Informatica Intelligent Cloud Services Data Integration mappings and an SAP ERP data source.
You can now run incremental metadata extraction jobs on the following catalog sources:
•Microsoft Azure Blob Storage
•Microsoft Azure SQL Server
•Microsoft Azure Synapse Data Warehouse
•Oracle
•SAP BW4HANA
•SAP Business Warehouse
•SAP ERP
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.
You can now leverage the Business Process Modeling Notation (BPMN) infrastructure to design multi-step approval workflows in Metadata Command Center. You can design workflows that suit your organizational needs and configure events for the workflows in Metadata Command Center. The workflows start when you work with assets in Data Governance and Catalog.
Important: After you upgrade to the April 2025 release, you need to redesign your workflows in Metadata Command Center. You can use predefined workflows that Informatica provides or build your own workflows.
For more information about designing workflows, see Workflows.
Configure business name and description assignment for glossary association
When you configure glossary association, you can choose to assign business names and descriptions to technical assets. If you assign business names and descriptions, you can choose to apply them only to unassigned assets and retain current assignments, or allow the overwrite of existing assignments.
For more information about assigning business names and descriptions to technical assets, see Glossary Association.
Export lookup tables
You can export lookup tables that you use in data classification.
Enable recommendations below the confidence score threshold for auto-acceptance
When you enable auto-acceptance for glossary association, you can choose to enable or disable recommendations below the Confidence Score Threshold for Auto-Acceptance. Specify a Confidence Score Threshold for Recommendations to get recommendations between 80 and your confidence score threshold for auto-acceptance, or between 80 and 100 if you don't enable auto-acceptance.
For more information about enabling and disabling recommendations, see Glossary Association.
Preview data classifications
You can preview details of a data element or a data entity when you configure data classification for a catalog source.
