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

      Release 5.2.3

      About OvalEdge 5.2.3

      The OvalEdge 5.2.3 is the latest service release improvised with the Data Catalog, Business Glossary, My Resources, and Administration modules and the critical and major bugs associated with the Data Catalog, Business Glossary, Governance Catalog, Query Sheet, Advanced Tools, Administration, and Connectors modules are fixed and working as expected.

      Release Type                                           Release Date

      Service Release                                     14 December, 2021

      What’s New

      • Data Catalog
        In the Data Catalog > Database > Schema Name, Summary page for the manual connection, the new option is included to enter the custom tables metadata from one screen itself. When the user clicks on the + icon, the system allows the user to enter the information with the following details at one instance:
        • Table Name, Title
        • Business Description
        • Technical Description
        • Tags, Term
        • Additional fields at the Table-level
      • Business Glossary
        The OvalEdge application is updated with an algorithm that runs for all the terms in Domains to newly crawled data sources. Here, when a term is found with more than a specific score, it reports to the steward of the data source so that they can apply the term.
      • My Resource
        • Inbox > Periodic Email Alerts
          In the My Resource > Inbox page, the new feature alerts were implemented through the customer's email id at the time of creating a license. This alert will send the notification periodically, before 7 days of the license expiry date and this email alert is sent on a daily basis for 7 days prior to the expiry date.
        • Inbox > Date filter
          In the My Resource, the Inbox page is enhanced with a calendar date filter to filter the list of tickets within a certain time interval or any chosen date.  
        • Metadata changes alerts
          Earlier, if any changes were made to metadata in the remote database for each schema multiple email notifications were sent but, now the metadata changes alert is improvised with single email notification.
      • Administrator
        • Advanced Job > RDAM 
          In the Advanced Job, now a user can select a SqlServerAdvanceJob for the data masking policy in the RDAM SQL server for users and roles. This Advanced Job takes the connection id and gets all the masked columns existing in that connection and pulls all the SQL server Roles who have access on table or schema or database with UNMASK capability of masked columns. 
        • Users & Roles > Masking Policy for Allowed Users
          Initially, the masking policy in Business Glossary and Column security was applicable for roles based on the remote connector but now, the OvalEdge supports the masking policy at the user level along with roles. 
          For example, synchronization with the Remote, for the Snowflake connection only Roles will be synced and for the SQL Server connection, both Roles and Users will be synced.
        • Configuration > Slack
          The main notion of integrating OvalEdge with slack is the extensibility of alert jobs that are sent to clients through emails. Along with email notifications, if users want to get slack notifications of the OvalEdge jobs, they can get them through this integration. Here a direct message is sent to their desired slack channel from the OvalEdge application.

      Improvements

      • Home > Chrome Extension
        • The existing Chrome Extension is improvised with the search bar to search a certified report column. Here the search results will display the source to which that column belongs (Example Report.column).
      • Data Catalog
        • In the Data Catalog, now the technical descriptions entered for tables, files or reports can also be viewed in the downloaded template.
        • Tables > Data Types
          The existing Data Types are improvised to support the data types like jsonb, array, and user defined. If these data types are profiled the system displays the null value in the statistics. 
        • Tables > Custom tables 
          The Custom tables are implemented with the title fields in the table’s columns and the table’s popup.
      • Business Glossary > Bulk Upload
        • In the Business Glossary, the existing bulk upload functionality is improvised to upload and display the information from the template into the detailed description text area of a term.
      • Project > Invite User
        • In the Project, the existing invite user feature is improvised to select multiple roles on that project database.
      • Administration
        • Users & Roles > users
          • In the Administration > User & Roles > Users, a new column by the name “Created Date” has been included to display the date and time stamp on which a user is created in the system. 
        • Security
          • In Security, the existing feature is enhanced for the users to change the stewards and owners of the tables and reports.
          • In the Tables page, the existing table column is enhanced with the filter option to filter views.
          • Earlier, the users with read and write access privileges to the databases are used to connect to them through OvalEdge but now, the existing functionality is improvised and the users with read only access to the database can only connect to through the OvalEdge and can log in to the different databases using the (primary.url, primary.username, and primary.password) parameters.
      • Advanced Job
        • In the Advanced Job, a  user can add an advanced job to download the business glossary. For instance, the Advance Job “Download Term Association Details” is added to download the associations of a term and upload it to a temp directory.
        • The new advanced job is created to read the server credentials for the Windows platform as well as SQL Server Auth Connection on Linux which automatically gets the new password, updates the connections, and validates the connections.
      • Custom Fields
        • The existing custom fields are improvised to choose the Object Type from the dropdown list instead of field types tabs
      • Configuration > SMTP > Base URL Alerts
        • The existing notifications settings are improvised to allow the older alert messages redirected to the newly added base URL.

      Bug Fixes

      1. Home
        1. In the License information page, when the user clicks the used count of a standard connector or number of auto lineage connectors. It is navigating to the users & roles page with the error message. Now, this issue is fixed and working as expected.
        2. The wildcard search with the operators (AND, OR, && ) was unable to produce satisfactory search results. Now, this issue is fixed and working as expected.
      2. Data Catalog > Profile
        1. When a user tries to profile any Xls file, instead of the data type of that column, the name of a column field is getting displayed in the column type field. Now, this issue is fixed and working as expected.
        2. The Last modified date is not getting updated even though the business description is updated at the table level.  Now, this issue is fixed and working as expected.
        3. The Tag search criteria are not clearing the search results from the list of tag names that are not required. Now, this issue is fixed and working as expected.
      3. Business Glossary
        1. Working with related data at the time of applying a large term + plus sign is not visible and not able to add that large term. Now, this issue is fixed and working as expected.
      4. Dashboard
        1. In the lineage graph, some of the dataset names are lengthy, earlier it was displaying long dataset names ending with dots (...). Now, for more clarity, the long dataset name is getting truncated with dots (...)  in the beginning so that column name is an important object here. 
      5. Governance Catalog
        DQR 
        1. In the DQR page, the user was able to enter the negative value in percentage. Now, it displays alerts to avoid entering the negative value for percentage. Now, this issue is fixed and working as expected.
        Data Classification
        1. In the Data Classification, when the table column and report tab were selected to filter with associated domains it was showing no data exist. Now, this issue is fixed and working as expected.
      6. Query Sheet
        1. In the Query sheet, a selected schema and table join condition is not working and the Query mode is not displaying the correct results as per the condition applied. Now, this issue is fixed and working as expected.
        2. In the query page, the execute button was not working for the existing connection. Now, this issue is fixed and working as expected.
        3. In the query sheet page, the schema is not showing in for the existing connections. Now, this issue is fixed and working as expected.
      7. Advanced Tools
        Impact Analysis > Download Impacted Object
        1. In the impact analysis, once impacted objects are reviewed they can be downloaded but the fields are not proper in the downloaded spreadsheet and the columns are not matching in the download spreadsheet. Now, this issue is fixed and working as expected.
        Compare Schema
        1. In the compare schema, required fields are selected to compare changes in the schema on different dates.  It was showing ‘No Data Exist’, instead of showing the comparison result. Now, this issue is fixed and working as expected.
        Load Meta From Files
        1. During the upload long list of terms, a few terms are missed in the transaction of upload through Load Metadata from Files. Now, this issue is fixed and working as expected.
        2. While building lineage through Load Metadata from Files in the Reference Name column providing the existing query names and trying to build lineage. It is building a lineage but the data set is not adding. Now, this issue is fixed and working as expected.
        3. Bulk upload of table owners and stewards is not captured in the Audit Trail Catalog tab. Job log values display the error of this failed job. Now, this issue is fixed and working as expected.
        OvalEdge APIs > Term
        1. The Term was getting created without giving a business description from API. Now the issue is fixed by making the description a mandatory field.
      8. Administration
        Crawler
        1. In the new connection page, All script connectors were not available in the search list to add in the new connection. Now, this issue is fixed and working as expected.
        2. The Crawling of the existing MySQL connection failed. Now, this issue is fixed and working as expected.
        3. In the Crawler > Connection > Settings > RDAM, earlier, when snowflake connection (remote is master) was crawled, existing users and roles are not getting added into the OvalEdge application and also permissions are not applied on the schema and table and the error message used to be get displayed in the job logs but now, this issue is fixed and working as expected.
        4. In the Crawler Setting > Remote Access tab, earlier, the remote access setting in the crawler was available for all connectors. Now, Remote Access in the crawler setting is hidden for all connectors except snowflake and oracle connection.
        5. In the Looker connector, when the user selects the license type as Manual and adds the port number. The port number is not getting displayed when the connection license is changed to auto. Now, this issue is fixed and working as expected.
        Users & Roles
        1. When a user of RACI is deleted in User & Roles still the user name is displayed in the RACI Panel. Now, this issue is fixed and working as expected.
        2. Earlier, a user has encountered an error while navigating to the Users & Roles page. Now, this issue is fixed and working as expected.
        3. When the OE public role is updated or assigned with the OE Admin role, the OE Public user should be able to run, delete and view the advanced jobs based on the permissions (allowed roles). Now, this issue is fixed and working as expected.
        4. At the time of creating a new ticket of the request type as Business Glossary (with RACI roles), all mandatory details are captured as assigned roles to the approval workflow in the form. A ticket for a business glossary with RACI roles was successfully created. However, when the user clicks on initiate workflow and views the tickets, users and anyone from the roles (RACI roles)  are not displayed in view mode. Now, this issue is fixed and working as expected.
        Advanced Job
        1. When the advanced job is executed for the base URL and whenever the user clicked on the created term notification was navigated for the particular term. Now, this issue is fixed and working as expected.
        2. Earlier,  the system was throwing an error of “Invalid Path” after running load SSIS packages manually advanced jobs. Now, this issue is fixed and working as expected.
        3. The Advanced Job for Select Process SQL statements for reading the zip files is throwing Thread 1 error in job logs. Now, this issue is fixed and working as expected.
        Security
        1. Users with the permission of Meta Read access were able to build the lineage.  As a security restriction, the system should only allow users having Meta write permission to build the lineage. Now, this issue is fixed and working as expected.
          Note: User having following roles should only build the Lineage
          MWDN, MWDP, MWDR, MWDW, and ADMIN
        Manage Service desk
        1. In the service desk, when any request is approved or closed, the status was not updated to Resolved or Closed based on the status of the request. Now, this issue is fixed and working as expected.
        2. In the Manage service desk, when the content changes request template for a business glossary with approval workflow is used a new service desk ticket is created and mapped to the external system but the external service desk JIRA or service now tickets numbers and details are not getting generated in the OvalEdge ticket page. Now, this issue is fixed and working as expected.
        3. When the content change is approved from the service desk, the corresponding Last Modified date is not getting reflected at the table level and the table column level. Now, this issue is fixed and working as expected.
        Security 
        1. For the Hive Connector, when the single schema is selected the system is taking too much time to update roles. Now, this issue is fixed and working as expected.
        Audit Trails
        1. In the Audit Trails, crawling a Snowflake connection (when OvalEdge is a master, ) and assigning a masking policy to any table column, the object policies and policies are getting updated with different user names. Now, this issue is fixed and working as expected.

      Known Issues

      1. RDAM
        1. In the Administration > Crawler > Crawler Information page > Snowflake Connection > Settings, when the RDAM is selected as the OvalEdge is Master option and crawl/profile the schema than in the Security > Schema > Remote privilege's, when the user adds the same role with different permissions which is already associated to the schema with some privileges the system is removing the existing permissions and adding the new privilege. Instead, the system should append the existing privilege.
        2. In the Administration > Crawler > Crawler Information page > Snowflake Connection > Settings, when the RDAM is selected as the OvalEdge is Master option and crawl/profile the schema than in the Administration > Job Work Flow when the user creates a new job and darg the connection name and save and run the job the system is displaying the errors in the job logs.
        3. In the Administration > Crawler > Crawler Information page > Snowflake Connection > Settings, when the RDAM is selected as the Remote is Master option and crawl/profile the schema than in the Security > Database the users are unable to view the schema.
        4. In the Administration > Crawler > Crawler Information page > Snowflake Connection > Settings, when the RDAM is selected and assign the masking policy to any table column from the Security or Add, Delete and Update the Remote Users & Remote Roles then in the Administration > Audit Trails > Remote > The system is displaying the other user name.
      2. OvalEdge API
        1. For all the API Services with Get and Post method, the added Custom Fields are not displaying.

      Copyright © 2019, OvalEdge LLC, Peachtree Corners GA USA