> 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/minor-release/release8.2.md). # Release8.2 The OvalEdge **Release8.2** introduces enhancements across askEdgi, metadata governance, Data Products, Data Quality, lineage, connectors, and job management, while improving usability, performance, and operational visibility. The release also includes new governance capabilities, AI-powered lineage enhancements, expanded metadata management features, and numerous bug fixes to deliver a more reliable and efficient user experience. ## Key Highlights ### askEdgi * Introduced **Recipe as a Product (RaaP)** with parameterized recipes, enabling reusable and governed analytical workflows across multiple business scenarios. * Enhanced workspace data management with automatic **dataset reload**, improved retention controls, and protection for workspace-generated assets. * Added **@Mention-based** contextual references for datasets, glossary terms, data products, files, live tables, and other governed assets. * Added **Thumbs Up / Thumbs Down** feedback capabilities to capture user feedback and support metadata improvement initiatives. * Introduced **AI Data Sharing Controls** to govern the use of physical data in external AI-powered analysis and enrichment workflows. * Implemented a system-wide workspace **purge policy** to improve storage management while preserving metadata, conversations, and object references. * Added **automated AI generation** of Recipe names, descriptions, and step descriptions to simplify recipe creation. * Enabled automatic persistence of recipe-generated tables with dedicated **workspace folders** and improved output traceability. * Introduced **Natural Language Code Editor**, allowing users to modify analytical logic using plain language instead of editing SQL or Python code directly. * Added **Data Cleanup Execution** capabilities to resolve legacy data quality issues directly from askEdgi workspaces. * Added a new **Recipe Execution Framework** with inline execution, execution history, dependency validation, and output review within askEdgi and Studio. * Expanded **RAG coverage across additional OvalEdge assets**, including Data Products, Reports, APIs, Projects, Columns, Data Stories, and governance objects. * Improved asset discovery accuracy using column-level Business Glossary associations and glossary-driven query generation. * Strengthened the agent framework architecture with specialized planning, discovery, and coding agents for improved analysis accuracy and reliability. * Revamped the Recipes experience and **My Recipes** pages for Enterprise and Marketplace users with simplified navigation, management, and publishing workflows. * Improved workspace object status validation to ensure assets are marked as added only after successful processing and workspace synchronization. ### Browser Extension * Enhanced the issue reporting experience with clearer navigation labels, automatic URL capture, and image attachment support for faster and more effective issue resolution. ### Global Search * Improved filter usability by correctly grouping tags under Tag filters and ensuring governance role filters follow configured system settings. ### Tags * Added the ability to clone existing Tags and Terms, enabling users to reuse descriptions, governance roles, custom fields, and settings while maintaining independent relationships. Also fixed misleading success messages to accurately reflect permission-based actions. ### Data Catalog * Expanded empty value filtering to additional metadata fields, enabling users to quickly identify objects with missing information across custom fields, classifications, CDE attributes, table columns, files, reports, code objects, and API attributes. * Enabled connector references in descriptions and Data Stories using @ mentions, allowing users to include source system information and navigate directly to connector details. * Standardized the display order of governance roles across the application to consistently follow Owner → Steward → Custodian, improving readability and usability. * Restored team member visibility by allowing users to select governance teams and view their assigned members directly from governance role sections. * Standardized date handling to ensure date formats are displayed consistently across the application and downloaded files. ### Data Products * Added administrator-configurable Featured Tags to the Marketplace, making it easier for users to discover relevant Data Products through curated filters. * Improved governance role inheritance and cascading by automatically populating Data Domain governance roles during Data Product creation and enabling role updates across existing products. * Enhanced subscription visibility and navigation by displaying subscription dates, introducing Marketplace navigation shortcuts, and renaming Access Mode to Availability. * Introduced Metadata Access as a new delivery mode, allowing organizations to share metadata and access instructions without exposing sample or full data. * Introduced draft versioning for published Data Products, allowing owners to update products without affecting consumer access, while adding automated notifications for key lifecycle events such as publishing, republishing, unpublishing, archiving, subscription expiry, auto-expiry, and delivery access mode changes. * Added configurable Sensitivity and Criticality values, enabling organizations to align classifications with internal standards. * Introduced approval-based Data Product requests, providing a governed process for users to request new Data Products directly from the Marketplace. * Added inline editing for Delivery Access Mode and Status in the Data Product List View, while expanding advanced filtering across additional columns with options such as Equals to Any of, Equals to All of, Not Equals to Any of, and Not Equals to All of, enabling faster updates and more precise Data Product searches. * Introduced dedicated governance role management for Data Products under Security settings, allowing administrators to control role availability and visibility. ### Business Glossary * Introduced support for referencing Business Glossary terms within Reference Data Management using rich text annotations to improve metadata consistency and reduce manual effort. ### ROPA Reports * Added filter labels to ROPA Reports to provide visibility into active filters and enable users to remove individual filters or clear all filters directly from the report view. ### Reference Data Management * Enabled direct association of Reference Data Management (RDM) objects with Business Glossary terms, improving access to authoritative reference data and reducing manual maintenance. ### Data Quality * Introduced a new Warn severity level with configurable thresholds, alerting, and remediation tracking to proactively identify borderline data quality issues and prioritize remediation efforts. * Enhanced the Data Quality Rule Summary → References tab to display associated Business Glossary terms, improving visibility and traceability between business definitions and Data Quality Rules. * Improved the LMDF → Download Data Quality Rules functionality to eliminate duplicate entries for rules associated with multiple objects and align the downloaded rule count. * Introduced an overall Data Quality index in the Last Execution Dashboard to provide centralized visibility into Data Quality performance across all rules. * All Data Quality Service Requests associated with an object, including manually reported issues, are now displayed in the Object Dashboard, providing a consolidated view of data quality remediation activities. ### Data Stories * Introduced the ability to download Data Stories as PDF files, making it easier to save, share, print, and access stories outside the application. ### Question Wall * Introduced drag-and-drop reordering for Community Rooms and Walls, enabling users to personalize their navigation experience without affecting other users. * Improved room visibility by categorizing Community Rooms based on their functionality and adding descriptive help text to help users identify the appropriate room more easily. ### File Manager * Introduced configurable file upload size limits of up to 100 MB, enabling larger file onboarding across all supported File Manager upload interfaces. ### Query Sheet * Enhanced auto-mode processing to automatically skip excessively large columns during execution, reducing processing overhead and improving query performance. * Added the ability to copy column names directly from query results, eliminating the need to download the entire result set when only column names are required. * Fixed execution failures for supported internal metadata table queries, such as oecolumn, ensuring existing data quality metric queries run successfully after migration. ### Jobs * Renamed the Jobs Load section to Jobs Queue Trend, added initialization time filtering, and introduced a Total Jobs column to provide better visibility into job processing trends. * Added an Execution Date filter to applicable job list pages, enabling users to quickly locate jobs executed within a specified time range. * Introduced configurable execution rules to control concurrent job processing, allowing jobs to run sequentially, simultaneously, or with restrictions based on dependencies and potential conflicts. * Enhanced visibility of Connector Health processing by running it as a monitorable background job, enabling users to track execution status, failures, and runtime behavior directly from the Jobs page. * Resolved an issue where crawling, profiling, and data quality jobs became stuck during Bridge activity, ensuring more reliable and uninterrupted job execution. ### Job Workflow * Fixed inaccurate health time calculations for Advanced Jobs, ensuring execution duration is correctly displayed from the moment a job starts. ### Advanced Jobs * Enhanced lineage parsing error handling by categorizing failures and replacing raw technical exceptions with user-friendly messages, while preserving access to detailed troubleshooting information and improving visibility into migration-related issues. ### Load Metadata from Files (LMDF) * Expanded the supported object types in the Sections tab to include Projects, Project Tasks, and Data Quality Schemes, allowing users to view and select these objects when preparing LMDF templates for bulk metadata uploads. ### Security * Introduced a new Masking Policies Associations view to provide centralized visibility into masking policy relationships, authorization details, and policy usage across data objects. ### Custom Fields * Added Rich Text Editor support for custom text fields, allowing users to apply formatting, create lists, and embed images and videos directly within custom sections for richer and more structured documentation. ### Lineage * Added connector name visibility for BUILD\_LINEAGE jobs, making it easier to identify the source connector associated with lineage processing. * Expanded manual lineage Association support to include Procedures, Functions, Views, and Triggers, enabling broader relationship mapping and impact analysis. * Introduced AI-augmented lineage generation for Azure Data Factory pipelines, improving automated dependency discovery across pipeline activities, transformations, and dynamic configurations. * Standardized lineage status messages across lineage execution scenarios, providing more consistent and meaningful status reporting. * Enhanced lineage parsing error handling by replacing raw technical messages with categorized error buckets and detailed error views for easier troubleshooting. * Improved lineage visibility and relationship coverage through expanded object associations and more comprehensive dependency mapping capabilities. * Simplified lineage job monitoring and operational analysis with clearer lineage execution identification and standardized status representation. * Improved user experience for lineage error investigation by providing structured, user-friendly error categorization while retaining access to detailed technical information when required. ### Connectors * Introduced the **Microsoft Fabric OneLake** connector to retrieve metadata from Microsoft Fabric workspaces, Lakehouses, folders, and supported file formats, with support for crawling, sample profiling, data preview, manual lineage, and Data Quality. * Enhanced **Bridge Status** monitoring with standardized statuses, heartbeat-based health tracking, restart and update lifecycle visibility, failure reporting, recovery tracking, and improved operational observability. * Standardized **Data Profiling** by fully adopting batch profiling as the default execution framework and retiring the legacy profiling flow. * Improved **Amazon QuickSight** crawl logging by eliminating unnecessary dataset crawl messages and reducing non-actionable log entries. * Enhanced **RDBMS Profiling** to capture Row Count and Null Count metrics for columns excluded from detailed profiling. * Added Draft Save support for connector configurations, allowing incomplete connector setups to be saved and resumed later. * Improved **AWS connector** performance and scalability through connection pooling and optimized connection management. * Added advanced filtering capabilities for Saved Connectors to simplify connector discovery and administration. * Enhanced **Salesforce** metadata visibility by exposing Picklist Values and Validation Rules within the Data Catalog. * Extended **Qlik Cloud** Connector support with Azure Blob Storage-based QVD ingestion and lineage generation. * Enhanced **Azure Data Factory** lineage extraction using AI-driven pipeline interpretation and automated relationship generation. * Improved lineage execution traceability by introducing Start Date and Job ID tracking in the Build Lineage interface. * Introduced a unified Connectors Master Page to provide centralized visibility into connector capabilities and supported features. * Added UI-based bridge management capabilities, including controlled deletion of inactive bridges with validation checks. * Enhanced **IBM Cognos** report curation with improved semantic model handling, metadata representation, and lineage consistency. * Standardized connector object classification through Primary Object support in connector SDK manifests. * Introduced Template Management for AI prompt and code template configuration used in lineage extraction workflows. * Strengthened connector security by enforcing authentication validation during permission mode changes. * Improved Python lineage extraction accuracy through enhanced AI-based parsing and structured lineage generation. * Resolved GreenPlum external table profiling limitations to improve profiling reliability and execution stability. * Added audit tracking for connector rename activities, including user, timestamp, and change history details. ### Release Details:
Release Type Release VersionBuild <Release. Build Number. Release Stamp>Build Date
Minor ReleaseRelease8.2Release8.2.82.4221b3e28 July, 2026
*** 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/minor-release/release8.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.