Release7.2.5.12
This release introduces key enhancements and bug fixes across Notifications, Data Catalog, Business Glossary, Dashboards, Data Quality, Service Desk, LMDF, Query Sheet, Lineage, Connectors, Data Access Management, and Security, improving alert accuracy, reporting visibility, lineage performance, metadata management, authentication flexibility, and platform security.
Key Highlights
Notifications & Alerts: Fixed incorrect role assignment notifications, inaccurate Data Quality alerts, and missing links in Service Desk emails to ensure accurate notifications and valid request access.
Data Catalog: Added role-based default views, allowing administrators to configure customized default layouts tailored to different user roles and responsibilities. This is applicable to Data Catalog and other modules that support Custom Views.
Business Glossary: Resolved missing glossary terms in Tree View by correcting category hierarchy handling, ensuring terms display under their respective folders.
Dashboards: Added row count change analysis between successive crawls, enabling users to track increases and decreases in table data with row count differences, percentage changes, and historical comparison details across connectors.
Data Quality: Fixed an upgrade issue that moved custom functions to Draft status, ensuring scheduled Data Quality rules continue to execute after migration.
Service Desk: Corrected loading failures on All Requests and Waiting for Approval pages caused by invalid ticket field values.
Load Metadata from Files (LMDF):
Resolved glossary upload log errors caused by unnecessary exceptions after successful processing.
Fixed editing issues for existing Data Quality functions after migration, enabling successful updates and saves.
Service Desk Templates:
Fixed “Depends On” configurations not persisting after save operations.
Resolved ticket submission failures when generic fields were included in templates.
Query Sheet: Fixed Arabic text handling in Query History to preserve and display multilingual query content correctly after execution.
Lineage:
Fixed QuickSight lineage report performance by reducing slow loading times.
Corrected Dell Boomi auto-lineage display issues for child components.
Resolved missing column mappings in Dell Boomi lineage to ensure complete end-to-end lineage visibility.
Fixed Tableau report-level lineage pages that remained stuck in a loading state.
Connectors (Snowflake): Enhanced Key Pair Authentication support to allow secure Snowflake connections without storing private key files in the OvalEdge environment, improving compatibility with SaaS deployment and security compliance requirements.
Data Access Management: Enabled editing of the Authentication Type field directly from the Snowflake Instance Summary page for a more consistent configuration experience.
Security: Strengthened session handling, cookie security, and platform security configurations to address vulnerabilities identified during penetration testing.
Release Details:
Hotfix Release
Release7.2.5.12
Release7.2.5.12.725123b21159
May 08, 2026
Notifications
Fixed
Resolved Incorrect Notifications and Alert Triggers
In Notifications & Alerts, an issue where role assignment notifications showed incorrect objects, data quality alerts were sent incorrectly, and service request emails contained missing links has been resolved. Notifications displayed more objects than those actually assigned. Data quality alerts were sent to incorrect recipients or triggered even when no issues existed. Service request emails sometimes included a null or missing link.
The notification logic has been corrected to show only the assigned objects. Data quality alerts are now sent to the correct recipients only when issues occur. Service request emails now include valid request links.
Data Catalog
New & Improved
Role-Specific Default View Configuration
In Data Catalog and other modules that support Custom Views, users can create customized views to display relevant information based on their needs. However, these views could not be assigned as the default for specific user roles, requiring users to manually configure their preferred layout each time.
With this improvement, administrators can now create and assign role-specific default views in Data Catalog and other supported modules. For example, Data Analysts can be provided with a default view that highlights only relevant sections such as Lineage, Data Quality, and Table Information. At the same time, other roles can receive views tailored to their responsibilities.
Business Glossary
Fixed
Resolved Missing Terms in Glossary Tree View
In Business Glossary, an issue where glossary terms within category folders were not visible in the Tree View has been resolved. Category folders showed no terms, even though terms were present and visible in the category details page. Only top-level terms appeared in the Tree View. The incorrect handling of category hierarchy data caused the issue. The logic has been updated to correctly display glossary terms under their respective category folders in the Tree View.
Dashboards
New & Improved
Row Count Change Analysis Between Crawls
A new reporting enhancement provides visibility into row count changes between successive crawls. Previously, users could view only the latest row count information, making it difficult to identify increases or decreases in table data over time.
With this improvement, the reporting framework now compares current and previous crawl results, displaying row-count differences and percentage changes for tables across connectors. The report highlights tables with changed row counts and provides details such as current and previous row counts, profile dates, and overall change trends.
Data Quality
Fixed
Fix for Draft Status Issue in Data Quality Functions
In Data Quality, an issue where custom functions moved to draft status after upgrading to version 7.2 has been resolved. Because the functions moved to draft status, scheduled Data Quality rules linked to those functions did not run, even though the jobs page showed successful execution.
The upgrade process has been corrected to ensure custom functions remain published after migration and scheduled Data Quality rules continue to run as expected.
Service Desk
Fixed
Fix for Service Desk “Oops” Error on Requests Pages
In Service Desk, an issue where the module displayed an “Oops Technical Issue Occurred” message and failed to load the All Requests and Waiting for Approval pages has been resolved. The module did not load due to invalid or empty values in certain ticket data fields.
The data handling has been corrected to properly process such values, allowing the Service Desk pages to load as expected.
Load Metadata from Files
Fixed
LMDF Glossary Upload Log Error Resolved
In LMDF, an issue where a ‘NoSuchElementException’ appeared in job logs after uploading glossary terms has been resolved. The terms were created successfully, but an error was recorded after all rows were processed, creating confusion about the job status.
The processing logic has been corrected to prevent this exception, ensuring the upload completes without errors in the job logs.
Fix for Editing Existing Data Quality Functions in LMDF
In LMDF, an issue where existing data quality functions could not be modified after migration has been resolved. Attempts to edit and save changes resulted in an error that blocked updates to already-deployed functions.
The issue has been fixed, allowing successful modification and saving of existing functions.
Service Desk Administration
Fixed
Fix for “Depends On” Settings Not Saving
In the Service Desk Templates, an issue where the “Depends On” configuration did not save has been resolved. The JSON settings added for a field were lost after saving and reopening the field. The configuration did not persist as expected.
The save logic has been fixed to ensure the “Depends On” configuration is retained and available when the field is reopened.
Resolved Ticket Submission Failure with Generic Fields
In Service Desk Templates, an issue where ticket submission failed after adding a generic field to a template has been resolved. Tickets were not created even after all required details were provided when a generic field was included in the template.
The submission process has been fixed to allow successful ticket creation when generic fields are present.
Query Sheet
Fixed
Resolved Arabic Text Removal in Query Sheet
In the Query Sheet, an issue where Arabic text was removed from executed queries has been resolved. Queries containing Arabic text appeared incomplete in Query History because Arabic characters were not preserved after execution, affecting queries that used Arabic values for filtering or validation.
The query handling process has been updated to retain and display Arabic text correctly in Query History.
Lineage
Fixed
Resolved Slow Loading in QuickSight Lineage Reports
In QuickSight, an issue where some lineage reports took more than a minute to load has been resolved. The lineage page responded slowly after establishing the QuickSight and Redshift connections, delaying access to reports.
Performance improvements have been applied to reduce page load time and improve report responsiveness.
Dell Boomi Auto Lineage Display Fix
In Dell Boomi, an issue where child components were displayed incorrectly on the Build Auto Lineage page has been resolved. Components such as PROCESS_START and PROCESS_DECISION were displayed as datasets rather than appearing only under associations, resulting in an incorrect lineage representation.
The lineage display logic has been updated to show child components in the correct section.
Resolved Missing Column Mapping in Dell Boomi Lineage
In Dell Boomi, an issue with missing column mapping for a specific component in the lineage view has been resolved. Column-level lineage was not captured beyond a single mapping component, resulting in incomplete mapping details in the summary lineage view and gaps in the end-to-end lineage flow.
The lineage processing has been corrected to capture column mapping for all components and display complete lineage information in both technical and summary views.
Resolved Report-Level Lineage Loading Issue in Tableau
In Tableau, an issue in which the report-level lineage page remained stuck in a loading state and would not open has been resolved. Lineage information was available at the table and column levels, but report-level lineage failed to load for Tableau reports even after rebuilding lineage.
The issue has been fixed to ensure report-level lineage pages load correctly and display the expected lineage information.
Connectors
New & Improved
Enhanced Snowflake Key Pair Authentication Support for SaaS Deployments
In the existing Snowflake integration setup, Key Pair Authentication requires users to place the private key file directly within the OvalEdge environment. This approach worked for on-premises deployments but created challenges for customers migrating to SaaS environments, especially when external credential files could not be stored on OvalEdge infrastructure.
With this improvement, users can now configure Snowflake Key Pair Authentication without storing private key files in the OvalEdge environment. Existing authentication methods continue to be supported, while the new capability provides greater flexibility for SaaS deployment and security compliance requirements.
Data Access Management
New & Improved
Editable Authentication Type Field in Snowflake Instance Summary
On the Snowflake Instance Summary page, the Authentication Type field was displayed as read-only, even though it was editable on the Connector Edit page, which created an inconsistent user experience between the two configuration screens.
With this improvement, the Authentication Type field is now enabled and editable in the Instance Summary page as well. This update provides a consistent configuration experience and allows users to modify the authentication type directly from the instance details page.
Security
Fixed
Resolved Session Exposure and Security Configuration Issues
In Security, an issue in which vulnerabilities identified during the second round of penetration testing exposed session details and revealed weak security configurations has been resolved. The testing identified risks related to session exposure, improper security settings, and cookie handling. Sensitive session information could still be accessed despite earlier fixes.
Security controls have been strengthened to protect session data, enforce appropriate security settings, and ensure secure cookie handling.
Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?