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

      Release 5.2.6

      About OvalEdge 5.2.6

      The OvalEdge 5.2.6 is the latest service release improvised with the Entity Delete Framework that allows the users with system administrator privileges to remove specific database connections, schemas, domains, and archiving or transfer of roles. Some minor enhancements are implemented in the Data Catalog, Business Glossary, My Resources, Service Desk, and Administration modules.

      In this release, the critical and major bugs associated with the Data Catalog, Business Glossary, Advanced Tools, Administration, and Connectors modules are fixed and working as expected.

      Release Type                                             Release Date

      Service Release                                       03 February, 2022

      What's New

      • Algorithm 
        A new algorithm is implemented to run for all the terms in the domain for the newly crawled Data sources. Here the system will keep track at what time the advanced job has run the algorithm, and when a new data source is crawled, the algorithm will run, and if a term is found with more than a specific score, the system will notify to Data Source Steward so that they can apply the term.
      • My Resources 
        • In the My Resources > My Profile details page, the Edit Profile pop-up window is provided with a feature to remove the profile picture. Here, the Edit Profile pop-up window provides options to change the profile picture using "Change Picture" or remove the picture from the profile using the cross icon that appears on the image.
        • In the My Resources > Inbox page, a new filter option is provided to search the messages as per the particular chosen date or in the specific time interval. 
      • Connector
        The new connector AWS Glue ETL is included in the OvalEdge connector list to crawl the files and folders associated with the AWS GLUE ETL. The folders and files in the AWS GLUE ETL can be cataloged and profiled. 

      Improvements

      • Entity Delete Framework
        The OvalEdge Entity Delete Framework allows the users with system administrator privileges to remove specific database connections, schemas, domains, and archiving or transferring roles. The purpose of this framework is to follow a pattern when the OE admin deletes an entity in the application. This pattern involves deleting all child objects iteratively, transferring all responsibilities, and archiving(if required) before deleting the entity.  
      • Data Catalog 
        When a particular data object is selected in the Data Catalog, the new option "Apply Certification" is provided in the 9 Dots menu option to certify the selected data object.
      • Business Glossary
        In the Business Glossary, the existing Category and Subcategory are improvised to accept the special characters. The user can now create the category and subcategory names with special characters.
      • Service Desk
        The Service Desk Tickets is improvised with a Collaboration messaging feature so that the user can now discuss the ticket details with the other users.
      • Policies 
        In the Audit Trails > Policies page, a new column "Connection Name" is included in the existing Policies data grid to know the Schema associated with which connection.
      • Jobs
        In the Jobs module, the existing search job logs functionality is improvised to display the more efficient results associated with an error.

      Bug Fixes

      1. Home
        1. In the Galaxy instance, when the users logged in with google credentials, the 'License Type' was not updated. Now, this issue is resolved and working as expected.
      2. Business Glossary
        1. In the Business Glossary, when the Chrome extension is added, users were unable to view any Business Glossary Terms on the Business Glossary page. Now, this issue is resolved and working as expected.
        2. In the Business Glossary > Select any Term > click on Related Objects edit icon > Files tab, users were unable to delete a File from Related Files pop-up, there was an error 'Problem Deleting Related Term' error. Now, this issue is resolved and working as expected.
        3. In the Business Glossary > Select any Term > Click on the Related Objects Edit icon > Reports tab, users were unable to remove Reports from Related Reports pop-up and an error 'Terms not Exists' was been displayed. Now, this issue is resolved and working as expected.
        4. In the Business Glossary > Select any Term > Click on the Related Object Edit icon > when the users navigate from Table tab to File tab, the file tab was displayed with the Table columns in the Related Data pop-up window. Now, this issue is resolved and working as expected.
        5. In the Business Glossary, when a new domain is added from the Administration> Security, the top-users are not displayed on the Business Term. Now, this issue is resolved and working as expected.
      3. Data Catalog
        1. In the Data Catalog > Database page, when the users crawl new databases, the results are not displayed in alphabetical order. Now, this issue is resolved and working as expected.

        2. In the Data Catalog, the catalog search is not giving the search result when the user is searching with numbers and special characters. Now, this issue is resolved and working as expected. 

        3. In the Data Catalog, if a user role is created with a numeric number and assigned that role to any user, and if that user logs in and searches any domain name, the catalog search results are not displayed. Now, this issue is resolved and working as expected.

      4. My Resources 
        1. In My Resources > My Profile > Add Slack Id > Edit profile > when the user logged in with SSO or LLAP credentials, the users were not able to save the Slack Id. Now, this issue is resolved and working as expected.
        2. For the Tables saved in 'My Watch list, there were no notifications been sent if any changes were made to the Table metadata that include changes made to Business Description, Tag, Term, Technical Description on the Table column level. Now, this issue is resolved and working as expected.
      5. Advanced Tools 
        1. In the Impact Analysis, when Public users created 2 or more Impact Analysis and deleted any Impact Analysis, all the Impact Analysis were deleted rather than the selected one. Now, this issue is resolved and working as expected.
        2. In the Impact Analysis > Add Impact Analysis > when a Tableau is added as a source object then an error message was been displayed. Now, this issue is resolved and working as expected.
        3. In the Impact Analysis > Add Impact Analysis > when a table without lineage is added to the Impacted Analysis object then the Impact Count field was left blank instead of displaying zero. Now, this issue is resolved and working as expected.
        4. In Build Auto Lineage, when the Tableau connection is crawled, and a few reports are selected to 'Export source code to File' an error message 'No dataset association found with given details' was displayed. Now, this issue is resolved and working as expected.
        5. In the Build Auto Lineage > when the Tableau connection is crawled, and the Correct Query column is selected to view the data report, the error message query is not available was displayed. Now, this issue is resolved and working as expected.
        6. In order to build a lineage using custom SQL query, when the user clicks on the Association tab, an error message "problem occurred" was displayed, and at the time lineage building if any table is not available or deleted in the database, an error message "Table Not found ID#" was displayed. Now, these issues are resolved and working as expected.
        7. In the Compare Schemas > when the same Connection and Schema is selected for different dates to Compare Schemas, the 'No data Exists' results message was displayed even if there are any changes. Now, this issue is resolved and working as expected.
        8. In the Load Meta Data from files > when the user was downloading the Report Columns, Lineage, Source code, Column Relationships, Dataset Correction, Impact Analysis Objects templates, an error message 'Problem Occurred' was displayed. Now, this issue is resolved and working as expected.

      6. Administration

        1. In the Crawler module, when the snowflake connection is crawled and OvalEdge is selected as master, when the users tried to assign Policy to any Table columns, the system displays the different user names in the Administration> Audit Trails> Remote> Policies and Object Policies field. Now, this issue is resolved and working as expected.

        2. In the Crawler module, when the snowflake connection is crawled, and Users & Roles is selected in Crawler settings. In the Administration> Job Work Flow > when Crawl users, role, and permissions are selected from the drop-down, the connection is dragged and dropped, and when 'Run' is clicked, the error was displayed in Job Logs. Now, this issue is resolved and working as expected.

        3. In the Crawler module, when a snowflake connection is crawled, and Remote is Master. The Remote users with empty email fields are getting mapped with different User Names from the OvalEdge application users having empty email fields. Now, this issue is resolved and working as expected.

        4. In the Crawler module, when the snowflake connection is crawled with Remote is Master. If the users try to Crawl Schema an error messages' Job is not continuing' was displayed in Job Logs. Now, this issue is resolved and working as expected.

        5. In the Crawler module, when a new connection is crawled and the 'Procedures, Functions, Triggers & views Source code' field selected and navigated to other tabs, the 'Save Changes' button is not working properly. Now, this issue is resolved and working as expected.

        6. In the Crawler module, when a connection is crawled and in the Profiler settings, if multiple orders are added the first order in the orders list was been selected and executed rather than selecting the matched profile. Now, this issue is resolved and working as expected.

        7. In the Crawler module, when users crawled a new connection using QlikSense connector and navigated to nine dots > Build lineage, an error 'Timestamp format changed in log file' was displayed in Jobs Logs. Now, this issue is resolved and working as expected.

        8. In the Crawler module, when the AWS DynamoDB connector is crawled, the Crawl/Profile, Profile and Profile Unprofiled radio button options were not displayed. Now, this issue is resolved and working as expected. 

        9. In the Crawler module, when a new ADL connection is crawled, the GCS details are displayed in the options. Now, this issue is resolved and working as expected.

        10. In the Crawler module, when the SFTP connection is crawled and while validating the connection, an error message 'Problem Occured' was displayed. Now, the issue is resolved and working as expected.

        11. In the Crawler module, while Crawling a SQL server connection with the profile type as a sample. A user crawls the Schema and profiles a table that has numerous data, but the Null count and the Distinct count are showing value more than the sample size provided. Now, this issue is resolved and working as expected. 

        12. In the Crawler module, the users were unable to delete a crawler connection for a schema that was no longer in use. Now, this issue is resolved and working fine.

        13. In the Crawler module > Oracle connection, while profiling the table for a few columns, the error message "Unsupported data type (varachar2)" was displayed. Now, this issue is resolved and working as expected.

        14. In the Users & Roles > Roles > when the users change the 'Role Name' then the Permissions are been assigned to default values (Read Only-No Access). Now, this issue is resolved and working as expected.

        15. In the Security > Approval Work Flow tab was displaying duplicate 'Approved By' fields and users were not able to select External drop-down options. Now, this issue is resolved and working as expected.

        16. In the Security > Applications, OE admin can restrict the OvalEdge modules to be visible to OE Public users by entering the path of the module. Once the module address path is specified in the application path column and if OE admin enables the toggle button, that particular application can be seen in OvalEdge, and specified roles can access the same. When the admin was trying to restrict access to modules of the OvalEdge application, it was visible to OE public users. Now, this issue is resolved and working as expected.

        17. In the Advanced Jobs module, while running the Advanced Job, an error message "Data truncation: Data too long for column 'column description' at row 1" was displayed in the job logs. Now, this issue is resolved and working as expected.

        18. In the Configuration module, after configuring the SMTP server, when users navigated to the Configurations tab to view Notifications the users were unable to get email notifications. Now, this issue is resolved and working as expected.

        19. In the Configuration module, when the SQL server connection is crawled and the user navigated to > Nine dots > settings > Profiler > Include Table & View Regrex to add tables to crawl then an error 'Data too long for column include_tables_regrex was displayed. Now, this issue is resolved and working as expected.

      Copyright © 2019, OvalEdge LLC, Peachtree Corners GA USA