> 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.3.x/release7.2.3.1.md). # Release7.2.3.1 This release introduces key enhancements across Data Catalog, Advanced Tools, Service Desk, Governance App, and Connectors, improving recommendations, metadata stability, approvals, configuration access, and Amazon S3 cataloging. **Key Highlights** * **Data Catalog**: Resolved an issue preventing recommendations when domains were selected, ensuring accurate suggestions based on domain terms. * **Data Catalog Rules**: Resolved incorrect term-level include and exclude handling, delivering precise recommendations as per configured rules. * **Advanced Tools (LMDF)**: Resolved memory failures during metadata updates, enabling stable processing for large-scale schema loads. * **Service Desk**: Resolved missing results in the Waiting for My Approval view when filtering by Status, ensuring proper approval visibility. * **Governance App:** Resolved configuration screen load failure by restoring required styling, enabling governance app setup access. * **Amazon S3 Cataloging**: Resolved incomplete subfolder cataloging and missing logs, ensuring full subfolder processing with traceable job logs. * **Amazon S3 Profiling**: Resolved profiling failure in Profile Folder Assuming Same Content due to endpoint mismatch, enabling successful profiling and data update. **Release Details:**
Release Type Release VersionBuild <Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.3.1Release7.2.3.1.72317688c725th Nov 2025
## Data Catalog ### Fixed **Data Catalog Recommendations | Domain Selection** In the **Data Catalog Recommendations (DCR)** module, recommendations failed to generate for tables when a domain was selected in the model configuration, even when table names matched terms in the selected domain. The issue has been resolved, and the recommendation engine now correctly identifies and recommends objects based on defined domain terms. **Term Level Include and Exclude Rules** In the **Data Catalog Recommendations** module, term-based include and exclude expressions were not applied as configured due to an incorrect internal request handling. The issue has been resolved, ensuring accurate recommendation results based on the defined rules. ## Advanced Tools ### New & Improved **LMDF | Memory Issue During Schema Updates** In the **Load Metadata Definition Framework** module, the metadata update job failed due to excessive memory consumption caused by loading all reference metadata at once. The issue has been resolved, enabling successful metadata updates and stable execution for large workloads. ## Service Desk ### Fixed **Error When Using Status Filter in Approval List** In the **Service Desk** module, the Waiting for My Approval section failed to display data after applying the Status filter due to a missing SQL join in the query. The issue has been resolved, and filtered results now appear correctly when using the Status filter. ## Governance App ### Fixed **Unable to Configure Governance Applications** In the **Governance App** module, configuration screens did not load after application creation because a stylesheet reference was missing. The issue has been resolved, restoring access to the configuration interface for governance applications. ## Connectors ### Fixed **Amazon S3 | Catalog All Subfolders Action Not Working** In **Amazon S3**, the Catalog All Subfolders option triggered the job but did not catalog subfolders or record folder paths in Job Logs because the path-tracking logic was missing. The issue has been resolved, and the action now catalogs all subfolders and logs folder paths and progress details. **Amazon S3 | Profile Folder** In **Amazon S3**, the Profile Folder Assuming Same Content action failed during the initial file check because the configured region's endpoint was not handled correctly. The issue has been resolved, enabling successful profiling, accurate file detection, and correct job status updates. *** Copyright © 2025, 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.3.x/release7.2.3.1.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.