Release7.2.2

OvalEdge Release7.2.2 is a service release that introduces improvements to notifications, data cataloging, data quality, query management, connectors, service desk integration, and system settings. It also strengthens lineage building, job monitoring, and API error handling while simplifying audit data archival.

Key Highlights:

• Notifications: Configurable templates with event-based subjects and global email footers.

• Data Catalog: Support for schema references, script uploads (.py/.sql), tag references in descriptions, and filtered profiling for large datasets.

• Data Quality: Concise, performance-optimized rule notifications with optional detailed reports.

• Query Sheet: Read-only access enabled to restrict data modification.

• Jobs & Lineage: Alerts for inactive jobs, improved SAP BODS workflow lineage.

• Connectors: Updates to Salesforce, SQL Server, ADF, and MicroStrategy connectors with clearer validation and improved stability.

• Service Desk: Expanded field mapping for integrations and broader user permissions.

• System Settings: New configuration to control user creation when using external identity providers.

• Audit Trails: Automated archival table population, detailed monitoring fields, and standardized CSV archival.

Release Details:

Release Type	Release Version	Build <Release. Build Number. Release Stamp>	Build Date
Service Release	Release7.2.2	Release7.2.2.7220.ceac1d7	08 October, 2025

Home

New & Improved

Enhanced Watchlist Notifications

Watchlist notifications now include updates from collaboration activities such as comments and questions on terms, ensuring complete visibility into all changes to watchlisted items.

Notification Template Configuration

Notification emails now include the event name in the subject line for better clarity and prioritization. The “Edit Notification Message” pop-up allows insertion of pre-approved variables in the subject line for selected notifications. Administrators can enable and configure a global footer using the system settings ovaledge.email.footer.enable and ovaledge.email.footer.configure, ensuring consistent branding, disclaimers, or compliance messages across all email notifications.

Change Management

• Notification subjects now include the variable name, improving clarity and prioritization.

  What Changed

  In the Notification Template, previously, subjects contained only static text, making it difficult to distinguish and prioritize multiple notifications. Variable names are now appended to the subject line for easier identification.

  Affected Users: Administrators

  👉 For more details, see Notification Template Configuration.

Data Catalog

New & Improved

Schema Reference Support Added

The Data Catalog now supports @ reference for Schemas in descriptions and collaboration messages. A new References tab has been added to the Schema Summary Page, along with a Reference Count field in Configure View and Catalog Details. Quick View for reference counts is also available.

Added support for .py and .sql file uploads

The Data Catalog did not support .py file uploads, requiring Python scripts to be stored as .txt files, which resulted in the loss of formatting and indentation. The enhancement now supports uploading and viewing .py and .sql files in the Data Catalog while preserving script formatting.

Tag Reference in Business Description

In the Data Catalog | Objects Summary (Tables, Table Columns, Reports, Report Columns, Files, and File Columns), users can now add a tag reference in the Business Description using the ‘@’ symbol. This improvement makes it easier to link and reference tags directly within Business Descriptions.

Data Preview and Profiling Filters

• A new option has been introduced to optimize profiling and data preview operations for large datasets. This enhancement enables the application of custom filters to focus on the most recent or relevant records, thereby improving performance and supporting the profiling of recent records. It also provides greater control over profiling behavior for object administrators. Key Features: Data Catalog > Table Summary > 9 Dots > Manage Profiling and Data Preview.

  • A configuration modal with two sub-tabs for Profiling and Data Preview is now available.

  • Filters can be saved at the table level and are automatically applied during profiling and data preview until updated.

  • Access is restricted to Integration Administrators for secure control.

Replace Quick View Cards with Shutter

Quick View cards in the Data Catalog and related modules have been replaced with the Quick View shutter, except on the Search Results page. Earlier, compact cards displayed limited information and required extra navigation. The new shutter interface delivers comprehensive metadata previews with a consistent layout, improving visibility and usability.

Change Management

