Release7.2.5
The OvalEdge Release7.2.5 is a service release focused on usability, performance, and security enhancements across key modules. It introduces a new governed marketplace for curated data assets.
Key Highlights
Introduction of the Data Products Module
A new governed marketplace enables users to discover, subscribe to, and consume curated data assets with full lifecycle management, versioned data contracts, governance controls, lineage, and audit visibility.
Enhanced Data Discovery and Catalog Accuracy
Global Search now supports Report and Sub-Report filtering.
Improved Code Custom View filtering, crawl tracking (via lastmetasyncdate), and Dell Boomi subsystem lineage access.
Power BI refreshed dates are now captured.
Strengthened Governance and Metadata Quality
Improved governance role inheritance in Business Glossary.
New Summary view in Data Quality for faster remediation insights.
Programmatic rule score updates via new API.
Separate notification templates for rule failures and execution failures.
Improved Query, Workflow, and Job Operations
Query Sheet now runs queries on masked tables with masking applied to sensitive fields.
Commented SQL queries are processed correctly.
The jobs page includes a JSON viewer for quick diagnostics.
Automated Job Workflows now honor the configured parallel or series execution mode.
Expanded Connector Capabilities
IBM Cognos subfolder Regex filtering.
SQL Server JDBC driver bundled with application WAR.
Optimized Bridge metrics storage.
Support for MS Fabric Warehouse via SQL Server connector with Managed Identity.
Qlik Sense KPI name extraction corrected.
User Experience and Security Enhancements
Team references now open an inline shutter showing team details.
Bulk permission updates support cross-page selections.
System tables previously hidden by oe.crawl.excludeTables are now available in read-only mode.
Audit and Retention Improvements
Updated audit table retention defaults and new “Last Updated By/On” fields.
Table–based retention rules were introduced to ensure consistent archival management.
Release Details:
Service Release
Release7.2.5
Release7.2.5.7250.bf2a055
26th Dec 2025
Data Products
New & Improved
A new Data Products module is introduced to provide a governed marketplace-style environment for discovering, subscribing to, and consuming reusable, curated data assets. It centralizes secure access to trusted datasets, enhances data transparency, and accelerates analytics, AI, and operational decision-making across the organization.
Key Capabilities
Governed Data Domains & Security
Domain-based structuring with role-based access controls (Admins, Governance, Product Managers, Browsers, Consumers).
Automated security provisioning and cancellation during subscription and lifecycle transitions.
Auto-subscription for governance roles; controlled or instant subscription access for others.
End-to-End Lifecycle Management
Full lifecycle: Draft → Curation → Publish → Subscribe → Consume → Update → Republish.
Inline editing of metadata, tags, governance roles, and associated objects.
Metadata Curation Score ensures quality before publishing.
Data Product Registry & Marketplace
Central registry for creating and managing Data Products with configurable views and governance metrics.
Marketplace for exploring Data Products using filters like domain, rating, tags, delivery mode, and popularity.
Subscription actions: Subscribe, Unsubscribe, Watchlist, AskEdgi Workspace with delivery shortcuts (Preview, Query Sheet, Access Instructions).
Rich Product Summary & Object Actions
Unified summary page featuring descriptions, lineage, relationships, ratings, conversations, and audit activity.
Supports multiple asset types (Tables, Files, Reports, APIs).
Data Contracts & Versioning
Structured, version-controlled contract templates with automatic version updates and mandatory re-acceptance on change.
Exportable as PDF, YAML, or JSON.
Lineage, Relationships & Tracking
Upstream lineage visualization, object relationship diagrams, and system-wide reference tracking.
Integrations & Audit
Integration with Service Desk workflows and AskEdgi Workspace.
Support for NFS file uploads and object-level quality scores.
Detailed audit history of governance, metadata, contracts, lineage, and subscription activity.
Home-Global Search
New & Improved
Improved Report Discovery
In the Global Search, a new “Report Level” filter has been added, allowing selection between “Reports” and “Sub-Reports” as needed. The backend clearly identifies sub-reports to support accurate filtering while maintaining existing performance. This will enable users to filter and view only Reports in their search results when needed.
Tags
New & Improved
Enhanced Configurable Visibility for Tag Views
The Tags module now includes configurable visibility options for the Tag views: Tiles, Tree, and List. This enhancement allows administrators to hide or unhide required Tag view types from the Security Settings, ensuring better alignment with organizational preferences and improving the user experience in environments that require simplified Tag navigation.
To configure Tag Views, navigate to Administration | Security | Application Security and search for Tag Views from the Application Name.
Data Catalog
New & Improved
Data Catalog Code Custom View Filters
In the Codes grid view, filtering now supports viewing records with blank custom field values. When filters are applied to code custom fields in custom views, rows with empty values are now included in the results, improving visibility of incomplete metadata and enabling more effective data quality and governance analysis.
Access to Sub-Process Lineage in Dell Boomi
In the Dell Boomi connector, users required a more efficient way to navigate from a process call dataset to its corresponding lineage from the main process lineage screen. To address this, a new “View Process Lineage” option has been added to the three-dot menu for process call datasets. Users can now click this option to navigate directly to the lineage of the selected process call within the same tab, improving workflow efficiency and reducing manual steps.
Refreshed Date Support for Power BI Assets
In the Data Catalog, the system now captures the “Refreshed Date” for Power BI reports and datasets. Previously, this field was not extracted during connector crawls, creating a visibility gap for users relying on data freshness. The platform now fetches the Refreshed Date from Power BI APIs during crawling and displays it as a read-only field under the Crawl Details section. The value updates automatically on each recrawl, providing accurate, up-to-date information about the most recent refresh of Power BI assets.
Fixed
Improved LMDF Download Accuracy in Table Columns
In Data Catalog | Table Columns Grid View, an issue occurred when downloading data from a configured view. The downloaded file did not include the expected information as follows:
Columns for Classification and Data Quality Score were missing from the downloaded file.
Arabic text appeared as question marks in the downloaded sheet.
After switching the interface to English, column headers in the downloaded file also appeared as question marks.
Only the first five rows were downloaded in both Arabic and English modes.
Data downloaded in Arabic mode displayed content in English instead of Arabic.
These issues have been resolved. Data now downloads correctly with complete row counts, accurate classification values, and proper Arabic text rendering.
Access Cart Option Disabled for Table Columns
In the Data Catalog | Table Columns Grid View, the Access Cart option for the Table Column object type was incorrectly enabled. This option was not supported according to the system setting access.cart.support.object.types. The issue has been resolved by disabling the Access Cart option for Table Columns. The behavior is now consistent across the Catalog and matches the handling applied to File Columns.
Incorrect Metadata Date Usage in Reporting Connectors
In the Data Catalog, an issue occurred for Reporting Connectors where the last modified date was updated on every crawl and, in some cases, disappeared after recrawls, even when no metadata changes existed. The issue was caused by the crawl logic using the last modified date instead of the last metadata sync date, treating each crawl as a metadata update. The issue has been resolved, and now the crawl logic uses the last metadata sync date for change tracking, so the last modified date updates only when metadata changes exist and remains unchanged during recrawls.
Business Glossary
New & Improved
Governance Role Inheritance and Selection Update
In the Term Summary | 9 Dots | Update Governance Roles, the assignment and management of governance roles have been improved. This update resolves a functional gap in which the system failed to correctly inherit governance roles when an empty value was provided during an update.
The enhancements include:
A dropdown list is now available when updating the governance role, enabling selection from all available users rather than requiring manual entry.
While updating governance roles, the user shows the existing governance roles for the term. Changes can be made, and new roles can be updated.
Empty value updates, which were previously problematic, are now resolved by a change to this component.
Fixed
Improved Tag Copying Behavior for Associated Data Objects
In the Term summary, an issue occurred in which additional tags added to a published term were not copied to the associated data object when the 'Copy Tags to Catalog' option is enabled in the 'Manage Data Association Preferences'. Tags were only assigned after manually drafting and republishing the Term. This issue has been resolved. New tags added or unassigned to a published Term now automatically copy or unassign from the associated data object without requiring Term republishing.
Projects
New & Improved
Manual Archive for Completed Projects
A new manual archiving feature allows Project Admins and Project Owners to move completed projects to a dedicated Archived Projects page, improving workspace organization and lifecycle management. Archived projects remain accessible for reference or audit purposes and can be restored or deleted when needed.
Service Desk
New & Improved
MetaWrite Permission Validation for Approval Workflows
An enhancement has been introduced in Service Desk to improve the approval workflow for content change requests, new asset requests, and term approval requests. This update ensures that only authorized users with the required MetaWrite permissions can approve changes that affect metadata and content integrity.
With this update, the MetaWrite permission check has been moved from the fulfillment stage to the approval stage. Service requests can now be approved only if the workflow includes at least one approver with MetaWrite permission. If no eligible approver exists in the workflow, approval actions will be restricted.
Delegation of Approval Responsibilities in Viewer Plus
In Service Desk Viewer Plus instances, approval delegation has been expanded to include both Authors and Viewers.
Approval delegation in Viewer Plus instances now allows both Authors and Viewers to be designated to approve service requests. This enhancement provides greater flexibility in managing approval workflows, ensures continuity when handling service requests, and helps reduce dependency on a limited set of approvers.
Data Classification Recommendations
Fixed
Incorrect Pagination and Count Display
The Data Classification Recommendations page showed “0 to 0 (out of 0)” for non-admin users, even when many recommended objects were visible. This made it difficult for users to understand the actual number of recommendations and verify classification results. This issue has been fixed. The pagination and object count now display correctly based on each user’s access.
Data Quality
New & Improved
New Summary Tab for Aggregated Remediation Insights
The Remediation Center now includes a Summary tab that provides an aggregated view of remediation status before loading detailed failed values. Earlier, the All tab displayed every failed record individually, which led to slow performance and made it difficult to understand the overall remediation workload, especially for large datasets.
The new Summary tab offers a high-level view of failures grouped by object, attribute, rule, scheme, and connector. It displays a progress bar for New and In Progress counts, along with a summarized table that supports sorting, filtering, pagination, and data export. Users can drill down into detailed pages or open the All tab with relevant filters applied. Workflow actions remain disabled in this view to keep it informational.
This enhancement improves navigation, reduces load time, and enables faster triage for data quality stewards by separating summary monitoring from detailed remediation actions.
API for Updating Data Quality Rule Scores
A new API has been introduced to enable programmatic updates of data quality rule scores for connectors that do not currently support data quality capabilities. With this enhancement, organizations can now integrate their existing workflows or external source systems to push rule scores directly into OvalEdge, ensuring accurate, consistent, and real-time data quality metrics.
Distinct Notification Templates for Rule Failures and Execution Failures
Data Quality notifications now use dedicated templates for rule failures and execution failures. Previously, both failure types relied on a single shared template, making it difficult for users to determine whether an issue resulted from a business rule validation or a technical problem.
In the updated version, the system generates context-specific notifications that clearly indicate whether a failure is rule-related or due to execution issues, such as connection problems or query errors. This enhancement enables users to quickly identify the failure type and take the appropriate corrective action without confusion.
Query Sheet
New & Improved
Enhanced Masking Support for Queries
The Query Sheet now allows queries on tables that contain masked or restricted columns without blocking execution. With this enhancement, only the sensitive columns are masked in the result set while the query continues to run, aligning the Advanced SQL behavior with Auto SQL. This improvement supports use cases in which users must access datasets containing PII or other protected attributes, while ensuring that sensitive values remain securely masked.
Navigate to Administration | System Settings | Others, and search with the Key (querysheet.masked.column.security). By default, the value is set to ‘Advanced’, which blocks query execution on tables containing masked columns. If users select ‘Standard’ as the default, queries are allowed to run, and masking is applied to sensitive columns in the results.
Fixed
Handle SQL Queries with Comments
In the Query Sheet, an issue occurred in which SQL queries containing comments were incorrectly marked as “Error,” and no results were displayed. The execution stopped before completing, rather than processing the query normally. This issue has been resolved. Queries that include comments now execute successfully, display results correctly, and show the appropriate job status, such as “Finished” or “Success.”
Jobs
New & Improved
View JSON Data on Jobs Page
In the Jobs module, a new eye icon has been added to each job entry, allowing users to view the complete JSON data for that job. Clicking the icon opens a modal that displays the unformatted JSON in a readable, scrollable format, with a clear close option. This provides quick access to job details without leaving the Jobs Page, improving visibility and debugging efficiency.
Advanced Tools-Impact Analysis
New & Improved
Enhanced Report Asset Selection with Report Type Filter
The Impact Analysis workflow now includes a 'Report Type' dropdown to clearly distinguish between selected report categories, such as Datasets, Dashboards, Pages, etc. This enhancement resolves the limitation that prevented identical-named objects from being differentiated during selection, improving clarity and accuracy when adding report-based assets to Impact Analysis.
Advanced Tools-Build Auto Lineage
Fixed
ADF Lineage | Metadata Parsing and Detection Issue
In the ADF Lineage module, an issue occurred where lineage could not be generated due to parsing gaps, incomplete activity detection, and run-discovery issues. The issue has now been resolved with improved parsing and metadata handling, and lineage is now generated correctly based on the available metadata.
Advanced Tools-Data & Metadata Changes
Fixed
Improved Filter Performance for Multi-Schema Selection
In Data & Metadata Changes, an issue occurred when applying filters with a Connection Name and selecting all Schemas. The system returned a 400 Bad Request error because the filter request exceeded the allowed request size when all Schemas were selected. This issue has been resolved by optimizing the filter handling process. Filtering by Connection Name with multiple Schemas now works without errors.
Administration-Connectors
New & Improved
IBM Cognos Analytics | Subfolder Regex Filtering
In the IBM Cognos Analytics connector, the system now supports defining regular expressions (Regex) for subfolder-level inclusion or exclusion. Previously, all subfolders were crawled by default, resulting in long processing times and increased manual effort to apply security restrictions. With this improvement, crawls can focus on only relevant subfolders, significantly reducing crawl duration, lowering database load, improving efficiency, and simplifying security configuration for business units.
Bridge | Enhanced Metrics Optimization
In the Bridge Metrics module, the earlier design results in significant data growth and unclear tracking due to missing JobStepId and multiple rows per metric. With this change, JobStepId is added to provide precise step-level mapping, and all metrics for the same JobStepId and connector are stored in a single JSON record. This reduces data volume, improves traceability, and provides a clean JSON pop-up view for better debugging.
MS Fabric – SQL Server Service Principal Connectivity
In the MS Fabric connector module, support for SQL Server authentication through Service Principal is now enabled to meet customer requirements for secure access to SQL Server within MS Fabric Warehouse. This enhancement includes updates to the connection logic and authentication flow, along with validation across multiple SQL Server authentication types in a Windows VM environment with on-premise Bridge on SaaS. This improvement provides a more secure, scalable, and authenticated option for users adopting MS Fabric.
Support for MS Fabric Warehouse Using SQL Server Connector
In the SQL Server connector, support is added to connect directly to Microsoft Fabric warehouses using Azure Managed Identity. This enhancement allows users moving to Fabric to use the same SQL Server connector for metadata extraction and Data Quality checks through the Fabric SQL analytics endpoint. Two new authentication options, System-Assigned and User-Assigned Managed Identity, are introduced, unnecessary credential fields are hidden, and a new client ID field is added where required. Backend updates ensure secure connectivity and smooth migration from existing SQL Server connections without impacting current setups.
External SQL Server JAR files
In the SQL Server connectors, the SQL Server driver is now included within the application WAR. The system references the built-in driver by default for all SQL Server connections. External SQL Server JAR files (<file name>) in the third-party JAR path are no longer required and must be removed.
Fixed
KPI Names Displayed as IDs in Qlik Sense Connector
In the Data Catalog, certain KPIs in the Qlik Sense connector were displayed using their IDs instead of actual names. The issue was caused by the title extraction logic handling only plain string titles, not expression-based ones. This has been resolved, and KPI names now display correctly, fetching names from the source when available and using IDs only if the source name is missing.
Administration-Job Workflow
New & Improved
Automated Job Workflow Execution
The Automated Job Workflows functionality has been improved to ensure that workflows execute according to their configured execution policy. Users can now enable workflows to run either in parallel or in series, depending on the specific requirement.
Automated Job Workflows are segregated based on their independent behaviors and executed accordingly. Workflows configured for parallel execution now run concurrently, while those requiring sequential execution continue to run in series, as intended.
Administration-User Management
New & Improved
Team Member Visibility Through Reference Links
A new enhancement simplifies how users access team details when a team is referenced in business or technical descriptions. Previously, clicking a team reference redirected users to the Teams module, which restricted visibility for many users, especially those with Viewer licenses who lacked permission to open the Teams page.
With the update, selecting a team reference now opens a shutter displaying the team’s name, description, a searchable list of all members with email addresses, the total number of members, and an option to copy all visible email IDs. This improvement enables users to view essential team information directly from their current page, without navigating away or requiring elevated permissions.
Administration-Security
New & Improved
Bulk Permission Updates with Selection Retention
The Security module now supports selection retention across multiple pages, allowing users to update permissions for many data objects in one action. Earlier, selections had to be made page by page, which made bulk updates slow and difficult for large datasets.
With this enhancement, selections across pages are retained, the total selected count is shown, and bulk actions apply to all selected items at once. This update simplifies permission management, reduces manual effort, and ensures accurate audit logging for all bulk updates.
System-Driven Restriction and Enablement for Metadata Table Columns
The system setting oe.crawl.excludeTables has been removed to ensure complete metadata availability and improve the reliability of dependent features. Previously, several OvalEdge system tables, such as connection, oecolumn, filecolumn, user, and role, were hidden through this setting, which caused metadata gaps that affected features like AskEdgi, diagnostic recipes, and success metric recipes.
With this enhancement, all system tables that were previously excluded are now available in the Security and Data Catalog modules with read-only access. Sensitive or irrelevant columns remain restricted at the connection layer, ensuring they are not exposed anywhere in the application. This update provides full metadata visibility needed for system features while maintaining strong protection of sensitive information.
Administration-Advanced Jobs
Fixed
Detailed Object Tracking Enabled for URL Migration Logs
In Advanced Jobs | Migrate Descriptions From Alation, an issue occurred in which job logs for the URL migration process only displayed summary counts of updated and failed Wiki IDs, without showing which specific objects failed, which limited the ability to identify affected tables, schemas, or columns. The fix adds detailed information to the job logs. Failed Object IDs and Object Names now appear alongside the existing counts, enabling precise identification of objects that did not update successfully during URL conversion.
Object-Level Logging in Alation URL Migration
In Advanced Jobs, an issue occurred with Alation's URL Migration: The job logs lacked sufficient detail to identify which specific tables, schemas, or columns failed during the URL conversion process. The logs only displayed total, updated, and failed Wiki ID counts, making it difficult to determine which objects were not successfully updated. This issue has been fixed. The job logs now include the failed Object IDs and Object Names for tables, schemas, and columns. This enhancement allows clear identification of objects requiring further investigation.
Administration-Audit Trails
New & Improved
Updated Default Retention Periods and New Audit Fields
The default retention settings for audit data have been updated to avoid the unintended deletion of historical comments during upgrades or migrations. Previously, the comment table used a 7-day retention period, which caused older comments to be removed immediately after migration.
With this update, the comment and message tables now use a 2-year retention period, and all other audit tables use a 30-day default retention period. Existing user-defined retention settings remain intact. Additionally, the User column has been replaced with “Last Updated By” and “Last Updated On” to improve audit tracking.
These changes prevent loss of historical comments, maintain consistency during upgrades, and provide clearer audit information.
Default Retention Settings by Table Type
Audit Data Archival now applies predefined retention periods based on table type, creating a more consistent and efficient archival process. Previously, all archival tables followed the same default retention policy, leading to inconsistent outcomes and, at times, unnecessary long-term data retention.
In the updated version, system tables are grouped into four categories, each with a specific default retention period:
Audit Table: 2 years (730 days)
Main Table: Do not archive
Main-Large Table: 6 months (180 days)
Diagnostic Table: 30 days
These retention values are automatically applied based on the table classification defined in system settings, while still allowing users to modify retention periods to meet their operational needs.
Advanced Jobs
The latest release introduces a set of new advanced jobs that allow users to update the data specific to modules or features using advanced algorithms.
Crawl Table Columns
This advanced job loads table column metadata from files located in the configured folder. It updates the corresponding table structures in the system based on the column information found in the files, ensuring that table definitions and column details remain accurate and up to date.
Process SAP HANA Tables Based on File Differences
This advanced job processes SAP HANA tables by comparing the latest files generated by the Bridge with previously processed files. Only the differences identified between these files are used to load and update SAP HANA table metadata, ensuring that changes are captured efficiently without reprocessing unchanged data.
Syncing Views, Procedures, and Functions
This advanced job synchronizes all Views, Procedures, and Functions within the specified schema. It ensures that the system accurately reflects the latest database object definitions from the source, keeping the metadata up to date.
Attribute1: Provide Connection ID
Attribute2: Provide Schema Names with Comma(,) separated
Existing Advanced Jobs - Updated
The latest release includes updates to existing advanced jobs, enhancing functionality to improve data-processing accuracy and operational efficiency across supported modules.
LITAT_SNAPSHOT_JOB
Help
This advanced job captures lineage information for each connection and stores it in JSON format. The generated lineage files are saved under the OvalEdge temp path inside the LITATSnapShotFolder, allowing the system to maintain connection-level lineage snapshots for further use.
Migrate Descriptions From Alation
Help
This job loads object metadata from Excel sheets in the specified folder path into the stage table. It then reads descriptions and stories from the OvalEdge database that contain Alation-format references and updates them to an application-supporting format to enable proper navigation.
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)
Default value: true
If set to True, the job first loads data into the stage table from the Excel files in the specified folder path, then updates the references.
If set to False, no data is loaded into the stage table, and the job directly updates the references.
Migrate Descriptions From Alation
ajname
ajname – Update References To Application Format
Specifies the name of the advanced job that updates existing references to an application-supported format.
Migrate Descriptions From Alation
ajtype
ajtype – UpdateReferencesToApplicationFormat
Defines the job type used to identify and execute the reference update process.
Migrate Descriptions From Alation
classname
classname – com.ovaledge.oasis.advance.UpdateReferencesToApplicationFormat
Specifies the fully qualified class responsible for executing the logic to update references to the application format.
REPORTING_CONNECTORS_ANALYSIS
Attrubute5label
Specifies the type of analysis to be generated for the QlikSense connector.
1 – Crawling Analysis
2 – Lineage Analysis
Blank – Both Crawling and Lineage Analysis
REPORTING_CONNECTORS_ANALYSIS
Help
This advanced job generates analysis reports for reporting connectors based on the provided input attributes. The analysis results are saved as Excel file(s) in the specified folder path.
Attributes:
Attr1 (Connection Id)
Reporting connector connection ID (e.g., QlikSense, Power BI).
Attr2 (Report Id)
Optional single report or chart ID.
If left blank, analysis is generated for all reports.
Attr3 (File Path)
Folder path where the analysis Excel file(s) will be created.
Attr4 (Report Group Id)
Optional report group or domain ID.
Restricts the analysis to the specified report group.
Attr5 (Qliksense Analysis Type – For Qliksense Connector only)
Blank - both analyses
1 - Crawling Analysis only
2 - Lineage Analysis only
System Settings
The latest release introduces new system settings that enhance user control over the application's behavior.
adf.runs.app.processing
This system setting determines where Azure Data Factory pipeline run processing is handled during crawling. It controls whether pipeline run information is processed within the application or at the platform level, helping define how and where pipeline execution details are managed during the crawling process.
Parameters:
When enabled, pipeline runs are processed at the application level.
When disabled, pipeline runs are processed at the CSP layer.
Connectors
merge.adf.runs
This system setting controls whether Azure Data Factory pipeline runs are merged during crawling. It defines how multiple executions of the same pipeline are handled and helps determine how pipeline run information is grouped during the crawling process.
Parameters:
When enabled, multiple pipeline runs are merged into a single consolidated run.
Reduces duplication and simplifies pipeline run information.
Connectors
adf.enable.partitionfiles
This system setting controls whether lineage is built for Azure Data Factory partition files. It determines whether lineage information is generated for partitioned files, helping capture and represent partition-level data flow details.
Parameters:
When enabled, lineage is generated for partitioned files.
When disabled, lineage for partitioned files is not generated.
Lineage
qliksense.websocket.timeout
This system setting configures the timeout (in milliseconds) for Qlik Sense WebSocket request–response communication. It defines the maximum time the system waits for Qlik Sense to respond after a request is sent and controls how long the system continues waiting before marking the request as unsuccessful, especially when working with large or complex Qlik Sense applications.
Parameters:
Specifies the wait time for a response from the Qlik Sense Engine after a WebSocket request is sent.
If no response is received within the configured time, the request is stopped and marked as a timeout error.
Useful when Qlik applications are large or require additional processing time.
Increasing the timeout helps avoid “WebSocket response timeout” or “Engine request timeout” errors during crawling.
If left empty, the application’s default WebSocket timeout is used.
Connectors
querysheet.masked.column.security
This system setting determines how the Query Sheet handles tables that contain masked or restricted columns. It controls how queries behave when accessing data with sensitive information, ensuring data security while allowing access to non-sensitive columns.
Parameters:
Advanced:
Blocks query execution when masked or restricted columns are detected.
Prevents any data from being returned.
Used when stronger data protection is required.
Standard:
Allows queries to run even when masked columns are present.
Sensitive columns remain masked in the query results.
Allows access to permitted data without exposing restricted information.
Query Sheet
sync.mincounttowritetofiles
This system setting controls when collected objects are written to files based on the total object count. It defines when the system saves objects during processing and helps manage file creation based on the volume of objects processed.
Parameters:
Objects are written to files only when the total number of objects exceeds the configured threshold.
If the object count does not reach the threshold, file creation is skipped.
Bridge
sync.mincounttoprocess
This system setting determines when the Bridge synchronization process is executed. It controls whether the sync runs based on the number of objects identified during processing and helps manage system load by skipping synchronization when the object count exceeds the defined limit.
Parameters:
The Bridge sync process is skipped if the total number of objects exceeds the configured limit.
Prevents execution of sync operations that may impact performance due to large object volumes.
Bridge
Change Management
Change Management helps stakeholders understand what has changed from the previous version to the latest version, who is impacted, and how processes or permissions are affected. This ensures smooth adoption and reduces operational risk.
The impacted modules include Service Desk, Data Quality, Job Workflow, User Management, Security, and Audit Trails.
Service Desk
In Service Desk, approval of content change, new asset requests, and term approval requests now requires at least one approver with MetaWrite permission.
What ChangedIn Service Desk, previously, for content change, new asset requests, and term approval requests, fulfillment would fail if the workflow did not include any MetaWrite approvers. Now, service requests cannot be approved unless at least one approver in the workflow has MetaWrite permission. There is no Meta-Write check in fulfillment, because users select this option when approving the service request.
Affected Users: Service Request Approvers
👉 For more details, see MetaWrite Permission Validation for Approval Workflows.
In Service Desk Viewer Plus instances, approval delegation has been expanded from only Authors to include both Authors and Viewers.
What ChangedIn Service Desk, previously, only Authors could be selected to delegate service request approvals in Viewer Plus instances. Now, both Authors and Viewers can be designated to delegate approval responsibilities in Viewer Plus instances.
Affected Users: Viewer license users (only in viewer plus instances)
👉 For more details, see Approval Delegation in Viewer Plus Instances.
Data Quality
Introduced separate notification templates for rule failures and execution failures to improve clarity and enable accurate remediation.
What ChangedIn Data Quality, previously, a single notification template was used for both rule failures and execution failures, resulting in limited clarity.
In the updated version, separate templates are now used for each failure type. This change provides precise identification of the issue and allows users to respond with the appropriate remediation action.
Affected Users: Administrators and Business Users.
👉 For more details, see Distinct Notification Templates in Data Quality.
Administration-Job Workflow
Automated Job Workflows now run according to their execution policy, either in parallel or series.
What ChangedIn Job Workflows, previously, automated Job Workflows executed in series, regardless of the configured execution policy. They are now segregated based on their independent behavior and can run in either parallel or series configurations, as intended.
Affected Users: Administrators
👉 For more details, see Automated Job Workflow Execution.
Administration-User Management
Team references in business and technical descriptions now open an in-page shutter instead of redirecting users to the Teams module.
What ChangedWhen a team was referenced in business or technical descriptions, clicking a referenced team name always redirected users to the Teams module, limiting access for users without the required permissions.
In the updated version, selecting a team reference opens a shutter displaying team details and member information, allowing users to view this data in place.
Affected Users: Administrators and All Users.
👉 For more details, see Team Reference Enhancements.
Administration-Security
System tables previously excluded through oe.crawl.excludeTables are now always available with read-only access.
What ChangedThe system setting oe.crawl.excludeTables was previously used to hide several OvalEdge system tables, causing missing metadata and failures in features that depended on those tables.
In the updated version, this setting has been removed, and all system tables are accessible in read-only mode, with sensitive columns still restricted at the connection layer.
Affected Users: Administrators and All Users.
👉 For more details, see Metadata Table Columns Controls.
Administration-Audit Trails
Comment and message tables now retain data for two years, and audit fields have been updated for improved clarity.
What ChangedIn Audit Trails, the comment table followed a 7-day retention rule, causing older comments to be deleted during upgrades.
In the updated version, the comment and message tables use a 2-year retention period, all other audit tables use a 30-day default retention period, and the User field has been replaced with Last Updated By and Last Updated On to improve audit accuracy.
Affected Users: Administrators and All Users.
👉 For more details, see Audit Data Retention Updates.
Default retention rules now follow table-type classifications instead of a single shared retention setting.
What ChangedIn Audit Trails, Audit Data Archival previously applied a single default retention period to all tables, leading to inconsistent archival behavior.
The updated version introduces four table types, each with its own predefined retention period: 2 years for audit tables, no archival for main tables, 6 months for main-large tables, and 30 days for diagnostic tables. These defaults apply automatically, and user-configured retention settings remain fully supported.
Affected Users: Administrators and All Users.
👉 For more details, see Default Retention Settings by Table Type.
Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?