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

      Release6.0.2.8

      OvalEdge Release6.0.2.8 is a hotfix release that includes improvements to the connectors supported with Azure Key Vault cloud service.  

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

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Hotfix Release

      Release6.0.2.8

      		 Release6.0.2.8.6028.12657c4

      26 May 2023

      Improvement

      • Connectors 
        The connection process with Azure Key Vault cloud service has been improved for certain connectors. This enhancement includes the addition of the following fields in the Add Connector pop-up window.
        • Azure Data Factory Connector
          • Resource Group Name: It refers to a logical container that holds related Azure resources, including the Azure Data Factory instance. A resource group is used to organize and manage resources collectively, providing a way to manage access control, billing, monitoring, and deployment across multiple resources.
          • API Version: It refers to a specific version of the Azure Data Factory REST API used to interact with the Azure Data Factory service. The API version represents a specific set of functionality and behavior supported by the Azure Data Factory service at a given point in time.
        • Azure Synapse Connector
          • Hostname: It refers to the fully qualified domain name (FQDN) or the network address used to access and connect to the Azure Synapse Analytics service. It represents the specific server or endpoint where your Azure Synapse workspace or SQL pool is hosted.
          • Database: It refers to a logical container for organizing and managing data within the Azure Synapse Analytics service. It is a structured storage entity where users can store and organize related datasets, tables, views, stored procedures, and other database objects.
        • Power BI Connector
          • Tenant Name: It refers to the specific name or identifier associated with an organization or entity. It is primarily used when signing in to Power BI or accessing Power BI services and resources linked to a particular organization.
          • Files Path: It refers to the location or directory where external files, such as data files or other supporting files, are stored and accessed within a Power BI project or report. The Files Path specifies the file system path or URL to the folder or location where these files are located.
          • Hostname: It refers to the name or address of the Power BI service or server that hosts your Power BI content. It represents the location where your Power BI reports, dashboards, datasets, and other artifacts are published and made accessible.

      Bug Fixes

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

      1. Data Catalog
        1. In the Data Catalog, there was an issue where the Advanced Search Filter option, including Select Conditions such as Equals, Contains, End With, etc., was not available for certain Column Fields such as Technical Description, Business Description, etc. As a result, users could not search the data using these filters. However, this issue has been resolved, and now the Advanced Search Filter option is available for all Column Fields that have the Search option enabled.
      2. Business Glossary
        1. Whenever a user creates a category and sub-category under a term and clicks on the term name, the hierarchy of categories and subcategories under that term is not displayed in the Business Glossary's Tree View mode. However, this issue has been resolved, and now, in Tree View, all the categories and subcategories under that term are clearly visible.
        2. In the Business Glossary, within the Term Summary, there is a Related Objects pop-up. Previously, when users attempted to add related data to specific data objects such as Tables, Table Columns, Files, Reports, etc., the count of objects was not displayed under the respective Data Objects Icons. However, this issue has been resolved, and now the count of objects under each data object icon is properly displayed.
        3. In the Business Glossary, specifically within the Term Summary and Associated Data tab, there was an issue where the added data objects such as Schemas, Tables, Table Columns, Files, File Columns, etc., were not reflected in the Associated Data tab. However, they were correctly displayed in the Data Catalog under the corresponding Term Column. This issue has been resolved. Now, when data objects are added for a Term, they are correctly displayed both in the Business Glossary's Associated Data tab and in the Data Catalog under the corresponding Term Column.
        4. In the Business Glossary, when users select a Published Term and attempt to update the Governance Roles, a warning message stating "A background job is initiated" is displayed instead of "Term is in Published Status". However, this issue has been resolved. Now, for all Terms in Published Status, the option to update Governance Roles is disabled, clearly indicating that these Terms cannot be modified in respect of their Governance Roles.
        5. In the Business Glossary, there was an issue where, when users selected a Term and attempted to raise a service request by selecting the Term Metadata change request, the Business Description field was not indicated as a mandatory field in the service request pop-up. However, this issue has been resolved. Now, in the Term Metadata change request pop-up, all the mandatory fields, including the Business Description field, are properly represented with the * mark.
      3. Projects
        1. When users navigate to projects from My Resources, specifically through Inbox, Project Alerts, and selecting a Project Name to Edit Object Status, an issue occurred. If the object name contained spaces, the $ symbol would be displayed instead of the actual spaces between the characters. However, this issue has been resolved. Now, when accessing the Project Object Status tab, the proper object name is displayed, including spaces as intended. This ensures accurate representation of object names without substitution of symbols.
      4. Service Desk
        1. In the Service Desk, when the users raise the Service Request using any Custom Template the synchronization with the JIRA Ticket is getting failed and the Job Log Value Exception while syncing Service Request to External Ticketing Systems is displayed. However, this issue is resolved and whenever the Service Request using any Custom Template is raised the JIRA ticket is automatically created.
      5. Advanced Tools
        1. In the Advanced Tools, specifically in the Build Auto Lineage, an issue occurred where users applied filters to search for desired data in field columns such as Schema Name, Job Type, Code Name, and others. After applying the filters, users clicked on the view query icon to see the query popup. However, upon closing the popup, the filter option reloads the page to its original state. This would result in the loss of filtered data. This issue has been resolved. The Filters option on the Build Auto Lineage page now functions properly. Users can apply filters, view the query popup, and close it without page reloads.
        2. In the Advanced Tools, under Load Metadata from Files and the Business Glossary Template with Data, there was an issue where the object types mentioned in the template were not accurately reflected in the downloaded template along with the data. Only a few object types were displayed in the downloaded template. However, this issue has now been resolved. All the object types mentioned in the template are correctly displayed in the downloaded template with the accompanying data.
        3. In the Advanced Tools, specifically within Load Metadata from files and the Business Glossary Template, there was an issue where selecting the business glossary template and uploading it with data resulted in an error, and the data was not reflected in the Business Glossary. However, this issue has been resolved. Now, the system accurately displays the data entered in the template within the Business Glossary. 
      6. Administration

        1. In the Administration, specifically in Connectors, upon establishing the connection, when users select the relevant schema and initiate the Crawl & Profile option, the job is triggered. However, there was an issue where the job status remained "Running" instead of indicating "Success" or "Failure". Now, this issue has been resolved, and users can now successfully crawl and profile the selected schemas, with the job status accurately reflecting the outcome as either "Success" or "Failure".

        2. In the Administration, for Workday Connector, after crawling and profiling the data from the Workday data source, there was a mismatch between the profile statistics, such as the Row Count in the OvalEdge Data Catalog, and the actual row count present in the data source. However, this issue has been resolved, and the row count in the data catalog now accurately matches the row count in the data source.

        3. In the Administration, specifically in Job Workflow, there was an issue where clicking on the Job Workflow name in the left menu would result in the page continuously loading without displaying the Job Workflow home page. However, this issue has been resolved. Now, when a user clicks on the Job Workflow name, the appropriate page is displayed without prolonged loading.
        4. In the Administration | Custom Fields, deleted Code Custom Fields details appeared on the Data Catalog Data Object Summary page. When users navigated to the Data Catalog Data Object Summary page and reloaded it, the deleted Custom Fields were displayed. However, this issue has been resolved. Now, when custom fields are deleted, they are properly eliminated and no longer appear on the Data Object Summary page.
        5. In the Administration | Users & Roles | Users & Roles Tab, there was an issue where the system was unresponsive when users attempted to delete or deactivate existing "Users." As a result, the selected users were not successfully deleted or deactivated. However, this issue has been resolved. Now, users can successfully delete or deactivate desired users without system unresponsiveness. 

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