Release6.3.3

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

Key highlights include:

Minor Enhancements

• Home
  • Application Environment Differentiator
    A new feature has been added to allow users to easily distinguish between application environments (e.g., QA, Production, Staging) through Color Indicators and email subject lines.
    
    New System Settings in Administration > System Settings > Others:
    
    • Instance Name (ovaledge.instance.name): Allows users to specify the name of the current instance, such as QA, Prod, or Staging. The instance name is displayed on the home header, enabling users to identify the environment they are working in quickly.
    • Instance Color (ovaledge.instance.name.color): Enables users to assign a background color to the instance name (options include Red, Green, Yellow, and Blue). This color-coded feature helps users visually differentiate environments.
    Enhanced Email Notifications: The instance details are now included in the subject line of all email notifications, allowing users to identify the environment associated with each notification quickly.
• Data Catalog
  • Unauthorized Options Disabled for Better User Experience
    An improvement has been made to the Data Catalog summary page to address user confusion over unauthorized options. The system now disables options for users who lack the necessary permissions, clearly indicating accessible features based on their permissions. This enhancement improves the user experience and reduces confusion.
    
• Jobs
  • A new download option has been added to the bottom right of the Job Summary page. This feature allows users to download Job Summary details in a grid format, making it easier to analyze the overall job status and use the information for future reference.
• Data Quality
  • In the Data Quality Rules for Code Object Types, the Custom SQL Functions have been enhanced with a new option allowing users to choose whether to send failed rows to the Data Remediation Center. A toggle button, "Add Failed Rows to Remediation Center," is now available in the Rule Summary, giving users control over the handling of failed values. When this option is selected, all failed rows are automatically captured and displayed in the Data Remediation Center, enabling access for further review and remediation.
• Advanced Tools
  • ‘Correct Query' Option Enabled/Disabled for Report and ETL Connectors
    A new enhancement has been made so that the Correct Query option is enabled/disabled for Report and ETL connectors by configuring the "is. correct query.required to True/False" in System Settings > Lineage.
  • Plain Text Display for Business Description
    A new enhancement has been made so that for GET/API/schema/{schemaId}/tables API, any bullets, bold text, or other formatting in the business description will now be displayed as plain text.
• Administration
  • Connectors
    • Bridge Support Now Available for QlikView Connector
      In Administration > Connectors > Add Connector, bridge support has been added for the QlikView connector.
      
    • BigQuery Connector: License Count Managed by Server Field
      Administration > Connectors > BigQuery Connector: The license management for BigQuery connections has been enhanced. A new input field, Server, has been added and is now used to count the connector license usage. This improvement ensures that the license count does not increase based on each Project ID but is managed through the Server field, providing more efficient license utilization.
      
    • Data Pipeline Connector: Enhanced JSON Reference Path Reading
      A new enhancement allows the Data Pipeline connector to read the reference path from the JSON file during schema crawl.
  • Data Access
    • ‘Row Access Policy' Column is Removed from Table Security in OvalEdge
      A new enhancement has been made. Since OvalEdge does not support syncing row access policies from the data source, the 'Row Access Policy' column has been removed from Security > Table Security. The functionality will be available for the source systems supported in the Data Access Management module screens.
  • Security
    • Data Quality - Control Center Renamed to Data Quality - Remediation Center in Security module
      In the Administration > Security > Applications, the Data Quality - Control Center is renamed to Data Quality - Remediation Center, aligning with the module name (Data Quality > Data Quality Remediation Center)
      
  • Schedule
    • Administration > Schedule, an issue where the values in the Cron Entry(UTC) drop-down were showing blank has been fixed. Now, the values are showing in the drop-down list.

New System Settings

The latest release introduces new settings that enhance user control over the application's behavior.

New Advanced Jobs

The latest release introduces a set of new advanced jobs that allow users to update the data specific to modules or features using advanced algorithms.

Note: Please don't run the advanced job "Restore BusinessGlossary SourceInfo" until further notice. This job is currently under investigation. An update will be provided once it is confirmed safe to proceed with this operation.

Bug Fixes

In Release6.3.3, the following bugs have been resolved, ensuring the OvalEdge application functions as expected.

• Home
  • On the Home Page, an issue where the IDs for My Approval and My Requests were not showing in sequence has been fixed. Now, the service requests are showing in the correct sequence.
  • When Elastic Search was configured successfully, the tooltip label in the OvalEdge header initially displayed as "Elastic Search." However, after refreshing the page or navigating to another module, the tooltip label changed to "Global Search" when searching for content using the main header. This issue has been resolved. The tooltip label now consistently displays as "Elastic Search," even after refreshing the page or navigating to different modules.
