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

      Release 5.2.5

      About OvalEdge 5.2.5

      The OvalEdge 5.2.5 is the latest service release improvised with the Data Catalog, Business Glossary, OvalEdge APIs, RDAM, Projects, and Administration modules and the critical and major bugs associated with the Data Catalog, Business Glossary, Governance Catalog, Advanced Tools, Administration, and Connectors modules are fixed and working as expected.

      Release Type                                                      Release Date

      Service Release                                                12 January, 2022

      What’s New

      • Jobs
        In the Advanced Tools > Impact Analysis, when a user creates or adds an object which is not having a lineage and runs the job, then those objects are not being impacted with the empty lineage and the message “no impacted objects for source objectid: id” is displayed.

      Improvements

      • Business Glossary 
        In the Business Glossary, when the user is trying to import the data through the  ‘Load metadata from files’ in  Category and Sub-Category, the system now accepts the data with a combination of alphanumeric and special characters, alphabets, numbers and restricts the data which contains only special characters or empty strings.
      • Projects 
        In the project page, the recently added project is now getting displayed at the top of the list of a project(s) for the user's better visibility.
      • Governance Catalog > Servicedesk 
        In the Service Request ticket template for Initiate workflow regarding terms is improvised with an edit option in the Purpose of the Service/Description text area. 
      • Advanced Tools > OvalEdge API
        • getJobDetails
          In the OvalEdge API, getJobDetails (/api/job/getJobDetails)  provides the details of the job run in the given UTC time in the response body. This API has Ending Time Stamp, Starting Time Stamp, and Status List
          • EndingTimeStamp: It displays the job id executed at the end of this timestamp.
          • StartingTimeStamp: it displays the job id executed from the starting of this timestamp.
          • StatusList: It displays job id with status as of job as (Finished or Error).
          • It also provides the job ID.
        • getJobStepStatus
          In the OvalEdge API, getJobStepStatus (/api/job/getJobStepStatus/{jobStepId})  provides the status of a job step. Users can enter the job step id in the API, and it displays the job step status as Success, Partial Success, and Error in the API response body
      • Jobs > Audit Data Archival 
        In the case of Audit Data Archival, job log value is improvised to display the exact path of achieved files that are being copied and if the path doesn't exist the system will display the message as “no such path exists”.
      • Advanced Tools
        • Advanced Tools - > Load metadata from Files > Tags
          There is a template available for tags for both templates with data and templates without the data. Here the user can click on the Tags download button of Template with the data option. This template has tags data pertaining to tag name, business description, and tag type. 
        • Advanced Tools > Impact Analysis
          The Impact Analysis feature has been enhanced to add Object names and Technical Descriptions to the target object.
      • Administration 
        • Administration > Users & Roles > Policies tab
          In the Users & Roles, the Allowed User column has been added to the policies tab. 
        • Administration > Crawler > RDAM > Masking policy
          Currently, the application supports only Allowed Roles in Masking Policy in Business Glossary and Column Security, but now the existing functionality is enhanced to support Users also as SQL server supports unmasking for users along with Roles.
        • Administration > Crawler 
          In the Crawler option, when the users select the Crawl/Profile of a schema that has been scheduled now displays with the combination of ConnectionName.SchemaName
        • Administration > Crawler > Build Lineage
          In the Crawler, the Start Time and End Time period rule is added to a connection at which time source may crawl and build lineage from a remote server. For example, users might want to run the database crawling on Tuesday, Thursday, and Saturday in the Time Period(6 PM to 03:30 AM).
        • Administration > Users & Roles
          In the Administration > Users & Roles, the User tab has been improvised with ‘Updated Date Column’, to display the date on which the users update the details.
      • Connectors
        • DB2 Connector
          The RDBMS connection for example DB2 now supports the license type as “Auto lineage”. In the Connection pop-up, users can now select the License type as “Auto Lineage”.  
        • Standardize the size of the pop-up window
          All the pop-up windows in the application are standardized to accommodate lengthy names of Term Tags, draggable, re-sizable, supports multi-column layouts, to prevent vertical scrolling, and the close icon and the close button is provided to exit from the popup window.

      Bug Fixes

      1. Home
        1. In the Home page, when the user is trying to search a dataset in the Global search, the internal search application is not working, but now, this issue is resolved and working as expected.
        2. In the Tag page, when the screen is zoomed out, less than 90% of tags were not visible. Now, this issue is resolved and working as expected.
        3. In the Tags page, when the user was trying to change the profile picture of Tag, the profile picture was not getting uploaded to the tags. Now, this issue is resolved and working as expected.
        4. When the users are trying to upload the Tags using Load Metadata from File template, the Tags were only being created as a Parent Tag and there was no Parent-Child hierarchy maintained while uploading the tags from the template. Now, this issue is resolved and working as expected.
        5. When the users are trying to load Tags using Load Metadata from File template, the Child Tag Business descriptions were not loading. Now, this issue is resolved and working as expected. 
      2. Data Catalog
        1. In the Data Catalog > Tables level, editing Technical Descriptions using the edit icon was displaying the Table Name instead of the Description details saved. Now, this issue is resolved and working as expected.
        2. In the Data Catalog > Database level when the user was searching for any tags and then navigating to another table level to search for other tags, then the previously searched tag results were being displayed. But now, this issue is resolved and the Tag search is displaying all the tags present in the application and working as expected.
        3. In the Data Catalog, the Top users were not getting displayed for Tables, Table columns, Reports, Report columns, and Terms Error was encountered when the user was trying to view the top users. Now, this issue is resolved and working as expected.
        4. In the Data Catalog, while adding multiple Tables - with Tags, Terms, BG Description, Technical Description, Custom field there was an error prompt displayed ‘while trying to Save’. Now, this issue is resolved and the user is able to create and save Multiple Tables.
        5. In the Data Catalog >Tables >Tags, the assigned child Tags which are removed from the Tag pop-up window were displayed multiple times in the ‘Add a Tag’ field. Now, this issue is resolved and working as expected.
        6. In the Data catalog module, the user was not able to see the Report/Report Column in the Data Catalog page. Also, in the Auto build lineage screen count of source coded loaded, processed unprocessed was displayed as 0. But now, this issue is resolved and working as expected.
        7. In the Table Column > Terms, when the users assigned a term to a column, the masking policy was not working properly and also top score value was displayed as the negative value. Now, this issue is resolved and working as expected.
      3. Business Glossary
        1. In the Business Glossary, on domain level users with RO (Read-Only) access were able to view the Edit icon and were able to change the description. Now, the Edit icon is removed and the issue is resolved.
        2. In the Business Glossary, the users were not able to view Recommendations even after the log from the Job module says that it found column recommendations. Now, this issue is resolved and working as expected.
        3. In the Business Glossary, when ‘Team’ is selected under Steward role and the term is published then a publishing error is displayed.  But, now this issue is resolved and the Team members are able to publish/review the Term.
        4. In the Business Glossary, upon creating any Term, adding objects to the Term, and then Run Recommendation Jobs for all unclassified objects, an error was getting encountered when the user clicks on the Table Column in the Associated Data page. Now, this issue is resolved and working as expected.
        5. In the Manage service desk, a service request template was created for ‘Business Glossary Content Change Request’ with details of JIRA integration in the request template. Once the ServiceDesk ticket is created and the approval process is initiated then the external JIRA ticket is not getting displayed in the ServiceDesk page. Now, this issue is resolved and working as expected.
      4. Governance Catalog
        1. In the Data Quality Rule, when applying Tags using the Edit icon the DAG Tags were being applied but the applied tags were not getting displayed.  Now, this issue is resolved and working as expected.
        2. In the ServiceDesk New Service Request page, when the user was trying to approve a Business Glossary ticket ‘Please Select Description’ error was displayed and the ticket was created with no description details added to it. Now, this issue is resolved and working as expected.
        3. In the DQR rule page, while adding the DQR rule, the Rule name page was getting frozen because of loading a huge number of Terms and the user was unable to enter the purpose of a rule as well. Now, this issue is resolved and working as expected.
        4. In the Governance Catalog > New Service Request, when creating a service request from Initiate workflow in the Business Glossary page an error ‘Please Select Description’ has been displayed while approving the ticket and the ticket got created without any description. Now, this issue is resolved and working as expected.
        5. When a user was navigating any DQR Rule page, it was not showing the Top user in the DQR page and the system was throwing a message ‘There is some problem getting Top users’. But now, this issue is resolved and working as expected.
      5. File Manager 
        1. In the File Manager, the Audit archive files were facing issues while moving the files to google cloud storage. But now, this issue is resolved and working as expected.
      6. Advanced Tools
        1. In the Advanced Tools, the issue related to the Build Auto Lineage page not loading properly is now resolved and working as expected.
        2. In the Load Metadata from Files, when the user was trying to create columns in custom fields the Table was getting created but the columns were not getting created and the Jobs Log was displaying null status. Now, this issue is resolved and working as expected.
        3. Data & Metadata Changes > Metadata changes when the ‘Added’ option was selected under the ‘Remarks’ tab the ‘Modified’ option was applied. Now, this issue is resolved and working as expected.
        4. OvalEdge API’s > Term API, when getBusinessTermInfo API was executed,  in response the users were not able to fetch the custom fields in Additional Information. Now, this issue is resolved and the users are able to fetch the results as expected.
        5. In the Advanced Tools > OvalEdge API’s, once after receiving the UserToken and UserSecret from the OvalEdge application, the user needs to make the request to the following endpoint (http://localhost:8080/ovaledge/user/token/generate) using any third-party tool like Postman. In the Postman API, the user was not able to fetch the bearer token fields. Now, this issue is resolved and working as expected.
        6. Advanced Tools > OvalEdge API getTableAndColumns(/api/getTableAndColumns), users enter the value in the ‘Table' field and execute. In the response, the user was not able to fetch business, Technical description, tags, terms for the API. Now, this issue is resolved and working as expected.
          In the Build Auto Lineage, the user encountered an error to build lineage for SAP BO Webi Crystal report through the correct query window. The failed lineage is corrected and executed in the correct query window. In the correct query window, it shows the status as SUCCESS_LINEAGE_BUILD but when it is copied and clicked on validate it was getting failed to generate lineage due to an error of ‘build lineage except for report’. Now, this issue is resolved and working as expected.
        7. In the case of Load Meta from Files, when users try to download the schema description  'template with data from the data catalog page and Load metadata from Files. The data catalog downloaded templates was not matching to Load metadata from Files. Now, this issue is resolved and working as expected.
        8. In the OvalEdge API, getBusinessTerm API (api/businessglossary/businessGlossaryData) allows users to search for a business glossary term. It has the following input parameters:
          1. Limit: It sets the limit of a term
          2. searchTerm: enter the term in the search box
          3. startindex: returns the results from the provided index from the final search results.
            In the response body, it displays the information based on the parameters set above. It also provides the classification value assigned to the term in domain classification. 
        9. Build Auto Lineage, lineage building for one of the clients was failing due to the backend issue of Timestamp format changed in the log file. Now, this issue is resolved and working as expected.
      7. Advanced Jobs
        1. In the Advanced Jobs, whenever a new column was added, an advanced job (Recommend Term to newly Added Columns) was run that applied the term automatically but it did not send notification or email to stewards. Now, this issue is resolved and working as expected.
      8. Administration
        1. In the Administration module > Crawler, when a user crawls a connection and builds a lineage from 9-dots >  Build Auto Lineage page is displaying blank results. However, this issue is resolved now and working as expected.
        2. In the Administration module > Users & Roles, when a user was trying to validate source connector with OE as master and Remote as a master in crawler settings there was a migration issue where all the connections were disappearing in the Remote Roles and Remote Users fields. Now, this issue is resolved and working as expected.
        3. In the Administration Module > Custom Fields, upon uploading a Table column template, when the user was trying to give custom definitions in Table/Table column object type for Manual Connection Type, there was an error showing while Saving Custom Field Definitions. Now, this issue is resolved and working as expected.
        4. In the Administration Module > Crawler, when Snowflake connection is crawled and the user navigating to 9dots > settings the ‘Users, Roles, Policies & Permissions’ checkbox and ‘Remote Access’ and ‘Query Policies’ were not being displayed. Now, this issue is resolved and working as expected.
        5. In the Administration module > Crawler Settings > Crawler Rules when the user was trying to insert long data in the Table & View Regex field there was an error displayed due to the 265 characters limit. Now, this issue is resolved and working as expected.
        6. In the Administration > Security > Data Asset Group tab, when the users were trying to update the roles of both Owner and Steward there was an error being displayed. Now, this issue is resolved and the users are able to add Roles.
        7. In the Administration > Security, RACI users for Business Glossary have been configured in the Security -> Approval Workflow page. But when the user navigates to approve the request in the ‘Approve Request’ page, RACI users are not displayed. Now, this issue is resolved and working as expected.
        8. Administration > Crawler, in Manage Connection for Role Based Authentication, when a user tries to connect a connector with IAM Role Authentication, it throws an I/O  exception error for the input given in Role Based Authentication. Now, this issue is resolved and working as expected.
      9. Connector
        1. In the Manual Connector, when a user added a term to the Table, Table Column, and then the user clicks on the Suggest Term option, then the Term was created and added to the object instead of showing any warning message. Now, this issue is resolved and working as expected.

      Copyright © 2019, OvalEdge LLC, Peachtree Corners GA USA