OvalEdge Releases
      Back to home
      1. Knowledge Base
      2. Architecture, Security & Releases
      3. OvalEdge Releases

      Release 5.2.7

      About OvalEdge 5.2.7

      The OvalEdge 5.2.7 is the latest service release enhanced with the Business Glossary, Data Catalog, OvalEdge APIs, and Administration modules and the critical and significant bugs associated with the Data Catalog, Business Glossary, Governance Catalog, Query Sheet, Advanced Tools, and Administration modules are fixed and working as expected.

      Release Type                                        Release Date

      Service Release                                     25 February, 2022

      What's New

      • Business Glossary
        • In the Business Glossary, the existing functionality of assigning an Object to Domains is improvised from "Synonym of" with "Synonym to" Related Objects to overcome the confusion of adding objects to the domain. 
        • In the Business Glossary > Term > Summary, the new clock icon is included before the Business and Technical Description to view and download the business or technical description history associated with that particular Term.
      • SSRS Connector 
        • In the Crawler Information > SSRS Connector, the new feature associated with the file association is implemented to read the RDL & RDS files from the Local File System to the OvalEdge application.

      Improvements

      • Home 
        • In the Home page, if the user selects an object and navigates to the detailed page view of the Object. The Top Values are by default set to display in descending order. 
      • Data Catalog
        • In the Tables module, the users can now download the Tables and Table columns using the download icon placed at the bottom of the page.
      • Business Glossary
        • In the Business Glossary, when the user with the Steward privileges changes the term status from published to draft, the Initiate Workflow button is enabled, where the user can republish the Term, following the new term approval workflow process.
      • My Resources 
        • In the Inbox module, the "Filter Range" and "Select Date Filters" options are added to refine the message search process by defining the date using the drop-down option and calendar options.
      • Advanced Tools 
        • In the OvalEdge API > Term API > the new "API Delete" field is included to delete the Term.
      • Snowflake Connector 
        • In the Jobs module, the existing Job Logs for the Snowflake connector related to the RDAM is improvised to show the differentiation for user and roles between every crawl similar to the tables.

      Bug Fixes

      1. Data Catalog
        1. In the Data Catalog module, the issue of showing the duplicate data in Table, Table Column, Report, Report Column, and Queries data objects for any crawled connection is now fixed and working as expected.
        2. In the Data Catalog > Table > Table Name, the issue related to the system displaying the Null Density value as a negative value for the particular Table is now fixed and working as expected.
        3. In the Data Catalog, the issue related to the Security Masking Policy is not working correctly for the columns when the associated Term is in Draft status is now fixed and working as expected.
        4. In the Data Catalog, due to an issue related to an advanced job executed for reports, the Reports Summary page was not showing the result of the reports, and the system was unable to retrieve the total user list of reports. A few reports were also missing in the results, and the 'Last accessed date' for reports was not displayed. But now, this issue is resolved and working as expected.
      2. Business Glossary
        1. In the Business Glossary, when the user creates a Domain, Category, and Terms and creates a user with Public Role and add that user as Steward and when the user with Steward privileges login into the application and tries to edit the metadata like Title, Related Objects, Custom fields, Classifications, Associations, Tags, Description, and Detailed Description for that Term, the error message is displayed. But now, this issue is fixed and working as expected.
        2. In the Business Glossary, the issue related to the system displaying the recommendations for the deleted Term is now fixed and working as expected.
      3. Governance Catalog 
        1. In the Data Quality Rule module, when the user adds a new DQR with Validate Regex Function and provides the correct input, associates the Object to the Rule, and Runs the Rule, the Validate Regex functionality fails even after giving the valid input values. But now, this issue is resolved and working as expected.
        2. In the Data Quality Rule module, when the user adds a new DQR with File Rule Function, and adds Azure CSV File column, and adds Parquet File column, and makes the Rule active, and Runs the Rule through Advance Job file process, the error message "Not executed after running the Rule for File DQR Rules" is displayed. But now, this issue is resolved and working as expected.
        3. In the Data Classification module, when a user downloads a template file with terms of a business glossary, the RACI members associated with terms are displayed in the file. However, the name of the 'RACI member' column header was not displayed. But now, this issue is resolved and working as expected.
        4. In the Service Desk module, the issue related to the user's inability to raise the Ticket in the Team Level Stewardship case is now resolved and working as expected.
      4. Query Sheet 
        1. In the Query Sheet module, when the user selects the Salesforce Connector and Salesforce Schema and selects any Table associated with the Salesforce Connector, an error message "Unable to fetch results" is displayed. But now, this issue is resolved and working as expected.
      5. Advanced Tools 
        1. In the Impact Analysis module > Impact Analysis Name, whenever the user adds affected objects to impact analysis through the "Impact Type (DR or UR or U or D)" advanced job, the system is showing the wrong count for the No of Downstream Objects, No of Upstream Objects, No of Downstream Objects with Association, No of Upstream Objects with Association, Total No of Source Objects, and Total No of Impacted Objects. But now, this issue is resolved and working as expected.
        2. In the Impact Analysis data grid, the issue related to the Sorting and Search criteria on the Last Updated By column is now fixed and working as expected.
        3. In the Impact Analysis, to discover the impacted objects, users need to select a source object and perform impact analysis. Here the system should display a complete path with the report group, but the system was only showing the name of the report group. This issue is resolved, and the report group name and the complete path associated with the impacted objects are displayed.   
        4. In the Build Auto Lineage, the issue related to the mismatching of columns for the data uploaded through the CSV file template is now fixed and working as expected.
        5. In the Build Auto Lineage, when a user selects the report which has queries and clicks on the 9-dots and selects the Build Lineage for all queries, then an alert message "there is no dataset association found with given details" is getting displayed. But now, this issue is resolved and working as expected.   
        6. In the Load MetaData from files module, when the user uploads the load metadata from files using the table column template, an extra tag with Null is obtained for all the columns. But now, this issue is resolved and working as expected.
        7. In the Load Metadata from files module, the issue related to re-uploading the files is now fixed and working as expected.
      6. Administration
        1. In the Crawler module, the issue related to the system not displaying the Last Profile Status and Last Profile Date details in the Crawler Information page is now fixed and working as expected.  
        2. In the Crawler module, when the QLiksense connector is crawled and the lineage is built, the issue related to Heap Space occurs. But now, this issue is resolved and working as expected. 
        3. In the Crawler module, when the Snowflake connector is crawled and when the user navigates to the User and Roles module in the Remote Users tab, the users are not shown, and an error message "there is some problem getting a result" is displayed. But now, this issue is resolved and working as expected.
        4. In the Crawler module, when the Snowflake connector is created and crawled and when the user wants to delete the connector, an error message is displayed. But now, this issue is resolved and working as expected.
        5. In the Crawler module, when the RDAM connection mode is chosen as 'OvalEdge is master' and a user tries to edit the user name from the OvalEdge application, the user login name is not updated. But now, this issue is resolved and working as expected.   
        6. In the Crawler module, when the Tableau connector is crawled and built lineage and when the user clicks on the correct query icon, the system navigates the user to the first crawled connection instead of the same connection. But now, this issue is resolved and working as expected.
        7. In the Crawler module, when the Awsglue ETL connector is crawled and built lineage and when the user navigates to the Data Catalog > Queries tab, the Title of the Query Name is getting displayed as Undefined instead of the dataset name and the Associations associated with the selected Query are not displayed even though there are available in the Source. But now, this issue is resolved and working as expected.
        8. In the Crawler module > Tableau connector, the issue related to the building lineage due to different repository locations is now resolved and working as expected.
        9. In the Crawler module > SAPBO_Universe connector, the issue related to the reports failing once after building lineage is now resolved and working as expected.
        10. In the Crawler module > ADB connector, the issue related to the improper loading of queries once after building lineage is now resolved and working as expected.
        11. In the Crawler module > Google Drive connector, the issue related to the system not cataloging files from its sub-folders is now resolved and working as expected.
        12. In the Crawler module, while connecting Google Drive using Manage Connection pop-up window, even if the user does not enter the mandatory details like "Google Service Account" and "Filepath," the system saves the details without any indication. But now, this issue is resolved and working fine.  
        13. In the Crawler module, when the Google Drive connector information is edited, the respective details are displayed to other users, and the data is not encrypted. But now, this issue is fixed and working as expected.
        14. In the Crawler module, when the Google Drive connector is crawled and when the user navigates to the File Manager module, the files are not displayed. But, now this issue is fixed and working as expected.
        15. In the Crawler module, when a Tableau connector via Personal Access token is crawled, the connection fails, and an error is displayed in the Jobs log. But now, this issue is resolved and working as expected.
        16. In the Security module, the issue related to the system not applying the default Job Role to the Table is now fixed and working as expected. 
        17. In the Security module > RDAM, when the user clicks on Edit available role (remote privileges), and adds, delete & updates permissions of users on any schema or table the changes are not getting recorded in audit trails. But now, this issue is resolved and working as expected.
        18. In the Manage Servicedesk module, when the user creates a Template, adds a Technical Description, changes the ToolTip as Summary, adds the fields only for Technical Description using Mapper, chooses JIRA field as Summary, and creates a Ticket. The Ticket is not getting created, and the system is throwing an error message. But now, this issue is resolved and working as expected.
        19. In the Manage Servicedesk module, when a user creates a new custom template, the user needs to enter brief details of Summary, description, and priority accordingly, and the user can add additional fields using the +add button in the template with a minimum of four fields. But, the system was unable to show the Default drop-down list of options associated with the template. Now, this issue is resolved and working as expected.

      Copyright © 2019, OvalEdge LLC, Peachtree Corners GA USA