• Data Catalog
  • In Data Catalog > Reports, an issue where the crawled Power BI API report count in the application did not match the API GET metrics has been resolved. Users can now see an exact match between the application's API report count and the API GET metrics.
  • In the Data Catalog, the issue of enabling Calculate Relationships for all data types—profiled, unprofiled, and sample profiled—has been resolved. Users can now enable Calculate Relationships only for profiled and sample profiled data, not for unprofiled data.
  • In Data Catalog > Table Column/File Column Summary, the issue where the Top Values sort option only worked the first time has been resolved. Users can now sort Top Values as many times as needed.
  • In Data Catalog > Table Columns, an issue where all Table Columns information was downloaded from a configured view regardless of the custom fields filter condition has been resolved. Users can now download information specific to the applied custom fields filter condition.
  • In the Data Catalog, previously, when a user updated governance roles for a table column and navigated to My Profile > Inbox > Data Catalog tab, clicking on the object name displayed an error message stating, "Object is no longer available." This issue has now been resolved, and users can now click on the object name to view the respective object page in the Data Catalog.
  • In Data Catalog > Object Summary, an issue preventing users from adding child tags to an object in the Data Catalog when using the Micro Edge browser has been resolved. Users can now successfully add child tags to Data Catalog objects.
  • In the Data Catalog > File Columns, the issue of Box connector file columns not displaying in the Data Catalog or included in the downloaded LMDF (Load Metadata from File) file has been resolved. Users can now view these file columns in the Data Catalog and the downloaded LMDF file.
  • In the Data Catalog > Codes, an issue that caused the % symbol to be automatically converted to $ during the update and execution of saved query codes has been resolved. Users can now execute their codes without any unintended value conversions.
• Business Glossary
  • In the Business Glossary > Term summary, an issue with the invisibility of Vertica table columns not found from the add objects pop-up screen has been resolved. Users can now view and select the Vertica table columns as per their requirements.
  • The following are the scenarios for publishing a term: 
    • In Administration > System Settings > Others, the default configured values—Owner, Custodian, Steward, and Governance Roles 4, 5, & 6—for the system setting (business glossary.term.publish) allow these roles to publish a term. 
    • If Governance Roles are not set at the Term level, they will be inherited from the Domain level. 
    • A Viewer user cannot publish a Term.

• • In the Business Glossary > List View 
    • An issue that prevented users from downloading filtered draft domain(s) after applying the domain filter has been resolved. Users can now download the filtered draft domain(s) without errors. 
    • After applying the domain filter with equal conditions for any Governance Role, the following issues have been resolved. 
      • In simple mode: The issue with no data download has been resolved. 
      • In Detailed mode: The issue with downloading all information related to the domain has been resolved. Users can now download domain-related information specific to the applied condition.
• Dashboards
  • In Dashboard Reports, the issue of OvalEdge DB reports displaying values as "NaN" in PIE or BAR charts has been resolved. Users will now see the actual values instead of "NaN."
• Projects
  • In Projects, an issue where adding a comment at the object level showed an admin profile icon has been resolved. Now, users will only see their logged-in profile icon while commenting.
• Service Desk
  • In the Service Desk has been resolved where users encountered difficulty creating new service requests using data object templates, such as the Table Metadata Change Request template. Previously, when users clicked Select Object during the selection phase, the Select Object pop-up displayed object names that appeared blurred, making it challenging to read or select the desired objects. This issue has now been fixed, and the Select Object pop-up window clearly displays all object names, allowing users to easily identify and select objects.

Governance Catalog

• Data Classification Reports 
  • In the Data Classification Reports, classifications associated with Report Columns object types are displayed in the Report Columns tab. Previously, when users attempted to filter classifications based on the Report Type filter, the Report Type column appeared empty, preventing users from filtering the classifications effectively. This issue has now been resolved, and the Report Type filter is functioning as expected, allowing users to filter classifications in the Report Columns using the Report Type filter.
• GDPR ROPA
  • In GDPR ROPA > Reports > Update Governance Roles, an issue with fetching governance roles 4,5 and 6 while updating the Governance Roles from nine dots has been resolved. Users can now view the fetched governance roles 4,5 and 6.
