Metadata Governance
Tags
New & Improved
Improved Visibility of Selected Master Tags in Custom Fields
In Tags, when users selected a Master Tag for custom fields, the selection did not appear in the dropdown list, making it difficult to confirm that the Master Tag was selected.
With this improvement, the selected Master Tag now remains visible in the dropdown after selection. Users can clearly verify the applied value without confusion.
Data Catalog
New & Improved
Improved Download Workflow for Code Results in Data Catalog
In Data Catalog | Codes, the Results tab allowed users to download query results directly without triggering a job execution. This behavior differed from that of the Query Sheet, where a job execution is initiated before the downloadable file is prepared.
With this improvement, clicking Download Results in the Codes Results tab now triggers a job execution similar to Query Sheet. Once execution is successful, the latest query results are prepared and downloaded.
Enhanced Image Preview and Zoom in Descriptions
In the Data Catalog and Business Glossary | Descriptions, images added to the Business Description or Technical Description fields could be viewed only within the description area. Clicking an image did not open it in a separate window, making it difficult for users to review detailed diagrams, workflows, or screenshots.
With this improvement, clicking an image now opens it in a larger preview window, allowing users to zoom in and view the image clearly without affecting the rest of the page. Users can now review image-based content more easily, especially for complex workflows and documentation.
Enhanced Critical Data Element UI in Data Catalog
In Data Catalog, the Critical Data Element (CDE) field and its related UI elements did not provide a clear, consistent experience. The CDE field displayed values such as None, Recommended, and Critical Data Element; the View History icon appeared prominently, and the “Not recommended as CDE – See Why?” message continued to appear even after an object was marked as a CDE. In addition, CDE justification details were not available in list view, filtering options were limited, and the “Marked as Critical Data Element” text was truncated in the summary page.
With this improvement, the CDE field now displays simpler values such as Yes and No, the View History icon is minimized, and the recommendation message is removed once an object is marked as a CDE. CDE justification is now available in the list view; users can filter objects by CDE values, and summary page labels are displayed in full without truncation.
Added Profiling Status for Databases in Data Catalog
In Data Catalog, users could view the list of databases but could not determine whether profiling had been completed for each database, making it difficult to identify which databases were fully profiled, partially profiled, pending profiling, or had encountered profiling failures.
With this improvement, the profiling status is now displayed for databases in the Data Catalog. Users can view statuses such as Profiled, Not Profiled, Partially Profiled, and Profile Failed directly within the database listing. The profiling status view for Databases must be configured from the configure view.
Enhanced View Access Details with User-Specific Access
In the Data Catalog, the View Access Permissions feature displayed access for all users and roles but did not clearly show the logged-in user’s effective access. Users had to manually identify their permissions, which made it difficult to understand their access.
With this improvement, a new “My Access” tab is introduced in the access panel. This tab displays the logged-in user’s access details, including role, permission, and access source. Users can now easily view how their access is granted, including multiple roles with different permissions.
Improved Visibility of Download Option in Code Results Page
In Data Catalog | Codes, users had to scroll to the bottom of the Results page after running a custom query to access the Download option, making it less convenient to download results quickly.
With this improvement, the Download option is now displayed directly on the Results page, in a more visible location. Users can access and download custom query results more easily without needing to scroll through the entire page.
Added Severity Field for Critical Data Elements
In the Data Catalog summary, Critical Data Elements previously lacked a dedicated field to indicate their criticality. Users had to rely on custom code fields, such as Critical 1, Critical 2, and Critical 3, to represent severity levels.
With this enhancement, a new Severity field is available for Critical Data Elements. Users can now assign a severity level directly within the CDE configuration to indicate how critical a data element is.
Redshift Tables | DistKey and SortKey visibility
In the Data Catalog, support for viewing DistKey and SortKey information for Redshift tables has been added to improve metadata visibility and understanding of data distribution.
The following improvements have been implemented:
DistKey column details are displayed for Redshift tables
SortKey columns are displayed with order and key type
Support for Compound and SortKey types
Metadata is fetched through an optional crawler configuration
Information is displayed under the Indexes & Keys section in the table summary
Sub-tabs are hidden when no DistKey or SortKey is available
Loading Indicator Added to the Data Tab
In the Data tab, users did not see any indication that a live sample data fetch was in progress. As a result, the screen remained blank until the data loaded, making it unclear whether the request was being processed.
With this improvement, a loading indicator is now displayed while sample data is being fetched. Users can clearly see that the system is processing the request and loading the data.
Fixed
Reports | Last Modified Date behavior
In the Data Catalog Reports, the issue where the Last Modified Date is updated by system-driven events results in inaccurate metadata tracking. The issue where the Last Modified Date was updated by system-driven events resulted in inaccurate metadata tracking.
Fixed Missing Tables in Breadcrumb Schema View
In Data Catalog, an issue where no tables were displayed for the schema in the breadcrumb view when Temporary Lineage was enabled has been resolved. Selecting the schema in the breadcrumb did not show the related tables, even though the schema was available in the filter.
The breadcrumb view has been corrected to display the appropriate tables for the selected schema.
Data Products
New & Improved
Centralized Audit Trails for Data Products
In Audit Trails, activities related to Data Products were previously available only in the Individual Activities tab of each Data Product, making it difficult to review changes in a centralized location and creating an inconsistent audit experience compared to other modules.
With this improvement, a dedicated Data Products option is now available under the Governance Catalog category in Audit Trails. Users can select either Data Products from the SubCategory list to view related audit records in a centralized interface.
New Audit Events Added for Data Products
In Data Products, the system now captures additional audit events for actions such as updating Instant Availability expiry, adding objects to the askEdgi Workspace, viewing Access Instructions, viewing Data Product lineage, and viewing Data Product relationships.
This enhancement provides better activity tracking and improves audit visibility for key user interactions within Data Products.
Enhanced Role-Based Access Control for Data Products
In Security | Applications, Data Products cannot be selectively restricted to specific roles. As a result, Data Product - Registry and Data Product - Marketplace remained visible based on general access settings, even when organizations wanted only OE_ADMIN users to access them.
With this improvement, administrators can now enable Role-Based Access for Data Products and assign authorized roles such as OE_ADMIN. Data Product - Registry can be restricted to Author users in the selected roles, while Data Product - Marketplace can be configured for both Author and Viewer users in the selected roles.
Fixed
Data Product Draft Mode Role Assignment Fix
In Data Product, an issue where Admins and Managers could not update Data Product Managers and Data Product Browsers while the data product was in Draft mode has been resolved. Role assignments were restricted during the Draft stage, preventing necessary updates from being made before publication.
The permission logic has been updated to allow Admins and Managers to modify Data Product Managers and Browsers in Draft mode.
Lineage Display Issue in Data Product Resolved
In Data Product | Lineage & Relationship, an issue where lineage was not displayed even when data objects were available for the selected product has been resolved. The Lineage & Relationship view appeared empty despite the presence of related data objects. This issue prevented visibility into how assets were connected.
The lineage display logic has been resolved to ensure relationships are shown whenever associated data objects exist for the selected product.
Data Quality
New & Improved
Data Quality Schemes
A new Data Quality Schemes feature provides a structured framework for grouping and managing multiple data quality rules across datasets. It helps users validate data against defined business and technical standards, automate rule execution, and centrally monitor results.
Data Quality Schemes support a holistic approach to data quality across both tables and files, enabling consistent rule application across different data sources, end-to-end validation, centralized visibility, and improved governance.
Key capabilities include:
Scheme Management: Create, edit, publish, and manage schemes with details such as name, description, object type, connector, and steward.
Rule Association: Add and manage multiple rules with functions, dimensions, validation criteria, and associated objects.
Dashboard & Summary: Review execution KPIs, rule quality trends, row quality trends, recent runs, and remediation impact.
Execution Monitoring: Track scheme and rule execution results, including pass, fail, undetermined, and execution failed statuses.
Scheduling & Notifications: Configure recurring executions, alerts, service requests, and downstream caution settings.
Service Requests & Contacts: Manage remediation requests and maintain contacts for notifications and escalations.
Audit History: Track scheme and rule changes for governance, accountability, and traceability. Add, update, and delete actions performed in the Data Quality Schemes module are recorded in dedicated DQS Audit Trails, separate from Data Quality Rules events.
Updated Naming Rules for Data Quality Rule Names
In the Data Quality module, naming validation for rule names has been updated to restrict unsupported special characters while allowing the period (.) character. This aligns Data Quality naming conventions with validations used in other areas of the application.
Existing Data Quality rules continue to work as expected. New or updated rule names must follow the revised naming guidelines.
Navigation Enhancements from Data Catalog
Navigation to Data Quality details from the Data Catalog has been improved for faster access to rule and scheme information. Clicking the Data Quality Rules Count now opens the selected object’s Data Quality Rules tab in the View Dashboard in a new browser tab. The same navigation is also available for Data Quality Schemes counts.
Data Quality Remediation Centre | Service Request Tracking for Failed Values
The Data Quality Remediation Centre has been enhanced to improve tracking and resolution of failed values identified during Data Quality Rule executions. A new Service Request ID column is available in the remediation view, allowing users to track tickets created for failed values directly from the Data Quality Remediation Centre.
Additional enhancements include:
New summary views for rule-based, object-based, and detailed failure analysis
Improved visibility into failed values reported, remediation status, and latest failure activity
Direct linkage between failed values and remediation requests
Support for external integrations such as Jira and ServiceNow, where failed values can be shared in a structured format
Data Anomaly Detection | Enhanced Inheritance, Object Visibility, and Job Log Details
Data Anomaly Detection has been enhanced to improve configuration consistency, anomaly traceability, and operational transparency. Anomaly detection settings now support hierarchical inheritance across object levels. Tables can inherit settings from schemas, and table columns can inherit settings from parent tables, schemas, connectors, or global defaults based on precedence.
Additional enhancements include:
Improved anomaly result visibility with separate columns for Connection Name, Schema Name, Table Name, and Table Column Name.
Clearer parent setting indicators while configuring anomaly detection
Enhanced job logs that identify the configuration source used during execution
Query Sheet
New & Improved
Background Job Support for Query Sheet Downloads
In the Query Sheet, downloading results generated the file immediately without triggering any background job. For large datasets, this could increase application load and impact performance during file generation.
With this improvement, downloading Query Sheet results now triggers a background job that appears in the Jobs section. The file is generated during job execution and becomes available once the process completes.
This enhancement improves performance and system stability by moving large download operations out of the main application flow.
GDPR ROPA
New & Improved
Improved Service Request Confirmation for ROPA Reports
In GDPR ROPA, users could submit a service request for Reports or Processing Activities, but no confirmation message was displayed after submission, which made it unclear whether the request had been submitted successfully.
With this improvement, a notification message is now displayed when a user submits a service request for a Report or Processing Activity.
Fixed
Improved Filter Scrolling in ROPA Reports
In ROPA Reports, an issue where the filter pop-up was difficult to scroll and use has been resolved. The filter window has been improved to make scrolling and accessing filter options easier.
Reference Data Management
New & Improved
Gold Source Indicator on Data Object Pages
Reference Data Management has been enhanced to improve visibility of authoritative data sources within the catalog. The data objects designated as a Gold Source now display an indicator directly on the object detail page. Users can quickly identify authoritative reference data sources without leaving the catalog.
Enhanced Reference Data Visibility and Data Preview
A new Data Preview capability allows viewing the first 150 rows of configured reference data values directly within the module.
Access has also been expanded for business users based on security permissions. Users with appropriate metadata access can view objects, while Data Preview is available according to assigned data permissions.
Viewer License Support in Security Permissions
Reference Data Management permissions can now be configured for Viewer users through Security settings. The License Type option is now selectable when assigning module permissions, allowing administrators to grant access based on viewer licensing.
Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?