Login & Home

Home

The Home page supports personalization, allowing users to move, resize, and remove widgets to create a customized layout.
What Changed
In the Home page, previously, widgets were static—non-movable, non-resizable, and non-removable—providing limited flexibility.
Now, on the Home page, widgets are movable, resizable, and removable, allowing users to personalize their homepage layout.
Affected Users: Administrators, Authors, Viewers

Browser Extension

In Browser Extension, Basic Authentication is removed for SaaS deployments and replaced with token-based authentication.
What Changed
In Browser Extension, Basic Authentication (database login using user ID and password) was previously supported for both SaaS and on-premises deployments. Depending on the login flow, credentials were either entered after providing the server URL or accessed via the More option in the login UI. This approach carried security risks, including credential exposure in headers, replay attacks, and logging vulnerabilities.
Now, Basic Authentication is removed for SaaS deployments and replaced with token-based authentication. A SaaS flag controls this behavior:
- For SaaS deployments:
  If Guest Login is available, the DB Login option under More… is replaced with token authentication.
  If Guest Login is not available, the DB Login screen after entering the server URL is replaced with token authentication.
- For on-premises deployments, Basic Authentication remains available for backward compatibility.
This update improves security for SaaS deployments while leaving on-premises deployments unaffected.
Affected Users: All users
In Browser Extension - Data Quality Request Templates, the Potential Business Impact Amount and Corrective Action fields are now hidden for a specific client.
What Changed
In Browser Extension, the Potential Business Impact Amount and Corrective Action fields in Data Quality Request templates were previously visible to all users and customers. Now, these fields are hidden in Data Quality Request templates for a specific client. This update affects only field visibility and does not introduce any functional changes.
Affected Users: All users

My Resources

Expanded Significant Data Change threshold range to 0.001%–100%
What Changed
In My Resources, data change monitoring in OvalEdge used a minimum threshold of 1% for significant changes. For large tables with millions of rows and hundreds of columns, this threshold was too high, limiting the ability to detect smaller but important data changes. Now, the range for configuring Significant Data Change notifications has been expanded to support thresholds from 0.001% to 100%. Users can specify thresholds with up to three decimal places, allowing more granular monitoring of subtle changes in large datasets.
Affected Users: Administrators, Authors, Viewers

Global Search

Reintroduced “Configure Search Keyword” for Projects, Tags, Data Stories, and Business Glossary.
What Changed
In Global Search, the Configure Search Keyword option was not available for Projects, Tags, Data Stories, or the Business Glossary, preventing business users from viewing synonym words. Now, the Configure Synonyms for Search feature (formerly Configure Search Keyword) is available for Projects, Tags, Data Stories, and the Business Glossary. Business users can view synonym words created by GR users or administrators.
Affected Users: All users
Added a note in the date filter to inform users that the available date range is limited to the dates present in the search results.
What Changed
In Global Search, the date filter allowed selection only from dates present in the current search results. This restriction was not clearly communicated, which could confuse users about unavailable dates. Now, a note has been added to the date filter explaining that the selectable date range is restricted to the available dates in the search results.
Affected Users: All users

PreviousChange Management NextMetadata Governance

Last updated 2 months ago

Was this helpful?