Release6.0.2.15

OvalEdge Release 6.0.2.15 is a hotfix release that includes improvements to Administration -  Users & Roles, System Settings, and Advanced Jobs modules.

In this release, the critical and significant bugs associated with the Global Search, Tags, Data Stories, Business Glossary, Data Catalog, Projects, My Resources, Data Quality Rules, Advanced Tools, Administration, and Connectors modules are fixed and working as expected.

Improvements

• Tags & Data Catalog
  • In the Tags | Association section, users are experiencing difficulties accessing the extreme right field details, and they require a horizontal scroll bar to view objects. In addition, the headers have been frozen to enhance the usability of the Associations section.
  • In the Data Catalog | Schema summary page, users are experiencing difficulties accessing the extreme right field details, and they require a horizontal scroll bar to view schema details. In addition, the headers have been frozen to enhance the usability of the Associations section.
• Administration
  • Advanced Jobs
    A new Advanced Job '"DbtFileParseAndUpdateDescription," has been deployed to automate extracting relevant data from the DBT file and synchronize it with the corresponding descriptions in OvalEdge.
  • Users and Roles
    Creating new users now supports the usage of spaces and special characters in the first name and last name fields. This enhancement allows for more flexibility and accommodates users with names that include spaces or special characters during the user creation process.
  • Configurations
    A new configuration, 'profile.all.files.enable', has been introduced in the 'Others' tab to facilitate the hiding/showing functionality of the 'Profile all Files' option within the File Summary >  Nine dots menu. If set to True, the ‘Profile all Files’ option will enable in the Nine Dots options menu; if set to False, the option will not be shown in the Nine Dots options menu.

Bug Fixes

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

1. Global Search
   1. In Global Search, there was an issue where data stories were not loading in the search results. This issue has been resolved. providing users to view and access relevant data stories for their search.
   2. In Global Search, users encountered an issue where the search results count displayed a high number for a specific keyword, even when the search results did not contain any relevant data objects. This issue has now been resolved and the search results display the number of relevant data objects matching the specified keyword.
2. Data Stories
   1. When adding a table in Data Stories using the table option from the toolbar, users encountered an alignment issue where the table would resize based on the content in the first column and row, resulting in uneven cell sizes and misalignment of data in subsequent columns and rows. The alignment issue has been resolved, and the table maintains consistent cell sizes, ensuring proper data alignment in all columns and rows.
3. Business Glossary 

   1. An issue was encountered where a column data object continued to appear in the Recommended tab of the Business Glossary, even after being recommended for a term. The problem has been resolved, and now, when a column data object is approved or rejected for a term, it is no longer displayed in the Recommended tab.

   2. In the Business Glossary, there was an issue where no error message was shown when attempting to suggest a term with the same name under the same domain. However, this issue has been resolved. Now, when trying to suggest a term with the same name under the same field in the Business Glossary, a prompt message will be displayed, indicating that it is not allowed.
   3. Previously, when attempting to download term details from the Business Glossary by clicking on the nine dots option, the downloaded Excel sheet did not include the term relationships. This issue has been resolved. Now, when downloading term details, the Term Relationships are included in the downloaded Excel sheet.
4. Data Catalog
   1. In Data Catalog | Tableau Reports, users were unable to retrieve reports during the crawling process and could not view the available views. However, both of these issues have been successfully resolved, restoring the functionality for retrieving reports and displaying views within the Data Catalog.
   2. In the Data Catalog | Tables section, there was an issue where downloading table metadata from the summary page did not display the complete content of the Business description in the field. This issue has been resolved and the full content of the Business description is displayed correctly.
   3. In the Data Catalog | Lineage, users previously encountered an error, where clicking on objects resulted in an inability to retrieve the desired information, impeding the navigation and exploration of object lineage. However, this issue has been resolved, enabling users to seamlessly click on objects within the lineage, and facilitating smooth navigation and exploration of the object lineage.
   4. In the Data Catalog, the breadcrumbs in the navigation path at the top of the page displayed the connector name twice. This duplication occurred because the schema label included both the connector name and the schema name, leading to an inaccurate representation of the navigation path. The issue has been resolved. The schema name in the breadcrumbs no longer includes the connector name, eliminating duplication. The navigation path now accurately represents the hierarchy as "connector name > schemaname'.
   5. In the Data Catalog, the issue with the tabular plugin, where the cell width was not adjusting correctly based on the field attributes, has been successfully resolved. The latest update ensures the complete information for the Domain, Category, and Subcategory fields is properly displayed. The cells now adjust their width appropriately, allowing for improved visibility and readability of the content.
