> 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.25.md). # Release7.2.5.25 This release introduces key enhancements across Reference Data Management, Connectors, and System Settings, improving reference data governance, metadata visibility, DBT project cataloging, and Splunk logging and error handling. **Key Highlights** * **Reference Data Management**: Expanded RDU descriptions to 100,000 characters, added tag management and governance role visibility, and introduced approval workflows to support controlled curation and publication of Reference Data Units. * **Connectors (Snowflake)**: Added support for crawling DBT projects from Snowflake, enabling DBT project definitions and manifest content to be cataloged as Code Objects for improved transformation and lineage visibility. * **System Settings (Splunk)**: Enhanced Splunk integration with clearer server identification, structured logging, improved activity capture, and more specific connection error messages for better monitoring and troubleshooting. **Release Details:**
Release TypeRelease VersionBuild<Release. Build Number. Release Stamp>Build Date
Hotfix ReleaseRelease7.2.5.25release7.2.5.25.72525.7e2f6e3August 19, 2026
## Reference Data Management ### New & Improved **Increased Character Limit for RDM Descriptions** The RDM Description field allowed a maximum of 10,000 characters. This limit made it difficult to add detailed descriptions, especially when the description contained the same level of information supported in Terms and Data Catalog descriptions. With this enhancement, the RDM Description field now supports up to 100,000 characters, aligning the limit with other description fields across the platform. **Tag Management for Reference Data Units** Users could not assign or view tags assigned to a Reference Data Unit from the Reference Data Unit (RDU) Summary or List pages. This made it difficult to manage and identify tagged RDUs without navigating to other areas of the application. With this enhancement, users can now assign one or more tags to an RDU directly from the RDU Summary or RDU List page. Assigned tags are immediately reflected across both views, and users can view the tags associated with each RDU. **Governance Roles Now Available for Reference Data Units** The Reference Data Unit (RDU) Summary page displayed only the Top Users section and did not provide a dedicated view of the users assigned to governance roles. This made it difficult to identify the Owner and Steward responsible for an RDU. With this enhancement, the RDU Summary page now includes a Governance Roles section that displays the assigned Owner and Steward. The RDU List page also maintains the same role information for consistency. **Approval Workflow and Draft/Publish Status for Reference Data Units** Reference Data Units (RDUs) lacked a defined workflow or status to indicate whether their content was still being updated or officially published. Any user could make changes to an RDU, which could lead to inconsistent content and affect the stability of published data. With this enhancement, RDUs now follow a three-stage workflow: Draft, Request to Publish, and Published. Newly created RDUs start in Draft, where users can make and review changes. When the content is ready, authorized users can publish the RDU directly or submit a Request to Publish through the Service Desk workflow for approval. Once published, the RDU is locked for changes and must be moved back to Draft before making any revisions. ## Connectors ### New & Improved Support Crawling DBT Projects from Snowflake The Snowflake connector did not identify or catalog DBT projects, making DBT project definitions unavailable in the Data Catalog and limiting visibility into transformation logic and lineage. With this enhancement, the Snowflake connector now includes a new DBT Projects crawl option. When enabled, OvalEdge discovers DBT projects, retrieves their manifest.json files, and catalogs each project as a Code Object with its manifest content. ## System Settings ### New & Improved Enhanced Splunk Integration for Better Logging and Error Handling The Splunk integration did not clearly identify the selected server in OvalEdge logs, and Splunk logs were displayed in a single-line format. Some activities, such as deleting Data Quality Rules or Business Glossary entries, were also not captured, while different connection issues displayed the same generic error message. With these enhancements, OvalEdge logs now provide server details during connection testing, and Splunk logs include clearer information such as the user and activity timestamp. Missing activities are now captured, and connection errors provide more specific messages based on the issue. *** 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.25.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.