> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/hotfix-releases/release7.2.5.x/release7.2.5.19.md). # Release7.2.5.19 This release introduces key enhancements across My Profile, Data Catalog, Business Glossary, Reference Data Management, Data Quality Rules, Jobs, Lineage, Connectors, Data Access Management, Job Workflow, Security, and Audit Trails, improving localization, governance capabilities, metadata consistency, lineage coverage, connector flexibility, access management, and security monitoring. **Key Highlights** * **My Profile**: Fixed missing Spanish translations for UI labels. * **Data Catalog**: Resolved certification management by allowing authorized governance roles, including stewards, to update certifications without requiring additional permissions. * **Business Glossary**: Resolved the term publishing experience by resolving delayed confirmation popups and ensuring published statuses are reflected immediately. * **Reference Data Management**: Added support for associating Reference Data assets with Data Products, introduced Owner information for Reference Data Units, simplified associated object views, and fixed invalid dates and table view loading issues. * **Data Quality Rules**: Added API support to execute an entire Data Quality Job Workflow with a single request, simplifying execution of workflows with multiple rules. * **Jobs**: Fixed job log download failures to ensure logs are generated and downloaded successfully. * **Lineage**: Expanded lineage support to include Oracle Editionable Views, improved ADF lineage handling for TXT files, resolved incomplete Power BI lineage generation, and corrected duplicate and missing mappings in Qlik Sense lineage. * **Connectors**: Added support for external storage locations for Informatica PowerCenter parameter files and introduced Service Principal authentication for Snowflake connections. Also resolved partial metadata extraction in SAP BO Universe crawls and validation failures for Amazon S3 connections configured with restricted permissions. * **Data Access Management**: Enabled Snowflake masking policies to be reused across schemas, reducing the need to create duplicate policies. * **Job Workflow**: Fixed sequential workflow schedule failures caused by duplicate metric entries and restored visibility of associated jobs in Weekly Lineage Build workflow details. * **Security**: Introduced break-glass access capabilities with security notifications to support emergency access scenarios, improve monitoring, and strengthen incident response. * **Custom Fields**: Corrected KPI counts by removing hidden custom field content retained in the database. * **Audit Trails**: Corrected logout activity tracking and export formatting issues to ensure accurate audit records and properly aligned reports. Release Details:
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.19release7.2.5.19.725196758fd8June 23, 2026
## My Profile ### Fixed **Resolved Missing Spanish Translations for UI Labels** In the OvalEdge application, an issue where some UI labels remained in English after selecting Spanish as the application language has been resolved. Translation support has been updated to ensure that the labels are displayed in Spanish when the Spanish language option is selected. ## Data Catalog ### Fixed **Resolved Certification Access for Authorized Roles** In Data Catalog, an issue where the Update Certification option remained unavailable for objects assigned to authorized governance roles has been resolved. Objects assigned to Owners, Stewards, or Custodians could not be certified unless additional metaWrite or administrator permissions were granted, even when those roles were configured for certification. The certification process has been updated to allow authorized governance roles to update certifications without requiring extra object-level permissions. ## Business Glossary ### Fixed **Resolved Delayed Confirmation Popup During Term Publishing** In Business Glossary, an issue where the confirmation popup remained open for several seconds after publishing a draft Term, and in some cases reappeared repeatedly or required a page refresh to reflect the published status, has been resolved. The Term publishing process was improved to close the confirmation popup promptly and display the updated term status correctly. ## Reference Data Management ### New & Improved **Reference Data Associations Added to Data Products** Data Products did not provide a dedicated place to associate and view related Reference Data assets. As a result, users could not easily identify which reference data supported a particular Data Product. With this enhancement, a new placeholder has been added to the Related Objects Summary in Data Products. Users can now link and manage Reference Data assets directly within a Data Product and view these relationships in a single location. **Added Owner Information for Reference Data Units** In Reference Data Management, there was no dedicated field to identify the person responsible for maintaining a reference data set. Users had to rely on other sources to determine ownership, making it difficult to know who to contact for updates or questions. With this enhancement, an Owner field has been added to Reference Data Units, allowing users to assign and display the person responsible for managing the reference data. This improvement provides better visibility into data ownership, makes it easier to identify the appropriate stakeholder, and supports more effective management of reference data assets. **Simplified Associated Objects View in Reference Data Management** In Reference Data Management (RDM), associated objects were displayed at the column level. When multiple columns from the same table were associated, the same table appeared multiple times, making the list crowded and difficult to understand. With this improvement, associated objects are now displayed at the table level. If a specific column is associated, it is highlighted in the table rather than the table being shown multiple times. ### Fixed **Fixed Invalid Dates and Table View Loading in RDM** In Reference Data Management (RDM), an issue where Reference Data Units displayed invalid Created and Modified dates in the List View and failed to load data in the Table View has been resolved. Dates were shown incorrectly in the List View, and opening the Table View displayed an "Unable to Load the Data" message even though top values were available. The date display and data-loading issues have been fixed to ensure valid dates are shown and data is displayed correctly in the Table View. ## Data Quality Rules ### New & Improved **API Support for Executing Data Quality Job Workflows** Data Quality Job Workflows could previously be run only through scheduled jobs. At the same time, APIs supported executing individual DQ rules, requiring users to make multiple API calls to run all rules within a workflow, which was difficult to manage in environments with many DQ rules. With this enhancement, users can now trigger an entire Data Quality Job Workflow through a single API call. The API executes all DQ rules included in the selected workflow while preserving the configured execution sequence and existing access controls. ## Jobs ### Fixed **Resolved Stuck Job Log Downloads** In Jobs, an issue in which downloading logs for an individual job would get stuck at the "Downloading Job Logs" stage and never complete has been resolved. The download process did not finish, preventing job log files from being generated and downloaded. The download functionality has been fixed to ensure job logs are generated and downloaded successfully. ## Lineage ### New & Improved **Support Added for Crawling Oracle Editionable Views** In the Oracle connector, lineage analysis did not include codes created as ‘EDITIONABLE VIEW’ objects. As a result, these views were not crawled and were missing from Build Auto Lineage, leading to incomplete lineage information. With this improvement, the crawler now identifies and processes ‘EDITIONABLE VIEW’ objects during code crawling. These views are included in lineage analysis and are available in Build Auto Lineage alongside other supported code objects. ### Fixed **Fixed Temporary Object Creation for TXT Files in ADF Lineage** In ADF (Azure Data Factory) Lineage, an issue where .txt files were incorrectly assigned an additional .csv extension during lineage creation has been resolved. This issue caused temporary lineage objects, such as Extract.txt.csv, to be created instead of linking lineage to the existing Extract.txt asset in the data catalog. The lineage process has been corrected to retain the original file name and accurately associate lineage with the corresponding catalog asset, preventing unnecessary temporary objects. **Fixed Incomplete Lineage Generation for Power BI Datasets** In Power BI Connection, an issue where the Weekly Lineage Build job completed with a partial success status and failed to build lineage for some datasets has been resolved. The job encountered processing errors, preventing lineage from being generated for all supported datasets. The lineage build process has been improved to complete successfully and generate lineage consistently across supported Power BI datasets. **Resolved Duplicate and Incomplete Qlik Sense Lineage Mappings** In Qlik Sense, an issue in which report lineage displayed duplicate mappings and missed some dashboard-level transformations has been resolved. This issue caused lineage paths to appear incomplete or inaccurate in certain reports. The lineage generation process was corrected to remove duplicate mappings and ensure all expected transformations are captured and displayed correctly. ## Connectors ### New & Improved **Support for External Storage Locations for Informatica PowerCenter Parameter Files** The Informatica PowerCenter connector previously required parameter files to be stored on the local Bridge server or virtual machine, limiting deployment options for organizations that restrict local file storage or file transfers. With this enhancement, the connector can now be configured to read parameter files from external storage locations such as Amazon S3, OneDrive, and other supported file systems. Existing local path-based configurations remain supported, ensuring backward compatibility. **Service Principal Authentication Support for the Snowflake Connector** The Snowflake connector previously supported only username/password and key-pair authentication methods. Organizations that use service principals as part of their standard security practices could not use this authentication approach when configuring Snowflake connections. With this enhancement, the Snowflake connector now supports Service Principal–based authentication. Users can configure Snowflake connections using a service principal, providing an additional authentication option alongside the existing methods. ### Fixed **Resolved Partial Success in SAP BO Universe Crawls** In SAP BO Universe Connector, an issue where crawl jobs ended with a partial success status and failed to retrieve all metadata has been resolved. The issue occurred because connection details were missing during processing, preventing some SAP BO universe objects from being fully crawled. The connector has been updated to correctly handle connection information, ensuring successful and complete metadata crawling. **Resolved Validation Failure for Restricted S3 Permissions** In the Amazon S3 Connector, an issue where connection validation failed when the 'ListAllBuckets' permission was not granted has been resolved. Previously, validation required access to list all buckets, which prevented connections configured with limited bucket-level permissions from being successfully validated. The validation process has been updated to support connections configured with restricted permissions, allowing validation without requiring access to all buckets. ## Data Access Management ### New & Improved **Reuse Snowflake Masking Policies Across Schemas** Snowflake masking policies crawled into the application could previously be associated with terms and applied only to objects within the same schema. Users who wanted to apply an existing masking policy to objects in other schemas encountered limitations and often had to create duplicate policies. With this enhancement, existing crawled masking policies can now be reused across objects in different schemas. Users can associate a masking policy with a term, apply it to objects regardless of their schema, and successfully synchronize the policy changes back to Snowflake. ## Job Workflow ### Fixed **Resolved Connector Schedule Failures in Sequential Workflows** In Job Workflow, an issue where connector schedules failed during sequential execution due to duplicate metric entries has been resolved. Some workflows stopped unexpectedly when multiple connector jobs ran in sequence. The workflow processing has been updated to prevent duplicate entries and ensure scheduled jobs complete successfully. **Fixed Missing Jobs in Weekly Lineage Build Details** In Job Workflow, an issue where the Weekly Lineage Build workflow displayed associated jobs in the workflow list but showed a blank details page has been resolved. The workflow details page did not display the configured jobs, preventing verification of the workflow setup. The issue has been fixed to ensure all associated jobs are displayed correctly in the workflow details page. ## Security ### New & Improved **Break-Glass Access Support with Security Notifications** Users relying on SSO authentication could lose access to the application during identity provider outages or authentication failures, making it difficult for administrators to perform critical tasks. In addition, security-related events such as emergency account usage, repeated failed login attempts, and unauthorized access attempts were not proactively communicated to relevant teams. The system setting 'ovaledge.breakglass.enable' must be set to true to enable the Break-Glass functionality after the upgrade. By default, the value is false. With this enhancement, OvalEdge now supports break-glass access, allowing authorized emergency users to sign in using DB authentication when SSO is unavailable. The platform also sends notifications to the Admin for break-glass account usage, automatic user lockouts due to multiple failed login attempts, and unauthorized access attempts via both DB authentication and SSO. This enhancement helps organizations maintain business continuity during authentication disruptions while improving security monitoring, auditing, and incident response. ## Custom Fields ### Fixed **Resolved Inaccurate Custom Field KPI Counts** In OvalEdgeDB, an issue where cleared custom field values were still stored in the database and counted as populated has been resolved. Although custom fields appeared empty in the application, hidden HTML content was retained in the database, resulting in inaccurate KPI counts. The cleanup process has been updated to completely remove custom field values and related HTML content, ensuring accurate reporting and metrics. ## Audit Trails ### Fixed **Audit Trail Logout Tracking Fix** In Audit Trails, an issue in which logout activities were not recorded on the User Logins page has been resolved. Logout events were missing from audit reports, and exported login reports contained misaligned column headings. The tracking and export processes have been corrected to ensure logout activities are captured accurately and that exported reports display the correct column headings. *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ovaledge.com/hotfix-releases/release7.2.5.x/release7.2.5.19.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.