Release7.2.1
OvalEdge Release7.2.1 is a service release designed to strengthen governance participation, improve license management, enhance session security, and resolve key issues across core modules. The release builds on Release7.2 with targeted fixes and incremental improvements that stabilize the platform and refine the user experience.
Key Highlights
Session Security
Automatic session logout when the last browser tab or window is closed, ensuring secure handling of user sessions.
Data Catalog & Tags
Fixes for filtering, downloads, partition folder visibility, and correct removal of deleted tag references.
Nullable column filters and lineage checks now function as expected.
Business Glossary
Improved handling of default classifications in domain templates.
AI-driven Data Classification Recommendations no longer override primary terms incorrectly.
Data Quality
New “Has Schedule” column in rules summary for easier monitoring of scheduled and unscheduled rules.
Collaboration (Question Wall)
Introduction of a Question Summary Page for centralized discussion.
New Accept Answer capability ensures only the reporter marks the validated answer, with auto-accept and notification features for accountability.
File Manager
Fixes for Bridge job failures and OvalSight visibility issues.
Connectors
Enhanced job logs now capture connector configuration details.
BigQuery connector supports multi-region dataset crawling.
System Settings & Audit Trails
Fixes for notification template filters and audit trail catalog filters.
New system settings introduced for API Basic Authentication and lineage relationship building.
Release Details
Service Release
Release7.2.1
Release7.2.1.7210.7d50a74
10 September, 2025
Login & Home
New & Improved
Session Logout
The system now automatically logs out users when they close the last browser tab or window. This improvement ensures better session security by preventing users from staying logged in after leaving the application without manually logging out.
Change Management
In the application, the user session now ends automatically when the last browser tab or window is closed. When the application is reopened, users are required to sign in again.
What ChangedIn the application, previously, the user session remained active if the browser tab was closed without logging out, allowing access to the application without entering credentials and posing a security risk. Now, the application ends the session when the last browser tab or window is closed. On reopening the application, users are required to sign in again, ensuring secure access and proper session handling.
Affected Users: Viewers
Tags
Fixed
Deleted Tag Removed from Object Reference Section
In Tags, an issue occurred where adding an object (e.g., a table) from the tag description using an @ annotation created a tag reference in the object's reference section. However, deleting this tag did not remove it from the object's reference section. This issue has been fixed, and deleting a tag now correctly removes it from the object reference section.
Data Catalog
Fixed
Report Summary Importance Search Not Working
In the Reports Summary, the search in the Importance field was not functioning correctly. Users were unable to search and filter values without errors, and the 8-dot conditions also failed to function. This issue has been fixed, and the search now works as expected with all conditions. In addition, users can create a custom view with all fields and apply conditions in the Importance field as expected.
Advanced Filters Not Handling Empty Values
In the Data Catalog, advanced filters such as Equals To and Not Equals To for custom fields did not return the expected results for empty or null values. When users applied the Not Equals To condition after selecting True and False, the system returned no data exists instead of retrieving rows with blank fields. This happened because the filter logic did not recognize empty values. The issue has been fixed, and advanced filters now correctly handle empty or null values.
Download Option Only Exported First Page
In the Table Summary, when users downloaded table summary columns, only the first page of results was exported. The same issue occurred for all objects. This issue has been resolved, and downloads now include all pages of results as expected.
Table Columns Download
In the Data Catalog, the download option for table columns was not functioning. Users were unable to export the table column details as expected. This issue has been fixed, and the download option now works correctly.
Filtered Data Not Downloading Correctly in Simple View
In the Data Catalog, when users filtered table columns and tried to download them in Simple View, the system still downloaded all table columns rather than just the filtered data. This issue has been fixed, and downloads now correctly include only the filtered table columns in Simple View.
Partition Folder Files Without Lineage Not Visible
Files of type partition folder with “no lineage” were not displayed in the Data Catalog as expected. This happened because the system did not correctly handle lineage checks for such files. The issue has been fixed, and all partition folder files without lineage now appear correctly in the Data Catalog. Additionally, data consistency issues in extension tables have been resolved to ensure accurate filtering.
Security ACL Entries Advanced Job
In the Create Security ACL Entries Advanced Job, users could not provide access to Reports because the Reports and Report Columns were not visible in the Data Catalog. This happened in rare cases due to database slowness or large data volume. The issue has been resolved, and running the job now makes all reports and related columns visible. Additional logging has been added to monitor similar scenarios.
Nullable Column Filter
The Nullable column filter in the Data Catalog did not work as expected and failed to return correct results. This happened because the filtering logic failed to evaluate the column’s nullable property. The issue has been fixed, and the filter now works correctly, displaying accurate results.
Empty File List
In the Data Catalog, the File List page displayed an error message instead of showing the message “No data exists.” This occurred because the system executed an incomplete SQL query when no files were available. The issue has been resolved, and the page now correctly displays “No data exists” when no files are present.
Business Glossary
Fixed
Default Checkbox Requires Valid Classification Name
In Administration | Security Domains, an issue occurred when uploading classifications through the Domain LMDF template. If the classification name was missing and the Default field was set to Yes, the system incorrectly enabled the Default option for the empty classification after upload. This issue has been resolved. The Default checkbox is now applied only when a valid classification name is provided in the domain template, ensuring consistency between template input and system behavior.
Data Classification Recommendations
New & Improved
Data Classification Recommendations | Incorrect Term Replacement
In the Data Classification Recommendations section, the primary term in the glossary is replaced with an auxiliary term after approving an AI recommendation using the thumbs-up icon. The system now keeps the existing primary term when an auxiliary term is recommended. This fix also ensures consistent term handling across related modules, including Business Glossary and Data Catalog.
Data Quality
New & Improved
Data Quality Rules – Has Schedule Column
In Data Quality Rules, a new “Has Schedule” column is added to the summary view to indicate whether a rule has scheduling configured. Previously, users had to inspect each rule to verify scheduling manually. With this enhancement, the column displays a clear Yes or No value, making it easy to find unscheduled rules and ensure proper monitoring of all Data Quality Rules.
File Manager
Fixed
Jobs Running Continuously in Bridge
In the File Connector - Bridge setup with HashiCorp Vault authentication, OvalSight jobs failed to complete. When users triggered a job, it intermittently failed, got killed, and continued running in the background. On the OvalSight Summary page, an error pop-up appeared but showed no error message. This issue has been resolved. Jobs now complete as expected, and in case of failure, meaningful error messages are displayed on the Summary page.
OvalSight Not Visible Without Re-Running File
In the OvalSight, the OvalSight visualization should appear after running the file once. However, users had to re-run the same file again after some time to make OvalSight visible. This caused unnecessary re-execution and impacted usability. The issue has been resolved. OvalSight now appears as expected after a single file run without requiring repeated execution.
Question Wall
New & Improved
Question Summary Page
A new Question Summary Page has been introduced to improve collaboration and knowledge sharing. Each question now has its own dedicated page where all replies, including accepted answers, are displayed. Users can reply directly from the summary page, where only the conversations related to that question are visible. With this enhancement, a question will have a centralized summary page, and users can also access it directly from the Conversation Shutter for easier navigation.
Question Wall – Accept Answer
In the Question Wall, a new Accept Answer capability improves the accuracy and reliability of responses. Previously, any reply automatically moved a question to the Answered state. This created uncertainty when multiple or incomplete replies existed. With this enhancement, only the question reporter can mark the most relevant reply as the accepted answer, ensuring accountability, building trust in shared information, and enabling quick identification of validated responses within the Question Wall.
Core Functions
The question reporter selects a single reply as the accepted answer.
Accepted answers are visually highlighted with a green tick and label.
A previously accepted answer can be withdrawn, which reopens the question.
The reporter can assign acceptance to a different reply when needed.
Admin override is available in exceptional cases.
Auto-Accept
If no reply is accepted within the configured duration (10, 20, or 30 days), the latest reply is automatically accepted.
A reminder is sent to the question reporter one day before auto-acceptance.
Auto-accepted replies display a distinct label to differentiate them from manually accepted answers.
The auto-accept cycle restarts if the question is reopened or a reply is withdrawn.
Notifications
Notification to the responder when a reply is accepted.
Notification when an accepted answer is withdrawn.
Reminder and confirmation notifications for auto-accepted replies.
Notification preferences can be managed under My Profile > Question Wall.
Sorting Enhancements Users can sort questions to view them in a preferred order:
Open Questions: Sort by Latest Posted (default), Oldest Posted, or Latest Replied.
Answered Questions: Sort by Recently Accepted (default), Question Created Date, or Latest Reply.
Availability
The Accept Answer feature is supported across the Question Wall and Conversation Shutter, ensuring consistent validation of responses across collaboration areas.
Change Management
In Question Wall – Accepted Answer, question reporters can now explicitly mark a response as the Accepted Answer.
What ChangedIn Question Wall, previously, any response from the assigned user or team would automatically mark the question as Answered, regardless of accuracy. Now, only the question reporter can designate an Accepted Answer. The accepted answer is visually highlighted, limited to one at a time, and can be reassigned if needed. Notifications are triggered for accepted answers, and a new “Notify on Accepted Answer” option is available in My Profile > Question Wall.
For existing questions, the most recent answer is auto-marked as accepted to maintain consistency.
This change improves clarity by highlighting validated solutions, holds reporters and responders accountable, and strengthens collaboration and user experience through consistent answer validation.
Affected Users: All Users
Load Metadata from Files
Fixed
Upload Option Disappeared
On the LMDF main page, the Upload option disappeared when users zoomed in on the page. In some cases, the option even disappeared at the default 100% zoom. This happened because the page layout did not adjust correctly for different zoom levels. The issue has been resolved, and the Upload option now remains visible at all zoom settings.
Table Column Metadata Not Updating
In LMDF, the Table Column metadata fields (Business Description, Technical Description, Tags, Terms, Governance Roles, and Custom Fields) were not updating as expected. The issue occurred due to a build instability. This issue has been fixed, and all column metadata fields are updated correctly.
Viewer License User Incorrectly Assigned
In the Advanced Tools, Load Metadata from Files > Users section, users with a Viewer license could be assigned the Author role. The system accepted the role assignment without validating the license type, allowing Viewer-licensed users to gain Author-level permissions. This issue has been fixed, and the system now enforces proper role-to-license validation.
Connectors
New & Improved
Job Logs
In crawl and profile jobs, the logs now capture and display all connector settings that were active during the job execution. These details appear at the beginning of each log entry, allowing users to review configuration parameters and validate applied settings. This enhancement improves transparency and supports easier troubleshooting during job analysis.
BigQuery Connector Crawl
In the BigQuery connector, crawling now supports datasets across multiple regions. A new connector attribute allows specifying regions as input, including multiple regions separated by commas. This enhancement ensures that datasets from all configured regions appear during the crawl process.
System settings
Fixed
Notification Templates
In the Notification Templates, the Created By search field allowed users to type text instead of only selecting a date. This happened because the date picker configuration (allowInput=true) permitted text entry alongside date selection. The issue has been resolved, and the field now correctly restricts input to valid dates only.
Module Filter Displayed Incorrect Results
In SystemSettings > Notification > Notification Template, the Module filter did not work correctly. When filtering by Governance Catalog or Business Glossary, the system also displayed results from other modules rather than just the filtered data. This issue has been fixed, and the filter now returns only the correct module-specific results.
Audit Trails
Fixed
Catalog Filter Showing Incorrect Object Type
In the Audit Trails > Catalog > Description filter, the object type is displayed as "Code" while the actual object type is shown as "Query". This mismatch happened because the filter label was not aligned with the object type value. The issue has been resolved, and the filter now displays the correct object type consistently.
New Advanced Jobs
Update Servicedesk Date columns from UTC to Database time zone
This job converts ticket creation and SLA (Service Level Agreement) dates from UTC to the database Time Zone. It also processes all tickets created after the first build date for the Release6.3 version.
New System Settings
api.basic.auth.enabled
This configuration controls whether Basic Authentication is enabled for accessing OvalEdge APIs. Basic Authentication requires API clients to provide a username and password in the HTTP request header for Authentication. A system restart is required for changes to take effect.
Parameters:
The Default value is false (Basic Authentication is disabled)
Enter the value as true to enable Basic Authentication for APIs, and enter the value as false to disable Basic Authentication for APIs.
Lineage.build.relationships
This configuration determines whether OvalEdge should build and display data lineage relationships for datasets within the same connection. For datasets with over 100,000 records associated with the same connection, it is recommended to set this parameter to false.
Parameters:
The default value is True.
Set the value to true to enable building lineage relationships for datasets within the connection. Set the value to false to disable lineage relationship building.
Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?