> 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/patch-releases/release8.2.6.md).

# Release8.2.6

This release includes key bug fixes and enhancements across Data Catalog, Data Access Management, Lineage, APIs, Administration, and Data Quality, improving lineage generation, masking policy assignment, connector management, API usability, scheduled job execution, and Data Quality monitoring.

### **Key Highlights**

* Data Access Management:
  * Fixed business glossary term publishing with masking policies linked to connector objects.
  * Resolved connector deletion failures when disabling lineage.
* Lineage:
  * Introduced lineage generation from XMLA files for on-premises assets, including temporary lineage when source or target objects are not crawled in OvalEdge.
  * Fixed Power BI lineage resolution to existing Azure Synapse objects.
  * Resolved temporary lineage generation for Tableau assets connected to Salesforce.
* APIs:
  * Removed the AI Functions API from Swagger to prevent unintended external usage and ensure that only APIs intended for external integration are exposed.
* Administration:
  * Introduced execution time restrictions for scheduled jobs to prevent delays in the job queue.
* Data Quality:
  * Fixed scheduled Data Quality Rules execution for rules associated with active user accounts.
  * Enabled importing and monitoring DBT Data Quality Rules and their execution results in OvalEdge.

### **Release Details:**

<table><thead><tr><th width="156.1983642578125" align="center">Release Type</th><th width="127.25921630859375" align="center">Release Version</th><th width="321.4815673828125" align="center">Build &#x3C;Release. Build Number. Release Stamp></th><th width="168.04248046875" align="center">Build Date</th></tr></thead><tbody><tr><td align="center">Patch Release</td><td align="center">Release8.2.6</td><td align="center">release8.2.6.826.38494f6</td><td align="center">October 28, 2026</td></tr></tbody></table>

## Data Access Management

### Fixed

**Masking Policies | Term Publishing and Security Policy Assignment**

In Data Access Management, publishing business glossary terms with masking policies linked to connector objects failed due to issues with role mapping and SQL generation. The issue has been resolved, and now masking policies can be created in Snowflake and business glossary terms can be published successfully.

**Connector Deletion | Lineage**

In Data Access Management, users could not delete a connector to disable lineage when connector settings were configured. The issue has been resolved, and now users can delete the connector successfully to disable lineage.

## Lineage

### New & Improved

**Lineage from XMLA Files**

In the Data Catalog, lineage for On-Prem assets was not available from XMLA files to identify the sources and targets of tables. The enhancement has been implemented, and now lineage can be built from XMLA files, with temporary lineage created when source or target objects are not crawled in OvalEdge.

### Fixed

**Power BI | Lineage Resolution to Existing Azure Synapse Objects**

In the Lineage module, Power BI lineage used temporary source objects even when the corresponding Azure Synapse objects were available in the Data Catalog, resulting in duplicate representations. The issue has been resolved, and now lineage links to the existing Azure Synapse objects when matching cataloged objects are available, reducing duplicate representations.

**Tableau | Temporary Lineage for Salesforce Assets**

In the Lineage module, Tableau lineage continued to generate temporary objects for Salesforce assets instead of resolving the corresponding Salesforce objects and fields. The issue has been resolved, and now Tableau lineage resolves Salesforce sources to the corresponding objects and fields when matching metadata is available.

## APIs

### New & Improved

**AI Functions API | Restricted API Visibility in Swagger**

In the OvalEdge API, the AI Functions API was listed in Swagger and was accessible for review and testing. However, the API does not serve a defined external use case and is not intended for external integration. To avoid confusion and prevent unintended usage, the AI Functions API has been hidden from Swagger. This ensures that only APIs intended for external use are available for review and testing.

## Administration

### New & Improved

**Scheduled Jobs | Execution Time Restrictions**

In Job Management, scheduled jobs could continue executing beyond the intended time window, causing delayed jobs to occupy the job queue and interfere with other application activities. The enhancement has been implemented, and now administrators can configure execution time restrictions for individual scheduled jobs to prevent them from running beyond the configured cutoff time. Jobs without configured restrictions retain their existing scheduling behavior.

## Data Quality

### New & Improved

**DBT Integration | Import Data Quality Rules and Execution Results**

In Data Quality, DBT Data Quality Rules and their execution results were not available in OvalEdge for monitoring. The enhancement has been implemented, and now OvalEdge imports DBT Data Quality Rules and their execution results, allowing users to view and monitor results in OvalEdge while DBT continues to run the tests.

### Fixed

**Scheduled Data Quality Rules | Execution According to Configured Schedules**

In Data Quality, scheduled Data Quality Rules did not execute according to their configured schedules when the associated job owner usernames were inactive or unavailable. The issue has been resolved, and now scheduled rules execute according to their configured schedules when associated with active user accounts.

***

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 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/patch-releases/release8.2.6.md?ask=<question>&goal=<user_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.
