Release 5.2.4

About OvalEdge 5.2.4

The OvalEdge 5.2.4 is the latest service release improvised with the Data Catalog, Business Glossary, 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 29 December, 2021

What’s New

Data Catalog
- Materialized View: The OvalEdge application is enhanced with Materialized view to filter the data based on the view types (View, MView). In the Data Catalog> Database> Schema> Views > A filter is now available to view the column in View & Materialized View formats.
Administration
- Advanced Job > ElasticSearch
  Initially, at the time of data migration, data is copied to the database application when ElasticSearch configuration is off and when a user runs the advanced job it reads all the objects of all types and populates all the data to ElasticSearch. Here the existing functionality is improvised to display the data correctly.
- Advanced Jobs > Business Glossary
  In Business Glossary, advanced jobs are created that load and associate business glossaries according to the business glossary template provided.
  - Upload Business Glossary and associated Terms CLS
  - Validate Business Glossary CLS
- Advanced Jobs > RDAM
  The AdvancedJob is created ( SqlServerAdvanceJob) to sync SQL server masking policies from a remote connection to OvalEdge for SQL server and get all the masked columns in that connection. This job will read all SQL server roles who have selected the access on the schema with unmask capability of masked columns and create a masked policy with allowed roles and users and assign them to the columns.
Audit Trails
- In the Audit Trails > Users > User Roles, the column ‘Updated Roles’ has a filter to search for a role.
Advanced Tools
- OvalEdge API
  The OvalEdge API is enhanced with two more Job APIs such as API "changeStatus" and API "getJobdetail".
  - changeStatus: This API is used to change the status of a job where the users can perform the following actions with parameters (INIT/KILLING/HOLD).
    - Initialize (INIT): It will initialize any job by giving multiple job ids.
    - Killing (KILLING): It will kill any job by providing jobs ids.
    - Hold (HOLD): It will hold a job.
  - getJobdetail: This API is to get job details of a job with help of the following parameters
    - startDate: This provides the start date of jobs performed by the user.
    - endDate: This provides the end date of jobs performed by the user.
    - statusList: This takes a list of status from a user like SUCCESS/PARTIAL SUCCESS/ ERROR by which the user can get the required status.

Improvements

Home Page
- Tags
  In the Tag description, the template date format is standardized to the date format of "YYYY-MM-DD hh:mm: ss”
- Elastic Search
  Elastic search functionality is enhanced to read the ElasticSearch credential from the key vault and it is improvised to provide the search result of the objects that contain the title, popularity, and total score in the download template.
Data Catalog
- Custom Column
  Initially, creating and adding metadata to a custom column was a 2 step process but now this process is improvised in a single step for creating and adding metadata to a custom column in one single page.
- When a user clicks on the + icon, the popup is displayed with the following fields:
  - Column Name
  - Column Type
  - Title
  - Business Description
  - Technical Description
  - Tags
  - Term
  - All the column-level additional fields are associated with the respective asset.
- Table Column > Key
  When a remote connection is crawled for a particular schema, now the Table column key displays whether it has a primary or foreign relationship from the source.
  Standardize the size of the pop-up window
  Popup window is 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.
Business Glossary > Related Objects
- In the Business Glossary - Related object, a category is provided with a proper tooltip for the terms present in the ‘search terms’.
Projects
- The Project module is enhanced to select the multiple roles in the invite user page to work on a project.
Build Lineage
- The Lineage call function is improvised to pick the procedure written in the query.
Advanced Tools
- Data & Metadata Changes
  When a data connection is re-crawled and re-profiled periodically, all the changes in the metadata and the data statistics are recorded and displayed in the Data & Metadata Changes. It is improvised to display the details of metadata that are modified, display the type of modification, the initial value, and the final. It shows the tracking where a table is undergoing changes in its metadata such as renaming a column name/change in type/length.
- Build Lineage
  In the Build Auto Lineage page, when the user selects a connection and clicks on the Correct Query option. A query is provided with a hyperlink in the correct query page to click the query and build lineage.
Administration
- Process Lineage Validation
  Advanced Job, “Process Lineage Validation” is showing two times with different id numbers, but now this issue is fixed and working as expected.
- Security > Tables
  In the Security - Tables, the filter is provided for column security, mask column, and restrict column to filter the checked tables.
- Jobs Log
  The Jobs Log Value is updated to provide the count of users and roles fetched from a source into the OvalEdge application and also enhanced with a search box to easily search for particular log details.

Bug Fixes

Data Catalog
1. Tables
  In the Data Catalog > Tables, the last modified date is not getting updated for business description but now, this issue is resolved and working as expected.
2. Table Column
  In the Data Catalog > Tables Column while adding an existing column again and again the system is not cautioning the user and during this process, the technical and business description is getting overriding the existing one but now, this issue is resolved and working as expected.
3. Report columns
  For the Tableau connector, the user was not able to fetch the report column and build lineage. Now, this issue is fixed and working as expected.