• Quick View shutter replaces Quick View cards in the Data Catalog, providing more consistent object previews.

  What Changed

  Quick View cards in the Data Catalog and related modules are replaced with the Quick View shutter, except on the Search Results page. The shutter shows richer metadata with a consistent layout, improving visibility and usability.

  Affected Users: All Users

  👉 For more details, see Quick View Cards with Shutter.

Data Quality

New & Improved

Downloadable Failed Values in Notifications

In the Data Quality Rules Summary, a new feature has been introduced to enhance Data Quality Rule (DQR) notifications. Notifications now include a concise summary by default, with the option to download a detailed report of failed values when rules fail.

• Default Behavior: Notifications contain only a summary table with execution metrics, ensuring emails and inbox alerts remain clear and consistent.

• New Toggle Option: A toggle labeled “Include Detailed Report in Notifications” has been added at the rule level in the Data Quality Rule Summary page. When enabled, notifications append a downloadable file with row-level failure details.

  • When the Toggle is OFF (default): Notifications include only the summary table, providing key execution metrics in a concise format.

  • When the Toggle is ON: Notifications include the summary table and a full detailed report with failed values and row-level results. The detailed report is sent as an attachment in email notifications.

• Inbox Notifications: Regardless of the toggle setting, a link is provided after the summary to redirect users to the Data Quality Rule page.

• User Benefit: Business users can download and review failed values directly from notifications, improving accessibility and reducing dependency on higher-licensed roles.

Change Management

• Data Quality Rule (DQR) notifications now include a concise summary by default, with the option to download detailed reports of failed values.

  What Changed

  In the Data Quality Rule (DQR) Summary, notifications previously included complete execution details, such as row-level data and extended metadata, which made them lengthy and slowed inbox performance.

  In the current version, notifications display only a concise summary table by default, with a new toggle to include detailed failed values when required. This change enhances readability, improves performance, and allows users to download detailed reports as needed.

  Affected Users: Administrators and Business Users.

  👉 For more details, see DQR Failed values.

Query Sheet

Fixed

Read-Only Access Enforced in Query Sheet

In the Query Sheet, an issue occurred where all data operations, including CREATE, DELETE, UPDATE, etc., were allowed, thereby creating a risk to data integrity. This issue has been resolved. The module now enforces read-only access, restricting all data modification operations.

Change Management

• Read-only access has now been enabled on the Query Sheet, preventing any data modification actions.

  What Changed

  In the Query Sheet, previously, all data operations (CREATE, DELETE, UPDATE, etc.) were allowed. Now, the Query Sheet is restricted to read-only access.

  Affected Users: Administrators

  👉For more details, see Read-Only Access in Query Sheet.

Jobs

New & Improved

Job Monitoring Alerts for Inactive Jobs Without Logs

In Jobs, Job Monitoring notifications are now triggered when a job becomes inactive because no logs are being generated. These alerts are delivered to the Inbox and via Email (if configured), ensuring timely awareness of inactive jobs. To prevent notification overload, repetitive alerts are suppressed. This enhancement helps reduce delays in corrective action and minimizes troubleshooting efforts.

Build Auto Lineage

New & Improved

SAP BODS | Workflow Lineage

In SAP BODS, the workflow lineage now includes the following updates:

• Automatic detection of missing SQL links to ensure accurate lineage generation.

• Updated parsing patterns and code changes to improve SQL identification within workflows.

• Server access in the acceptance environment now allows correct loading of related tables.

• Reliable execution of data flows and crawling, so workflows run as expected.

• Consistent workflow lineage generation, with manual lineage required only for complex cases.

Application APIs

Fixed

Error Handling for Add/Delete User Requests

In the Application APIs, the Add User and Delete User API requests now return clear error messages when an invalid request body is sent. In earlier versions, invalid requests resulted in a generic 404 error (“Oops! Technical issue. Retry later. We apologize for the inconvenience”), which created confusion and made troubleshooting difficult.

