> 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.23.md). # Release7.2.5.23 This release introduces key enhancements and bug fixes across Data Catalog, Business Glossary, Data Quality, Service Desk, Connectors, Data Access Management, and Advanced Jobs, improving navigation, data accuracy, notification reliability, connector visibility, and large-scale metadata processing. **Key Highlights** * **Data Catalog**: Fixed query links in the Entity Relationships tabular view, ensuring cataloged queries open correctly from relationship records. * **Business Glossary**: Corrected the Tree View pagination logic to prevent duplicate glossary terms when loading additional entries. * **Data Quality**: Fixed incorrect job statuses after bridge outages, ensuring successfully completed Data Quality jobs are accurately reflected in the execution history. * **Service Desk**: Resolved the SLA notification redirect issue, ensuring email links open the correct pending service request for faster action. * **Connectors** * **DBT Core**: Fixed source code visibility in column lineage and sub-query views, ensuring related SQL is displayed correctly. * **Oracle**: Fixed schema crawling failures caused by long metadata values by improving metadata handling, ensuring successful crawling even when metadata exceeds the previously supported column length. * **Data Access Management**: Resolved an issue where newly created Snowflake connectors were not displayed, ensuring connectors appear correctly after creation. * **Advanced Jobs (QlikSense Metadata Export Service)**: Enhanced large-scale report export reliability by introducing automatic retries for failed reports, configurable connection delays, and a detailed execution summary with processed, successful, failed, retried, and skipped report counts. **Release Details:**
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.23release7.2.5.23.725239aa7c9eJuly 28, 2026
## Data Catalog ### Fixed **Fixed Query Links in Entity Relationships Tabular View** In the Data Catalog | Entity Relationships Tabular View, an issue where links to cataloged queries from the tabular view (Relationship Code column) did not open correctly has been resolved. The query links generated incomplete URLs, preventing access to the related query. The link generation has been corrected to ensure cataloged queries open successfully from the Entity Relationships tabular view. ## Business Glossary ### Fixed **Fixed Load More Issue in Business Glossary Tree View** In Business Glossary, an issue where selecting Load More in the Tree View displayed duplicate glossary terms instead of loading the next set of terms has been resolved. The pagination logic has been corrected to load the next batch of glossary terms, preventing duplicate entries in the Tree View. ## Data Quality ### Fixed **Fixed Incorrect Job Status After Bridge Outage** In Data Quality, an issue where scheduled Data Quality jobs were marked as Not Executed after resuming from a bridge outage, even though the jobs completed successfully, has been resolved. The execution status now updates correctly after bridge recovery, ensuring completed jobs are accurately reflected in the Data Quality rule execution history. ## Service Desk ### Fixed **Resolved SLA Notification Redirect Issue** In Service Desk, an issue where the SLA Expired link in email notifications opened a blank or generic Service Desk page instead of the related service request has been resolved. The link now opens the correct pending service request, making it easier to review and take the required action. Additionally, service requests are displayed correctly when opening the page from the notification link. ## Connectors ### Fixed **Resolved Source Code Visibility in DBT Core Connector** In the DBT Core Connector, an issue where source code was not displayed correctly from the column lineage view and sub-query code page has been resolved. The related SQL code was missing or did not load as expected when viewing lineage details. The source code display has been corrected to show the appropriate SQL for both column lineage and sub-query views. **Fixed Oracle Schema Crawling for Long Metadata Values** In Oracle Connector, an issue where schema crawling failed because some metadata values exceeded the supported column length has been resolved. The metadata handling has been updated to correctly process longer values, allowing schema crawling to complete successfully. ## Data Access Management ### Fixed **Resolved Snowflake Connector Display Issue** In Data Access Management, an issue where newly created Snowflake connectors did not appear in the Data Access Management screen after successful creation has been resolved. The connector was created successfully and assigned the required permissions, but it was not displayed under the associated instance. The display logic has been corrected to ensure newly created Snowflake connectors appear correctly in the Data Access Management screen. ## Advanced Jobs ### New & Improved **Improved Reliability for Qlik Sense Metadata Export Service** The "QlikSense Metadata Export Service" Advanced Job failed when processing a large number of reports in a stream. In some cases, only a few reports were exported successfully, and the remaining reports failed due to application loading and session-related issues, requiring users to rerun the job for the entire stream. With this enhancement, the Advanced Job now retries only the reports that fail, supports additional retry attempts, introduces a configurable delay before establishing the connection, and provides a detailed execution summary with processed, successful, failed, retried, and skipped reports. *** 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.23.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.