4. Queries
  In Data Catalog > Queries, when a user has edited a query and saved, and then executed the query. It was showing an alert that “before executing save the query”. Now, this issue is resolved and working as expected.
5. My Watchlist
  If the user selects a table that is not added to MyWatchlist and clicks on the 9-dots -> ‘Remove from Watchlist’, the system should display an alert message that “Already removed from my watchlist. Instead, it should display the alert message as “It is not in Watchlist”. Now, this issue is resolved and working as expected.
6. Table Summary Page > Top Users
  If any Team is created and gets associated or interacted with selected objects (tags/terms). In a database page, the top user's icon was not displaying the name of a team that was in the top user lists. Now, this issue is resolved and working as expected.
7. Tables > Data tab
  In the Data Catalog - Tables, select any table with SQL connection and navigate to the Data tab. The user was unable to see data under the Data tab of the SQL connection table. Now, this issue is resolved and working as expected.
Business Glossary
1. Top Users
  When a team of Steward was created in a domain. Steward was not getting listed in Top Users in the Business Glossary term page. Now, this issue is resolved and working as expected.
2. Related Object
  For the related object when the user chooses, “Is related to” term relationship assignment creates a relationship of “Contrasts with” to the related term. Now, this issue is resolved and working as expected.
3. RACI
  If the RACI is enabled with the configuration and in the Security Approval Workflow if the workflow is assigned in the business glossary and if the RACI users are added in the Business Glossary and when a user navigates to the ServiceDesk approval request page, RACI users are not getting displayed, nor the status of approval is getting displayed. Now, this issue is resolved and working as expected.
4. Term > AI Recommendation
  When the user ran the AI recommendation the system was showing a null recommendation for a term in the business glossary. Now, this issue is resolved and working as expected.
Query Sheet
1. In Querysheet, aggregate function SUM was not able to compute for the NUMBER data type. Now, this issue is resolved and working as expected.
Jobs
1. When the user crawls and profiles the RDBMS and File connection, it is not showing the hyperlink in the Jobs page for profiling of files. Now, this issue is resolved and working as expected.
2. In the Job execution process for ‘job service background’, and ‘re-initialization jobs’ were getting stuck during the execution, Now this issue is resolved and working as expected.
Administration
1. Crawler > New Connection
  In the Manage Connection page, when the authentication was selected as RoleBase Authentication, the cross Account role ARN field was a mandatory field to enter. Now, this Cross-Account Role ARN is an optional entry during the connecting to the source (S3, Athena, AWS DynamoDB, and AWS Glue). Now, this issue is resolved and working as expected.
2. Crawler> 9-dots> Build Lineage
  In the Administrator > Crawler> 9-dots> Build Lineage, it failed to build lineage when a source code was selected and clicked on ‘Build Lineage for unprocessed source code’, after successfully running the job. Correct Query window displays the status as failed (‘Failed-to-build lineage’). Now, this issue is resolved and working as expected.
3. Security>Remote Connection
  When the remote is master, for a remote connector that allows both the Users and Roles, the system is not able to add new users and give permission. Now, this issue is resolved and working as expected.
4. Servicedesk > RACI
  The business user who is a member of the RACI panel was unable to Reject the approval. Now, this issue is resolved and working as expected.
5. Servicedesk
  In the Servicedesk - approver page, the approved by field is enhanced with proper spacing to correctly display the approver name.
6. Manage Servicedesk
  The user was unable to save the changes made in the edit drop-down field in the Manage Servicedesk - Edit custom template. Now, this issue is resolved and working as expected.
7. Advanced Jobs
  Asset Usage Advanced job for the total user's list of the reports was not rendering correct results. Now, this issue is resolved and working as expected.
8. DQR
  Unable to associate the right connection details, the connection name gets auto-updated to another. Here there was an issue of associating the DQR rule to the schema connection it was selected for. It was displaying the result mapped to some other schema connection. Now, this issue is resolved and working as expected.
Advanced Tools
1. Load Metadata from Files> NFS
  When the xls. file is uploaded and crawls into OvalEdge, the file uploaded is empty. XLS file cannot be read via NFS. Now, this issue is resolved and working as expected.
2. Load Metadata from Files > Business Glossary
  At the time of upload of terms in Business Glossary using Load Metadata from Files, terms were not able to be uploaded when team stewardship was applied at the domain level. Now, this issue is fixed and working as expected.
3. Build Auto Lineage
  In the Build Auto Lineage, the user is not able to select any connection. Also, when no connection is selected, the user is able to click on 9-dots and then nothing happens on various options of build lineage available. When no connection is selected, the 9-dots option needs to be disabled. Now, this issue is resolved and working as expected.
Governance Catalog
1. In the Governed Data Query, the issue related to the user with Meta Read and Data No Access permissions could able to get the entries for the data after configuring the terms and running the query is now fixed and the users with Meta Read and Data No Access permissions are restricted to get the data.