The API token generation and role assignments were functioning correctly, but the invalid request body was not handled properly. With this update, error messages are more descriptive and accurately identify invalid request scenarios.

Change Management

• In Advanced Tools, Application APIs: Add and Delete User requests now return descriptive error messages for invalid request bodies, improving clarity and troubleshooting.

  What Changed

  In the Application APIs, previously, Add and Delete User requests returned a generic 404 error for invalid request bodies, which caused confusion and slowed troubleshooting.

  In the current version, these APIs return descriptive error messages that clearly identify issues with the request body. This change improves error clarity, reduces troubleshooting time, and enhances integration reliability.

  Affected Users: Administrators

  👉 For more details, see Error Handling User Requests.

Connectors

New & Improved

Salesforce Connector Setup

In the Salesforce connector setup, the following updates have been implemented:

• Entering an invalid API version now triggers a clear and accurate error message, helping users quickly identify and resolve issues.

• Unsupported API versions have been removed to prevent selection errors.

• Validation now uses the latest supported API version to ensure proper connector setup.

SQL Connectors | Deletion Job

In the SQL Server connectors, deletion jobs now complete successfully and accurately report their status. The performance issue in the deletion service has been resolved, and the deletion process has been optimized to handle all associated objects and dependencies. Connector removals are now fully executed and consistently reflected across all related components in the system.

Connection Pool Login Management

Database accounts are no longer inactivated due to repeated failed login attempts in the connection pool. The system now safely manages multiple incorrect login attempts, ensuring account stability while maintaining connectivity for active sessions. Logs clearly capture failed attempts, helping administrators monitor authentication issues without affecting the database account status.

Connection Page | Quick View

In the Connection Page, the Quick View now displays detailed information on key data elements and operational metrics, providing faster access and improved monitoring. The following updates have been implemented:

• A new tabbed layout shows detailed information for catalog objects, certified objects, reports, dashboards, and queries.

• Tables can be sorted and filtered for easier navigation and review.

• Automatic refresh displays updated information as soon as the jobs are completed.

• Layout changes improve access to insights and support better operational monitoring.

ADF Connector | Crawling Process

In the ADF connector, duplicate objects no longer appear when crawling is performed after migration to the AKS environment.

The following updates have been implemented:

• Crawling after migration to the AKS environment now prevents duplicate factories and pipelines.

• Parent dataset mismatches that previously caused duplicates have been resolved.

• Metadata integrity is now maintained during both fresh and re-crawls.

• The crawling process ensures that accurate and consistent object information is maintained after migration.

MicroStrategy Cloud Connector | Validation and Crawl

In the MicroStrategy Cloud Connector, validation failed because the connector was unable to establish communication with the server, which affected subsequent operations. The following updates have been implemented:

• Connector validation now completes successfully and functions as expected.

• Issues that caused communication failures during validation have been resolved.

• Crawl failures observed after validation are now tracked separately for better monitoring and troubleshooting.

Change Management

• In the Connection Page, connection statistics now provide real-time and detailed insights into connection health, performance, and usage.

  What Changed

  In the Connection Page, previously, the Quick View showed only high-level statistics. Now, the Quick View displays detailed information for catalog objects, certified objects, reports, dashboards, and queries with options to sort, filter, and automatically refresh tables.

  Affected Users: Administrators and business users

  👉 For more details, see Connection Page | Quick View.

• In the ADF connector, duplicate objects no longer appear when crawling is performed after migration to the AKS environment.

  What Changed

  In the ADF connector, previously, crawling after migration to the AKS environment created duplicate objects. Now, the crawling process prevents duplicates and maintains metadata integrity.

  Affected Users: Administrators and users managing ADF connectors

  👉 For more details, see ADF Connector | Crawling Process.

• In the MicroStrategy Cloud Connector, validation now completes successfully, ensuring stable connectivity and normal operation.

  What Changed

  In the MicroStrategy Cloud Connector, validation previously failed due to server communication issues. Now, validation works as expected, and crawl failures are tracked separately.

  Affected Users: Administrators and users managing MicroStrategy Cloud Connectors

  👉 For more details, see MicroStrategy | Validation and Crawl.

