Release6.3.4.2

The OvalEdge Release6.3.4.2 introduces key enhancements, bug fixes, and change impact across various modules, improving functionality, usability, and system performance.

Key highlights include:

Release Type

Release Version

Build

<Release. Build Number. Release Stamp>

Build Date

Service Release

Release6.3.4.2

Data Lineage Dashboard

Known Issue

In the Lineage Dashboard, we see the ovaledgedb connection, which happens when the schema or connector containing lineage tables is deleted. This issue will be fixed in the upcoming release, and users will not see the OvalEdgedb in the lineage dashboard.

Data Quality

Fixed

In Data Quality Rule previously in Data Quality Rule execution, failed values appeared unmasked in the Data Quality Remediation Center (DQRC) and Notifications despite being correctly masked in Rule Executions and Object Executions. This issue is now resolved, and failed values are correctly masked across all relevant sections, ensuring consistency and data security.

Build Auto Lineage

Fixed

Go to Data Catalog > Report Columns > Select any object, then click on Lineage. In the tabular view, an issue where the icons for report columns were showing as tabular icons has been fixed. Now, the icon for the report column is showing correctly.
Go to Data Catalog > Tables and click the Has Lineage button; it navigates to the Lineage tab. Then, if the user clicks on Dashboard > Data Lineage and clicks on Lineage, again, if the user clicks on Data Catalog > Tables and clicks on Has Lineage, the page is not found error has been fixed. Now, if the user navigates from the Dashboard, able to view the Lineage.

Connectors

Fixed

In Administration > Connectors, when you crawl tables from the Salesforce connector, they are crawled into OvalEdge. If a table is deleted from Salesforce, it should automatically be marked inactive in OvalEdge after the next crawl. However, this process was slow and caused performance issues. Now, the issue has been resolved by optimizing the performance by simplifying the inactivation of tables while using relationships.
In Administration > Connectors > select any connector of type RDBMS or Report connector, go to Connector Settings and Others tab; an issue where when the user chooses any Team and saves changes and again navigates to Others tab, then the user is unable to see the added team is resolved. Now, the user can see the selected team.

New & Improved

In Administration > Connectors > OAS7 connector, AWS Secrets Manager has been introduced as a Credential Manager.

Reporting Framework

New & Improved

The ovaledgedb connector now supports Azure Key Vault and AWS Secrets Manager when users store their credentials in the oasis.properties file. While validating the ovaledgedb connector using these Credential Manager, the connector gets authenticated based on the values specified in the oasis.properties.file. This functionality has also been applied to Azure Entra ID and MariaDB connections.

Migrated the Reporting Framework (RFW) from file-based storage to Liquibase for improved data management and integrity.
- Previous Challenges:
  - Deleting and inserting RFW data led to data loss and disrupted associations.
- Enhancements with Liquibase:
  - Corrects inaccurate queries and ensures data consistency.
  - Inserts new scripts without affecting existing data.
  - It protects data and formatting, preventing any unintentional changes.