OvalEdge Releases
      Back to home
      1. Knowledge Base
      2. Architecture, Security & Releases
      3. OvalEdge Releases

      Release6.0.2.4

      OvalEdge Release6.0.2.4 is a hotfix release that includes improvements to the Home, Data Catalog, Business Glossary, Service Desk, Advanced Tools, and Administration modules.


      In this release, the critical and significant bugs associated with the Home, Data Catalog, Business Glossary, Advanced Tools, and Connectors modules are fixed and working as expected.

      Release Type  Release Version Build
      <Release. Build Number. Release Stamp>      		 Build Date

      Hotfix Release

      Release6.0.2.4

      		 Release6.0.2.4.6024.

      09 April 2023

      Improvements

      • Home
        • The Global Search Results now include a new "Quick View" option that allows users to quickly view the summary of data objects. Within the Quick View Summary, a "View Details" option is also provided, allowing users to access more detailed information such as Data, Entity Relationship, Lineage, References, and Column Details associated with the selected data object from the Data Catalog page.
      • Data Catalog
        • In the Data Catalog | Codes | Code Name | In the Code Summary details a new field Lineage Status is included to display the status of the Lineage as either "Success Lineage Build" or "Unprocessed".
      • Business Glossary
        • In the Business Glossary, previously only terms in “Published” status were able to be associated with data objects. However, the existing functionality has been improved to allow users to now associate terms in "Draft" status with data objects as well.
      • Service Desk
        • In Service Desk, when a user submits a request to create a new term, a new option is now available for the user to choose between a draft or published state for the term.
      • Advanced Tools
        • The Build Auto Lineage now includes enhancements to the "Correct Query" information with the following additions:
          • Code Name: A "Search" option has been added to assist users in searching for a specific code by name.
          • Code: A "Search" option has been added to assist users in searching for a specific code based on code operations such as "SELECT", "FROM", and others.
          • Query ID: A "Search" option has been added to assist users in searching for a specific code by ID.
          • Status: The “Filter” option is provided to view the status of the lineage as either “SUCCESS” or “ERROR” or “SUBMITTED”.
          • Created Date: The “Sorting” option is provided that enables users to sort and view code details related to a specific schema for the selected connector according to the date it was created.
        • In the Load Metadata from Files | Lineage Template now includes the "Action" column. Users can perform various operations on the lineage template sheet's data, including adding, editing, and deleting information. Users can add, edit, and delete data associated with columns like SourceConnection, SourceSchema, TargetConnection, TargetSchema, TargetName, TargetType, etc.
        • In the APIs, users can now add Code Custom Fields options to the OvalEdge supported APIs such as User API, Data Quality Rule API, Service Desk API, Business Glossary API, Tag API, Security API, Connector API, etc.
      • Administration
        • In the Service Desk Template |  Edit Service Desk Template | In the Nine Dots, the "Move to Draft" and "Delete Template" options are now disabled for system-specific templates. As a result, users cannot move system-specific service request templates to draft and edit existing template fields or delete system-specific templates.
        • In Configuration | Others, a new configuration called “oe.globalsearch.searchorder” has been added to control the order in which the search results appear on the Global Search page.
        • In Configuration | Others, a new configuration called “homepage.welcomestory.fullsize” has been added to control the display of the welcome story.
          • The default value is False.
            • If the user sets the default value to True, the welcome story will be displayed to its maximum size.
            • If the user sets the default value to False, the welcome story will be displayed within a limited size with "See more" and "See less" options.
        • In Configuration | Others, a new configuration called “Oderbycreateddate” has been added to configure the order of the API output based on the created date of terms.
          • The default value is False.
            • If the user sets the default value to True, the API output will display the latest terms first.
            • If the user sets the default value set to False, the API  displays terms in alphabetical order based on the domain name.

      Bug Fixes

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

      1. Home
        1. In the Home | Bookmarks, previously, there was an issue on the homepage where added bookmarks would overlap in the bookmarks pop-up and not display correctly. However, this issue has now been resolved and the bookmarks are being displayed clearly.
        2. In the Home | Catalog Highlights section, previously, there was an issue with the Top/Recent toggle button in the Catalog Highlights section where the results associated with different data objects such as Tables, Reports, Files, Codes, etc., were not displaying properly. However, this issue has been resolved now and the results for the data objects are being displayed according to the user's choice of top or recent.
      2. Data Catalog
        1. In the Data Catalog | Entity Relationships | Tabular View, the header columns filters in the Entity Relationships data grid were not functioning properly. However, this issue has now been resolved, and filters for each column name such as Base Connection Name, Base Asset Group Name, Base Table Name, Base Column Name, Base Table Row Count, etc are working properly.
        2. In the Data Catalog and Security, there was an issue in the Reports Tab data grid, where the search functionality for the Path column was not working properly. Specifically, if the user clicked on the Eight Dots and selected any condition filters such as Equals, Not Equals, etc., the results were not displayed correctly. However, this issue has been resolved and the conditional filters for the Path column are now working correctly.
      3. Business Glossary
        1. In the Business Glossary, under Term Summary and Manage Data Associations, the "Copy title to catalog" option was previously selected by default. However, this issue has now been resolved, and it is up to the user to choose whether or not to select this option.
      4. Advanced Tools
        1. In the Impact Analysis | Impact Analysis Name | Impacted Objects tab, whenever the user tries to download the selected impacted objects, an internal server error occurs and the object cannot be downloaded. However, this issue has now been resolved and the impacted objects can be successfully downloaded by the user.
        2. In the Build Auto Lineage, while building a column lineage feature there was an issue where it would get broken in the middle and not extend until the original source existed in the procedure. However, this issue has been resolved and column lineages can now be successfully built until the original source exists.
        3. In the Load Metadata from Files | Business Glossary Template, there was an issue with the Business Glossary Template, where error messages associated with the "No Action" column were not being displayed in the Jobs Logs. However, this issue has been resolved and appropriate error messages are now being displayed in the Jobs Logs.
        4. In the APIs | Report Group API, there was an issue with searching for report groups using the offset parameter, as not all report groups were being retrieved. However, this issue has now been resolved, and users can retrieve all report groups specific to their parameters.
      5. Connectors
        1. For the ADB Connector, even when the original tables exist, the lineage is built based on the temporary tables. This issue has now been resolved and the lineage is built using the original tables.
        2. For the Data Lake Connector, queries failed while parsing and lineage was unable to build from the data. However, this issue has now been resolved, and the lineage can be built successfully.
        3. For the Azure SQL Manager Connector, the profiling statistics for 'Views' were not being updated and displayed in the Data Catalog. However, this issue has been resolved and the profiling results are now being displayed on the Schema page of the Data Catalog.
        4. For the Snowflake Connector, in the Administration | Users & Roles | Connector Roles, the User Roles data related to Snowflake was not displayed on the Connector Roles page. However, this issue has been resolved now and the data is being displayed properly.

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