Service Desk Administration

New & Improved

Enhanced Field Mapping for External Integrations

In Service Desk Templates, field mapping has been enhanced to provide greater flexibility when integrating with external systems.

• All fields (system and custom) from an external integration are now available for selection when mapping fields between OvalEdge and the integrated tool.

• For ServiceNow integrations, this support extends to custom fields of API type – Service Catalog.

• A new system template field, Service Request Source, has been introduced. This is a dropdown with a default option of OvalEdge. It can be mapped to external integrations as Label, Parent, or Source, and can be edited or removed at the template level as needed.

This improvement ensures more comprehensive field mapping, better alignment with external service desk tools, and greater flexibility in template configuration.

External Integration via Read-Write Permissions

In Service Desk Templates, only users with Admin permissions on external integrations (Azure DevOps/ServiceNow) were able to integrate with OvalEdge. This limitation has been addressed. Now, users with Read-Write permissions on these external integrations can also establish and manage integrations with the OvalEdge application, enabling broader access while maintaining security and governance controls.

Change Management

• In Service Desk Templates, users with Read-Write permissions on external integrations such as Azure DevOps/ServiceNow can integrate with OvalEdge.

  What Changed

  In Service Desk Templates, previously, only users with Admin permissions on external integrations (Azure DevOps/ServiceNow) could integrate with OvalEdge. Now, Users with Read-Write permissions on external integrations can integrate with OvalEdge.

  Affected Users: All Users

  👉 For more details, see External Integration | Read-Write Permissions.

System Settings

New & Improved

Authentication: Control User Creation with External Identity Providers

In Administrator > System Settings, a new configuration, nonlocal.user.creation, has been introduced to manage new user creation when authentication is handled through external identity providers (SSO such as Okta, Azure Entra, ADFS, etc.) instead of a local User ID and Password.

• When set to False (default), the Add User icon is disabled, and user creation is restricted to external systems integrated with OvalEdge.

• When set to True, the Add User icon is enabled, allowing new users to be created directly in OvalEdge.

This update enhances security and compliance for organizations with strict user management requirements.

Audit Trails

New & Improved

Table-Level Actions and Standardized CSV Format

Audit Data Archival now provides administrators with greater control and visibility. A new column allows table-level action selection, with options to Archive in CSV, Do not archive, or Delete without archiving once the retention period is reached.

Additional monitoring fields have been introduced, including Current Row Count, Retention Row Limit, Retention Period (days), Processing Batch Size, Last Archived On, Last Archived Rows, Last Execution Status, Last Run Error, Last Execution Start & End Time, Execution Duration (ms), and the user who executed the job.

Archival format options have been simplified. The SQL option has been retired, and all archival is now standardized to CSV format only.

Change Management

• Audit Data Archival now supports table-level action selection with new monitoring fields.

  What Changed

  In Audit Data Archival, previously, administrators had no table-level control, and archival followed a uniform process with the option to select between CSV and SQL formats.

  In the current version, administrators can define table-level actions and view enhanced monitoring fields, while archival is standardized to CSV format. This change improves flexibility, transparency, and consistency in data archival.

  Affected Users: Administrators

  👉 For more details, see Table-Level Actions.

New Advanced Jobs

Name	Description
User Favorite Code Migration Job	This job migrates user favorite codes by matching navigation links to appropriate favobj values. It processes all user favorites in the userfavorite table and updates their favobj column based on the link patterns.
Migrate Descriptions From Alation	This job loads object metadata from the Excel sheets in the given folder path into the stage table. Then it reads descriptions from the OvalEdge database, updating the references from the Alation format to the OvalEdge format. Attributes: Folder Path: Path of the folder that contains the Excel sheets of object metadata required to identify the related object IDs in the database Load Excel Data to stage table(true/false)? The default value is true. If set to True, the job first loads the data into the stage table from the sheets in the given folder path and then updates the references. If set to False, the job does not load any data; instead, it updates the references directly. It must be False when the user re-initiates the job on the same folder path, which prevents data duplication.

