The October 2026 release of Data Governance and Catalog includes the following changed behavior.
Changes to deletion behavior of data quality rule occurrences
You can delete a data quality rule occurrence after it generates data quality scores. The deletion is no longer blocked by the presence of data quality scores, because data quality scores are no longer treated as child assets of the rule occurrence.
Previously, you could not delete data quality rule occurrences that were associated with data quality scores.
Changes to secondary data element selection for data quality rule occurrences
When the measuring method of a data quality rule occurrence is any value other than Informatica Cloud Data Quality, you can select primary and secondary data elements that belong to different sources and tables for the rule occurrence. This also applies when you upload the rule occurrence through bulk import.
Previously, the secondary data element had to belong to the same table as the primary data element, regardless of the measuring method.
Changes to lifecycle status updates for business assets
You can configure an approval worflow when a business asset changes its lifecycle status from Published to Obsolete. Data Governance and Catalog creates a ticket and starts the configured approval workflow. The asset remains visible to other users with its Published status, and edits are blocked for all users, including stakeholders, until the ticket is closed. When the ticket is approved and closed, the lifecycle status changes to Obsolete. The ticket captures the lifecycle change.
Similarly, when you change the lifecycle status from Obsolete to Published, Data Governance and Catalog creates a ticket for approval. The ticket captures the lifecycle change along with any description updates since the asset was last published.
Previously, if you had edit permission, you could change an asset's lifecycle status from the asset page without triggering a workflow or creating a ticket.
Obsolete asset modifications
You can remove a reference dataset association from an obsolete asset. To keep obsolete assets consistent with their lifecycle state, you can no longer associate a reference dataset with obsolete assets.
Previously, you could add or change the reference dataset associated with an obsolete asset.
Changes to permissions to manage connections of a catalog source
In Metadata Command Center, you can assign, modify, and unassign the connections to a catalog source for which you aren't a stakeholder. To manage the connections of a catalog source, the organization administrator must grant you the Manage Lineage Settings and Super Admin privileges for the Metadata Command Center service in Administrator. With these privileges, you can manage connections without edit permissions on catalog source assets.
Previously, you had to be a stakeholder of the catalog source to manage its connections.
Changes to the row count limit for data quality rule occurrences
The total number of rows and the number of failed rows that a data quality rule occurrence can report is extended beyond the previous limit.
Previously, the total rows and failed rows were limited to approximately 2.1 billion integer range.
Changes to stakeholder management
Options for the Stakeholder Status column
In a search export file, the Stakeholder Status column includes the Both option. This status indicates that the asset can include stakeholders who are assigned by you or inherited through its hierarchy.
Previously, the available status options for stakeholders on an asset were either Inherited or Assigned.
Prevent stakeholder re-inheritance
You can prevent the re-inheritance of a parent asset's stakeholders after you remove them from a child asset.
Previously, when you removed all stakeholders from an asset, the stakeholders of the parent asset were immediately re-inherited.
Include technical data elements in export
When you export a business data set with the Include Child Assets option, the export includes technical data elements that are children of the business data set. You export the assets in a separate sheet along with the business data set's manual data elements.
Previously, a Business Data Set export with child assets included only manually created Data Elements.
Changes to the CLAIRE Activity widget
When you click the CLAIRE Activity widget on the dashboard, the Curation Center page opens, where you can review and curate recommendations for assets. While the CLAIRE Activity widget shows the total number of recommendations for all assets in your catalog, the Curation Center shows the total number of assets that have recommendations. In the Curation Center, you can view and act only on assets for which you're responsible.
You can click the different types of recommendations on the CLAIRE Activity widget to open the filtered assets in the Curation Center. The generated classification recommendation type is disabled on the CLAIRE Activity widget because you cannot curate generated classifications in the Curation Center.
Previously, the CLAIRE Activity widget opened its own drilldown page where you could only view assets with different types of recommendations and their statuses.
Change in export behavior for rich text fields
When you export assets that contain rich text fields, such as Description, Business Logic, rich-text custom attributes, you can preserve the HTML formatting or export the fields as plain text without HTML tags. If you preserve the formatting of the rich text fields, the field remains editable. Your edits take effect when you re-import the file. If you export the fields without HTML tags, you cannot edit the fields for re-import.
If the rich text fields contain non-HTML strings in angle brackets, the export preserves the formatting regardless of your choice during the export. For example, the fields might contain <Enterprise> and <CustomerName>.
Previously, rich text fields were always exported with HTML tags.
Changes to propagation jobs
Data Governance and Catalog runs batch jobs for propagating data set relationships, stakeholders, and asset groups. For these updates, a placeholder job queues the changes you make. After which, Data Governance and Catalog runs a dedicated job for each propagation. The batch job propagates the changes in the order you make them and changes appear on assets after the job completes.
Relationship Batch Propagation is the batch job for data set relationships, and Asset Group & Stakeholder Batch Propagation is the batch job for propagations in asset stakeholders and groups.
Previously, propagation jobs for data set relationships, stakeholders and asset groups ran concurrently.
Catalog source configuration options based on the selected model
When a catalog source type supports more than one model, you now view only the configuration options that apply to the model you select. Previously, you viewed all the configuration options for the catalog source type regardless of the selected model.
Microsoft PowerBI connector name change
The Microsoft PowerBI connector in Administrator is renamed to Microsoft Fabric. Both the Microsoft PowerBI catalog source and the new Microsoft Fabric catalog source use this connector. The Microsoft Fabric connector also includes additional connection properties.
Decision gateway path conditions based on expressions
You can configure the outgoing paths from a decision gateway with an expression or with a previous user task outcome. When you use an expression, a path can use the outcome of a service task that runs earlier in the workflow.
Previously, you could configure the outgoing paths from a decision gateway only with a user task outcome.