What's New > Data Governance and Catalog > Changed behavior
  

Changed behavior

The April 2025 release of Data Governance and Catalog includes the following changed behaviors.

Updated minimum number of data points for detecting anomalies

You can specify the minimum number of data points that are required for data observability to start detecting anomalies. Specify any value between 3 and 10.
Previously, you could specify the minimum number of data point values between 3 and 5.

Edit primary data element in a data quality rule occurrence

After you create a data quality rule occurrence, you can edit the primary data element only if the new primary data element belongs to the same catalog source as the previous one. You cannot edit the primary data element after you have run the rule occurrence. You can perform this action only in the user interface.
Previously, you could not edit the primary data element after you created the rule occurrence.

Select rule specifications with multiple outputs in technical rule reference

When you create a data quality rule occurrence or a data quality rule template, you can use the Technical Rule Reference field to select rule specifications that have multiple outputs.
Previously, the rule specification that you selected could have only one additional output other than the available exception task outputs.

Renamed the Rule Port Name column in the bulk import template

The Rule Port Name column in the data quality rule template and a data quality rule occurrence bulk import template is renamed to Input Port Name.

View upstream and downstream assets on the Hierarchy tab

On the Hierarchy tab of an asset, you can now view both the upstream and downstream assets.
Previously, the Hierarchy tab displayed only the child assets of the open assets.

Addition of data element sensitivity icon

You can now see the sensitivity icon for each data element individually, if they have a data sensitivity level set. You can view the sensitivity icons for data elements in the Data Classification section, Contains tab, asset Overview page, and asset preview panel.

Relationship search and export improvement

You can now view and export all the search results when searching for assets.
Previously, you could export a maximum of 2000 assets for relationship-based search queries, and a maximum of 10,000 assets for other search queries.

Predefined workflows

Predefined workflows are now available in Metadata Command Center.
Previously, you had to download and import predefined bundles from Administrator as processes to Application Integration.
For more information about configuring workflows, see Configure workflows.

Schedule organization upgrades

You can now schedule organization upgrades of Metadata Command Center, Data Governance and Catalog, and Data Marketplace after Informatica makes the version available on the POD that you connect to.
Previously, you could not schedule organization upgrades.
For more information about upgrading your organization, see Upgrade organization to the latest version.

Privileges for organization upgrades

To initiate the organization upgrade, you must now be the organization administrator or have the Manage Upgrade privilege for your user role. If you don't initiate the upgrade, Informatica upgrades your organization six weeks after it makes the version available on the POD.
Previously, to initiate the upgrade, you had to be the organization administrator or have the Super Admin privilege for your user role.
For more information about feature privileges that are available for Metadata Command Center in Administrator, see Feature privileges in Administrator.

Snowflake metadata extraction method

Metadata Command Center can now also use information_schema.tables, information_schema.views, and information_schema.columns to extract metadata from Snowflake catalog source.
Previously, Metadata Command Center only used show commands.
For more information about configuring metadata extraction in Snowflake, see Configure metadata extraction.

Catalog source type name change

The following catalog source types have been renamed:
Previous name
Current name
Microsoft Azure Synapse
Microsoft Azure Synapse Data Warehouse
Microsoft Azure Synapse Script
Microsoft Azure Synapse Data Warehouse Script

Extract pipeline instances from Microsoft Azure Data Factory source system

When you extract metadata, pipeline instances get extracted by default.
Previously, you had to enable the operational metadata option to extract pipeline instances for the catalog source.
For more information, see Microsoft Azure Data Factory.

Select objects for metadata extraction

When you define filters for metadata extraction, you can select an object from a list of objects available in the source system.
Previously, you manually entered the object name in the filter value field.
You can select an object from a list when you configure the following catalog sources:
For more information, see Catalog Source Configuration.

Extract pipeline instances from Microsoft Azure Data Factory source system

When you extract metadata, pipeline instances get extracted by default.
Previously, you had to enable the operational metadata option to extract pipeline instances for the catalog source.
For more information, see Microsoft Azure Data Factory.

Catalog source type name change

The following catalog source types have been renamed:
Previous name
Current name
Microsoft Azure Synapse
Microsoft Azure Synapse Data Warehouse
Microsoft Azure Synapse Script
Microsoft Azure Synapse Data Warehouse Script