OvalEdge Releases


The OvalEdge Release6.0.2 is the latest service release that includes a Question Wall where users can tag another user and associate a data object with their questions and answers. The Service Desk has been redesigned to display predefined templates when creating a new service request. 

Additionally, OvalEdge supports the integration of OKTA, Azure AD, and HashiCorp, allowing users to set parameters for algorithms that generate term recommendations.

In this release, the critical and significant bugs associated with the Home, Tags, Data Catalog, Business Glossary, Data Stories, Dashboard, Service Desk, Administration, and Connectors modules are fixed and working as expected.

Release Type  Release Version Build
<Release. Build Number. Release Stamp>
Build Date
Service Release Release6.0.2 Release6.0.2.6000.0a3bc13 25 February 2023


The OvalEdge Release6.0.2 is a service release that includes the following features:

  • Home:
    • Global Search: New Inbox tab for viewing collaboration messages
    • Chrome Extension: Link to the service request ticket for suggesting terms or data quality requests.
    • Bookmark: Redesigned for a better user experience. 
    • SSO: Encrypted hash passwords for authentication with a reset password option
  • Data Catalog:
    • Complete path of a data object is displayed in breadcrumbs navigation.
    • Addition of Data Type Size and Key Column to display Primary Key/Foreign Key relationships. 
    • New ‘Profile’ option is added in the Nine Dots icon for Schemas.
  • Business Glossary:
    • Ability to change the domain of a term and update governance roles.
    • Term policy takes precedence over Security.
    • List View and the Tree View both have “Add Term” and “Suggest Term”.
  • Service Desk:
    • OvalEdge automatically populates some service request templates and selected tables with all the necessary attributes.
    • Collaboration feature is added to service requests.
  • Audit Trails:
    • Deleted term logs are shown in audit trails
    • Logout time of users who logged in through SSO will be displayed.
  • Administration - Connectors: 
    • OvalEdge supports various authentication types, including token-based and JSON Web Token (JWT) for salesforce connection setup.
    • Integrates with OKTA, Azure AD, JIRA, ServiceNow, AWS Secrets Manager and HashiCorp for access authorization.
  • Administration - Service Desk Templates:
    • Creating new Service Desk Templates can only be done by admin users.
    • A custom Report Column templates option has been added.
    • Integration with Azure DevOps helps users to manage tickets in Azure DevOps.
  • Administration - Advanced Jobs: 
    • 'TeradataLineageJobForExternalSourceFile' builds lineage using source files from the WhereScape Red tool for the Teradata connector. 
    • 'Import SQL DQRules' allows bulk uploading of custom SQL data quality rules.
    • 'TableauUsageAnalysis' fetches Tableau usage details from the source system.
  • Configurations:
    • New AI tab has been added to list all AI-related configurations.
    • ‘Ovaledge.login.application’ key has been moved from the Others tab to the Users & Roles tab.
  • Miscellaneous:
    • Data Story: Adding videos is possible.
    • Jobs: Displays the latest job logs at the top.
    • User’s List: Status column displays the ‘Active/Inactive’ status of the users.
    • Advanced Tools - APIs: A new API, 'addCustomFields', has been added.
    • Load Metadata from Files: Download the template "Template with Data" for Table Columns and Datasets.

