> 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/release8.2/patch-releases/release8.2.2.md). # Release8.2.2 This release introduces key enhancements and bug fixes across Business Glossary, Data & Metadata Changes, and Connectors, improving governance role inheritance, change tracking, lineage accuracy, connector capabilities, and schema crawling flexibility. **Key Highlights** * **Business Glossary**: Corrected the Published By field and governance role inheritance behavior, ensuring the field remains empty until publication and categories inherit roles defined at the domain level when no roles are assigned. * **Data & Metadata Changes**: Enhanced change tracking with consistent Previous, New, and Change values across data and metadata objects, detailed column-level comparisons, dedicated views for reports, APIs, and codes, improved filtering and navigation, and download options for supported changes. * **Connectors**: Improved Salesforce-to-Tableau lineage by mapping Salesforce Label Names to API Names, introduced a new Salesforce Marketing Cloud connector for Data Extension metadata, and enabled system schemas to be included in crawls through editable schema exclusion rules. * **Change Management:** * **Data & Metadata Changes**: Previously, the module combined OvalEdge-generated metadata with source-system changes and did not consistently provide Previous/New comparisons across Data Changes, Tables, and Codes. Now, the module focuses on source-system changes and provides consistent Previous/New/Change values across tabs, including column-level changes in Table Column for attributes such as Source Description, Data Type, Length, Position, Constraint, and Key. Missing Previous and Change values are displayed as –, and count changes are calculated as New − Previous. **Release Details:**
Release TypeRelease VersionBuild <Release. Build Number. Release Stamp>Build Date
Patch ReleaseRelease8.2.2release8.2.2.822.03010b7September 03, 2026
## Business Glossary ### Fixed **Resolved Published By Field Display Issue** In Business Glossary, an issue where the Published By field was displayed for newly created terms before they were published has been resolved. The field now remains empty until the term is published. **Fixed Governance Role Inheritance in Security Domains** In Security Domains, an issue where categories and subcategories without assigned governance roles inherited Principal Admin roles instead of the governance roles defined at the domain level has been resolved. Categories and subcategories now inherit the governance roles from their parent domain when no roles are specified. ## Data & Metadata Changes ### New & Improved **Enhanced Data & Metadata Changes** The Data & Metadata Changes module now provides a more detailed view of changes between crawls across data and metadata objects. Users can compare previous and new values, identify the change type, and access detailed changes for tables, columns, codes, reports, and APIs. The following enhancements have been implemented: * **Data Changes**: Row Count now includes Previous, New, and Change values, along with Previous and New Profile Dates. * **Table Metadata Changes**: Source Description, Last Crawled Date, Last Meta Sync Date, and Column Count are available as Previous and New values. * **Table Column**: A new Table Column tab provides detailed column changes, including Source Description, Data Type, Length, Position, Constraint, and Key. * **Change Type**: Column changes are identified as Added, Modified, Deleted, or No Change. * **Codes**: Code values are displayed as Previous and New, with Latest Version available for tracking. * **Reports and APIs**: Dedicated views show Report, Report Column, API, and API Attribute changes. * **View Changes**: Dedicated View Column Changes, View Report Column Changes, View API Attribute Changes, and View Code Changes options provide detailed change information. * **Navigation**: Selecting a table, report, or API opens its existing Data Catalog Summary Page. * **Filtering, Searching, and Sorting**: Relevant fields support filtering, searching, or sorting based on the type of information displayed. * **Download**: Download options are available for Table Column, Report Column, and API Attribute changes. * **Previous Values**: A dash (–) is displayed when a previous value is not available. * **Change Calculation**: Row Count and Column Count changes show the difference between the New and Previous values. These enhancements provide a consistent way to compare, review, and download changes across different data and metadata objects. ## Connectors ### New & Improved **Enable Accurate Salesforce-to-Tableau Lineage Using Label Name Mapping** Tableau reports that used Salesforce as a source created temporary lineage when the Tableau XML contained Salesforce Label Names while the Data Catalog identified the same objects using API Names. This mismatch prevented OvalEdge from establishing direct source-to-report lineage and required manual intervention. With this enhancement, the lineage engine can map Salesforce Label Names from Tableau XML to their corresponding API Names in the Data Catalog. This enables accurate object-level Salesforce-to-Tableau lineage, reduces temporary lineage creation, and removes the need to modify individual Tableau reports. **Salesforce Marketing Cloud (SFMC) Connector | New Connector Support** In the Connectors module, a new Salesforce Marketing Cloud (SFMC) connector has been introduced to enable metadata crawling and management of Data Extensions using supported SFMC APIs. The connector supports organizing Data Extensions based on the available SFMC structure and provides streamlined access to supported metadata. However, Query Sheet, Profiling, and Data tab features are not supported for this connector. **Allow Crawling of System Schemas Through Editable Schema Regex** The system schemas such as sys, guest, and INFORMATION\_SCHEMA were automatically excluded from crawling, with no option to include them when required for governance, auditing, lineage, or advanced analysis. With this enhancement, the Exclude Schema Regex in Crawler Settings is pre-populated with the default system schemas but can now be edited. Users can remove specific system schema entries from the exclusion list and re-run the crawl to include the required schemas. ## Change Management ### Data & Metadata Changes * Data & Metadata Changes now provides consolidated source-system change tracking with Previous/New comparisons.

What Changed

In Data & Metadata Changes, previously, the module combined OvalEdge-generated metadata with source-system changes and did not consistently provide Previous/New comparisons. Data Changes, Tables, and Codes displayed a mix of current values and tracked fields, while attributes such as Row Count, Profile Date, Column Count, and column-level changes could not be consistently compared or viewed. A consolidated Table Column view was also unavailable.

Now, the module focuses on source-system changes with consistent Previous/New/Change values across tabs. The Data Changes and Tables tabs provide Previous/New comparisons for relevant attributes, while Table Column provides column-level changes such as Source Description, Data Type, Length, Position, Constraint, and Key. Missing Previous values and corresponding Change values are displayed as –, and count changes are calculated as New − Previous.

Affected Users: Administrators, Authors, Viewers

👉 For more details, see Enhanced Data & Metadata Changes

*** 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/release8.2/patch-releases/release8.2.2.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.