Release6.0.2.35

OvalEdge Release6.0.2.35 is a hotfix release that includes improvements to the SAML Authentication, Data Catalog, My Watchlist, Advanced Tools, and Connectors modules. Additionally, in this release the critical and significant bugs associated with the Data Catalog, Data Stories, Dashboard, Advanced Tools, and Connectors modules are fixed and working as expected

Improvements

Authentication

• OvalEdge provides a set of APIs that allow users to manage SAML (Security Assertion Markup Language) authentication. SAML is a standard protocol for single sign-on (SSO) authentication that enables seamless and secure user access across different applications. 
  To manage SAML authentication in OvalEdge, users can use the following APIs: 
  • Create User 
    Example Endpoint: POST/api/user/add 
  • Update User 
    Example Endpoint: POST/api/user/update 
  • Delete User 
    Example Endpoint: DELETE/api/user/delete 
  • Active/Inactive User 
    Example Endpoint: POST/api/user/status 
  • Add/Delete User Role(s) 
    Example Endpoint: POST/api/user/role 
  • Update User License 
    Example Endpoint: PUT/api/user/license

Data Catalog

• Within the Data Catalog's "Tables Summary" section, an issue was identified when users downloaded table metadata. Special characters present in the business/technical/source descriptions were not included in the downloaded content. This issue has been resolved; when the user downloads Tables Summary metadata, any special characters are accurately captured without loss, ensuring a complete and accurate representation.

My Resources

• Within the "My Resources" section, specifically in "My Watchlist," a new column called "Tags" has been introduced in the Tables and Table Columns List View. This addition facilitates the filtering of metadata and tracking of significant data changes for data objects based on tags.

Advanced Tools

• Within the "Load Metadata from Files'' feature, specifically in the Business Glossary Template, users faced an issue while uploading a template with data. An error occurred where the datatype length (max) was transformed to -1.0 instead of the intended -1, based on the data type size from the data catalog. This issue prevented users from successfully importing business descriptions for table columns. This issue has been resolved; users can now seamlessly import business descriptions for table columns without errors.

Connectors

• Oracle Service Cloud Connector Redesign: Now users can efficiently access and analyze data dictionary metadata, including table structures and attributes, via REST APIs. This update enables seamless crawling for data extraction and offers data profiling capabilities, providing valuable insights. The redesigned connector also intuitively handles metadata columns and relationships, integrating them into parent tables and identifying subtables via referenced URLs. This enhancement streamlines metadata utilization within Oracle Service Cloud.
• Previously, lineage construction was not implemented for the OPENQUERY function. OvalEdge has now introduced a solution specifically tailored for SQL Server to SQL Server scenarios. The OPENQUERY function serves as an ad-hoc approach to accessing remote server data. It's important to note that if frequent queries are made to the remote server, it's recommended to use the linked server instead. We have extended the implementation of OPENQUERY functionality to include not only SQL Server to SQL Server interactions but also to support connections between SQL Server and PostgreSQL/MySQL.

Bugs Fixes

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

Data Catalog

• In the Data Catalog, an issue arose when attempting to open various data objects like Tables, Table Columns, Files, File Columns, Reports, Report Columns, and codes in a new tab resulting in a blank screen being displayed as blocked. This issue has been resolved; users can now seamlessly view data objects in new tabs without encountering obstacles, ensuring a smoother experience within the Data Catalog.
• In the Data Catalog's List View previously displayed incorrect behavior for the advanced search operator "Greater Than" applied to the Row Count column. This issue has been resolved, and the "Greater Than" advanced search operation displays results accurately and correctly.
• In the Data Catalog's List View under the Table page, an issue occurred where clicking on the database name led to an incorrect page being displayed instead of the intended relevant page. This issue has been resolved; clicking on the database name now directs users to the relevant page, ensuring a smoother and more accurate navigation experience within the Data Catalog.
• In the Data Catalog's Tables and Codes section, specifically in the Lineage view, an issue was encountered after cataloging and building the lineage. There were some tables and codes missing from the source lineage, causing confusion for users attempting to understand the lineage construction process. This issue has been resolved; the source lineage now accurately displays all tables and codes in the source system, ensuring a clearer and more comprehensive understanding of the lineage-building process.
• In the Data Catalog's Reports Summary section, users faced limitations where hovering over the chart didn't display the count, and clicking on the report group bar failed to reveal details. This issue has been resolved; users can now effortlessly view the count on the chart upon hovering over it as well as access report group details by clicking on the respective bar.