What’s New

  • Question Wall

    In My Resources | Inbox, a Question Wall is newly implemented to allow any users to post their questions and answers by tagging another user and associating a data object. As a result, the message will be displayed in the global search results for the associated object. 
    In the Question Wall, responses can be classified into Active and Closed categories. Users can convert the active conversations into closed.
  • AI Recommendations 

    AI Recommendations now allows users to set parameters for algorithms that generate term recommendations. It includes adjusting the threshold for the Smart Score, Weightage of the Smart Score, Rejected Score, Maximum Columns on which AI recommendations can work, and more.
  • Service Desk Refactoring

    In Service Desk, the existing feature of creating a new service request is enhanced by displaying predefined templates from OvalEdge. Whenever the “New Service Request” button is clicked, a list of all the existing templates in the OvalEdge application is displayed.
    Users can search for the desired template using the search option. When a service request template is selected, all mandatory fields associated with that template, such as Summary, Priority, Select Table, etc., are displayed to the user. If a user selects multiple objects based on grouping, multiple service requests are created with information provided in the mandatory fields for each data object selected. 

    In addition, Automatic Team approvals are being replaced by respective Role approvals, and any existing service request with an automatic team approval workflow now has a respective role approval.
  • Connectors Integration

    OvalEdge supports the integration of OKTA, Azure AD, and HashiCorp.
    This integration of an external connector will help in access authorization while creating a datasource connection. 
    In the Connectors module, the Manage Connection details are enhanced with following parameters that the user needs to provide while creating a datasource connection.
    • For OKTA, the user can provide the SSO Connection ID, SSO Application ID, and Role ID. 
    • For Authentication, the user can provide the Credential Manager details based on the connector selected. 
  • Salesforce Connector Authentication

    The following authentication types are now supported by OvalEdge when connecting to Salesforce.
    • Token Based: In this authentication process, users use the security token generated when creating a salesforce account to connect.
    • JSON Web Token (JWT): In this authentication process, users set up a connection by providing an additional layer of security in the form of a Keystore file. The Keystore file is in JSON format and contains all the authentication details in the encrypted format. 
  • New Connectors

    • ADP Connector: ADP is a leading provider of cloud-based human capital management solutions, including payroll processing, time and attendance tracking, benefits administration, and more. 
      ADP Connector automates time-consuming tasks of data entry, record keeping, and training enrollment, increasing company compliance.
      The ADP Connector is a Relational Database Management System (RDBMS) that allows users to crawl and profile the datasets such as Tables, Columns and helps build the data catalog and relationships.
    • Couchbase Connector: Couchbase is a distributed NoSQL cloud database that delivers unmatched versatility, performance, scalability, and financial value for all of your cloud, mobile, on-premises, hybrid, distributed cloud, and edge computing applications. 
      OvalEdge uses the REST API to connect to the data source, which allows users to Crawl, Profile data objects (Tables, Table Columns). 
    • Greenhouse Connector: Greenhouse is an applicant tracking system and recruiting application that simplifies the recruitment process by finding suitable candidates, conducting effective interviews, and making easy hiring decisions. 
      OvalEdge uses the Greenhouse API to connect to the data source, which allows users to Crawl, Profile data objects (Tables, Table Columns, etc.), and build Relationships.
    • Hopsworks Connector: Hopsworks is the most compelling feature platform for designing and operating feature pipelines, training pipelines, and inference pipelines. It runs out of the box with existing pipelines, so users do not have to redesign it to work with Hopsworks. 
      OvalEdge uses Rest API to connect to the Hopsworks instance.
    • IBM Cognos Connector: IBM Cognos Analytics is a business intelligence and performance management software platform that is used to create dashboards, reports, and data visualizations.
      OvalEdge uses Cognos Analytics REST API and JDBC Driver to connect to the data source, which allows users to crawl data objects (Reports, Modules, Exploration) and build Lineage.
    • SAP SuccessFactors Connector: SAP SuccessFactors provides cloud-based software for human capital management. Using the Software as a Service model. 
      OvalEdge uses the REST API to connect to the data source, which allows users to Crawl, Profile data objects (Tables, Table Columns). 
  • New Advanced Jobs
    • GDQR Custom Query Process: This advanced job executes the query sequentially based on the information provided in the input file and provides the result of the last executed query in an excel sheet. 
      Note: The advanced job can be used for all the RDBMS connectors.
    • Qliksense CustomFields: This advanced job retrieves the custom field information for the Qliksense connector from the client-server and displays it in the application.
    • Loading QVDS: This advanced job fetches the QVDs from the network path to the local path, which helps build lineage for the dashboards of the Qliksense connector. 
    • SAP BO Last Accessed Date Updater: This job updates the Last Accessed Date of the SAP BO reports available in the OvalEdge application based on the remote audit events.
    • Hopsworks Table Lineage: This advanced job assists the user in building lineage between two future groups for the Hopsworks connector.
    • Delete Duplicate Records From Oesecure Table: This advanced job deletes the duplicate records from the Oesecure table.
    • DSAR API SYNC: This advanced job caches DSAR API results and stores them in the cache table for the better performance of DSAR API.
    • Servicedesk V1: This advanced job helps to migrate existing service desk templates to a new version. This allows users to select existing templates and fill out the mandatory fields before raising service requests on multiple objects for multiple users. 
    • Load Scope and SysId Into Tables: This advanced job fetches the scope and sysid from the input file and stores it in the OvalEdge database. 
    • Snowflake Tag Sync Service: This advanced job retrieves the tags from the Snowflake database and displays them in the OvalEdge application.
    • TeradataLineageJobForExternalSourceFile: This advanced job assists the user in building lineage using the source file from the WhereScape Red tool for the Teradata connector. 
    • Tableau Usage Analysis: This advanced job fetches the Tableau usage (the most visited user) details from the source system, and the details will be displayed on the Top Users. 
    • Get queries form Vertica by Using a query: This advanced job fetches the query from a .txt file and executes it in vertica db. As a result, the bunch of queries available in the vertica db will be fetched and displayed in the data catalog queries along with the lineage.
    • Import SQL DQRules: This advanced job uploads Custom SQL Data Quality rules in bulk rather than manually entering them.
    • Code Custom Fields Options CleanUp: This advanced job enhances the performance and better search results associated with the Code Custom Fields.
  • New Configurations
    • glossary.association.count: This configuration allows users to update selected data objects with Managed Term Data Associations (example: Copy title to catalog, Copy business description to catalog). 
      Parameters: The default value is 20. Users can enter any value in the field provided. 
      • The synchronous process occurs if the number of data objects is less than or equal to the default value. 
      • The asynchronous process occurs if the number of data objects exceeds the default value. 
    • max.characters.count.for.data.story: This configuration allows users to define the maximum character count allowed for a Data Story.
      The default value is empty, which allows 10000 characters. Users can enter the desired value in the field provided.
    • tablequerylimit: This configuration allows the users to set limits for table queries when retrieving remote tables.
    • ai.associate.object.threshold.score: This configuration allows the user to set the value of the threshold score to directly associate a term with a data object without having to manually Accept/Reject a Term recommendation on a data object.
      The default value is set to 0. Users can enter the threshold value in the field provided.
    • bg.term.governanceroles.copytocatalog: This configuration allows to show/hide the copy Steward/Owner/Custodian options under Manage Associations in Business Glossary | Term Detailed page. 
      • If the configuration is set to true, then the options are displayed under the Manage Associations tab.
      • If the configuration is set to false, then the options are not displayed under the Manage Associations tab.



  • For the Force Reset Password for Database Authentication, OvalEdge now allows new users to reset their password upon logging in for the first time.
  • In the Set Password page, an eye icon provides an enable/disable option to view or hide the entered password.  
  • When a password is updated, a notification is sent to the user.
  • OvalEdge now supports encrypted hash passwords along with a basic password.
  • Globalsearch is enhanced with a new Inbox tab for viewing collaboration messages pertaining to the search results.
  • Using Globalsearch result after adding an data object to the default project. It is now possible to remove the data object from the default project. 
  • The Bookmark User Interface has been redesigned to display the ‘Add Bookmark’ window.
  • The Chrome Extension now links to the service request ticket page when users submit a Suggest a Term or Data Quality request.
  • The expanded Main Menu view will stay expanded and will not collapse when the page is reloaded.
  • The Update Helpful Resource pop-up is enhanced to add the Resource Name first and then Resource Link. Also, the existing Helpful resource name is displayed with a background color.
  • The Chrome Extension for Tableau now provides individual URL links for different reports in the same workbook.


  • In Tags, an option is provided to keep the tag profile picture empty.
  • The Parent Tag column in the List View has been enhanced with a filter option to search and select multiple parents simultaneously.
  • When assigning Tags using Tags API, both oeschema and schema were being shown for data objects, but now to maintain consistency, only the oeschema is displayed. 

