> 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.15.md). # Release7.2.5.15 This release introduces bug fixes across Data Catalog, Business Glossary, Service Desk, Security, and Connectors. **Key Highlights** * **Data Catalog:** Improved readability in Business Description and Technical Description fields by updating the default font size from 12 to 16. * **Business Glossary:** Fixed the issue where images were not getting deleted from the Manage Image popup after confirmation. * **Service Desk** * Strengthened Service Desk access controls to prevent unauthorized access to restricted tickets and comments. * **Security** * Enhanced Question Wall authorization controls to restrict unauthorized access to discussions and collaboration content. * **Connectors** * Improved Greenplum connection handling to properly release idle sessions and prevent database connection exhaustion. * **QlikSense** * Enhanced QlikSense lineage parsing to correctly generate upstream lineage and avoid temporary or failed lineage states. * Fixed QlikSense Metadata Export Service Advanced Job to retrieve complete and accurate metadata information from the QlikSense server. **Release Details:**
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.15Release7.2.5.15.72515d99c868May 22, 2026
## Data Catalog ### Fixed **Resolved Small Default Font Size in Business and Technical Descriptions** In Data Catalog, an issue where the default font size for Business Description and Technical Description fields appeared too small has been resolved. Previously, the text editor used a default font size of 12, which reduced readability while viewing or editing descriptions. The default font size has now been updated to 16 to improve readability and provide a more consistent user experience across description fields. ## Business Glossary ### Fixed **Resolved Image Deletion Issue and Manage Image Popup** In Business Glossary, an issue where users could not delete images from the Manage Image pop-up has been resolved. Previously, when users attempted to delete an image from the Business Description section of a glossary term, a confirmation pop-up appeared, but the image remained visible in the Manage Image tab. The image deletion functionality has now been corrected to properly remove images from the Manage Image popup and to refresh the image list after deletion. ## Service Desk ### Fixed **Resolved Access Control Issues** In Service Desk, security issues related to unauthorized access to tickets and comments have been resolved. Previously, users without appropriate permissions could access or interact with restricted Service Desk tickets and comments in certain scenarios. Access control validation has now been strengthened for all ticket-related operations. Users can access and interact only with tickets and comments for which they have explicit permissions. Unauthorized access requests are now blocked by default. ## Security ### Fixed **Resolved Unauthorized Access to Question Wall Discussions** In Question Wall, security vulnerabilities related to unauthorized access to collaboration discussions and comments have been resolved. Previously, users could access restricted Question Wall conversations through direct requests in certain scenarios Authorization controls have now been strengthened to ensure users can access discussions, comments, and collaboration content only for objects they are authorized to view. ## Connectors ### Fixed **Resolved Idle Connection Accumulation in Greenplum Connections** In Greenplum connections, an issue where idle database sessions were not released properly after metadata crawl, profiling, and reporting operations has been resolved. OvalEdge accumulated a large number of idle Greenplum connections, which exhausted database connection limits and prevented new client connections. The connection handling logic has been improved to properly release idle sessions after execution. This prevents unnecessary accumulation of database connections, improves connection stability, and reduces the risk of exhausting connection limits. **Resolved QlikSense Temp Lineage Status and Missing Upstream Lineage** In QlikSense lineage processing, an issue where several QlikSense codes were built with the status “Success Temp Lineage” has been resolved. Previously, some SQL queries failed to parse, while others appeared empty in the Correct/View Query section. Due to these parsing inconsistencies, the upstream lineage was not generated correctly for the affected Qlik Sense dashboards and code. The lineage parsing logic has now been improved to correctly parse Qlik Sense SQL queries and scripts. Upstream lineage is now generated accurately, and query parsing statuses are displayed consistently, with no empty or failed states for supported queries. **Resolved Incomplete Metadata Retrieval in the QlikSense Metadata Export Service Advanced Job** In the QlikSense Advanced Jobs, an issue where the Metadata Export Service did not fetch complete or expected metadata information from the QlikSense server has been resolved. Previously, the advanced job completed successfully, but the exported metadata returned inaccurate or incomplete information from the server. The metadata retrieval logic has now been improved to correctly fetch and process metadata information from the Qlik Sense server during Advanced Job execution. *** 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.15.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.