Advanced Tools

Impact Analysis

Users with a Meta Read & Author License can now perform all operations in Impact Analysis, including adding and deleting objects, discovering impacts, and versioning.
What Changed
In Impact Analysis, actions could be performed by Meta Read Data No-Access (MRDN) users. Now, security controls restrict these actions. Only users with Meta Write Access can perform critical actions such as adding objects to Impact Analysis, deleting objects, discovering impact for added objects, and versioning objects.
Affected Users: Administrators

Lineage Maintenance

In Lineage Maintenance, the API Group dropdown was missing for API objects.
What Changed
In Lineage Maintenance, the API Group field dropdown was not available, which prevented the selection or assignment of an API group for API objects. Now, the API Group field has been added, allowing users to select and assign an API group directly within the maintenance interface. This enhancement improves organization, management, and visibility of API objects.
Affected Users: All Users
In the Advanced Tool, an API to schedule schema crawl for connectors.
What Changed
Schema crawls for connectors had to be scheduled manually after adding and validating a connector, which added extra steps and delayed automation. Now, a new API allows users to schedule schema crawls immediately after connector setup, enabling automated crawling and improving efficiency.
Affected Users: Administrators

Build Auto Lineage

In the Build Auto Lineage, the option to add column-level lineage has been removed from Lineage Shutter.
What Changed
The option to add column-level lineage using the Lineage Shutter did not function as intended and caused complications. Now, column-level lineage can no longer be added or managed through the Lineage Shutter. This update ensures a more stable, reliable, and predictable lineage experience for users.
Affected Users: Administrators & Authors

Load Metadata from Files

LMDF upload allows “Ignore if empty” and “No action” settings for business descriptions.
What Changed
In LMDF, during a Business Glossary LMDF upload, setting the configuration to “Ignore if empty”, removing the business description, and uploading the template triggered a “Mandatory field missing” error. The system incorrectly validated the business description field despite the “Ignore if empty” setting. Additionally, when the configuration was set to “No action”, only the detailed description was updated, and the business description remained unchanged. Now, the LMDF upload process honors the “Ignore if empty” setting, skipping validation for empty business description fields while applying other updates successfully. The “No action” setting correctly preserves the existing business description while allowing detailed description updates.
Affected Users: Administrators
LMDF – Unified Download Settings: A new setting, unified download.row.limit, has been added. Additionally, the “Download with Data Template” option has been disabled.
What Changed
In LMDF, downloading tables with data through LMDF failed for large datasets (for example, 1 million objects), as the job was terminated before completing the export. Now, the Download with Data Template option is disabled for modules such as Data Catalog, Business Glossary, and Tags. A unified download.row.limit setting enforces a maximum download size (default 10,000 rows, configurable up to 50,000) across the application. The deprecated rows.to.download setting has been removed.
Affected Users: Administrators
Load Metadata from Files Template uploads now include hidden sheet–based validation to ensure data integrity and correctness before processing.
What Changed
In LMDF, LMDF template uploads were validated based on the file name and column structure. Users who renamed templates for business purposes or collaboration encountered errors, even if the column structure was correct. Now, LMDF template uploads are validated using a hidden sheet within the template that stores required validation details. File name–based validation has been removed, and the system validates only the hidden sheet and column structure. Column structure validation continues unchanged to ensure data integrity.
Affected Users: Administrators

Compare Schema

In Compare Schema, schema comparisons can now be run from saved folders that contain the schemas to compare, enabling history tracking of previous comparison results.
What Changed
In Compare Schema, schema comparisons previously required users to manually enter the schema and date each time before running a comparison. Results were displayed after the job was completed, but no history of past comparisons was available. Now, users must create a folder to store the schemas for comparison and run the comparison from the 9-dot menu. This new approach maintains a history of schema comparisons for reference.
Note: Customers using Compare Schema must coordinate with the GCS team to transition to this new workflow.
Affected Users: Administrators & Authors
In Compare Schema, schema comparison supports multiple schema comparisons instead of a single comparison.
What Changed
In Compare Schema, previously, only a single schema comparison could be performed at a time. Now, the module supports multiple schema comparisons in one execution, expanding its comparison capability.
Affected Users: Administrators & Authors

PreviousCollaboration NextConnectors

Last updated 2 months ago

Was this helpful?