Release6.1.0.7

OvalEdge Release6.1.0.7 is a hotfix release that includes improvements to the connectors and advanced tools.

In this release, the critical and significant bugs associated with the Data Catalog, Business Glossary, Service Desk, My Resources, 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.1.0.7

Release6.1.0.7.6107.a226471

31 July, 2023

Improvements

Connector
Azure Data Factory (ADF): This release introduces support for crawling "Pipeline_Run_params" objects into OvalEdge and includes the implementation of loggers to track and identify root causes for any encountered difficulties. Job logs now provide valuable insights for effective issue diagnosis. Furthermore, this update resolves the previously encountered crawling process issue for "Pipeline_Run_params" objects into OvalEdge, ensuring successful completion. A code fix has been planned to address the root cause and will be implemented at a later stage.
Advanced Tools
In the "Load Metadata from Files" feature within Advanced Tools, specifically in the "Business Glossary Templates" section, a known issue was identified when uploading new terms for the first time. The governance roles associated with the newly uploaded terms failed to update as intended. However, this issue has been successfully resolved. Now, when uploading new terms for the first time, the governance roles are correctly updated as expected.

Bug Fixes

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

Data Catalog

In the Data Catalog, users faced an issue where after running a profile job for Azure Data Lake (ADL) in OvalEdge, they were unable to view sample data under the DATA TAB. The DATA TAB displayed a message indicating that no data existed, even though the profiling process had been completed. However, the issue has now been resolved. Users can now access and view the sample data in the DATA TAB successfully after the profiling process.
In the Data Catalog > Reports tab > The report column filter displayed an incorrect count of reports when compared with the total count of reports. This issue has now been resolved and the Report Type filter now accurately reflects the correct reports present in the catalog.
In the Data Catalog, users encountered an issue where the "Add to Impact Analysis" option from the Nine Dots menu was not clickable which prevented users from adding data objects to the Impact Analysis. This issue has now been resolved and the option is made clickable and fully functional.

Business Glossary

In the Business Glossary, the masking feature encountered issues with the "Number" and "Date" column types. Users reported that when adding new policies for these column types, the policies were not applied to the data as expected. However, this issue has been resolved. Now, users can successfully add new policies for the 'Number' and 'Date' column types, and masking is accurately applied to the designated columns as intended.
In the Business Glossary, specifically on the Summary Page, there is an issue where clicking on one checkbox unintentionally checks all the other checkboxes. This issue has been resolved and the checkboxes now function correctly.
In the Business Glossary, an issue was encountered where the "Approval By" and "Approver Date" fields are displayed when the term is in the "Draft" status. This issue has now been resolved and the fields are displayed only when the term is in the "Published" status. In the "Draft" status, these fields are appropriately hidden.
In the Business Glossary, when users select the "Copy to Steward," "Copy to Custodian," and "Copy to Owner" checkboxes and then publish the term, the expected results are not updating for that data object. This issue has been resolved and the selected checkboxes effectively update the steward, custodian, and owner fields for the published term, providing accurate and up-to-date information in the Business Glossary.

Service Desk

In the Service Desk module, users encountered spacing issues while creating new service desk templates. The problem was specifically related to the “filecolumn” and “GlobalDomain” objects, which resulted in errors during the template creation process. However, the issue has been resolved, and users can now create templates without facing any spacing issues related to the filecolumn and GlobalDomain objects. The template creation process is now smooth and error-free.

My Resources

In the "My Resources" > Notification section, users had reported an issue with the notification emails. The problem was related to the incorrect display of the special character “$” in the content of the emails. Additionally, the type of object referred to in the notifications was not spelled out, causing confusion and making it difficult for users to understand the context of the messages. However, the issue has been resolved, and users no longer experience any problems with special characters appearing incorrectly in the email content.
In the "My Resources" > Notifications section, users encountered a recurring issue where they received the same notification alert every half an hour for terms that were created. This constant and repetitive stream of notifications caused inconvenience and potential information overload for the customers. However, the issue has been successfully resolved. Users are no longer receiving the same notification alert repeatedly for the terms that were created.
In the "My Resources" > Notifications section, users encountered an issue with email entries being duplicated when a term is suggested through Load Metadata from Files. This issue has been resolved, and users will now receive a single email notification for each term suggestion, eliminating redundancy.
In the "My Resources" > Notifications section, users are experiencing the issue of receiving multiple emails for a single action. This issue has been addressed, and the system now sends only a single email for each action performed by the user.

Advanced Tools

In the “Impact Analysis”, users encountered an "HTTP status 500 - Internal Server Error" when they tried to access Impact Analysis. This issue prevented them from analyzing data dependencies effectively. The issue has been resolved, and users can now access Impact Analysis without encountering any "HTTP status 500 - Internal Server Error".
In the "Load Metadata from Files" > "Business Glossary Templates" section, users encountered an issue where they were unable to load the Business Glossary Templates. This problem impacted their access to the predefined templates, hindering their ability to maintain consistent data terminologies and definitions. However, the issue has been resolved, and users can now access and utilize the predefined templates without any problems.
In the "Load Metadata from Files" > "Business Glossary Templates" section, users encountered issues related to data associations, custom fields, tags, and governance roles. The checkbox behavior was incorrect, but refreshing the page resolved it. Moreover, the problems with tags not applying correctly through Load Metadata from Files and governance roles not updating as expected were also addressed. The issue has been resolved, and now all the issues related to data associations, custom fields, tags, and governance roles in "Load Metadata for Business Glossary" have been successfully fixed.

Administration

In the Administration | Security | Databases | List View, the Custodian filter is not functioning as expected. When users select specific custodians using the filter, the corresponding results fail to display in the list view. This issue has been successfully resolved and the relevant results are correctly displayed in the list view
In the Administration | Security | Databases | In the Status filter, when both the "Active" and "Inactive" checkboxes are selected only the "Inactive" results are displayed. As a result, users are unable to view the complete list of databases with both active and inactive statuses. The issue has been fixed, and the status filter now functions correctly.
In the Administration | Security | Applications, there is a tooltip issue where it incorrectly displays "disabled" even when the toggle for the application is set to "enabled." This issue is now resolved and the tooltip is displaying the correct status.

Connectors

For Azure Synapse Connector, users encountered an issue where certain procedures within specific source codes could not be parsed, leading to the inability to build lineage for those codes. This limitation hindered the ability to trace data flow and dependencies accurately. However, the issue has been addressed and resolved effectively. The system now successfully parses and interprets all procedures during the lineage-building process, enabling users to establish lineage for each source code accurately.