> 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/minor-release/release7.2.md).
# Release7.2
OvalEdge **Release7.2** delivers significant enhancements across the application, focusing on usability, governance, and performance.
### Key Highlights
* **Login & Security**
* Restriction on concurrent logins for better account security.
* End User License Agreement (EULA) pop-up disabled in production environments.
* **Home & Navigation**
* Customizable homepage widgets, announcement banners, and personalized layouts.
* Improved first-login experience with actionable inbox pop-ups.
* **Browser Extension**
* Guest user login for external stakeholders with secure domain restrictions.
* Enhanced visibility of reports, datasets, steward information, and audit logs.
* **Tags & Business Glossary**
* Master Tags hierarchy and secure governance with role-based access.
* Improved filtering, cascade tagging, and glossary role updates across terms.
* **Data Catalog & Lineage**
* Toggle between summary and detailed lineage views.
* Column-level transformation visibility and Critical Data Element recommendations.
* Improved lineage graph readability and new attributes for source identification.
* **Service Desk**
* Configurable templates with rich-text formatting, ticket integrations (Jira, ServiceNow, Azure DevOps).
* Draft versions for templates, file upload fields, configurable views, and SLA enhancements.
* **Data Quality**
* Row-based scoring for accuracy, incremental rule execution, and UDF remediation support.
* Expanded coverage with BOX connector support (BETA) and standardized file functions.
* **New Modules**
* **Policy Manager** for managing and enforcing data policies.
* Enhanced **GDPR ROPA** with alerts, customizable attributes, and compliance tracking.
* **Connectors**
* Extended support for SharePoint Lists, Delta Lake, and DBT Cloud.
* Connector health checks, license tracking improvements, and role-based authentication for AWS.
* **Dashboards & Projects**
* Enhanced Data Quality Scoreboards and execution reports.
* Auto-assignment of tasks, custom priority labels, and improved project workflows.
* **Other Enhancements**
* Schema comparison, history, and scheduling.
* Impact analysis with version comparisons.
* Advanced jobs for migration, lineage building, and metadata sync.
* Improved role management, user-role transfers, and advanced job utilities.
### Release Details:
| Release Type | Release Version | Build <Release. Build Number. Release Stamp> | Build Date |
|---|
| Minor Release | Release7.2 | Release7.2.7200.b97830f | 19 August, 2025 |
### **Release Trailer:**
Discover the key highlights of **OvalEdge Release7.2** through our trailer. This quick walkthrough showcases the major enhancements in usability, governance, performance, and other improvements across the application.
{% embed url="" %}
***
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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ovaledge.com/release7.2/minor-release/release7.2.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.