Login & Home
Login
New & Improved
Restrict Concurrent Logins
A new system setting, restrict.concurrent.logins, has been introduced to enhance account security by limiting users to a single active session.
When enabled, any new login automatically terminates existing sessions on other browsers or devices. This does not impact multiple tabs within the same browser.
When disabled (default), users can maintain multiple concurrent sessions across different devices or browsers.
EULA Disabled for Prod Login
The EULA (End User License Agreement) pop-up, previously displayed during the first-time login, is now disabled by default in all production environments.
Home
New & Improved
Appearance
In My Resources, Appearance allows theme customization with six color options, each one is available in light and dark modes, offering 12 unique combinations. A toggle button in the header allows switching between light and dark themes while retaining the selected base color. The default theme is set to OvalEdge Blue and Light Mode.
Inbox Pop-Up for First Login
Inbox displays pending actions through a pop-up during the initial login. Each item can be clicked to view details. Automatically closes upon switching tabs and does not reappear during the same session.
Announcement Banner
Administrators can configure an announcement banner at the top of the homepage to share updates. Banner content and visibility are managed in System Settings.
Restore to Default Layout
A “Restore to Default Layout” button is now available in the “Manage Homepage Widgets” section. Upon confirmation, the current layout is reset to the admin-defined default layout. All user customizations, including widget size and placement, are cleared.
Custom Data Story Widget
Administrators can now add specific Data Stories to the homepage using the new ‘Add as Custom Homepage Widget’ option. These widgets are user-personalized and enhance the visibility of targeted content directly on the homepage. Created by users with admin privileges.
Enhanced Homepage Widgets
Widget Management Enhancements: Admins can now manage and configure homepage widgets from Administration > Security > Manage Homepage Widgets. They can assign widget owners, control visibility for authors, enable or disable widget resizing/removal, and push or withdraw widgets across all user homepages.
Widget – User Preferences: In My Profile > Manage Homepage Widgets, users can personalize their homepage layout using intuitive drag-and-drop functionality to:
Add or remove widgets.
Rearrange widget positions.
Resize widgets for optimal display.
My Bookmarks Widget: The My Bookmarks widget now supports unlimited bookmarks with actions like Edit, Pin, Delete, and easy reordering.
Customization via System Settings
home.videos.viewall.link
Configure to redirect the specific helpful resources link.
Parameters:
Enter the specific URL link in the Value column.
ovaledge.main.logo
Configure to upload the main logo at the top-left black bar.
Parameters:
Enter the specific image in the Value column.
ovaledge.login.logo
Configure to upload the logo for display on the login page.
Parameters:
Enter the specific image in the Value column.
Allowed image types: png, jpeg, and jpg
ovaledge.onboarding.widget.enable
Configure to enable/disable the onboarding widget screen.
Parameters:
The default value is False.
If set to True, the onboarding widget screen is enabled.
If set to False, the onboarding widget screen is disabled.
login.support.enable
Configure to enable/disable the support information on the Login page.
Parameters:
The default value is False.
If set to True, the support information will be displayed on the Login page.
If set to False, the support information will not be displayed on the Login page.
ovaledge.login.title
Configure to view the title or tagline for the application on the Login page.
Parameters:
The default value is Empty.
Based on the specified value, the title or tagline will be displayed on the Login page.
ovaledge.login.description1
Configure to view the description for the application on the Login page.
Parameters:
The default value is Empty.
Based on the specified value, the description will be displayed on the Login page.
ovaledge.login.description2
Configure to view the additional description for the application on the Login page.
Parameters:
The default value is Empty.
Based on the specified value, the additional description will be displayed on the Login page.
login.doc.link
Configure to view the documentation and video URL link for the application on the Login page
Parameters:
The default value is Empty.
Based on the specified value, the URL will be displayed on the Login page.
login.faq.link
Configure to view the Frequently Asked Questions URL link for the application on the Login page.
Parameters:
The default value is Empty.
Based on the specified value, the URL will be displayed on the Login page.
home.actionitems.alert.enable
Configure to enable/disable the alert pop-up functionality.
Parameters:
The default value is True.
If set to True, the alert pop-up functionality will be enabled.
If set to False, the alert pop-up functionality will be disabled.
online.assistance.enable
Configure to enable/disable the Online Assistance.
Parameters:
The default value is False.
If set to True, the Online Assistance option will be enabled.
If set to False, the Online Assistance option will be disabled.
restrict.concurrent.logins
It allows administrators to control whether users can log in to multiple sessions simultaneously.
Parameters:
The default Value is False (users can log in to multiple sessions)
To Restrict: Set the value to True to limit users to a single active session at a time.
enable.welcome.story
Configure to view if the Data Story can be added to the Home Page or set as Welcome Story.
Parameters:
The default value is False.
If set to True, the Data Story can be added to the Home Page or set as Welcome Story.
If set it to False; the Data Story should neither be added to the Home Page nor set as Welcome Story.
oe.profile.importancescore.threshold
This setting defines a threshold value for the importance score of data assets in the profiling process. Only assets with an importance score equal to or greater than this threshold will be included in the profiling. This ensures a focus on high-priority data, optimizing resource use and enhancing the relevance of profiling outcomes. Value should be in the range of 0-100.
My Resources
New & Improved
Email Configuration
Administrators can configure system-defined email notifications using SMTP, and now also through AWS SES and Azure Graph API.
Inbox Notifications
Provides a simplified way to manage platform notifications.
Key updates include:
Categorized Notifications: Organizes notifications into All, My Actions, and @mentions for system and custom-triggered alerts.
Bulk Actions: Allows marking as read, deleting, or archiving multiple notifications at once.
Advanced Filtering & Sorting: Filters by event type, read status, or module, and sorts alerts to highlight important ones.
My Watchlist Significant Data Change Notifications: Triggers a notification when significant changes occur in remote data objects, such as row addition or deletion. A threshold between 0.0001% and 100% can be set, and if the row count change exceeds this limit, the system sends an alert. Example: if the threshold is set to 50% and the row count of the data object increases by more than 50%, a notification will be generated.
Compare Schema Notifications: Notifications are automatically sent when schema differences are detected.
Customization via System Settings
enable.slack.communication
Configure to enable/disable Slack on the My Profile page.
Parameters:
The default value is False
If set to True, the Slack option is enabled.
If set to False, the Slack option is disabled.
enable.slack.channel
Configure to view the 'Add Slack id' on the Profile page.
Parameters:
The default value is False
If set to True, the Add Slack id option displays on the Profile page.
If set it to False, the Add Slack id option does not display on the Profile page.
enable.google.chat.channel
Configure to view the 'Add GoogleChat Webhook URL' on the Profile page.
Parameters:
The default value is False
If set to True, the 'Add GoogleChat Webhook URL' option displays on the Profile page.
If set it to False, 'Add GoogleChat Webhook URL' option does not display on the Profile page.
enable.ms.teams.channel
Configure to view the 'Add Microsoft Teams Webhook URL' on the Profile page.
Parameters:
The default value is False.
If set to True, the 'Add Microsoft Teams Webhook URL' option displays on the Profile page.
If set it to False, 'Add Microsoft Teams Webhook URL' option does not display on the Profile page.
ms.teams.integration.type
Configure Microsoft Teams integration method for sending notifications.
Parameters:
The default value is Webhook.
If you have updated Microsoft Teams to a version that no longer supports Webhooks, switch the integration method to Workflows and set the value to Workflow.
ovaledge.email.server.type
It allows users to select the type of email server used for sending notifications.
Parameters:
The default value is SMTP.
Users can choose the server type from the dropdown list (SMTP, AWS SES, and Azure Graph API).
Based on the selection, the relevant configuration fields will be enabled.
ovaledge.azure.graphapi.emailaddress
It allows users to specify the sender email address used for sending notifications through the Azure-authorized application.
Parameters:
The default value is EmptyNote.
Users must enter a valid and active email account within the organization’s Microsoft environment with Outlook access.
The Azure application will use this email to send notifications on the user’s behalf.
ovaledge.azure.graphapi.tenantid
It allows users to specify the Tenant ID from the Azure application registration.
Parameters:
The default value is Empty.
Users must enter the Tenant ID associated with your organization's Azure Active Directory.
ovaledge.azure.graphapi.clientid
It allows users to specify the Client ID of the OvalEdge application from Azure application registration.
Parameters:
The default value is Empty.
Enter the Client ID assigned during Azure application registration.
ovaledge.azure.graphapi.clientsecret
It allows users to store the Client Secret generated during Azure application registration securely.
Parameters:
The default value is Empty.
Enter the Client Secret obtained from the Azure portal for the registered application.
ovaledge.awsses.smtp.server
It allows users to specify the AWS SES SMTP Server URL for sending email notifications.
Parameters:
The default value is Empty.
Enter the SMTP Server URL provided by AWS SES.
ovaledge.awsses.smtp.port
It allows users to specify the AWS SES SMTP Server Port used for sending email notifications.
Parameters:
The default value is Empty.
Enter the port number provided by AWS SES (e.g., 25, 465, or 587).
ovaledge.awsses.smtp.mode
It allows users to specify the mode used by the AWS SES SMTP server for secure communication.
Parameters:
The default value is Empty.
Enter the server mode (e.g., TLS, SSL) based on your AWS SES configuration.
ovaledge.awsses.smtp.username
It allows users to specify the username for the AWS SES SMTP server.
Parameters:
The default value is Empty.
Enter the SMTP username provided by AWS SES to authenticate and send email notifications.
ovaledge.awsses.smtp.password
It allows users to specify the password for the AWS SES SMTP server.
Parameters:
The default value is Empty
Enter the SMTP password associated with the AWS SES username. This is required for authenticating and sending email notifications.
ovaledge.awsses.smtp.from.address
It allows users to specify the email address used to send notifications through the AWS SES SMTP server.
Parameters:
The default value is Empty
Note: This must be a verified email address in your AWS SES configuration.
conversation.notification
Configure governance roles to receive notifications for new questions, comments, and unanswered questions in Conversations.
Parameters:
The default value is Empty.
Click the field to select one or more roles from the drop-down.
You can configure any combination of the following roles: Steward, Owner, Custodian, Governance Role 4, Governance Role 5, Governance Role 6.
Global Search
New & Improved
Enhanced Search and Visibility Options
In Service Desk, all service requests and their statuses now appear in search results. Only the created requests are visible to viewers, while authors can access all requests.
In Data Catalog, selected filter values now display on object cards, providing clearer context during browsing. The Curation Score is available as a filter and also appears in Quick View and on object cards to support more informed decisions.
When specific modules are disabled through Application Security, related data is excluded from search results, ensuring restricted access by design. Additionally, members of the Admin and Governance Role members can configure search keywords for Data Catalog objects to improve search accuracy and relevance.
Customization via System Settings
search.es.searchcontext
Configure to view the object types in the Search box drop-down list.
Parameters:
Available object types: All, Table, Topic, File, Report, API, Schema, Query, Data Attributes, Business Glossary, Service Request, Help & Resources, Project, Question Wall.
The default value is All.
Select them from the drop-down list to add more objects to the Value. The selected values appear in the Search drop-down.
If left blank, "All" is displayed.
search.es.pagination.count
Configure to specify the maximum number of records to be added to an Index while running the advanced job to fetch from the local DB to Elasticsearch.
Supports: Min - 5000, Max - 10000.
Parameters:
The default value is 5000.
Enter the required value in the field provided. Based on the specified value, the records will be added to an Index.
search.es.activedetails
Configure to show the active objects in the search results.
Parameters:
The default value is Active.
If set to Active, active objects are displayed in the search results.
If set to Inactive, inactive objects are displayed in the search results.
If set to Empty, then both the active and inactive data object results are displayed in the search results.
search.score.use.synonym
Configure to include the Synonym score in the Relevance score formula to determine the most relevant search results.
The relevance score is calculated based on three components: the Elasticsearch score, the popularity score, and the synonym score (if configured).
Parameters:
The default value is False
If set to True, the search results calculation includes the Synonym score.
If set to False, the search results calculation excludes the Synonym score.
search.score.use.popularity
Configure the Popularity Score in the Relevance score formula to determine the most relevant search results. The relevance score is calculated based on three components: the Elasticsearch score, the popularity score, and the synonym score (if configured).
Parameters:
The default value is False
If set to True, the search results calculation includes the popularity score.
If set to False, the search results calculation excludes the popularity score.
The relevance score calculation depends solely on the Elasticsearch score and the settings configured for synonym score.
search.es.active.filters
Configure the specific active filters used on the Global Search page to refine search results. Each filter corresponds to a particular attribute of the search items, allowing users to narrow down results based on various criteria. Users can remove filters based on the requirement.
Parameters:
The default value are Connection, Schema, Business Glossary, Table Type, Folder, Report Group, Term Status, Quality Index, Service Request Status, Question Wall, Additional Information, and Created Date.
Enter the required value in the field provided. Filters will be displayed on the Global Search page based on the specified values.
globalsearch.match.type
Configure the Global Search function that analyzes search queries against document fields:
best_fields: This type optimizes precision by searching multiple fields and returning the highest score for the best match.
most_fields: This type is used to optimize recall, which means it adds the scores of each match across multiple fields to potentially increase overall relevance scores.
cross_fields: This type analyzes multiple fields as a single combined field, increasing relevance for queries that span multiple fields. It's beneficial for searches that are expected to have various terms across different fields.
ovaledge.searchbar.enable
Configure to enable/disable the search bar on the home screen.
Parameters:
The default value is False
If set to True, the search bar on the home screen is enabled.
If set to False, the search bar on the home screen is disabled.
search.es.governancerole.filters.optional
Configure to view the Governance Roles filters used on the Global Search page to refine search results.
Parameters:
Owner, Steward, Custodian, Governance Role 4, Governance Role 5, Governance Role 6
The default value is Data Owner.
To add more Governance Roles to the Value, select them from the drop-down list.
If left blank, "Empty" is displayed.
search.es.dataobjects.filters.optional
Configure to view the additional filters for data objects used on the Global Search page to refine search results.
Parameters:
Certification, Rating, API Group, Popularity, Report Type, Metadata Curation Score
The default value is Certification.
Select them from the drop-down list to add additional filters to the Value.
If left blank, "Empty" is displayed.
index.max.result.window
Configure to return the maximum number of Data Catalog records in a single search request.
Parameters:
The default value is 10,000.
The minimum allowed value is 5000, and the maximum is 10,000.
es.datacatalog.grid.mysql.fallback.force
Configure to fetch the Data Catalog data from My SQL or Elastic Search.
Parameters:
The default value is False
If set to True, Data Catalog data will be fetched from the My SQL.
If set to False, Data Catalog data will be fetched from the Elastic Search.
Custom.search.requirements
Configure custom tuning of relevance scoring for search results.
Parameters:
The default value is "level1": 500, "level2": 300, "level3": 50}.
Additional.sorting.options
Configure to enable sorting of search results based on object types with the highest number of service requests.
Parameters:
The default value is False
Browser Extension
New & Improved
Browser Extension Authentication Options
The OvalEdge Browser Extension supports multiple authentication methods for secure and flexible access.
Licensed users log in using their OvalEdge Server URL, User ID, and Password on the plugin login screen.
Guest User Login: The Guest (External) User Flow in the OvalEdge browser extension provides limited access to predefined functionalities for external stakeholders, including consultants, third-party vendors, or external teams.
External users log in using their email. Only emails from approved domains (configured in the System Settings under the Browser Extension tab) are allowed access.
To ensure secure access, the administrator specifies valid email domains (e.g., @overage.com, @gmail.com).
External Users can:
Access Published Terms and Submit Data Quality Requests: View only glossary terms marked as Published and raise data quality requests by submitting a URL with relevant details. A proxy user, defined in system settings, handles these requests.
Authenticate via the More Option: Use the More option to access various login methods, including OvalEdge credentials, SSO, and API tokens.
View Report Certifications: Access report certification statuses such as Certify, Caution, and Violation for reports from Power BI, Tableau, Qlik Sense, and Delta Lake.
Enhanced Report and Dataset Visibility in Browser Extension
In the OvalEdge Browser Extension, metadata visibility for reports and datasets has been enhanced across key report sources. For Power BI, both Report and Dataset object types are now viewable. In Tableau, the extension displays the View Type as 'Report', and in Delta Lake, the Table object type is accessible.
Report details can be viewed even if the report is not certified, including the business description, associated terms, and column details.
A new "View Dataset Details" option provides access to the related semantic model (dataset), including its business description, semantic columns, and related terms, directly within the extension.
The "View Report Details" option enables navigation back to the report view from the dataset screen.
For Guest access, only Favorite Columns are displayed in both views to maintain metadata restrictions.
Audit Logs for Browser Extension
A new Audit Logs feature has been introduced to track user sign-in and sign-out activities in the OvalEdge Browser Extension. It records key details such as user email, name, type, sign-in/sign-out time, session duration, IP address, browser, OS, and session status (success or failure). Failed login attempts, along with failure reasons, are also logged.
Display of Steward Information in Browser Extension
The Browser Extension now displays the assigned Steward’s name, governance role, and avatar directly below the names of Terms, Data Objects, and Data Stories (Story Authors). This helps identify the appropriate point of contact for clarification or data governance queries.
Customization via System Settings
browser.extension.enable.guest
Configure to enable/disable the Browser Extension for non-licensed users.
Parameters:
The default value is False
If set to True, enable the Browser Extension.
If set to False, disable the Browser Extension.
browser.extension.allowed.email.domains
Configure access for guest users to the browser extension by specifying valid email domains as comma-separated values.
Parameters:
The default value is Empty.
Enter the valid email domains in the specified Value field.
Example: @ovaledge.come, @google.com
browser.extension.proxy.user.for.guest
Specifies the admin user to be associated with data quality service requests raised by guest users through the plugin. The actual email of the guest user will be recorded separately in the service request details.
Ovaledge.browser.extension.isauthdb
Configure to enable or disable database login through the browser extension.
Parameters:
The default value is False
Enter true to enable or false to disable.
Advanced Jobs
Migrate Homepage Widgets
This job migrates the Homepage Widgets layout from 6.3.x and 7.x versions to the 7.2 version.
Advance Job for adding subject in comment table
This job adds subject information for team-related notifications, ensuring that the details appear in the My Recent Notifications widget on the homepage.
User Notification Preferences Manager
This job enables the addition of new modules and submodules in the notification preference table of the My Profile section for all users.
Migration of Mention and Myaction Comments
This job updates the 'tab' column in the 'comment' table with 'Mention' or 'My Action' for existing messages. All existing messages are marked as Read, except for 'My Action' messages, which remain pending without requiring action. This advanced job should be run only once post-migration.
Collaboration Message Migration
This job migrates all collaboration messages older than Release 6.2 and should be executed only once after the migration.
Advance Job for Indexing Existing
This advanced job enables the indexing of pre-existing data into Elasticsearch and controls the indexing process based on the specific object types you select.
Enter the names of the object types that need to be supported in Attribute1, such as 'oetable' or 'oeschema'. The data corresponding to the specified object types will be indexed in Elasticsearch. If multiple object types need to be indexed, separate them with commas. If no object types are provided, data from all object types will be indexed.
Attributes:
Comma separated Object Types - oetable,oecolumn, etc.
Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?