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

      Release6.2

      In Release6.2, OvalEdge has introduced new features and enhancements to streamline data management and user interaction. These include:

        • Governance Apps: Customizable survey forms designed to meet compliance standards.
        • AI-Assisted Description Generation: Automated creation of business, technical, and detailed descriptions.
        • Virtual Objects: Manual creation of data catalog objects preemptively before crawling.
        • Reference Data Management: Grouping and monitoring related reference data objects across source systems.
        • Data Lake Folder and File Analysis: Enhanced analysis capabilities for folders and files within the Data Lake.
        • GDPR Record of Processing Activities (ROPA): Enables PII handling across departments and provides assessment, collaboration, and reporting.
      • API Support in Data Catalog: APIs and API Attributes support in the Data Catalog

      This release also addresses critical and significant bugs in various modules, ensuring a smoother experience.

      Release Details: 

      Release Type 

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Minor Release

      Release 6.2

      		 Release6.2.6200.3965596 March 15, 2024

      What’s New?

      Governance Apps

      The Governance Apps enable the creation of customized survey forms (apps) to collect feedback from respondents within and outside the organization. 

      Two different app types are supported:

      • Collaboration Survey allows multiple respondents to work together on a single form

      • Open Survey allows each respondent to submit individual responses.

      For further details, please refer to the Governance App Deep Dive

      Virtual Objects

      Virtual Objects are temporary data objects created in OvalEdge to manage the request process for new data objects that might be in the future pipeline of any Data Source. This feature enables the creation of Tables and Reports. Users can modify the object's metadata by adding descriptions, assigning tags, and manually creating lineage.

      For further details, please refer to the Virtual Objects Deep Dive

      Reference Data Management

      The Reference Data Management tool allows grouping similar data objects into Reference Data Units, making it easier to track diverse data from different source systems. 

      For further details, please refer to the RDM Deep Dive

      AI-Driven Description Generation

      Business, Technical, and Detailed descriptions are generated using a Generative AI tool to accelerate the catalog curation process, leveraging object metadata and data structure hierarchy.

      Folder & File Analysis

      Folder Analysis profiles the folders and their hierarchies in S3 (Amazon S3), NFS (Network File System), and ADL (Azure Data Lake) file systems. It provides information such as total folder size, number of folders, subfolders, levels, aggregate file count, top file types, and file size range analysis chart. 

      Also offers a concise breakdown of files within folders, including their name, type, size, and last modified date. The Tree View feature allows further navigation to folders and subfolders.

      For further details, please refer to the File Manager Deep Dive.

      API & API Attributes

      APIs (Application Programming Interface) and API Attributes are now supported in the Data Catalog, allowing for governance such as access management, classification, curation, and manual lineage.

      ROPA

      ROPA (Record of Processing Activities) helps organizations assess data privacy risks and implement necessary measures. Users across various departments handling PII (Personally Identifiable Information) can record activities, collaborate, generate reports, and take stakeholder approvals before finalizing and storing reports. The platform also sends reminders for timely validation and updates.

      For further details, please refer to the ROPA Deep Dive.

      Data Access Management (RDAM-Redesign)

      RDAM has been renamed to Data Access and now includes sub-modules "Data Access Management" and "Data Access Audit."

      The Data Access Management module allows for managing access to catalog objects from OvalEdge and synchronizing it with the source. The data Access Admin role was exclusively introduced to manage module functionalities, including creating/modifying roles, groups, and users, defining permissions on data objects, and enforcing policies (masking policies, row access policies). 

      Any action that results in a change in data through the Data Access Management module gets audited in the Data Access Audit module, including the action that took place, the timestamp of when it occurred, the user responsible, and a brief description.

      Important: The primary focus of this release is the Snowflake connector. Future releases will extend support to Redshift and other connectors.

      Custom Fields

      Custom Fields now have a user-friendly interface for creating different types of fields. 

      Users can organize fields up to six sections on the data catalog summary page. The History icon is provided for each custom field type to track changes over time. 

      A separate tab is provided for System fields to show/hide in the data catalog summary page. 

      For further details, please refer to the Custom Fields Deep Dive.

      Enhancements

      User Interface 

      To enhance overall usability and user experience, OvalEdge introduces a refined user interface.

      • Redesigned User Interface: The Home, Tags, Data Catalog, Business Glossary, Service Desk, Dashboards, and Projects modules have undergone a visual transformation, providing users a user-friendly interface.

      • Redesigned Application Buttons: The buttons in the application have been redesigned to enhance the visual appeal

      • Color-Coded Terms: Terms are now color-coded with dots corresponding to their respective domain colors for easier identification.

      • Inline Edit Options: Users can edit and delete Tags and Terms directly from the Table List View

      • Tooltips for Enhanced Information: Hovering over Tags, Terms, and Metadata Descriptions reveals tooltips displaying hierarchy, descriptions, and complete metadata descriptions

      • Certification Management: Inline edit options for Certifications allow users to edit certification types directly from the Table List View

      • User Information Tooltip: High-level user information, including name, userID, and roles, is now conveniently displayed as a tooltip when users hover over the User Name.

      • Inline User Modification: Users can now modify user details directly from the Table List View

      • Redesigned Configure and System View: The Configure and System View have been redesigned, presenting a dropdown that allows users to view all system and custom views for improved navigation and accessibility.

      Home

      The Home Page has been enhanced with multiple new sections explained below

      • Navigation Bar:

        • Glossary: The dropdown menu allows users to explore different domains and terms. Hovering over a domain displays the categories and terms created under the domain.

        • Tags: It allows users to browse different tags. Hovering on the dropdown icon reveals child tags nested within the Parent Tag, and the left and right arrows are used to discover more Tags.

      • Waiting for My Approval: Displays the 10 most recent service requests that need approval from the user.

      • My Requests: Displays the 10 most recent open service requests raised by the user.

      • My Assigned Tasks: Displays the 10 most recent assigned tasks related to the project.

      User Profile 

      • The "My Resources" and its sub-sections have been moved to the User Profile for easier access. 

      • The Inbox feature has been enhanced by categorizing notifications into sections such as Data Catalog, Business Glossary, Projects, Service Desk, Governance Catalog, Data Quality, and System Alerts. This allows users to receive notifications related to specific areas of the application.

      • My Watchlist now includes Databases, Tables, Table columns, Reports, Report Columns, Codes, APIs, API Attributes, Domains, Terms, ROPA Processing Activities, and ROPA Reports. Users get notifications for metadata changes, source metadata alterations, and significant data modifications.

      • In My Watchlist, previously, viewer licenses didn't have access. All users, including those with viewer licenses, can access My Watchlist.

      • My Permissions have been renamed 'My Desk' and added to the User Profile. It displays the permissions of the logged-in user based on their associated roles. The dropdown menu at the top left provides flexibility to select from Governance roles and Access in OvalEdge.

      • The "My Profile" section now allows users to customize notification preferences for various channels, including MS Teams, Google Chat, Email, and Slack, providing a more personalized and user-friendly experience. 

      For further details, please refer to the My Resources Deep Dive

      Global Search

      • The Global Search bar features a left-side dropdown filter to refine search results by object type. It provides quick access to the five most recent searches, allowing navigation to previously viewed items.

      • Advanced Search functionality is now available on the right side of the Global Search bar. The icon activates after search results are displayed, further narrowing results based on entered keywords.

      • Three new System Settings control the visibility of search results based on data object titles, descriptions, or attributes.

      For further details, please refer to the Global Search Deep Dive

      Tags

      • The Tags breadcrumb has been improved by incorporating a three-dot icon designed to manage situations with many parents and multiple parent hierarchy cases.

      For further details, please refer to the Tags Deep Dive

      Data Catalog

      • New out-of-the-box Systems Views have been added:

        • System View - Virtual Objects: It displays Virtual Objects created in the application and is available for Tables, Table Columns, Reports, and Report Columns.

        • System View - Temp Lineage Objects: It displays all the Temporary Lineage objects within the application and is available for Tables, Table Columns, Files, and File Columns.

      • The Certification of data objects can now be performed at the column/attribute level (Table Columns, File Columns, Report Columns, and API Attribute level).

      • The Classifications field is now added to the summary pages for tables, files, file columns, reports, report columns, APIs, and API Attributes to display the classifications configured to the term associated with the data object.

      • A new column, “Reference Count,” has been added to the ListView and summary page that displays the count of references made to the data object. A Quick View icon is also provided to view the details of the references.

      • A new 'Profiling Status' column has been added to display the profile status, allowing users to filter options based on profiling status 'Profiled,' 'Unprofiled,' and 'Sample Profiled.’

      • A Tableau icon has been introduced in the Reports Summary Pages of Tableau, which, upon clicking, navigates the user to the Report on Tableau directly from OvalEdge.

      • There are more than 20 new OvalEdge reports available for immediate consumption.

      For further details, please refer to the Data Catalog Deep Dive

      Business Glossary 

      • A dedicated domain summary page has been newly added to display the domain details; it can be accessed via Business Glossary and Domain Security.

      • Suggest a Term option now redirects users to the service request page to select the domain from the dropdown and display category and subcategories (optional fields) associated with the domain. 

      • A new Status button has been introduced to indicate whether the term is in a published, draft, or pending approval status. Additionally, an authorized user can directly publish the term using the provided checkmark icon next to the Status button.

      • The Related Objects section has been enhanced. Users can add objects related to the term and define the relationship by clicking the edit icon visible when hovering over the relationship type. 

      • In the Term Summary Page, a new tab named Relationships Diagram has been introduced to display a term's relationship with other terms and data objects within the ecosystem. 

      • The User Interface of the Tree View has been enhanced. Users can now view the Quick details of the Categories and Subcategories of the domain.

      For further details, please refer to the Business Glossary Deep Dive

      Dashboards

        • To improve the user experience, all Dashboards in our application's Dashboard module are now displayed in Tile View.

          • New System Dashboards: The Domain Relationship Dashboard illustrates relationships between multiple domains within the organization. It visualizes how terms are related to each other across domains. Users can hover over a domain to access detailed insights such as categories, subcategories, relationship counts, and specific relationships. 

          • New Custom Dashboards: The application now has Custom Dashboards, allowing users to create personalized dashboards, organize reports, categorize reports through labels, and manage roles. Users can update dashboard details through the security module's dashboard tab, which offers access control for the entire Dashboard.

      For further details, please refer to the Dashboards Deep Dive

      Projects

      • Users can create projects via a project creation service request

      • The Project Task pop-up window is now streamlined by combining the task and status sections, providing Object Name, Status, Assignee, Description, Comments, and History details. 

      • The Download Projects functionality is improved to allow users to download all details displayed in the list view.

      For further details, please refer to the Projects Deep Dive

      Service Desk 

      • Release6.2 introduces a stepper feature to enhance the clarity and progression of each phase in a service request that includes: 

        • Select items

        • Enter details and submit

        • Review tickets

        • Approve requested items

        • Provide additional information

        • Fulfillment

      • New system templates have been introduced to allow users to raise service requests. Streamlined template organization by transferring selected templates from system templates to custom templates for better customization and removing custom object types and custom request types.

      • New options to create service requests have been introduced for the Tags, Data Catalog, and Projects modules. When a service request is created from the Data Catalog, the system automatically groups similar requests together, streamlining the process.

      • A new tab, 'My Approval History,' is now available to view the approval history.

      • Service Requests can now be bulk approved or rejected through a user-friendly interface with checkboxes in the list view. 

      • Service Requests can now be saved as drafts in the Creation phase.

      For further details, please refer to the Service Desk Deep Dive

      Data Quality 

        • Data Quality Rules

          • The Data Quality Rules creation process now includes the option to select supported object types and their corresponding functions, simplifying the selection process.

          • The Data Quality Functions’ Help has been updated with comprehensive information, listing captured statistics, supported connectors, and supported data types for selected functions. 

          • Validation Modes, Input, and Success Criteria operators have been introduced, providing flexibility in defining rule execution criteria.

          • Statistics generated after DQR execution cover more data quality functions, offering improved insights into associated data objects.

        • Data Quality Remediation Center

          • Cost and Criticality columns have been added in the Data Quality Remediation Center to better understand the impact of failed records.

          • Remediation Help now incorporates Corrective Action and Assistance SQL to support remediation.

          • The introduction of new statuses helps in categorizing reported values. These statuses also allow for the archival of failed records from the Data Quality Remediation Center.

        • Data Anomalies

          • Anomaly Detection Settings have been enhanced to detect anomalies at both the schema and connector levels. Additionally, a skip anomaly option is now available at the object level for each profiling metric. This allows for more granular control over anomaly detection processes.

          • Data Quality Scores

            • Acceptance and Optimal Scores can now be configured with threshold ranges for improved data quality score visualization.

            • A Profile Score Parameter is introduced for the calculation of the DQ Score.

            • Data Quality Function Queries

              • The capability to modify template queries for Data Quality Functions has been introduced to address execution issues for both global and specific connectors.

              • The capability for object-level modification of data quality function queries has been introduced to facilitate distinct configurations for specific data objects.

            Advanced Tools

            Lineage Improvements 

            • Lineage Visualization now uses color differentiation to distinguish between manual (pale blue) and automated (dark blue) lineages, allowing easy identification of origins. Hovering over any data object reveals a 3-dot pop-up menu offering "View History" and "View References" options for viewing historical changes, lineage type, and references, eliminating the need to visit specific data object pages.

            • Users with Meta Write permissions are now restricted from editing automatically generated lineage within the system, except for within the Build Auto Lineage feature, where editing or deletion remains permitted within the Correct Query pop-up and Lineage Shutter window.

            • Temp tables now feature a suffix 0, 1, or Lineage, aiding in their identification within the lineage. This simplification enhances clients' understanding of the context and relationships of these data objects.

            • Users can now select specific lineage levels for download when obtaining lineage information.

            For further details, please refer to the Data Lineage Deep Dive

            Load Metadata from Files 

            • The templates are now converted to the .xlsx file format from .csv, keeping standardization in mind.

            • Three new templates have been introduced for three object types: APIs, API Attributes, and Domains. A new template has also been introduced for creating user-defined Data Quality Functions.

            • A new column called "Action" with a dropdown menu has been introduced for both the template and template with data, which enables users to choose multiple options like Add, Modify, Delete, and No Action for metadata update.

            • Whenever a field is updated or added to the template and uploaded, users will find visible job loggers in the uploaded template, which can be downloaded. These loggers are shown in the columns: "Action Success Message" and "Action Failure Message," they offer transparent feedback for each field, indicating whether the input was successfully updated.

            • The Template Configuration Page now includes a dedicated Excel page for controlling tags, terms, business descriptions, technical descriptions, and custom field behavior. Users can choose options like Append, No Action, and Modify for each attribute, allowing precise control over template changes.

            • Only active custom fields for that object will be displayed for all possible templates.

            • Downloading templates with data is now available for all objects except Data Quality Functions, Datasets, Lineage, and Dataset Correction.

            • Users can now download LMDF Templates in the List view of modules like Data Catalog and Business Glossary using the 'Download' button at the bottom of the page. Upon clicking the button, users are provided with two download options, as listed below:

              • Simple Download: To download object details or attributes configured for the selected view (whether a system view or a custom view) to the local system.

              • Detailed Download: Users can choose the "Detailed" option to either download an empty LMDF template or the data LMDF template for the configured view. The template with data can be downloaded from Inbox > system alert notification and the Job logs.

            For further details, please refer to the Load Metadata From Files Deep Dive.

            Administration

            User Licenses

            • OvalEdge has updated its licensing structure by transitioning Contributor User Licenses to Authors. Additionally, a new parameter in the license key now distinguishes between production and PoC customers, improving alert accuracy after license expiration and ensuring smoother renewal processes.

            Security 

            • API and API Attribute tabs have been included, aligning with other data object tabs. A convenient bulk deletion option for User access to Data objects is now available via the 9-Dots menu. Release6.2 also enhances the handling of Governance Roles for ROPA under Security -> Governance Roles -> Compliance dropdown.

            • A new feature has been implemented for color coding the created domains. This color is now consistently reflected throughout the application. When users create a term in the business glossary for a specific domain, the domain's color becomes visible, and subsequently, the terms created under this domain will adopt the same color scheme.

            • The Dashboards Tab in the Security Module is made for admins, giving them privileges to manage dashboards securely. With Dashboard Security, they control who can view and manage both systems and custom dashboards. 

            For further details, please refer to the Object Security Deep Dive

            Users & Roles

            • Administrators can reactivate deleted or deactivated users via the 9-Dots menu and use filters to distinguish between active and inactive users. Connector Users, Roles, and Policies have been moved from Users & Roles Management to RDAM's associated page (Data Access).

            For further details, please refer to the Users & Roles Deep Dive

            Service Desk Templates 

            • New Service Request Templates have been made to standardize the process of requesting services for these specific objects. Here are the new system-defined templates added to the application:

              • Schema Metadata Change Request

              • Report Column Metadata Change Request

              • File Metadata Change Request

              • File Column Metadata Change Request

              • Project Creation Request

              • Tag Creation Request

              • Role Access 

              • Team Access

              • User License Access 

              • Change Business Glossary Term Structure

              • Delete a Term

            • New Object Types and Request Types have been added to facilitate the new service desk templates. These can be utilized when creating custom templates.

            For further details, please refer to the Service Desk Templates Deep Dive

            Bridge 

            A compute engine model now supports the existing Bridge setup, offering users increased flexibility and customization. Users can choose between the pre-existing and revised models to align the system precisely with their specific requirements.

            • Optimized Request Distribution: In this updated configuration, incoming requests are intelligently routed to the Orchestrator. This efficiently manages the load and directs requests to available compute engines.

            • Improved Request Handling: In the conventional model, requests were managed using a queueing mechanism, which had limitations. However, OvalEdge implemented a dynamic load distribution mechanism in the revised model to process requests efficiently, minimize wait times, and enhance overall system responsiveness.

            • Bridge Automation Enhancements: OvalEdge introduced two pivotal options to streamline bridge setup and management:

              • Restart: The 'Restart' option allows users to restart both the bridge client & bridge server and the compute engines, ensuring system reliability and stability.

              • Update: The 'Update' function allows users to ensure that the bridge setup is always up to date and adaptable to changing requirements.

            Bridge Log Management Enhancement and Automated Log Retrieval:

            All client logs were consolidated into one file, requiring manual retrieval. To address this, significant changes were implemented:

              • Unified Log Storage: OvalEdge merges Application logs and NiFi Logs into a single log file for convenient access

              • Custom Logging for OvalEdge Application: OvalEdge introduced custom logging for the OvalEdge Application with a dedicated log file for application-specific logs

              • Automated Log Retrieval: The log retrieval process at the client's location has been automated, eliminating a manual log provision

              • Enhanced Viewing in OvalEdge Log Viewer: Automatically retrieved logs are seamlessly displayed in the OvalEdge log viewer, facilitating prompt issue resolution

              • Flexible Log Retrieval Scenarios:

                • Scheduled Mechanism: OvalEdge incorporates a NiFi processor ('getFile') into the Client Server, sending all application logs to a designated server path periodically, simplifying log retrieval

                • Retrieving Logs at Any Time: A custom endpoint triggers log retrieval from the NiFi client whenever required. This endpoint moves the most recently modified log file to a custom folder, ensuring real-time access for immediate viewing and analysis.

                OvalEdge APIs 

                • Two new User APIs have been added: a PUT API (User License) to update the User License and a POST API (User Reactivate) that can reactivate the deactivated users.

                • A new Service Desk GET API (getActiveTemplatebyName) is added to get the Active ticket template for the given request name and request object name, which is in a published state.

                • Two new Endorsement APIs have been added: the POST API to insert endorsements and the GET API to retrieve average endorsement ratings.

                • Two new Collaboration APIs have been added: the POST API to insert collaboration messages and the GET API to retrieve collaboration messages.

                • With the introduction of APIs & API Attributes Cataloging, Two Object Group APIs have been added, three new Object APIs, and three new Object Attribute APIs. These APIs will help update or fetch API details with the POST and GET methods, respectively. 

                • Users have the capability to retrieve multiple tables, up to a maximum of 50, by using commas in the GET API field (table name) - specifically in the api/column/getTableColumnsByName.

                • Access to the GET method for specific users can be granted by OvalEdge through the Users & Roles configuration found in the System Settings.

                • The improvements made to the Report APIs, specifically under 'api/reports/all,' empower users to retrieve crawled reports precisely by utilizing 'offset' and 'limit' values.

                • In the User API, the GET /api/user/getUserList endpoint has been enhanced to include support for offset and limit options. This allows users to retrieve user lists with greater precision and control over the results.

                • New APIs have been created to support Power BI reporting, allowing the generation of success metrics reports specifically tailored for Power BI.

                New Connectors 

                Connector Name

                Type

                Crawl

                Profile

                Lineage

                DQ

                Query Sheet

                Bridge 

                Connectivity Information

                Apache Pulsar

                Integration Tool - RDBMS

                Yes

                Yes

                No

                No

                No

                Yes

                REST API connects to the data source to crawl and profile.

                AWS AppFlow

                Integration Tool

                Yes

                NA

                Yes

                No

                NA

                Yes

                AppFlow SDK connects to AWS AppFlow to crawl and build lineage.

                AWS Quicksight

                Reporting Tool

                Yes

                NA

                Yes

                No

                NA

                No

                SDK driver connects to the data source to crawl and build lineage.

                Azure Key Vault

                Integration Tool

                No

                No

                No

                No

                No

                Yes

                OvalEdge creates the Azure Key Vault connector to store keys, and these Azure Key Vault keys will be utilized in other connectors created by OvalEdge. The actual values will be used as connector attribute keys whenever users connect to the source system.

                Azure DevOps Repo

                FILES

                Yes

                No

                No

                No

                No

                No

                REST APIs connect to the data source to crawl.

                Azure ML

                ETL

                Yes

                NA

                No

                No

                NA

                No

                REST API connects to Azure ML to crawl.

                Azure Synapse

                RDBMS

                Yes

                Yes

                Yes

                No

                No

                No

                JDBC driver connects to the data source to crawl, profile, and build lineage.

                Box

                FILES

                Yes

                No

                No

                Yes

                No

                No

                Java SDK connects to the data source to crawl.

                DB2 for z/OS

                RDBMS

                Yes

                Yes

                Yes

                No

                Yes

                Yes

                JCC driver connects to the data source to crawl, profile, query, and lineage.

                DBT Core

                ETL

                Yes

                No

                Yes

                No

                No

                Yes

                The latest manifest file from a DBT project is retrieved by the application and saved as source code to build the lineage.

                Erwin CSV Import

                RDBMS

                Yes

                No

                No

                No

                No

                No

                The CSV files from Erwin Data Modeler are read using Erwin CSV Import to crawl.

                Feature Manipulation Engine (FME)

                ETL

                Yes

                No

                Yes

                No

                No

                Yes

                Files produced by FME are parsed within a specified file path. These files contain metadata related to each data flow to build lineage.

                GitLab

                FILES

                Yes

                Yes

                No

                Yes

                No

                Yes

                REST API connects to the data source to crawl.

                IBM DataStage

                ETL

                Yes

                No

                Yes

                No

                No

                No

                Export jobs from the DataStage and save them in the NFS path to crawl and build the lineage.

                IBM Cognos 10.2

                Reports

                Yes

                No

                Yes

                No

                No

                No

                JDBC driver connects to the data source to crawl and build lineage.

                NetSuite CRM JDBC

                RDBMS

                Yes

                Yes

                No

                No

                Yes

                Yes

                JDBC driver connects to the data source to crawl, profile, query, and build lineage.

                OracleFusionHCM

                RDBMS

                Yes

                Yes

                No

                No

                No

                Yes

                REST API connects to the data source to crawl and profile.

                Qlik Sense Cloud

                Reports

                Yes

                No

                Yes

                No

                No

                Yes

                REST APIs connect to the data source to crawl and build lineage.

                Redis

                NoSQL

                Yes

                Yes

                No

                No

                NA

                No

                SDK driver connects to the data source to crawl and profile.

                Salesforce Reports

                Reports

                Yes

                No

                Yes

                No

                No

                Yes

                APIs connect to the data source to crawl and build lineage.

                Spline

                ETL

                Yes

                No

                Yes

                No

                No

                No

                OvalEdge utilizes the Spline connector to build and fetch lineage through APIs.

                SSAS Lineage

                		  

                Yes

                No

                Yes

                No

                No

                No

                SSAS plugin connects to the data source to crawl, profile, and query.

                Sybase ASE

                RDBMS

                Yes

                Yes

                Yes

                No

                Yes

                No

                jTDS driver connects to the data source to crawl, profile, query, and build lineage.

                SybaseIQ

                RDBMS

                Yes

                Yes

                Yes

                No

                Yes

                No

                sybase.jdbc4 driver connects to the data source to crawl, profile, query, and build lineage.

                Zendesk

                RDBMS

                Yes

                Yes

                No

                No

                No

                Yes

                REST APIs connect to the data source to crawl and profile.

                New Advanced Jobs

                Advance Job Name

                OvalEdge Module

                Description

                Load oereportext table for reporting framework

                Reports

                The objective of this job is to generate predefined reports in the OvalEdge DB.

                Example: Reports with the total number of tables with business descriptions, tables with no relationship, tables with zero row count, etc, are displayed.

                On the report catalog, the created reports for OvalEdge DB can be viewed.

                Advance Job for Indexing Existing Data into ElasticSearch

                Elastic Search

                This advanced job allows the indexing of pre-existing data into Elasticsearch and controls the indexing process based on the specific object types chosen.

                Enter the object type names that require support in Attribute1 by providing their names, such as 'oetable' or 'oeschema'. Data corresponding to that specific object type will be indexed in Elasticsearch. If there are multiple object types that need to be indexed, they should be separated with commas. If no object types are provided, data from all object types will be indexed.

                Attributes:

                Comma separated Object Types - oetable,oecolumn, etc.,

                Sync Project Status and stats for old and new project

                Projects

                Advanced job is created to sync the old and new project status and stats in the updated version. It is required to migrate the current application version to 6.0.

                Migrate Data To Denormalized Tables

                Data Catalog

                This job will Migrate Data To Denormalized(ext) Tables

                Servicedesk V1

                Service Desk

                This advanced job helps to migrate existing service desk templates to a new version. This allows users to select existing templates and fill out the mandatory fields before raising service requests on multiple objects for multiple users.

                Note: No attribute is required to execute this job.

                Migrate User License and Connector License to 61

                Users & Roles

                This job will update the User and Connector License Type based on current Permissions to 6.1.

                No attributes are needed

                Update Schedule Next Execution Date Time

                Job Workflows

                The purpose of this job is to update the next execution date & time in the database > Schedule table > Next Execution date column. This gets updated only when the Next Execution date field is empty or null. It is important to note that it is mandatory to run this advanced job for the first time when the database is new or updated.

                Attributes not needed.

                Term Masking Migration JOB

                Business Glossary

                This job migrates masking policies assigned to terms and their associated data objects from older versions to the 6.1 version.

                Custom Field Migration JOB

                Custom Fields

                To migrate custom fields to 6.2

                Notification Preferences Migration

                Notifications

                This job will migrate notification preferences

                Enable system dashboards

                Dashboards

                To enable the Dashboard tab in the Administration> Security module.

                Attributes:

                No attributes are needed.

                Migrate favorite dashboard to new dashboards flow

                Dashboards

                To migrate all existing default dashboards to Administration > Security > Dashboard Security, where admin users can create new dashboards based on requirements.

                Attributes:

                No attributes are needed.

                Update Origin for Objects

                Data Catalog

                This job will update the origins for existing objects

                Advanced Jobs Removed in Release6.2

                Advanced Job Names

                Class

                Build BusinessGlossary for table column

                com.ovaledge.oasis.advance.BuildBusinessGlossaryAuto

                Build Terms

                com.ovaledge.oasis.advance.TermBuilderAIService

                Process CouchDb Lineage

                com.ovaledge.oasis.advance.CouchDbAdvanceJob

                Advance Job for updating editor from md to froala

                com.ovaledge.oasis.advance.MdEditorMigration

                Load DataQuality Function

                com.ovaledge.oasis.advance.LoadDataQualityFunctionsSql

                Build Lineage and Associate Term

                com.ovaledge.oasis.advance.AssosciateTermLineage

                Process File Data Quality Rules

                com.ovaledge.oasis.advance.DQFleRuleProcessorJob

                Update technical table and column descriptions from user table

                com.ovaledge.oasis.advance.AssignTableTechDescriptions

                Servicedesk Data Migration

                com.ovaledge.oasis.advance.TransferServicedeskData

                Reference Data CodeList

                com.ovaledge.oasis.advance.ReferenceDataCodeList

                Download Term Association Details

                com.ovaledge.oasis.advance.DownloadTermAssosciations

                Object Tagging

                com.ovaledge.oasis.advance.ObjectTaggingService

                Object Access History

                com.ovaledge.oasis.advance.ObjectAccessService

                SqlServer RDAM Sync

                com.ovaledge.oasis.advance.SqlServerRDAMSyncJob

                Sort DataCatalog Tableau Reports

                com.ovaledge.oasis.advance.SortDataCatalogReports

                VALIDATEDBUDF

                com.ovaledge.oasis.advance.ValidateUDFDataBricks

                ENCRYPTDBPII

                com.ovaledge.oasis.advance.EncryptDataBricksPII

                BUILDENCRYPTDBPIIVIEWS

                com.ovaledge.oasis.advance.BuildEncryptDatabrickViews

                Create Team Using Roles

                com.ovaledge.oasis.advance.CreateTeamUsingRoles

                CacheSummaryResults

                com.ovaledge.oasis.advance.CacheOEPages

                Create AccessCart For Existing Users

                com.ovaledge.oasis.advance.CreateAccessCartForExistingUsers

                S3 policy marker file reader

                com.ovaledge.oasis.advance.S3PolicyMarkerFileReader

                Tag Relation Creator

                com.ovaledge.oasis.advance.TagRelationCreator

                Catalog Creator

                com.ovaledge.oasis.advance.CatalogCreator

                CDR Integration Job

                com.ovaledge.oasis.advance.CDRIntegration

                Redshift Column Masking

                com.ovaledge.oasis.advance.EncryptRedshiftPII

                GDQR Custom Query Process

                com.ovaledge.oasis.advance.GdqrCustomQueryJob

                Snowflake Tag Sync Service

                com.ovaledge.oasis.advance.SyncSFTaggingService

                Load Snowflake SQLS

                com.ovaledge.oasis.advance.LoadSnowflakeSqlsWithBridge

                Migrate Terms to organization and departments

                com.ovaledge.oasis.advance.HandleTermsForDQR

                ALERT FILE CHECK

                com.ovaledge.oasis.advance.AlertFileCheckChanges

                DataLake Analysis First Level

                com.ovaledge.oasis.advance.DataLakeFirstLevelAnalysisAdvanceJob

                 

                New System Settings

                Users & Roles

                Key 

                Description

                oe.ropa.contributors

                To configure administrative privileges for the ROPA feature, assign a role to perform actions such as adding, editing, and deleting ROPA.

                Parameters:

                The default value is set to OE_ADMIN.

                Select the role(s) by clicking on the field to designate them as ROPA Contributors.

                is.apirole.mandatory

                This system setting acts as a trigger to authorize access to APIs for roles designated in the system settings "oe.apirole.read" and "ovaledge.api.role".

                Parameters:

                • If set to true, the roles defined in both "oe.apirole.read" and "ovaledge.api.role" will be granted the privilege to access the APIs.
                • If set to false, it will override the roles specified in "oe.apirole.read" and "ovaledge.api.role", granting all users the ability to access the APIs.

                oe.apirole.read

                To grant view access for multiple roles exclusively through the HTTP GET method.

                Parameters:

                • The default value is OE_ADMIN.
                • Select the role(s) by clicking on the field to designate them as Project Administrators.

                role.rdm.admin

                This system setting allows configuring admin privileges to a role for the Reference Data Management feature. Assign a role to perform actions such as creating, deleting, updating stewards, viewing audit trails, and more.

                Parameters:

                • The default value is OE_ADMIN.
                • Click on the field to select a role you assign as Reference Data Management Admin.

                role.gov-app.admin

                To configure administrative privileges to a role(s) for the Governance Application feature to perform actions such as adding, editing, and deleting apps.

                Parameters:

                • The default value is set to OE_ADMIN.
                • Select the role(s) by clicking on the field to designate admin privileges for Governance Apps.

                 

                Notifications

                Key 

                Description

                ms.teams.client.id

                Configure the Microsoft Teams client ID for authenticating the integration with Microsoft Teams.

                Parameters:

                • The default value is Empty.
                • Enter the value in the field provided.

                ms.teams.client.secret

                Set the Microsoft Teams client secret to authenticate and authorize access for the integration.

                Parameters:

                • The default value is Empty.
                • Enter the value in the field provided.

                ms.teams.tenant.id

                Specify the Microsoft Teams tenant ID to identify and authenticate the tenant for the integration.

                Parameters:

                • The default value is Empty.
                • Enter the value in the field provided.

                ms.teams.redirect.uri

                Define the Microsoft Teams redirect URI for handling the callback after authentication and authorization.

                Parameters:

                • The default value is Empty.
                • Enter the value in the field provided.

                google.chat.credentails.path

                Provide the file path to the Google Chat credentials for authentication and authorization in the integration.

                Parameters:

                • The default value is Empty.
                • Enter the value in the field provided.

                 

                Global Search

                Key 

                Description

                globalSearch.objectMatch.weightage

                This configuration allows users to adjust how search results are prioritized and displayed by identifying matching search keywords in the names and titles of data objects.

                 This adjustment depends on the "globalSearch.objectDescriptionsMatch.weightage" and "globalSearch.objectOtherAttributesMatch.weightage" system settings, which adjust results related to descriptions and other attributes, respectively. The displayed search results are determined by the greatest value among the three specified system settings.

                Parameters:

                The default weight is set at 2.

                Enter the value in the field provided.

                globalSearch.objectDescriptionsMatch.weightage

                This configuration allows users to adjust how search results are prioritized and displayed by identifying and matching search keywords in the descriptions (Business, Technical, and Source Descriptions) of data objects. This adjustment depends on the "globalSearch.objectMatch.weightage" and "globalSearch.objectOtherAttributesMatch.weightage" system settings, influencing results related to Names/Title and other attributes, respectively. The displayed search results are determined by the greatest value among the three specified system settings.

                Parameters:

                The default weight is set at 3.

                Enter the value in the field provided.

                globalSearch.objectOtherAttributesMatch.weightage

                This adjustment allows users to adjust how search results are prioritized and displayed by identifying and matching other attributes of data objects (Tags, Terms, Custom Fields, etc). This adjustment depends on the "globalSearch.objectMatch.weightage" and "globalSearch.objectOtherAttributesMatch.weightage" system settings, influencing results related to Names/Title and other attributes, respectively. The displayed search results are determined by the greatest value among the three specified system settings.

                Parameters:

                The default weight is set at 3.

                Enter the value in the field provided.

                 

                Data Quality

                Key 

                Description

                anomaly.detection.analysis.algorithm.selection

                These values represent the algorithm that will be used for anomaly detection on different objects.

                Parameters:

                Enter the algorithm that should be considered to identify anomalies.

                anomaly.detection.analysis.algorithm.list

                Configure anomaly detection analysis algorithms.

                Parameters:

                Enter the names of the algorithms that should be used, separated by commas. Currently, we support the 'iqr' (interquartile range) and 'deviation' algorithms.

                anomaly.detection.analysis.enabled

                To activate or deactivate the anomaly feature within the application.

                Parameters:

                If set to "True," the anomaly feature is activated, allowing it to function as intended.

                If set to "False", the anomaly feature is deactivated and the connector and data object-level anomaly-related settings will appear grayed out and will not function until set to “True”.

                 

                Service Desk

                Key 

                Description

                servicedesk.template.fields.limit

                Specify the maximum number of fields that can be configured within a service desk template. These could include fields such as requester name, issue description, and other relevant information that the service desk template is designed to capture and manage.

                Parameters:

                • The default value is 20.
                • Maximum value is 50.
                • Enter the value in the field provided.

                servicedesk.approvalworkflow.team.role.limit

                Specify the maximum number of users within the team or role who can approve the request.

                Parameters:

                • The default value is 5.
                • Maximum value is 20.
                • Enter the value in the field provided.

                servicedesk.business.hours

                To customize and define the operational business hours in a day (using a 24-hour format) for SLA (Service Level Agreement) calculation. 

                Parameters:

                • Value can be entered within the range of 00:00 - 23:59.

                servicedesk.business.days

                Specify the relevant days considered Business Days in a week for SLA calculation.

                Parameters:

                • Values accepted: Mon (Monday), Tue (Tuesday), Wed (Wednesday), Thu (Thursday), Fri (Friday), Sat (Saturday), Sun (Sunday).

                servicedesk.holiday.days

                To specify dates that will be excluded from the SLA calculation. This ensures that holidays are excluded from the SLA calculations.

                Parameters:

                • Enter dates in dd-mm-yyyy format. The chosen days will not be considered for SLA calculation.

                 

                Lineage

                Key 

                Description

                lineage.spline.file.connection

                To specify the file connection ID for constructing lineage on selected file connections for the Spline connector.
                Parameters:
                Specify the File Connection ID in the field provided. 

                lineage.businessview

                The Business View simplifies lineage for non-technical users by displaying only source and target information, excluding intermediary details, for easier comprehension.

                Parameters:

                • The default value is set to False.
                • If set to True, the Technical View is enabled, showcasing the detailed flow of lineages.
                • If set to False, the Business View is enabled.

                 

                AI

                Key 

                Description

                openai.activation.token

                It allows establishing a secure connection and utilizing the ChatGPT service. This token serves as the authentication key, allowing Ovaledge to integrate and communicate with ChatGPT seamlessly.

                Parameters:

                • Users are required to provide their ChatGPT token in the specified field.

                 

                Others 

                Key 

                Description

                impactanalysis.source.objects.limit

                This configuration allows the user to specify the maximum number of source objects that can be added to a single impact analysis.

                Parameters:

                Enter the value in the field provided.

                status.assignee

                This will enable/disable the assignee list in the status popup of the Processing Activity and Report summary page.

                Parameters:

                The default value is set to False.

                bridge.nifiversion

                To configure the NiFi Bridge version.

                Parameters:

                • Enter the desired version of the NiFi Bridge.

                bridge.compressed.value

                To control and determine the threshold or size at which data payload compression is applied to any request originating from the bridge side. For Example, if set to 10KB, any data payload exceeding 10 kilobytes in size will be compressed before transmission, whereas payloads smaller than 10KB will not undergo compression

                Parameters:

                • The default value is set to 10KB.
                • Enter the desired value in the field provided.

                scroll.pagination.search.limit

                This limit is to display the number of users for each scroll wherever scroll pagination is available

                Parameters:

                • The minimum value is 20.

                enable.project.statusbar

                Enable/disable the Status Bar functionality in the project module.

                Parameters:

                • The default value is False.
                • If set to True, the Status Bar functionality is enabled in the project module.
                • If set to False, the Status Bar functionality is disabled in the project module.

                supported.folderanalysis.connectors

                Specify the connector names on which folder analysis can be performed to determine the size and count of folders.

                Parameters:

                • Please enter the value in the provided field.

                ovaledge.gov.app.host

                This allows the user to configure the host server URL for governance apps, allowing the redirection of users to governance apps via email or direct links.

                Parameters:

                Enter the URL in the provided field.

                header.glossary.reload.limit

                To set a limit on the number of domains to be preloaded within the header by configuring a specific value. As users scroll down, the system loads more domains in the background, enhancing performance.

                Parameters:

                The default value is 20.

                The configured value will be the number of domains displayed in the header in one go, with the remaining domains refreshed on scroll.

                domain.default.color

                This configuration is used to define the default color of the domain icon in the Business Glossary Dashboard.

                Parameters:

                The default value is 067FA7.

                Enter the desired Hexa color code in the field provided. 

                domain.icon.max.width

                This configuration is used to specify the maximum width of the domain icon in the Business Glossary Dashboard.

                Parameters:

                The default value is 150 pixels.

                Enter the value in the field provided.

                domain.icon.min.width

                This configuration is used to specify the minimum width of the domain icon in the Business Glossary Dashboard.

                Parameters:

                The default value is 50 pixels.

                Enter the value in the field provided.

                questions.wall.panel

                To designate stakeholders (users or teams) for the question wall who will receive email notifications when a question is posted.

                Parameters:

                Enter the users/teams, separated by commas.

                ovaledge.extendedheader.display

                This configuration is used to control the visibility of the Glossary Terms and Tags carousel header within the application. 

                Parameters:

                The default value is set to True.

                If set to True, the glossary terms and tags section will be displayed across the top of the application.
                If set to False, both the glossary section and carousel headers are disabled, ensuring they are not displayed anywhere in the application.

                file.tree.pagination.limit

                To define and display the maximum number of records in the Data Catalog's file tree view.

                Parameters:

                • The default value is set to 100.
                • Input the value in the field provided. 

                folder.analysis.api.limit

                To set the threshold for the number of API calls allowed for Folder Analysis. The system automatically stops further calls when the number of calls reaches the configured threshold.

                Parameters:

                • The default threshold is set at 5000.
                • Enter the value in the field provided.

                bridge.request.timeout

                It is used to configure bridge request timeout interval

                ovaledge.instance.name

                Allows to set the environment name to display it under the OvalEdge icon in the top left corner of the main header. Additionally, notifications will have a prefix indicating the instance type (e.g., dev, prod) for users to distinguish notifications based on the instance.

                Parameters:

                The default value is set to empty.

                Enter the Instance Name in the field provided. Supports alphanumeric characters up to 15 characters in length.

                Copyright © 2024, OvalEdge LLC, Peachtree Corners GA USA