> 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/release7.2/hotfix-releases/release7.2.5.x/release7.2.5.3.md). # Release7.2.5.3 This release introduces fixes across the Query Sheet, Lineage, Data Quality, Advanced Jobs, Jobs, Service Desk, and Impact Analysis modules. These updates improve navigation behavior, ensure stable job execution, enhance API functionality, and provide reliable processing across modules. **Key Highlights** * **Query History Navigation Issue**\ Resolved navigation behavior in the Query History window and ensured smooth horizontal scrolling. * **Lineage Job Stability and Performance**\ Improved lineage processing speed, resolves long-running job status, and ensures successful lineage build for multiple scenarios. * **Data Quality, Contact Management, and API Improvements**\ Restored contact update functionality for active rules and enhanced API filtering and data retrieval capability. * **Job Execution and File Download Reliability**\ Fixed job execution issues after migration and ensured successful file download from job results without errors. * **Service Desk Notification Behavior**\ Ensured approval notifications trigger correctly after governance role updates. * **Impact Analysis Path Visibility**\ Restored visibility of path information in impact analysis results. **Release Details:**
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.3Release7.2.5.3.72536c3ec0e27th Feb 2026
## Query Sheet ### Fixed **Query History Navigation Arrow** In the Query Sheet module, the left navigation arrow in the Query History window was not working, while the right arrow worked as expected. This affected horizontal navigation in the history view. The issue has been resolved, and both navigation arrows now work correctly. ## Lineage ### Fixed **Performance Delay During Lineage Build** In the Lineage module, the lineage build took more time than expected due to slow processing, which caused long-running jobs. The issue has been resolved, and lineage build now completes faster with stable job execution. **Build Lineage Job Stuck in Running Status** In the Lineage module, the build lineage job remained in running status for a long time due to processing issues. The issue has been resolved, and lineage jobs are now complete successfully without remaining in running status. **Memory Error During Lineage Build for Multiple Codes** In the Lineage module, lineage build failed with memory errors when multiple codes were processed together. The issue has been resolved, and lineage now builds successfully for multiple codes. ## Data Quality ### Fixed **Add Contacts Disabled for Active Rule** In the Data Quality module, the add contacts option was disabled when a rule was active, which required additional steps to update contacts. The issue has been resolved, and contacts can now be added and modified regardless of rule status. **Additional Condition Support in Bulk API** In the Data Quality module, the bulk API supported limited condition options for the update date field, which restricted filtering flexibility. The issue has been resolved, and the API now supports extended conditions for improved data retrieval control. **Delta Load Support in Bulk API** In the Data Quality module, the bulk API did not support delta retrieval based on modification date, which limited selective data extraction. The issue has been resolved, and the API now enables efficient delta data extraction for integration scenarios. ## Advanced Jobs ### Fixed **Generate Identifier Job Execution and Log Download** In the Advanced Jobs module, the identifier generation job failed after environment migration, and job logs could not be downloaded even though the download process was initiated. The issue has been resolved, and now the job executes successfully and logs downloads correctly without errors. ## Jobs ### Fixed **Download Hyperlink Error After Job Completion** In the Jobs module, clicking the download link after job completion redirected to an error page due to an invalid path format, and the file was not downloaded from the application. The issue has been resolved, and files now download successfully from the job completion screen without any error. ## Service Desk ### Fixed **Trigger Notification After Governance Role Update** In the Service Desk module, updating governance roles on an object did not trigger approval notifications for newly assigned approvers in related service requests. The issue has been resolved, and approval notifications now trigger correctly when governance roles are updated. ## Impact Analysis ### Fixed **Path Information in Impact Results** In the Impact Analysis module, path information for impacted objects was not visible after running the analysis, even though the system processed the path information. The issue has been resolved, and path information now appears correctly in the Configure View. *** 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/release7.2/hotfix-releases/release7.2.5.x/release7.2.5.3.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.