Data Stories

• In the Data Stories feature, an issue occurred when users attempted to draft a story and used the "@" symbol to select items, resulting in an inability to fetch specific codes. Additionally, despite the presence of codes, a "no data found" message was displayed. Alongside this, users encountered an error message when attempting to reorder the story. These issues have been successfully resolved; users can select desired codes and seamlessly incorporate them into the story using the "@" symbol. Furthermore, reordering the story is now error-free, allowing users to arrange story elements as they prefer.
• In the Data Story feature, users previously faced limitations when adjusting column widths and using drag-and-drop functionality within a table. This issue has been addressed; users can now seamlessly modify table column widths and utilize the drag-and-drop feature as intended, enabling smoother formatting of table columns within the Data Story.

Dashboard

• In the Dashboard's Data Quality Score feature, a problem was identified with the search functionality for selecting specific table columns. As a result, users could not access the data quality scoreboard for their desired table columns. This issue has been successfully resolved; users can now utilize the search operation to locate table columns and seamlessly view their corresponding data quality scores.

Advanced Tools

• Previously, when conducting an Impact Analysis on over one thousand Source Objects, the system identified around one million impacted objects. However, attempting to access the list of these impacted objects led to a blank page displayed, followed by a 504 error. This issue has been resolved; users can now seamlessly view the complete list of impacted objects without encountering any errors.
• Within the Advanced Tools section, specifically in the Build Auto Lineage feature for the ADF Connector, an issue emerged where users could not successfully export the associated source code for ADF. Upon selecting the "Export Source code to file" option, the relevant job was executed, generating a download link for a .zip file. However, clicking on the file link led to a blank page. Now this issue has been resolved and the .zip file is correctly displayed in the designated temporary location, containing the relevant data.
• In the "Load Metadata From Files" section, specifically within the "Business Glossary Template," an issue arose where downloading the template, adding required values along with custom field entries, and then re-uploading the template resulted in the system failing to include the custom field values upon upload. This issue has been addressed; users can now expect custom field values provided in the business glossary template to be accurately retained upon reuploading, ensuring a seamless experience in managing metadata from files.

Connectors 

• For the SQL Server connection, users encountered an error when attempting to perform profiling operations. The error was related to a spacing issue within the "Email_Address" column, which prevented successful profiling. This issue has been resolved and profiling is performed on the data within SQL Server without interruption.
• For the NFS connector, a concern arose when users established a successful connection and initiated crawling. This resulted in the creation of duplicate folders appearing within the File Manager. This issue has been rectified and following the crawling process, files and folders are organized in a hierarchical structure without any duplicate instances, ensuring a streamlined and accurate representation.
• When using the NFS connector, the system was unable to perform profiling or generate statistics for files uploaded via the NFS. This issue has now been resolved successfully. The system now effectively profiles and derives comprehensive statistics for files uploaded through NFS, ensuring accurate insights are available.
• For the Power BI connection, users encountered an error when establishing the connection and performing crawling operations. The system displayed an error message indicating "Port is out of range" during connection validation and crawling attempts. This issue has been resolved; users can now seamlessly establish connections and conduct crawling operations without errors.
• For the Power BI connection, users faced difficulties building a lineage. Certain reports were not linked comprehensively, failing to capture all sources. Additionally, dependencies on other reports were also unnoticed. This issue has been resolved; users can build lineages with all selected reports.
• A client notified that the Tableau server received excessive traffic, totaling over a million hits from the OvalEdge Tableau account. Following this report, a thorough analysis of the issue was conducted and the issue was resolved by optimizing the code.
• For the AWS Athena connection, users encountered an error while profiling. This issue has been resolved; profiling can now be seamlessly conducted on data within AWS Athena without disruptions.

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