New System settings

Key	Description	Impacted Modules
inactive.job.threshold	Configure the time (in minutes) after which a job with no log generation is considered inactive. Parameters: The default value is 60 minutes. Enter the required threshold in minutes.	Jobs & Notification
inactivejob.notification.timeout	Configure the time (in hours) to identify inactive jobs for notifications. Parameters: The default value is 24 hours. Enter the required timeout in hours.	Jobs & Notification
lineage.codes.process.limit	Configure the maximum number of codes to be parsed when building lineage for new or changed codes. Parameters: The default value is Empty (no limit; parses all codes). Enter a numeric value (X). Only the first X codes are parsed, and the remaining are skipped. Example: If set to 500 and 1500 codes are detected, only 500 are parsed.	Data Catalog
long.running.job.threshold	Configure the maximum duration (in hours) a job can run before it is considered long-running. Parameters: The default value is 24 hours. Enter the required duration in hours.	Jobs
nonlocal.user.creation	Configure whether to allow new user creation when authentication is managed through external providers. Parameters: The default value is False. If set to True, new users can be created with non-local authentication. If set to False, new user creation is disabled with non-local authentication.	Users
ovaledge.email.footer.configure	Configure the text to display as a footer in all email notifications. Parameters: The default value is Empty. Enter the required footer text for consistent branding, compliance, or disclaimers.	Notifications & System Settings > Notification Templates
ovaledge.email.footer.enable	Configure to enable or disable a global footer in all email notifications. Parameters: The default value is True. If set to True, footer text is displayed. If set to False, footer text is disabled.	Notifications & System Settings > Notification Templates
stripe.api.key	Configure the Stripe API key. Parameters: The default value is Empty. Enter the required API key.	AI
stripe.public.key	Configure the Stripe public key. Parameters: The default value is Empty. Enter the required public key.	AI
stripe.webhook.secret	Configure the Stripe webhook secret. Parameters: The default value is Empty. Enter the required webhook secret.	AI

Known Vulnerabilities

This release includes some known security vulnerabilities. These issues come from third-party open-source libraries packaged with the product images and do not affect OvalEdge’s own code.

Standard Image

• 7 High-severity vulnerabilities were found in commonly used libraries:

  • Netty (CVE-2025-55163, CVE-2025-24970)

  • Tomcat (CVE-2025-48989)

  • Spring (CVE-2025-41248, CVE-2025-41249)

  • Commons IO (CVE-2024-47554)

  • Jetty (CVE-2024-13009)

• These issues could cause service disruption, denial of service, or unauthorized access.

• No Critical vulnerabilities were found.

Big Data Image

• 1 Critical vulnerability was identified in Hive JDBC (CVE-2018-1282), which could allow SQL injection attacks.

• 17 High-severity vulnerabilities were also detected in libraries such as:

  • Hadoop (CVE-2021-33036)

  • Hive (CVE-2015-7521, CVE-2016-3083, CVE-2015-1772)

  • Protobuf (CVE-2021-22569, CVE-2022-3509, CVE-2022-3510, CVE-2024-7254)

  • Gson (CVE-2022-25647)

  • Commons IO (CVE-2024-47554)

  • Netty (CVE-2019-16869, CVE-2025-55163, CVE-2025-24970)

  • Tomcat (CVE-2025-48989)

  • Spring (CVE-2025-41248, CVE-2025-41249)

  • Jetty (CVE-2024-13009)

• These issues could allow unauthorized access, denial-of-service attacks, or data handling risks.

Action Plan

• The identified vulnerabilities, including both critical and high-severity issues, will be remediated in the upcoming release. Fixes will be applied through updated libraries and components to ensure the product images include the latest security patches.

---

Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.