Data Catalog

  • A key column is added to the tabular plugin to display whether any table column contains PK - Primary Key or FK - Foreign Key data.
  • The visual representation of the navigation flow (breadcrumb) is improvised to display an object name with its full path and hyperlink. When the user clicks on the hyperlink, the respective page is displayed.
  • The Impacted Objects can now be added to data object summary.
  • The Quick Tips option is removed from the Data Catalog Nine Dots menu.
  • All the Columns and Tables of a specific schema can be profiled using Profile option.
  • Data Type Size column field is added to the tabular plugin to provide data type size information.
  • In Data Catalog | Codes now displays the username beside the query version.
  • The Quick View icon is now available in the Data Catalog for all the data objects to provide a data object summary.
  • The filter option is added instead of the search option in the below modules.
  • Data Catalog | Databases | Schema
  • Service Desk Template | Request Type, Object Type, Created by and Updated by
  • Jobs | Job Status
  • Governance Catalog | Certification Policy | Status
  • Users & Roles | Roles | User License Type
  • Users & Roles | Users & Roles | User Full Name
  • Administration | Security | Database | Schema, Status
  • Administration | Security | Report Group | Report Group Type
    • In the Data Catalog | Reports, PowerBI Report visualization is now authenticated, requiring user credentials to view.
    • Reporting Framework is improvised to generate a database report based on the analysis of objects added, modified, and deleted between the time period of the last crawled date and the current crawled date.
    • A See more / See less button is provided to show lengthy contents of the Business Description, Technical Description, and Source Description fields.
    • To differentiate between tags and DAGs, the DAG suffix is written in square brackets when data object details are downloaded into an excel sheet.
    • Configure Search Keywords can only be added or edited by users with Meta-Write permissions. Users with Meta Read Permissions can only view or use search keywords in GlobalSearch.
    • The certificate logs are now archived for future reference and auditing.
    • Last Meta Sync Date option has been added to the Configure View options.
    • Data Catalog| Folders | File icon is replaced with folder icon.
    • The Last Crawled Date field displays the latest date and time on which crawling is performed on the data object.
    • In the data catalog, the certification columns now display icons instead of text.
    • In Data Catalog | Data Object | Summary | Nine Dots, after creating a service request, when the user clicks on the service requests count by default, it filters the object ID in the service desk page. Now it is improvised to filter the service request id (Ticket Id) when the user clicks on the service request count. 
    • The projects column field now displays the projects associated with a data object by displaying the project names separated by commas rather than the numbers 0, 1, or 2, which displays the total number of projects associated with a data object.
    • The Reports Group column field in the tabular plugin now includes a select all checkbox to select multiple reports at a time.
    • In the tabular plugin, the Governance Roles Columns (Steward, Custodian, and Owner) now is enhanced with a filter option for searching and multi-selecting multiple users at the same time.
    • The Top Users field now displays all team members in a tooltip when it is hovered on.
    • User can now view all the objects, including tags, terms, codes etc., in a new tab from the quick view | view details option.
    • Administrators can now select 'Set as default for all users' under Views| Public Views to make a selected public view the default view for all users.

    Business Glossary

    • Business Glossary tabular plugin now sorts results ascendingly (A-Z) instead of descendingly (Z-A).
    • The Change Domain option is newly added to change the domain of a Term.
    • The Draft Term option is now available in the Tree View, and ADD a Term and Suggest a Term option is available in both theTree View and List View.
    • A user can now click on the domain to view its hierarchy, and by clicking on the small triangle next to the domain name, the hierarchy can be collapsed.
    • In the conflicting situations between enforcing policies using the Term and Security, the Term policy takes precedence. Now, the admin user is restricted from modifying the column policies from the security module if the Term policy is enforced.
    • When a domain for a specific term is changed, now a caution message is displayed whether to update the governance roles of the term according to the new domain or migrate the previous governance roles.
    • For a Term, a Cascade checkbox option is provided under Manage Data Associations for applying Governance roles to associated data objects and their child objects (schema - table - table columns).
    • In the Term summary, now a Service Request Count field is added to view the count of service requests raised for the term, along with the hyperlink that navigates to the service request details.

    Data Stories

    • The default character limit for data story content increased from 10,000 to 100,000 characters. Here a  configuration is provided to set max character count limit for data story content. The max limit can be set to 100,000 characters.
    • Users can now add videos to a story.


    • In the Data Lineage Dashboard, for the sankey view, now a tooltip is provided to display the source/destination object details along with the count of lower level data objects associated with it. When the user hovers over the node, the tooltip will be displayed.


    • The Last Activity on field column is included in the Projects tabular plugin to display the date and time when the project was last updated.
    • In the Project Summary | Nine Dots menu, the new option “Update Owner” is included to update the project owner.
    • In the Projects, an option to search for the status of the project is provided while modifying the existing project.
    • In Project | By using the right click option, a user can easily open a selected object associated with a project in a new tab.

    Service Desk

    • New Database Profile request templates now display only the schemas associated with the selected connection.
    • New Business Glossary Creation Request now displays categories and subcategories associated with the selected domain.
    • When a ServiceNow ticket for API access is generated, now the user can access the ServiceNow ticket details in a new tab rather than opening in the same tab.
      • When a service request is closed or resolved, users can now add and view comments.
    • While creating a content change request, now the user can see the existing business description, custom field information, etc., for the selected object.
    • In Service Desk, after creating a new Business Glossary creation request, when the user was trying to edit or update the field values after saving the details and refreshing the page, the updated values were not displayed. Now it is improvised to view the saved changes after refreshing the page.

    Governance Catalog

    • In the User’s List, the status column is now available to display the ‘Active/Inactive’ status of the users.
    • In the Certification Policy, a confirmation popup will now appear before deleting a Certification Policy.

    My Resources

    • In My Resources, the collaboration feature now shows thread based notifications in the email. Each time any collaboration message is used, the Steward(s) of the data object are notified.
    • In My Resources | My Project Tasks, a download option has been added to the bottom right of the List View to allow users to download tasks/data objects.
    • In My Resources | My Profile, when the Slack checkbox is selected, notifications are sent to Slack.

    File Manager

    • In File Manager, for NFS connection, the Upload File Option is renamed to Upload File/Folder.
    • The Data tab of the Data Catalog didn't display the data after uploading and cataloging PDFs, Words, or PowerPoint documents from File Manager. This functionality has now been improved, and the data is displayed appropriately.


    • The Jobs module is enhanced with the 'Start Time' and 'End Time' columns to view the Job execution times.
    • When a job is triggered after refreshing the log value, it is not displaying the latest log. Now the functionality is improvised to display the latest log value automatically after refreshing the logs.
    • A new a job-based synchronization process for tickets with external integration systems is implemented, where upon approval, an alert will be displayed to the approver to confirm that the ticket has been approved and the job has been successfully submitted. In case of rejection, there won't be any job, but the rejector will still see an alert that it's rejected.

    Advanced Tools

    Impact Analysis

    • The Business users are now restricted from using the Impact Analysis Tool.

    Load Metadata from Files

    • In the Load Metadata from files, the ‘Template with Data’ option is enabled for the table column and dataset, and the Table Columns - Template with data is now made downloadable.
    • In Load Metadata from Files, now the user can download the Template with Data for the Data Quality Rules.
    • Users can now update the Gov Role users for Table Column objects using the Load Metadata from Files template. 
    • While updating report data from Load metadata from files, the owner and steward were not notified. Now it is improvised to send the notification to owners and stewards.
    • In Load Metadata from Files, the Term in ‘Published’ status can now be changed to ‘Draft’ status using load metadata from files in bulk, and the required fields can be modified to reflect the same in the application.
    • In Load Metadata from Files, after uploading a file with a valid query and invalid SQL type, the job status was displayed as success, and in the job logs, the quote was displayed in black color instead of red. Now, it is improvised to display the job status as ‘ERROR,’ and the quote is displayed in red color.
    • In the Load Metadata from Files , a template is included in the Users & Roles module for a team to migrate users and roles from a pre-production environment to a production environment

     Data & Metadata Changes

    • In the Data & Metadata changes, the Last Meta Sync Date column is newly added to Metadata changes-Tables/Queries/Reports.

    Temp Lineage Correction

    • In the Temp Lineage Correction, the job status is either empty or is not displayed. Now, it is improvised to display the job status as failure or success.

    Build Auto Lineage

    • In the Build Auto Lineage, an unprocessed filter option has been added to the status column for the reporting tools.


    • As part of this release, new APIs are introduced along with modifications to existing APIs, which enhance current functionality and improve usability.
      • New APIs
        • In the Business Glossary APIs, a new GET request (/api/businessglossary/domain/getBusinessTermsDomainWise) is introduced to fetch the details of the terms based on domain types. 
          API Name: GET /api/businessglossary/domain/getBusinessTermsDomainWise
        • In the Custom Fields APIs, a new POST (/api/addCustomFields) is introduced to add a custom field for an object by providing the object name and object type.
          API Name: POST /api/addCustomFields
        • In the Security APIs, a new GET request (/api/fetchUserPrivilegesOnObject) is introduced to fetch a user's permissions on a particular object.
          API Name: GET /api/fetchUserPrivilegesOnObject
      • Modified APIs
        • The term ‘Connection’, which refers to the connectivity to a source data system for crawling and profiling metadata has been changed to ‘Connector’. This change has been reflected in all the APIs that use connector as a parameter. 
          For more information on the API Changes, please refer to the API Changes in OvalEdge Release6.0.2 article.



    • In the Manage Connection pop-up, users can now select OAuth2.0 authentication and can provide the following details.
      • Client ID
      • Username
      • Token URL
      • Certificate Path
      • Company ID
      • Whenever crawling takes longer time to load schemas a spinner is displayed on the Connector page.
      • SAP Connector, the Crawl/Profile page settings now display SAP Module names, abbreviations, and table counts. 
      • A search field can search modules or tables based on the selected modules. 
      • Module names are limited to 4-5 characters. Based on selected tables, the crawled date, crawled status, profiled date, and profiled status are displayed in a tabular plugin with a delete option to delete the table line item.
      • SAP BODS Connector capability is enhanced to handle Global variables in SQL and to replace them with default values to build the lineage.
      • PowerBI Reports, users can now build lineage from the Data Flows.
      • Snowflake Connector, a visualization report can now be generated based on the RDAM activities performed on it for the last 24 hours with the option to download it. 
      • Snowflake Connector now supports JavaScript Stored Procedures where parsing of the javascript query can be performed to build the lineage.
      • SAP SuccessFactors Connector is enhanced with OAuth2.0 Token access authentication enabling users to provide passwords for data security. 
      • Databricks Connector, a new JAR library, is installed on the client cluster to support Databricks encryption of PII information.
      • Databricks Connector, Ovaledge now supports SQL Data Warehouse connectivity 
      • Delta Lake Connector, is now enhanced with the Auto lineage license type to build lineage for the views.
      • Denodo Connector is now improvised to build lineage for the source code with XML format.
      • Power BI Connector, the reports from OneDrive can be crawled through Power BI connecter by entering the OneDrive ID and validating it in the PowerBI connector settings.
      • In the Connectors Settings | Remote Access, the label name of Remote Access, Remote Data Access Management, and Remote Policy is renamed to Data Access, Data Access Management, and Connector Policies.
      • In the Connectors Settings | Others, the Data Custodian option is now available to send metadata change notifications to the custodian.

      Users & Roles

      • In the Users & Roles, when a new role is created, a team will be automatically created with the same role name. Whenever a user is removed from the same role or when a new user is added to it, the same user will be removed from the team or will be added to the team, respectively.
        The auto-creation of the team will be controlled by automatic.team.enabled configuration.
      • In the Users & Roles | Connector Users, to add a new connector user, it is now required to enter the First Name, Last Name and Email Address. 
      • In the Users & Roles Management, the user tab is provided with a ‘Team’ column. It helps the user to understand what type of user has grouped in a team. If any user is added to any team, users can see the team name under the team column to which they belong. 
      • In the Users & Roles Management | Teams, while assigning a user to a team, the label name in the right pane of the pop-up window is changed from Assigned Teams to Assigned to Teams for better clarity.
      • In the Users & Roles Management | Users, the label name from one of the Nine dots options is changed from Delete User to Delete/Deactivate User.
      • In the Users & Roles Management, OvalEdge now automatically updates Users and Roles in OKTA.
      • When a user is deleted from OKTA, OvalEdge will automatically sync with it to resolve the license compliance issue.
      • When the user's licensing type is changed through Role addition or deletion, it will be reflected in OvalEdge.
      • Administrators are now notified by email when it is time to renew the application license. The license expiry email will be sent periodically when the license expires in 28 days, 21 days, 14 days, and less than 7 days. 
      • In the Users & Roles | User tab, if an admin user belongs to SAML or SSO source of login, the edit option is enhanced to allow admin users to use the inline edit icon for modifying the user profile details such as First Name, Last Name, Job Title, Address, Email, Slack Id, and Phone number.


      • In the Security | Database tab now shows all available schemas regardless of whether they have been crawled or not. Users can filter those non-crawled schemas using the “Crawled” column to provide permissions. 
      • In the Security | Report tab is enhanced with the 'Path' column, which helps the user to distinguish the report having the same name. With this, users will be able to search reports  and understand whether the report is duplicated or it is different reports in different path locations.
      • In the Security | Application tab earlier, the enable/disable option for OvalEdge API was unavailable. Now it is improvised to provide Business User Permission and Roles-based permission to the OvalEdge API.
      • In the Security | Application tab, a search option is now available for the ‘Modified By’ and filter option for ‘Modified On’ column.
      • In the Security, when a Privacy Term status is changed from PUBLISHED to DRAFT, the content of the table column is displayed as masked. Now it is improvised to display the content as unmasked when the Privacy term status is changed to DRAFT.
      • In the Security | Applications tab, if the user disables the 'Role-Base-Permission' for an application, then the ‘Available Role’ column is enhanced to hide the roles in the Available Role column. 

      Service Desk Template

      • In the Service Desk Template, the create new template button was enabled for all the application users. However, only OE_Admin users have the privilege to create a new service request template. Now, the create new template button is disabled for all the users other than OE_Admin users.
      • In the Service Desk Template, there was no provision to create a custom template for Report columns. Now, the custom template option is available for the report column. Additionally, these custom templates will also be displayed on the report column summary  | Nine dots | Service desk for easy access of the user to raise a service request. 
      • In Service Desk Template, Azure DevOps Integration, while creating a ticket in Azure DevOps, the user could not switch from one instance to another. Now, it is improvised to assist the user in switching from one instance to another by cleaning up the old instance.
      • In the Service Desk Template, the other mapper options are now disabled when one mapper is enabled.

      Advanced Job

      • In the Advanced Job, the input template (.xls) of the 'Load DataID Details' advanced job is now enhanced with the 'comment' column to reflect the same in the output template (.xls).
      • The Advanced Job tabular plugin includes a field, Available Role, that allows admin users to add Roles with Author & Analytical License, to edit attributes, and run advanced jobs.
      • In Advanced Job, now the connection Id column is removed from the template of GDQR Custom Query Process advance job. Here the advanced job will now be executed by reading the connection id information from the attribute.


      • In the Schedule, active status of a scheduled task is now displayed as Yes or No instead of 0 or 1.


      • In the Configuration | Notifications, email notifications are configured to send emails without any password authentication. Here the SMTP is now validated without using a password.
      • The ldapext(OVALEDGE_SECURITY_TYPE) configuration is removed. 
      • The Configuration Key (Ovaledge.login.application) is moved from the Others Tab to Users & Roles Tab.
      • In the Configurations, a new key (oasis.properties = db. password. encrypted) is added to the oasis.properties file to provide the encrypted password in the DB password field.
      • Every configuration line item now includes a History icon to keep track of who, when, and what made changes to the configuration.
      • AI Recommendations now support Report Columns.

      Audit Trails

      • The Audit Trails now allows users to view deleted terms.
      • In the Object Privileges, the object type filter menu items are re-labeled from OETABLE to TABLE, OEDATABASE to DATABASE, and OESCHEMA to SCHEMA.
      • In the Audit Trails, the log out time of the user logged in via SSO will now be displayed on the User | Logins Audit trail.

      Bug Fixes

      The following bugs have been fixed in this release, and the application is working as it is expected.


      1. On the home page, the Pin to Header option is unresponsive when the user tries to bookmark any subfolder.
      2. Using Service Accounts when logging in to applications, users are experiencing errors. 
      3. In Tables & Views, Files & Folders, and Reports, the counts are not displayed.
      4. While creating a new password, the password guidelines are not displayed
      5. In the Globalsearch, the last modified date field is displayed with the created date. 
      6. In the Globalsearch, when the user searches the object all the search keywords configured to the data objects are not displayed.
      7. In the Globalsearch results, the user was unable to find the SSIS package information.
      8. The Globalsearch option displays irrelevant information instead of Domain.story.
      9. In the Global search, whenever a user searches for a data story, it will display a list of data stories available, and when a user hover on a particular data story, it displays the content of the entire story in the tooltip instead of showing domain name and story name. 
      10. The user is not able to navigate to the same data object using the ‘recent search’ option in the global search drop-down window after searching with Globalsearch.
      11. The OE Login page displays the “Forgot Password” link when the user logs in using an SSO credential. The “Forgot Password” link is removed when login is via SSO credential. 
      12. Users onboarded to OvalEdge through OKTA were sent an email notification to change the user password. Now it is fixed to send only the confirmation email to the user after creating an account in OvalEdge through OKTA
      13. In Home Page | If the user searches and selects a particular data object in the Search box, the search result is redirected to the wrong page
      14. While reloading a page or while switching from one module to another, the user was getting a 504 error in the application.

      Access Cart

      In the Access Cart, when the access request is raised on oracle tables for both select and insert privileges, only the select privileges are getting displayed in the ticket.


      1. In the Tag Page, while loading the associated objects count a spinner is introduced to let the users know that OvalEdge is working on getting the requested information.
      2. The partial tag names are shown when a user removes or adds a tag.
      3. The child tag icon disappears whenever the See all button under child tags is clicked.
      4. After creating a tag and deleting it, users were unable to create a tag with the same name. It was throwing an error.

      Data Catalog

      1. In the OvalEdge Application, the drag and drop option of data objects is disabled for users.
      2. In the Data Catalog, any newly added custom field shows as the first row. However, it's shown as the last row when designed on the catalog page.
      3.  In Data Catalog, while running the upstream/downstream copy metadata, a warning is displayed instead of just a confirmation popup.
      4. In the Data Catalog, the see more/see less option redirects the user to the tags/terms page instead of displaying the information in the same page.
      5. Top users now display user names instead of userID or login information.
      6. Pagination controls were not working on tables.
      7. The extension is showing as "csv" for gz files.
      8. The assigned tags are showing in both new tags and assigned tags pop up
      9. The data object count in Databases and Tables were not displayed in the bottom download option after migration. 
      10. Sorting columns in Data Catalog clears additional filters that have been applied.
      11. Users searching queries using deleted query ids were throwing incorrect error messages.
      12. Data Catalog Tables were displaying duplicate tables.
      13. For References, the Advanced operators (eight dots) were not functional.
      14. The table content for Business Description was blank, but could be viewed when the edit icon was clicked in Data Catalog.
      15. File columns in the left panel overlapped in the Files | Column details page.
      16. Now the Nine Dots options display relevant options for selected code tabs (Lineage, Associations,  References) and other relevant options are disabled.
      17. A problem occurred when sending messages via Nine dots' 'Send Message' option.
      18. In Data Catalog | Databases, 'Table Count' and 'Row Count' were displayed as '0 count' for a few schemas.
      19. Previously, timestamps were displayed using the local time of the database, these have now been changed to display server time zones.
      20. Pattern Relationships, when the filter applied to Tables and Schemas, repetitive options appeared.
      21. A popup with the reason is displayed instead of an error message when a user is unable to add a data object to the access card.
      22. Business users were able to add pattern relationships to the relationship at the column level.
      23. In the data catalog,  the column summary page is not displaying minimum or maximum values, but the values are displayed in the top right Row Count window.
      24. In Column Details | Relationships | the business users were able to toggle the ‘Show in ER Relationships’ button for the relationships added at column level.
      25. In the Data Catalog | Queries | Results, users were able to edit the query results.
      26. If Copy Title to Catalog option under Manage Associations is checked, and the data object is associated with a term, Then the existing title of the data object is replaced with the title of the Term associated with it and it will be reverted back to the initial title if the term and data object are dissociated.
      27. Performance issues while searching keywords using Business Descriptions and Technical Descriptions.
      28. In the Data Catalog | Data Object | Lineage, a few connector icons are broken in the lineage graph.
      29. In the Data Catalog | Reports | Lineage, the alphabet of the column names were overlapped, and the pointing arrow was missing in the lineage diagram for the looker connector.
      30. In the Data catalog | Quick view, when a user opens and closes the Quick View for data objects, the Edit business description popup is displayed. 
      31. User was able to save details entered in "Process upstream/downstream objects" window without being prompted to fill out mandatory fields in the Data Catalog | Table Objects.
      32. In the Data catalog | Code, the downloaded code count is more than the actual download count. The Download result is incorrect if the user downloads code. 
      33. In Data Catalog | Report tab, column type is displayed instead of Report Type. 
      34. In the Data Catalog | Table | Lineage, the user was unable to view the column mapping for few data sources despite having references for that column.
      35. In the Data Catalog | Table, when a user entered a desired page number in the pagination box, it did not display the desired table page.  Pagination control was not functional. 
      36. In Data Catalog, after adding any url link in the business description and technical description, the user was unable to open that link in a new tab.
      37. In Data Catalog | Table Columns, when the user downloaded the data, the downloaded file was displaying the data with some special characters.
      38. In Data Catalog, the object count displayed near the pagination after applying filters in the source description was mismatching with the actual count.
      39. In the Data Catalog | Term filter option does not return accurate results. When the user filters with the term “PII.Address”, it displays irrelevant results that contain “PII.EmailAddress”. 
      40. In the Data Catalog | Table Column Summary, The business and technical descriptions mentioned are not getting displayed.

      Business Glossary

      1. In the Business Glossary, the search result is not working properly for the subcategory level, It is showing duplicate subcategories in the same domain for different terms, even subcategories not present
      2. Weightage configuration for AI recommendations is corrected in the backend as it appears in the frontend.
      3. When deleting Terms using Load Metadata from Files with either wrong ID or Term Name the Job logs clearly shows the status' ‘No Delete are not matched’’ instead of deleting the Term from the application.
      4. The @ annotations in a business description were causing problems in navigating to data objects.
      5. Although permissions were disabled from Administration| Security| Applications, public users could still view the tree view and list view in Business Glossary.
      6. In the business glossary, removing code custom fields value is returning an error.
      7. In the Business Glossary | List view, the user is able to view only a fraction of the terms, and no scroll bar or “Show More” button.
      8. In Business Glossary, the user was unable to publish the term after associating objects to it.
      9. In Business Glossary, while creating a term, the Add Term pop-up window did not allow the user to select a domain. Instead, the domain that was recently used to create a domain was displayed.
      10. In Business Glossary | Term Summary, the Top users button was not clickable to view all the users. Now, the ‘SEE ALL’ option is provided to view all the users.
      11. In Business Glossary | Term Summary, users were unable to change the term status from published to draft.
      12. When the Don't Cascade option is selected when updating Gov Roles on data objects, the columns are still updated with the details of the users of the gov role. This has been fixed to the intended behavior.

      Data Stories

      1. In Data Story, while copying the rows from excel, the content displayed differs with respect to the operating system used.
      2. Error message is displayed while creating a data story.
      3. The images saved to data stories when edited are getting deleted.
      4. When a user copies and pastes a table from google doc sheet to Data Story | Edit Description. It is copied properly in MAC OS and whereas in Windows OS it displays only a single line. 
      5. When a user copies and pastes a table or an image, it is not showing in the Data Story. 


      1. In the All Reports Dashboard, users are unable to see the text under Tableau Reports.
      2. In the Data Literacy Dashboard not all reports are being displayed.
      3. The Home View tab has been removed from the Dashboard home page. 
      4. The application is throwing an error when the user is trying to view the DQ Dashboard Score on a particular object.


      1. Users were not able to add Users to the project task notes using @annotations.
      2. In the Project, Invite User List displayed a deactivated user name in the User List that was deleted from the OE application. The Invite User List should not display the deactivated user when that user was deleted from the OE application. 
      3. The Collaboration tool did not display all users or codes when @annotation was used to add users or codes.
      4. In the Project | Invite Users, if user invites any other user, ‘User List’ will display the Full Name of the user invited but when page is refreshed again it was displaying the First Name only in the User List
      5. The downloaded file did not contain any information except the path to the file when the user downloaded the project's information.
      6. In the Projects | Collaboration, instead of showing Codes, still showing Query.
      7. In Projects | Board view, after changing the assignee of a project, the assignee name and updated date were not updated unless the user refreshes the page.

      Service Desk

      1. In Service Desk | Waiting My Approval, the sort option is not available in the Age and Pending Since column.
      2. Service Desk templates were not opening from the Data Catalog or Service Desk module.
      3. When the user creates a table access request for API connector, the Axiomatics Policy is not getting created in the application. Also, the name of the access request template is displaying New External Access instead of API Access Request.
      4. Application Owner and Application Technical Lead are mandatory fields in the API Access Request template.
      5. During the API Access Request approval process, the approver encountered some issues. Also, the Application ID placeholder was different in API Access Request Template.
      6. For a Content Change Request for Business Glossary, when the user is trying to add a tag, the DAG tags are also getting displayed in the pop-up window.
      7. Even after the Admin user approves the ticket, the ticket was not getting created in JIRA using the JIRA integration feature.
      8. In the email notification sent to approvers after the user creates an API access request, the subject line was different from API Access Request.
      9. In the Snowflake connector, when a data object is selected to raise an access request through Data catalog | Nine dots | Access Request. In the 'Access Request' form, the error prompted when the user was searching for a product in the product dropdown list. The user was unable to search the product list.
      10. In the Snowflake connector, when a user select a data object and raise an access request access from Data Catalog | Tables | Nine dots | Servicedesk| Access Request.On the Request Access form, all buttons except the Submit Request Access button were not visible. 
      11. While creating a ‘Database Profile Request’, after entering all the mandatory details and saving it, the database name did not appear in the Service Desk | Request summary. 
      12. While creating a new ‘Data Quality Request’ on Table Column, the object name in the service request template is different from the selected object.
      13. In Service Desk while integrating with Azure Devops with acceptance criteria in the OE Mapper fields. When a user using the same service desk template to raise the ticket and approver failed to approve the ticket.
      14. In Service Desk despite the expiration date being passed to the creation date, the user could create an 'Access Request'.
      15. The approved ServiceNow ticket was displaying a ‘Zero’ status instead of ‘Open’ status.
      16. An approver approves a service request during this process if the ticket fails. The log error message should capture the reason in the Servicedesk comment box.

      Governance Catalog 

      1. In the DQR Function window, if the user types special characters % or ^ in the search box. It doesn't search for any functions and displays an error message.
      2. In Data Classification | Tables, after assigning tags to the object, when the user was trying to remove the associated tags from nine dots, the associated tags were not displayed.
      3. In the Data Classification, removing tags from multiple data objects using the Nine Dots option is displaying all the tags existing in the application instead of assigned tags.
      4. The Add Tag option was not responding and the Remove Tag pop-up window displayed all tags in the application instead of assigned tags.
      5. In the Governance Catalog | Data Quality, the Data Quality Rule was unable to execute the ‘HAS_NO_NULL_VALUE(FC)’ for .CSV File size of 700 MB due to unsupported characters for the huge file.
      6. In the Certification Policy, the ‘Created By’ field in the tabular plugin displayed the user who created the domain instead of the user who created the certification policy.

      My Resources

      1. In the My Resources | My Desk, when user clicks on any Governance Roles | Report Group, it is navigating to the Administration | Security | Report Groups, instead of Data Catalog | Reports.
      2. Error message not being displayed even though the mandatory fields in the update password page are not entered. 
      3. My permissions page is getting blocked when governance roles are updated in Administration | Security | Governance rules
      4. Unable to save the profile picture
      5. In My Resource | My Profile, the profile picture was not updated because of space or special characters in the image file. The profile picture can be changed with the image name having no special character or space.

      File Manager

      1. Users are experiencing page freezing when trying to open files in File Manager.
      2. When the Profile Folder Assuming Same Content is selected, profiling doesn't take place if the folder contains unsupported files or no files at all. Previously, the job status was displayed as successful, but now it displays, “the folder cannot be profiled since the file is unsupported or does not exist in the folder ”.

      Query Sheet

      1. In the Query Sheet and Data Catalog | Codes module, MRDR users were able to perform create, select, insert, update, delete, truncate commands. MRDR users should only be able to use the Select command.
      2. Users had difficulty reading the Query in an unstructured manner. The syntax of the query format was fixed for better readability.  


      1. Whenever the Job is being executed there is a null value, a validation is added to the null pointer and it is fixed.
      2. The Job Logs displayed inappropriate message logs when Term fields are modified in the Published status and uploaded to the application using Load Metadata from Files.
      3. In Jobs > Logs, when the user is deleting an existing Lineage an error is displayed.

      Advanced Tools 

      Impact Analysis

      1. In Impact Analysis, the Source object type was displayed incorrectly. Instead of the ‘Fact Table’ object type it displayed the Source object type as ‘View’.
      2. In Impact Analysis, the user was unable to download the file with more than 38000 records of impacted objects.


      User was facing some server error while trying to execute an alert from the Job Workflow.

      Build Auto Lineage

      1. In Build Auto Lineage, the lineage status ‘UNPROCESSED’ was displayed twice.
      2. In Build Auto Lineage, the ‘last updated count’ was not displayed for the Qlik Sense and SAP BO connector.
      3. In Build Auto Lineage, for the queries with no lineage, the lineage status is displayed as Success Lineage Build.
      4. Users are unable to build lineage for 'Select Statements' from the SQL Server connector.
      5. After building the lineage for SQL server connector from Advanced Tools | Build Auto Lineage, for a particular object from the same connector, a few records were displayed blank on the Lineage Maintenance page due to some orphan record.
      6. The source for column lineage is not being precisely identified during the lineage building process.

      Compare Schema

      In Compare Schema, following the execution of the comparison job for a schema, after clicking on the column object name, it isn't navigating to the Data Catalog | Selected object summary. Instead, a blank screen was displayed.

      Load Metadata from Files

      1. In Business Glossary, the detailed description column is not displaying the new values, while uploading an excel sheet using the load metadata option.
      2. In Business Glossary, the status of the job is displayed as a success even when the application returns an error while uploading an excel sheet using the load metadata option.
      3. When a user Loads metadata from files, custom fields are not getting updated.
      4. In the Load Metadata from Files, when the user downloaded the Report Column template with data the custom field information was missing in the template despite being available in the application.
      5. Data Catalog was not displaying the Schema metadata information when loaded using the template from Load metadata from files.
      6. Data Catalog was not displaying the Table metadata information when loaded using the template from Load metadata from files.
      7. When a user downloads a Template with Data from Load Metadata from file, the name of the download file is not displayed the same.
      8. When loading Term details using Load Metadata from Files, the Gov Role field details were getting updated with the current user name details.
      9. While importing data from load metadata from files to add a custom field to the terms, the job log's description was incorrect.
      10. In Load Metadata from Files, the user was unable to download the Business Glossary template with data.
      11. The Application security setting was not working for Advanced Tools | Compare Profile Results.
      12. Using the Load Metadata from Files | Business Glossary template, the user was unable to associate the terms with the data objects.
      13. In Load Metadata from Files, after downloading the ‘template with data’ for table and table column, changing the file name, and uploading the template, when the user downloaded the template with data again, the uploaded information was missing in the template.
      14. In Load Metadata from Files, uploading the template with data for table columns was taking more time than usual.
      15. In the Load Metadata from Files | the Customer user was not able to load custom field names due to the limitation of the length of up to 16 characters. Now it is enhanced to accept the name of a custom field of more than 16 characters.
      16. In the Load Metadata from Files, a user creates a custom field in the Business Glossary with Text Code, Number, and Date, then adds values to it. Using Load Metadata from Files, the user downloaded the template with the data, but the Date custom field's values were not captured in the file.
      17.  In the Load Metadata from Files, when custom fields are updated using load metadata from files template, the job logs are not getting displayed for the updated custom fields.
      18. When a users trying to update Term details by downloading Term details from Nine dots and updating into the application using Load Metadata from files, there was an issue, and now users are able to update a specific term details using Load meta
      19. In the process of uploading the business glossary template through load metadata, data was not being updated for domain names that were bigger than 32 characters.

      Data & Metadata Changes

      In the Data & Metadata Changes | Codes, the downloaded file was not displaying the appropriate information.

      Temp Lineage Correction

      1. Microstrategy connector lineage is getting mapped to temporary tables rather than to the actual tables available in the OvalEdge application.
      2. In Advanced Tools | Temp Lineage Correction, after running the recommendations, the last job status was not reflected appropriately. It was displaying as ‘Recommendations not yet run for this schema’ even if the job status was successful.
      3. For SSRS connection | Metadata was not being fetched for files with .xml extension and also the temp lineage.


      There was no option to add tables to existing schemas for RDBMS connections using the API’s. Now, tables can be added to existing Schemas using the API’s.



      1. In Connector, in the popup window of Select Import Schema for Crawling and Profiling, the search icon suggestion was showing incorrect search results for columns of (1) Last crawl Status, (2) Last Crawl Date, and (3) Last Profile Status.
      2. There was a technical issue with the Java Jar upgrade that prevented the user from crawling the MSTR connector and retrieving dossiers and documents.
      3. In the Connectors Page, while editing the existing connector settings an error is displayed.
      4. A delimiter error occurred in the partition file when profiling the HDFS connector
      5. The simple-xml jar file was causing connector vulnerabilities.
      6. For any connector, after a crawl, the description from the source should be displayed in the source description rather than the technical description.
      7. Users could not validate the connection in the Cloud Instance with Bridge as it was throwing an error. 
      8. Users could not 'Crawl/Profile' the Snowflake database after establishing a connection via key pair Authentication and Bridge.


      In the Workday Connector, There is a mismatch with the JSON files while crawling.

      SAP BODS

      1. SAP BODS, lineage building was interrupted.
      2. For the SAP BODS connector, after recrawling the failed job and building lineage for the same, the lineage failed, with the status 'parse failed' for some of the queries.


      1. Hive Connector was unable to crawl the schema due to a table name with a reserved name. For this, a query is written to crawl the table name with reserved words.
      2. For the Hive connector, a few queries failed resulting in failure in lineage building.
      3. In both Qlik Sense and RWB connectors, when navigating to the Edit Setting option, NULL attributes were displayed as errors. 

      SAP SuccessFactors

      SuccessFactors Connector was unable to crawl EmpJobs into Ovaledge. 


      Although the Salesforce connector was profiled successfully. In the Data Catalog Summary page, the user was not able to see the row count of a table.

      SAP BO

      1. There is no report group available when the user clicks the Crawl radio button in the 'Select Important Schema For Crawling and Profiling' popup.
      2. When the user was trying to build a lineage using the ‘@prompt function’ in the query, it displayed the lineage status as Success Lineage does not exist.
      3. In SAP BO connector | In command reports, Failed Exceptions occur because the query is not picked up by the lineage if it has the same report name in different reports groups of the same connection.


      1. If a Snowflake connector is crawled, the crawler job is displaying ‘Partial Success’ due to more number of tables in the crawling activity taking a long time to fetch the tables in Snowflake. Now, a few tables are fetched based on the limit setting made in the configuration.
      2. Whenever a user was crawling Snowflake Schema, Job Log was displaying partial success for few schemas due to usage permission.


      In the OData (Open Data Protocol) connector, the user was not able to profile the schema(s). The profiling process was prevented and did not proceed due to error messages about truncated data. It also displayed that the profile had been processed, but there was no profile result. 

      SQL Server  

      1. In the SQL server, when the user profiles a table displays error messages for a few columns, including java.sql.SQLException: Invalid column name 'ID' and 'Bad SQL Grammar', because the column was not present in the source system.
      2. SQL Server connector, the column lineage was missing despite having data movement.

      Azure Data Factory

      1. When a user crawls an Azure Data Factory successfully, then in the Build Auto Lineage, table plug in display the object types are shown as ADF Pipeline and ADF Data Flow object types are displayed instead of Triggers.
      2. Metadata changes are not notified to users when reports are moved from inactive to active states. 


      1. The Informatica Power Center connector was successfully validated and connected to the Bridge environment. At the time of crawling the schema, Job Step Status displayed an error. 
      2. During crawling and profiling, the Informatica connector encountered migration issues.


      1. For the Redshift connector, there was a problem parsing stored procedures for lineage building.
      2. User was unable to build a lineage for the Redshift connector. It was throwing some errors.


      1. When the user was trying to open the Tableau report in Tableau with Chrome extension as well as in OvalEdge, he was logged out from the Tableau server. 
      2. For the Tableau connector, after building the lineage, the formula for the table column and table column type was not displayed on the Data Catalog | Table Column | Summary.
      3. When Tableau crawls a report, the source description should display in the source description rather than the technical description, and the details of the report's owner and creator should be displayed in custom fields.


      OE_Public Users with no privileges to the API connector could still view the objects from this connection in the Data Catalog.


      While crawling the MicroStrategy connector the user was getting a null exception error.


      For the DellBoomi connector, a few queries failed resulting in failure in lineage building.


      For the Hopsworks connector, duplicate entries were found in the lineage graph.


      1. In the Dremio connector, the Manage Connection pop-up window is updated with a version dropdown list so the user can choose between Dremio version numbers greater or less than 21 to make use of Apache Arrow Flight drivers available for Dremio.
      2. In the Query Sheet, the application is throwing an error while querying on the Dremio connector.


      In Oracle Connector, when a user was building a lineage a column was mapped incorrectly for some queries.


      While crawling MongoDB for a few schemas, the crawl was not working properly and the job was killed at the end.

      Azure AD

      Azure AD was unable to integrate with OvalEdge due to an Azure Key Vault issue.


      1. In the PowerBI connector, an error was encountered while crawling the PowerBi Report type “Paginated”.
      2. In the PowerBI connector, an error was encountered for exporting the PowerBI PBIX file. Advanced Job is configured to add a ‘Readtimeout’ parameter that gives read time out for exporting the PBIX report request. 
      3. After crawling the PowerBI connector, the user was unable to view some of the report columns due to an error in downloading the PBIX file.
      4. For PowerBI Connector, reports were not loading in the detailed page.


      1. PostgreSQL was not able to crawl the source type as 'View'.
      2. In PostgreSQL, while crawling and profiling schemas, jobs submitted have been canceled.  


      1. The source lineage for a few tables in the SSIS connector was missing, and for a few, it was displayed incorrectly.
      2. For a few SSIS packages, no status was displayed when users tried to build lineage.

      Informatica Connector

      For the Informatica connector, the lineage building failed due to some special characters in the source code.

      Qlik Sense

      For the Qlik Sense connector, a few objects in the master objects file could not be retrieved to the application after crawling.

      Delta Lake

      Delta Lake connector was earlier able to connect only to the data machine cluster. Now it is able to connect to the SQL warehouse cluster as well. 


      When a Greenhouse connector is crawled some of the columns are mismatched and missing from the tables. Here, by default the system is unable to retrieve all the columns. 

      Job Workflow

      1. In Job Workflow, when data quality rules are added to the workflow grid, the Data Quality Rule drop-down list is showing the wrong pagination.
      2. Job Workflow the users are unable to modify workflows that have multiple rows.
      3. In the Job Workflow, when a user deletes workflows on the 2nd page, the page is not refreshed to display the remaining workflows on the first page.

      Users & Roles

      1. Users & Roles Management | Team,  when the user clicks on the + icon and enters a name for the team, then clicks on the Save button. The error message 'Team cannot be empty' is displayed. 
      2. In the User & Roles | Login users were not able to register in the Registration page due to an exceeded number of users in the application. Unless the user is registered, it will not display in the login page. 
      3. Users onboarded to the OvalEdge application via Okta were automatically assigned with OE_Public roles if no role is defined to the user.
      4. The Delete button is enabled in the Teams tab for Business users.
      5. Extra white spaces are added to the team name when the user tries to search it by copying it.
      6. In the Users & Roles | Team, a filter icon was not available for team type on the team table plug-in.
      7. The Author & Analytical License Type users  were not able to change to the Business License Type if the user is associated with any data object as a Owner or steward.
      8. In the Users & Roles Management | Connector Policies tab, the filter option available on the columns (Source and Policy type) was not working for RDAM Connectors.
      9. The Users & Roles Management | Connector, the Connector Users, Connector Roles, and Connector Policies modules are missing the download option.
      10.  In Users & Roles, the user was getting errors while editing the user details. 
      11. The Source Type and Policy Type filters in the Administration > Users & Roles section were not working as expected.


      1. In Security, when the user creates a story zone, the name of the story zone appears twice in the Data Story module.
      2. In the Security | Domain tab, while updating the Governance Roles, the cascade and not cascade hierarchy functionalities are now working as expected.
      3. In Security | Table Columns | There was an issue saving allowed roles for masking policy at table column level.

      Service Desk Templates

      1. In the Service Desk Template, while creating a new custom template, after entering the object name and saving the details, the object name did not appear in the Service Desk | Request summary.
      2. An Access Request raised for External Access was displaying Processed even if it was Failed.
      3. For a service request with three-level approval, if the admin user approves the request at level three, then the first and second-level approver names are changed to the admin user name.
      4. In the content change request template, after adding a term, the same term is still displayed on the suggested term pane with enabled + icon.
      5. In the Service Desk Templates, the ‘Select tables’ field is improvised with a scroll bar instead of three dots, for easy access of the approver to view the objects before approving.
      6. In the Service Desk Template, after cloning a system template and making it inactive, the user was unable to publish and change the status to active.
      7. In the Service Desk Template, the user could not create a custom template for Business Glossary Object.
      8. In the Service Desk Template, the user was unable to remove/delete the fields from a custom service desk template.
      9. The requested for field in the service tickets now displays user sys_id and the requester field is empty 
      10. On the approval page for service requests, the Request URL field now includes a hyperlink for the users to navigate to the request URL.
      11. In Service Desk Templates, while switching to another template and returning to the existing page, any sorting filters applied were getting cleared.

      Advanced Jobs

      1. In Advanced Jobs, the extra space in the edit advanced job fields is removed.
      2. Executing the Migrate Data to Denormalized Tables advanced was displaying some errors.
      3. The Load DataID Details advanced job was not producing the correct details in the line column of the output file.
      4. The MicroStrategy Delta Lineage advanced job is working as expected.
      5. The AI_TERM_BUILD_SERVICE advance job is not working properly to create Terms.

      Custom Fields

      1. In Custom fields | Table Columns, when the date custom field for global is deleted, the connection level custom field is also getting deleted
      2. In Custom Fields | Code Custom Fields, after clicking on the back button, the user is redirected to some other pages in the application.
      3. Content entered in the custom field is misaligned.
      4. Code Custom fields are accepting duplicate values
      5. Code Custom Fields were not saving when the Save button was clicked in the pop-up window.
      6. The Code Custom fields displayed 'Select Code Custom Options' when edited and options were selected. The field now displays the options selected.
      7.  In Custom Fields, text overlaps when more information was added. Issue is resolved.
      8. The Date Custom field was taking default time instead of server time.
      9. When the Code Custom fields were edited, and options were selected, a message appears saying, "Select Code Custom Options." The field now displays the options selected rather than the select code custom options message.


      After scheduling a job from the Administration | Job Workflow, the job was not triggering at the scheduled time.


      1. If the expiry time for JWT bearer token is set to empty then the default expiry time is considered as 60 minutes.
      2. The server is not restarting when the configuration Ovaledge.admin.principal is set to empty.
      3. In the Configuration, the changes made in the values of ‘lineage.width.nodes’ and ‘lineage.height.nodes’ were not reflected on the Lineage graph.
      4. Configuration pagination.row.limit is not working as expected after updating.
      5. The subject and email format of the Axiomatics mail notifications have been modified in Configuration | SMTP notifications.

      Known Issue

      In Service Desk, if the approver doesn't have permission to the requested object, then post approval of the content change request, the tag/terms will not be associated with the requested object (fulfillment has to be done manually). i.e., the user having access to the requested object needs to associate the tag/term from the object page in the Data Catalog.

      Copyright © 2023, OvalEdge LLC, Peachtree Corners, GA USA