5. Projects 
   1. In the My Access Cart project, there was an issue where the added objects did not display their corresponding Governance Roles in the tabular plugin. This issue has been resolved, and the governance roles are now correctly displaying for the added objects.
6. My Resources 
   1. In My Resources | My Permissions, there was an issue where the Governance role names were not updating after label changes from the Administration | Governance Roles section. This issue has been resolved. Now, in My Permissions, the corresponding Governance role names are successfully getting updated.
7. Data Quality Rules
   1. In Data Quality Rules, issues are encountered when attempting to remove a tag from the Data Quality Rules. This issue has been resolved and working fine.
8. Advanced Tools 
   1. In Lineage Maintenance, the Code Name field displayed duplicate values in the user interface when associating a source data object with another data object. However, this issue has been successfully resolved, ensuring that the code name field now correctly displays unique values, eliminating the occurrence of duplicate entries in the UI.
   2. In Load metadata from files, when using the template with data for Table Columns, there was an issue where the business descriptions were not getting updated when the template was loaded. This issue has been resolved and the Business Descriptions are getting updated upon loading the template.
   3. In Load metadata from files, previously users were able to create role names with special characters such as "@@@" or "@#$". However, code changes have been implemented to enforce a restriction, preventing the creation of role names with invalid characters.
   4. In Load Metadata from files, there was an issue where the Custom fields label or name was not being displayed in the headers column of the Excel sheet when downloading the template with data for Data Quality Rules. However, this issue has been addressed and the template now includes the configured Custom fields in the template headers when downloading templates with or without data for Data Quality Rules.
   5. In the Build Auto Lineage, users were encountering a 504 error when attempting to export the source code from the nine dots menu on the Auto Lineage page. This issue has been resolved and working fine.
   6. While Build Auto Lineage users experienced a 504 error when trying to export the source code from the nine dots options. However, this issue has been resolved and users can now successfully export the source code from the Auto Lineage page as intended.
   7. Administration
      1. In Advanced Jobs, when the "Build Lineage from extract queries" advanced job is executed, a file named "extract_queries.txt" is received. However, there was an issue with building the lineage from the extracted queries. This issue has now been resolved, and the lineage can be successfully built from the extracted queries.
      2. For Advanced Jobs ‘Build Lineage form Extract Queries’ and ‘Extract Queries from Source to Build Lineage’, the file path attribute now replaces the previously used temporary path to specify the exact location of the queries' text file to build lineage. The file path is the exact location of queries text file to build lineage ensuring accurate and reliable lineage creation based on the provided file path. 
      3. In Security | DAG, when a DAG is updated, there was an issue where the updated governance roles were not getting applied to the data object, and it continued to display the previous governance roles. This issue has now been resolved, and the governance roles are successfully getting updated as intended.
      4. In the User & Roles | Roles, users are encountering an error when attempting to update the role name This issue has now been resolved, allowing users to successfully modify role names.
      5. In the Configurations, a new configuration 'ovaledge.aws.ses.configset', has been added to the 'Others' tab to allow users to utilize the AWS SES (Simple Email Service) to send email notifications. To configure this feature, enter the credentials in the designated field provided. This will enable seamless communication through SES for sending reliable email notifications.
9. Connector
   1. For Workday Connector, there was an issue where the row count obtained during profiling did not match the actual row count. This issue has been resolved, and the profiling results now display the row count accurately with the actual count.
   2. For Matillion Connector, encountering an "access denied" error message when attempting to crawl. However, this issue has now been resolved, and users perform the crawling process.
   3. An issue was encountered during Sigma Connection validation, where a null point error occurred when the number of data objects was less than the specified pagination limit. However, this issue has been fixed, and the connection validation now functions smoothly, successfully validating the Sigma connection even with a smaller number of data objects.
   4. There was an issue while profiling Azure Data Lake connectors files. This issue is fixed now and files are getting profiled.
   5. For Azure Synapse Connector, there were issues encountered when fetching stored procedures due to improper structuring. This issue has been resolved, and users can now retrieve stored procedures.
   6. Migrating the Azure SQL Managed Instance connector from release 6.0_gamma to release 6.0.2.5, experienced malfunctioning, resulting in its improper functionality. However, this issue has been successfully resolved, restoring the normal operation of the connector.

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