- You can extract metadata from Informatica Application Integration source systems.
- You can perform connection assignment to view lineage between an SAP ERP source system and an Informatica Intelligent Cloud Services source system.
- You can perform connection assignment to view lineage between an SAP Business Warehouse source system and an Informatica Intelligent Cloud Services source system source system.
- You can now configure how the catalog source reads Cloud Data Integration mapping task XML files when you extract metadata. Choose one of the following input fetch modes:
▪ API. Default. Fetches tasks through the Informatica Intelligent Cloud Services API.
▪ Files. Reads only the files in the input files folder.
▪ Both. Combines both modes, matching objects in the files and through the API.
- You can now extract metadata from the following activities in Automation Studio:
▪ Data Copy or Import
▪ Data Extract with no wildcard characters
▪ File Transfer
▪ Filter
▪ SQL Query with data extension and data view sources
- You can add metadata extraction filters based on the automation object type.
- You can now extract metadata and add metadata extraction filters for the following Salesforce Data 360 and Salesforce CRM objects:
▪ Activation
▪ Segmentation
- You can perform connection assignment to view lineage between a Salesforce Marketing Cloud source system and the Salesforce Data 360 and Salesforce CRM applications.
- You can perform connection assignment to view lineage between a Cloudera Hadoop source system and a Tableau source system.
- You can extract metadata from published data sources and Salesforce sources such as CRM, Data360, and Semantic Layer through Tableau. You can also view the real project hierarchy along with more detailed assets information and lineage in Data Governance and Catalog.
This release includes the following workflow enhancements:
Service task to retrieve asset details in a workflow
You can add a service task to route a workflow dynamically, based on asset groups and the custom attribute values of the asset the workflow runs on. You can use these values in expressions that define the gateway conditions.
Using the asset details available in the gateway conditions, you can configure an inclusive gateway that directs the workflow based on the asset metadata. For example, you can route the workflow along a different path for an asset that belongs to a specific asset group.
Inclusive gateway
You can add an inclusive gateway to a workflow to route the flow along one or more outgoing paths based on conditions. The inclusive gateway evaluates the condition on each outgoing path independently, and the workflow follows every path whose condition is true. If no condition is true, the workflow follows a default path. An inclusive gateway activates one or more paths based on conditions.
Periodic review of assets (Preview)
You can set up a periodic review of assets while configuring workflow events in Metadata Command Center to certify business and data access assets on a schedule. Periodic review helps you keep assets accurate, up to date, and audit ready. You can configure a workflow event that reviews the assets that meet a condition, such as glossaries in a specific domain. When the schedule runs, the event automatically creates a review ticket for each qualifying business asset and data access asset.
Data Governance and Catalog creates review tickets automatically for the qualifying assets based on the schedule. The stakeholders defined in the workflow can review the asset, set its lifecycle to complete the review, and close the ticket. Each asset shows the last review date and the next review date. You can also search and browse assets by the last review date and the next review date.
Approval workflows for asset lifecycle changes
You can configure a workflow that runs when the lifecycle of an asset changes. Under the asset management event category, a new event type, Approval Request for Lifecycle Change, triggers a workflow when an asset's lifecycle state changes. The workflow runs when an asset moves from the Published state to the Obsolete state, or from the Obsolete state to the Published state. When you configure a workflow for this event type, you can select only the Obsolete or Published state.
You can now define rules that assign a sensitivity level to Document assets. A Document asset represents an unstructured file, such as a PDF or Microsoft Word document, in the catalog. You can apply sensitivity levels to these assets based on the classification policies that you define.
Access control based on data classification sensitivity
When you create or modify an access policy in Metadata Command Center, you can add a sensitivity level as a predicate to a condition. The new predicate allows you to control access to assets based on the sensitivity level of their data classifications.
You can configure catalog sources to propagate enrichments to related assets based on lineage.
Enable autonomous enrichment to propagate curation values such as classifications, descriptions, business names, and glossary associations across catalog source assets. Enable autonomous enrichment globally, and then configure each catalog source to control how it receives enrichments.
Propagation settings determine which enrichment types propagate, from how many lineage levels they propagate, and whether values are automatically accepted or recommended.
For information about autonomous enrichment, see Autonomous Enrichment and the corresponding catalog source help.
Global settings for generated descriptions
You can now configure global settings that shape the descriptions Data Governance and Catalog generates for your assets. Set the industry and text length that apply to all generated descriptions. You can override these settings in Data Governance and Catalog.
For information about configuring generated descriptions, see Autonomous Enrichment.
Incremental metadata extraction
You can now run incremental metadata extraction jobs on the following catalog sources:
•Microsoft Fabric OneLake
•Microsoft OneDrive
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.
LIKE operators in data classification rules and lookup tables
When you build data classification rules in Cloud Data Governance and Catalog, you can use the LIKE ALL, LIKE SOME, and LIKE ANY operators to match a value against multiple patterns in a single condition. You can also reference a lookup table column as the pattern source. Use LIKE (lkp.<table>.<column>), LIKE SOME (lkp.<table>.<column>), or LIKE ANY (lkp.<table>.<column>) to match against the values in a lookup column.
You can now extract metadata from additional file formats across multiple catalog sources.
Newly Supported File Types:
•EML
•EMLX
•MSG
•RTF
•PPT
•PPTX
•JSONL
Supported 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.
Classify Microsoft Word documents
You can now use Document Classification in Metadata Command Center to classify Microsoft Word documents with the DOC and DOCX extensions. You can classify Microsoft Word documents for the following catalog sources:
•Amazon S3
•Hadoop Distributed File System
•Microsoft Azure Blob Storage
•Microsoft Azure Data Lake Storage Gen2
•Microsoft SharePoint Online
•Oracle Cloud Object Storage
•SFTP File System
For more information about catalog sources, see the corresponding catalog source help.
Deleting lookup tables
You can delete a lookup table that is not used in any data classification rule.