• Jobs
  • On the Job Summary page, under Job Execution History, clicking the count link in the Success column for any row resulted in a "Bad URL—400" error page. This issue has been resolved. Clicking the count link now correctly redirects users to the Job main page, which displays all successful job details.
• Advanced Tools
  • In the Advanced Tools > Impact Analysis > Select Impacted Object > Click Impacted Objects tab > Go to Nine dots > Download Impacted Objects. An issue where the objects were downloaded twice the number from the given range has been fixed. Now, the downloaded objects are showing in the given range.
  • In Advanced Tools > Impact Analysis, an issue with displaying the impacted levels in the wrong order has been resolved. Users can now view the impacted levels in the proper order.
  • In Advanced Tools > Build Auto Lineage, an issue while building lineage for the Dataset semantic tables expression, a new type of MCode function used in an expression, i.e PostgreSql.Database() has been resolved. Now that function is handled and the lineage is populated for the expression as well.

Administration 

• Connectors
  • For the Azure SQL Managed Instance connector, go to Advanced Tools > Build Auto Lineage. For Parse Failed queries, click on Correct Query, correct the query, and validate it. Previously, an incorrect status message was displayed, but it has now been updated to show the correct message: 'Success Lineage Does Not Exist.'
  • For the Oracle Connector, applying a Regex pattern to include or exclude schemas under Crawler rules did not work correctly. The schemas matching the Regex pattern were not loaded in the "Select Schema to Crawl & Profile" pop-up, and an incorrect error message appeared: "Oops! Technical Issue. Retry later. We apologize for the inconvenience." This issue is now resolved. Schemas matching the Regex pattern are correctly displayed in the "Select Schema to Crawl & Profile" pop-up, and a valid error message is shown if no schemas match the pattern.
  • For Power BI Connector, the issue with previewing Power BI paginated reports has been resolved. Users can now preview Power BI paginated reports without any problems.
  • For Informatica connector, an issue where columns did not display formulas, even when specific auto-lineage code columns had formulas, has been resolved. Users can now view column formulas without any issues.
  • For API Connectors, previously, after establishing and validating a connection, users encountered an error when attempting to Crawl/Profile a YAML file. The job logs incorrectly displayed an error message stating, "No API exists in remote for API group: ovaledgefiles." This issue has now been resolved, allowing users to successfully crawl data from the YAML file and view it in the data catalog.
  • For the Salesforce connector, an issue where crawling the Salesforce connector took too long and killed the job, has been fixed. It can now crawl successfully with less time.
  • For the QlikSense, BigQuery, Snowflake, Azure Data Factory, Azure ML, FME, and Qlik View, in Administration > Security, if governance roles 4, 5, and 6 were deselected, then in the connector creation pop-up, the governance roles will not display. Again, go to Security and select the governance roles in the 4, 5, and 6 checkboxes. Then go to Adminstrator > Connectors > Nine-dots > Edit Connector. A null exception was shown. This issue has been resolved, and if governance roles 4, 5, and 6 are entered in the Edit Connector pop-up, save and validate it. The entered governance roles 4, 5, and 6 are showing.
  • For the Tableau connector, an issue was encountered when using the OvalEdge Browser Extension. If the Tableau API version selected during connection setup was not 3.9, Certified Tableau View Type Reports did not display in the OvalEdge Browser Extension.
• Data Access
  • Administration > Data Access: An issue where the Data Access Module was incorrectly enabled when no connectors supported Data Access Management has been resolved. The Data Access Module is now disabled.
• Schedule
  • Administration > Schedule: An issue where the values in the Cron Entry(UTC) drop-down list were showing blank has been fixed. Now, the values are showing in the drop-down list.
• System Settings
  • In System Settings, under the SSO tab, when the hide.saml.login setting was configured to "true," clicking the OvalEdge App icon on the Clients Apps page directed users to the OvalEdge Login screen, requiring them to enter their credentials instead of logging in automatically. This issue has been resolved. Clicking the OvalEdge App icon takes users to the OvalEdge Home page without additional login steps.
• Application Diagnostics
  • In Administration > Application Diagnostics > Log Viewer, the issue of displaying an invalid path during log file download has been resolved. Now, users can download the log file without encountering this error.

Known Issue

Data Catalog

• In the Data Catalog > Custom View, an issue exists where objects associated with categories, subcategories, and classifications display correctly in the grid view, but the downloaded template shows blank values for these columns. This issue is scheduled to be resolved in the upcoming release.

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