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

      Release6.3.4

      The OvalEdge Release6.3.4 introduces key enhancements, bug fixes, and change impact across various modules, improving functionality, usability, and system performance.

      Key highlights include:

      Release Type   

      Release Version

      Build

      <Release. Build Number. Release Stamp>

      Build Date

      Service Release

      Release6.3.4

      		 Release6.3.4.6340.a4b576d 28 January, 2025

      Login

      New & Improved

      • OvalEdge now supports integration with ADFS using OpenID Connect (OIDC) protocol, enabling secure OAuth2-based authentication. This enhancement allows organizations to configure ADFS application groups and set up the OvalEdge server for seamless user authentication via ADFS credentials.
      • Before logging into the OvalEdge application, a new Warning Banner is displayed to inform users about the organization's privacy and security notices. When the user clicks the Okay button, the Sign In page is displayed, allowing the user to enter their credentials and sign in.
        A new system setting, 'login.warning.enable,' has been introduced to display a warning banner when logging into the OvalEdge application.
        • If set to 'true,' the warning banner appears.
        • If set to 'false,' the warning banner does not appear.
        To display content on the banner, another system setting,  'login.warning.description,' has been developed, and 'login.warning.enable' is set to 'true.' The description supports up to 2000 characters. Users can click 'Okay' on the banner to enter their login credentials.

      Home

      New & Improved

      • Previously, users could not view the total number of unsuccessful login attempts or the last successful login date on the Home page.
        With this improvement, users can now see the last successful login date and the number of unsuccessful login attempts between the current and previous successful logins on the Home page.

        Configuration:
        To enable this feature:
        • Navigate to Administration > System Settings > Others.
        • Use the key home.lastlogin.enable and set its value to true.
        • By default, this system setting is set to false.

      My Resources

      New & Improved

      • In My Resources > My Project Tasks, drag and drop functionality has been implemented for task cards in the Board view for individual projects.

      • A new component has been built, allowing users to choose language preferences so the application shows in that language. In the My Resources section, go to My Profile and select your preferred language from the drop-down menu. The application will then be displayed in the chosen language.

      Data Catalog

      New & Improved

      • Administrators can now control access to the report preview tab in the Data Catalog and Dashboards. They can enable or restrict other users' access to the report preview tab as needed. Additionally, they can manage report preview access by setting viewer permissions and role-based controls.
        Navigate to Administration > Security > Applications and search for the Application Name (Report - Preview).
      • In the Data Catalog's list view, users now have the provision to add comments when certifying multiple data objects using the 9-dots action menu. This functionality allows users to include relevant comments during bulk certification.
      • The Froala Editor now supports Right-to-Left (RTL) and Left-to-Right (LTR) text alignment when adding business and technical descriptions in Arabic. This enhancement allows users to achieve proper indentation and formatting for languages like Arabic that require RTL alignment.
      • A new feature, 'Add to Impact Analysis,' has been introduced to enhance impact analysis workflows. Users can access this feature in multiple areas. 
        • Navigate through Tables, Table Columns, File, File Columns, Report, and Report Columns, click on the Nine Dots, and select the '+Add Impact Analysis' option. 
        • Alternatively, on the Tables, File, and Report Summary page, go to the Lineage tab, open the Graphical View, locate the nodes section, click on the three dots, and select 'Add to Impact Analysis'. This enhancement provides a streamlined approach to managing impact analysis.
      • Previously, there were no loading bars to inform users when a page was loading. Now, loading bars have been implemented on all the pages in the Data Catalog.

      Fixed

      • In the Data Catalog objects grid view, an issue where the naming conventions of statuses in the "Certification" column and its filter did not match has been resolved. Users will now see consistent certification status names in the 'certification' column and its filter.
      • In the Data Catalog’s Object Summary, the issue of terms becoming invisible in the object summary after being associated with data objects has been resolved. Users can now view the associated term(s) in the object summary without issues.
      • In Data Catalog’s Object Summary, the issue that caused the URL field to be invisible in the business and technical descriptions during edit mode has been resolved. Users can now view the URL field in the pop-up after clicking the "Insert Link" icon.
      • In Report Columns, the issue where the formula field for a virtual report column became non-editable for a manual connector after saving has been fixed. Users can now edit the formula field for virtual report columns linked to a manual connector, even after saving.
      • In Data Catalog’s Object Summary, an issue where the Data tab displayed "No Data Exists" even after crawling and profiling the SSAS on-prem connector has been resolved. Users can now view the data in the Data tab for the SSAS on-prem connector objects as expected.
      • In Data Catalog > Databases > Create New View, the issue that prevented users from creating a Public View when the "View Visible to All" option was selected has been resolved.
        Users can now create and configure Public Views without encountering any issues.
      • In the Data Catalog > Tables, an issue where if the cloned table did not exist, column-level lineage was not built has been fixed. Now, column-level lineage is also built along with table-level lineage.
      • Users can now hide/display the "Generate with AI" button across all the metadata description fields using the system configuration.
      • The Remote Tags section has been removed from the Data Catalog's File Column Summary, as it applies solely to files, not file columns.
      • In the Data Catalog object summary's nine-dots action menu, the label in the 'Update Governance Roles' pop-up has been updated to "Cascade all Governance Roles to Hierarchy."
      • Creating Virtual Tables and Reports no longer requires adding at least one column during setup.

      Business Glossary

      New & Improved

      • Users can now clone any existing term. The cloned term will be created in the same domain but not linked to any specific category or subcategory. It will inherit the following metadata: Business Description, Detailed Description, Tags, Custom Fields, Related Objects, Classification, and Policies.
      • In the Term Summary > Associated Objects, users will now find an "Originative Source" column within each associated object type category tab. This column allows users to mark data objects (e.g., tables, columns, files, APIs) as originative sources, enabling quick identification of the origin of data within the organization.
        This enhancement improves clarity and significantly enhances data traceability, particularly lineage tracking.
      • In the Term Summary, users can now filter report columns in the Associated Objects and Recommendations tabs by connection name. This enhancement simplifies navigation, making it easier to find relevant report columns.

      Fixed

      • In the Term Summary, an issue has been resolved where the metadata curation scores for terms were not updating after running the metadata curation advanced job. Previously, the scores would only refresh when users clicked the metadata curation icon. Now, users can view the updated metadata curation scores for terms automatically without clicking the icon.
      • In the Term Summary, an issue where the associated code count was missing on the summary page has been fixed. Additionally, the issue of connector names not appearing for Codes and Report Type objects in the Associations tab has been resolved. Users can now see the code count in the Term Summary and the connector name details in the Associations section for Codes and Reports.
      • In the Tree View, text wrapping and justification issues in term descriptions have been fixed. Users can now read term descriptions without any text layout problems.
      • Admins can now reset the default system configuration and grant access to only specific Governance Role(s) users to publish the Term.
      • Changes made by SGA to the default classifications within a domain will no longer impact the classifications already checked or unchecked in existing terms within the same domain.
      • Users won't be able to download the masked data when a masking policy is applied to a term associated with a file column.
      • Users can now select multiple objects as authoritative sources.

      Question Wall

      New & Improved

      • The assignee will receive email notifications for the initial question and all follow-up replies.

      Dashboard

      Fixed

      • In Dashboard, previously, when a report was unavailable, the corresponding tile appeared blank, causing confusion. Now, the system displays a placeholder message within the tile to inform users that the report is unavailable clearly. 

      Projects

      New & Improved

      • The Project's Board View has been enhanced to improve object naming conventions, display curated task descriptions, and show task status history.
      • Previously, users needed to manually configure the status workflow when starting a new project. With the "Copy Existing Status Workflow" option, users can choose an existing project from a dropdown menu to apply its workflow to the new project. The new project will default to system-generated statuses if no project is selected.
      • A new "Priority" column has been added to the Projects List View, enabling users to view and manage task priorities.

      Fixed

      • The issue of data stories not showing up in the List View after being added to a project has been resolved. Now, users can see data stories linked to a project in both the List View and the Board View.
      • In All Projects, an issue where the project label in connected modules such as Grid View (Data Catalog, Business Glossary) and tags associations was incorrectly displayed as "Project" even after selecting the default project type as "Access Cart" has been resolved.
        Users will now see the default project type set in the Projects module, and the same is reflected as the project label in all connected modules.
      • A safeguard mechanism has been implemented in projects to prevent the accidental deletion of the default project, whether during single project deletion or as part of a bulk deletion process.

      Service Desk

      New & Improved

      • Automated Metadata Curation allows users to transfer metadata from one report to another. When a new report is created in the source system, and the connector is crawled in OvalEdge, the report is added as an object with its metadata.

        A new request type, Curating New Asset, is introduced and available when Tables or Reports are selected as object types. A custom template guides this process, enabling users to curate metadata for a new report based on an existing one. Users can fill in fields such as Business Description, Technical Description, and Associated Tags.

        During the approval phase, users can select the new report group and name the report. After the request is fulfilled, a virtual report with the curated metadata is created. The virtual report remains in the Data Catalog even if the connector is crawled again. When the report is fully created and crawled in OvalEdge, it is added as a crawled object with the existing metadata from the virtual report.
      • In the Service Desk Template, previously, fields such as Placeholder Text, Tooltip, and Field Label could not be edited once a service request was raised. Additionally, system-defined Workflow Action and Status Labels were not editable. In the current version, these fields are now editable if the template has no pending service requests. System-defined Workflow Action and Status Labels are also editable. A new Description field has been added for Status, allowing users to specify the use case for each System Status and modify the name accordingly, providing greater flexibility and control.
      • Enhanced Service Request Closure Permissions in Service Desk.

      Data Classification Recommendations

      New & Improved

      • In the Governance Catalog, Data Classification Recommendations, the AI configuration for setting the maximum number of data objects for AI recommendations was previously limited to Table Columns. This functionality has now been enhanced to support additional data objects, including Report Columns and File Columns.
      • In the Data Classification Reports Overview, identifying data classifications while filtering and downloading records was challenging for users. Now, a “Classification” column has been added to every object page. This addition provides clear visibility of the classification applied to each data object, enhancing data clarity and accessibility.

      ROPA

      Fixed

      • In ROPA Reports, the issue of Top Users being invisible under the "Top Users" section in the report summary has been resolved. Users can now view the Top Users list.

      Data Quality

      New & Improved

      • In the Data Quality Rule Overview, previously, users had to navigate to the Rule Executions tab to view metrics such as Passed Count, Failed Count, Undetermined Count, and Execution Failed Count. The updated Data Quality Rule module now displays these fields directly on the overview page, providing immediate visibility based on the latest rule execution.
      • The labels for "Report Data Quality Issue," "Report Metadata Change Request," "Term Data Quality Issue," "URL Data Quality Issue," and "Data Literacy" have been corrected to Arabic from the current version to the correct version.
      • The supported data types for the Exasol connector were previously outdated and caused potential inaccuracies in the rule application. Following the update, the data types now align with the accurate list, ensuring consistency and accuracy in applying table column rules. 
      • The Data Quality Remediation Center has been enhanced to display failed values for Custom SQL Rules, addressing a significant limitation in the previous version where failed values were not shown. This improvement allows users to view problematic data directly, enabling quicker identification and resolution of data quality issues.
      •  In Data Quality Rules, users can now create custom SQL rules using the LMDF template, addressing the limitations of the previous version that required manual rule configuration. This enhancement allows users to upload templates containing boolean, statistical, and failed value queries, simplifying the creation of complex or customized rules for their datasets. Additionally, the feature supports direct query uploads via the template, reducing manual effort, streamlining the rule creation process, and ensuring the system efficiently interprets, catalogs, and applies these queries.
      • Previously, Data Quality rules were not directly linked to terms, making it difficult to track their associations. The new solution allows users to add Data Quality rules in the 'Related Objects' section, enabling them to link rules with specific terms and specify relationship types. This change improves tracking and organization, offering a functional way to manage Data Quality rule relationships.
      • Standardized Default View and Enhanced Customization for Data Quality Rules.

      Fixed

      • Change in Operator Default Values
      • Enhanced Access Controls for Inline DQR Menu Actions
      • Accurate User Attribution for Data Quality Rule Modifications
      • In Data Quality Rules, scheduling conflicts are resolved to ensure the "Last Run By" field accurately displays the user who scheduled each rule, even during simultaneous executions.
      • In the Data Quality > Rule Recommendations section, the "Add Objects" widget now displays only the connectors associated with the Data Quality Add-On license.

      Query Sheet

      New & Improved

      • Users can now copy and paste SQL queries into the Query Sheet and execute them without errors.

      Fixed

      • An issue where users encountered blank data when downloading a query related to the Azure Synapse connector after increasing the row count limit has been resolved. Users can now view the complete SQL query data in the downloaded file, regardless of the adjusted row count limit.
      • An issue where an error was thrown when users added the complete SQL code with intermittent line breaks has been resolved. Users can now execute queries, even if the SQL query includes line breaks.
      • An issue where SQL queries failed to execute has been resolved. Users will no longer face query execution issues caused by line breaks, spaces, or other formatting in the SQL commands.
      • Enhanced Security for Query Sheet Column Access

      Jobs

      Fixed

      • An issue where the file name displayed a temp path after downloading has been resolved. Now, users can view the created user ID and timestamp included in the file name for better clarity and tracking.

      Compare Profile Results

      Fixed

      • Previously, the Source and Target drop-down list placeholder was shown as "Please select the connector," is fixed and now showing as "Please select the schema" as per the functionality.

      Compare Schemas

      Fixed

      • An issue was encountered when comparing schemas by selecting Schema A from one connector and Schema B from another, where only the latest crawl date appeared in the Select Date dropdown, even though the schema had been crawled on multiple dates. This issue has been resolved, and now the Select Date dropdown displays all the dates on which the schema was crawled, allowing users to select from a complete set of crawl dates.

      Build Auto Lineage

      New & Improved

      • Lineage dashboard has been enhanced.
      • Metadata propagation has been enhanced.
      • Temp connector is not displayed on the Connectors page.

      Fixed

      • An issue with the clone table not building the lineage in the OvalEdge application when using the Clone function in Snowflake SQL. This issue has been fixed, and the Clone function is now supported in OvalEdge for Snowflake SQL.
      • An issue while building lineage for the Dataset semantic tables expression, a new type of MCode function used in expression i.e. Analysis.Services() has been resolved. Now that function is handled and the lineage is populated for the expression and connected to the SSAS server, which is mentioned in the MCode.

      Load Meta Data from Files

      New & Improved

      • Users who uploaded the Datasets LMDF template with the code type set to "OTHER" encountered an invalid SQL error.

      Fixed

      • In the Load Metadata from Files > Data Quality Rule, an issue with downloading the “Data Quality Rule” template with data from the “Object Name” column has been resolved. Users will now be able to download the Data Quality Rule template with data. 
      • In the Load Metadata from Files > Table Column, when users renamed a downloaded template file and uploaded it an error occurred. This issue has been fixed, allowing users to upload renamed files successfully.
      • In the Load Metadata from Files, when users uploaded table details where the table name and view name were identical, the governance roles were not updated. This issue has been fixed, and governance roles are now correctly updated for these tables on the Data Catalog page.
      • In the Load Metadata from Files > Upload Users, when users logged in using SAML and attempted to upload user data, the upload failed if the username and first name fields were empty. This issue has been fixed, and the sheet now uploads successfully even if these fields are empty.

      OvalEdge APIs

      New & Improved

      • A new API has been developed to retrieve all the reports based on the Report Group ID.
      • A new API '/api/getAssociatedCustomFieldValueObject' has been developed to get the object details with a particular custom field.
      • A new API, DELETE /api/connector/{connectorid}, has been introduced to remove connector information from the OvalEdge application.
      • A new API (GET/api/v1/entity-relationships) has been developed to get the entity relationship information.
      • A new API, 'GET/api/query/lineagegraph' has been developed based on 'lineageid'. This returns the Query details such as query, summary, its associations, references, and lineage details.
      • The Table and Table Column APIs now display all associated term details, including the term ID, domain name, term name, category name, and subcategory name, based on the table or column ID.

      Connectors

      New & Improved

      • The SAP Table connector in OvalEdge is now enhanced to fetch relationships from the source system and display them in the data catalog. A new Relationships option has been added to the connector settings. When enabled, the crawler automatically retrieves the relationships from the source SAP system and displays them in the entity relationship diagram (ERD), providing a clear view of table relationships and improving data governance and discovery.
      • The Crawler options in Connector Settings have been enhanced with a new Indexes checkbox. When users select the Indexes checkbox, indexes from SQL, Oracle, and Greenplum databases are automatically crawled and displayed in the Data Catalog under the Index tab within the Table Summary.
      • A new enhancement has been made for the Sybase connector to build the lineage from files to tables for stored procedures.
      • The size limit for fields in Secrets Manager has been increased.
      • For the Synapse connector, 
        • The Synapse labels from the source system were not crawled in OvalEdge's regular crawling process. Now, an advanced job (Fetching Labels for Synapse Columns) has been developed to crawl the Synapse labels from the source system to OvalEdge.
        • The Azure Active Directory - Password authentication is supported.
      • For the MySQL connector, previously, Username/Password authentication was supported. Now, it has been enhanced to support Azure Entra ID authentication, providing more security for users.

      Fixed

      • An issue in the About OvalEdge section, where the number of connectors was displayed incorrectly, has been resolved. Previously, a temporary connection (Connector ID—1 MySQL) was incorrectly counted as the Base Connector. Now, temporary connections are excluded from the count, and the number of connectors is displayed accurately.
      • An issue with the Power BI connector not displaying the correct lineage status has been fixed. Now, if the lineage is built successfully, the status shows Success. The specific error details are displayed in the Error column if there are errors.
      • For the CartoVista connector, an issue where the connector failed to save after validation due to a database connection error has been fixed. Now, the connector successfully saves after validation.
      • For Qlik Sense, FME connectors, an issue where a null exception occurred while fetching connector attributes during Edit Connector using the 9-dots menu has been fixed. Now, all connector attribute values display correctly when accessing 9-dots > Edit Connector.
      • For SharePoint connector, an issue where the crawling job failed and was unable to catalog the folders and files, which has been fixed. Now, able to catalog the files and folders.
      • For SharePoint connector, an issue such as 'Requested array size exceeds VM limit' has been fixed. The connector now validates successfully.
      • For SQL Server connector, an issue where the Delete Connection job failed while deleting the connector has been fixed. Now, the connector is deleted successfully.
      • For the Looker connector, an issue of an error occurring when the port number was entered, and the connection string was set to 'auto' has been fixed. If the string is set to manual' during validation, the user should enter the port number in the string field. The connector now validates successfully.
      • For Delta Lake Connector, an issue with connection validation has been resolved. Previously, connection validation failed when using a Personal Access Token in internal and client environments or Service Principal Authentication in the client environment. This issue has been fixed, and connections are now validated successfully for both authentication methods.
      • For Qliksense On-Premises Connector, an issue was encountered where report columns were missing during metadata crawling. This issue has been resolved, and now, when users crawl or profile the report, the report columns are successfully fetched from the data source and displayed in the Data Catalog Report Column.
      • For Talend Connector, an error occurred when users attempted to crawl and build lineage using the GitHub Workspace ID, with the job logs stating that the query could not be parsed. This issue has been fixed by manually correcting the query in the Build Lineage > Correct Query page. Users can now successfully build lineage without encountering any errors.
      • Disabling unsupported options for SharePoint Connector

      Known Issue

      • The Google BigQuery connector encounters an issue where the application fails to load the required library, resulting in a ClassNotFoundException error.
        Temporary Workaround:
        A necessary library will be added to the OvalEdge configuration to ensure proper loading.
        Resolution:
        This issue is scheduled to be fixed in the upcoming release.

      Users & Roles

      New & Improved

      • In Users & Roles, previously, when using Okta for authentication, the user's title or job title was not mapped to the corresponding field in the OvalEdge Users table. Now, if an instance uses Okta for authentication, the user's title or job title is correctly mapped to the OvalEdge Users table during login. This update ensures that the user's title or job title is accurately reflected in OvalEdge, improving user data consistency.

      Security

      New & Improved

      • In Administration > Security > Domains, users can now input Domain, Category, and Subcategory names and their descriptions in Arabic, providing improved support for multilingual configurations.

      Service Desk Templates

      New & Improved

      • In Service Desk Templates, for Azure DevOps integration, the mapping of Service Desk Template Fields to Azure DevOps Fields, Area, and Iteration fields was unavailable. This functionality has now been enhanced. When an Azure DevOps ticket is created, the Area Paths and Iteration Paths specified in the Service Desk Template mapper fields are now mapped and displayed in the Azure DevOps ticket.
      • In Service Desk Templates, for the Associated Workflow, the Actor dropdown previously displayed all Team or Role names, even if no users were associated with them. This caused confusion for users.

        This functionality has now been enhanced:
        • The Actor dropdown displays only Team or Role names with at least one user assigned.
        • If a Governance Role is the approver in the workflow and an empty team is assigned as the Governance Role for an object, the workflow will skip that team and move to the next approver.
      • In the Service Desk Template, the default term status for the Term Creation Request template was previously set to "Published." Additionally, system templates were not editable, and custom templates could not be modified once a service request had been raised. In the current version, the default value of Term Status has been changed to "Draft." Custom options in service request templates are now editable when the template is inactive and has no pending service requests.
      • Specific fields in the Service Desk Template and Workflow Actions and Status Labels are now editable if no service requests are pending.

      Custom Fields

      Fixed

      • An issue causing inconsistent visibility of custom fields while navigating between Global Custom Fields and Connector Custom Fields has been resolved. Users can now view the global and connector custom fields without any issues.

      System Settings

      New & Improved

      • A new System Setting (oe.profile.importancescore.threshold) has been developed to define a threshold value for the importance score of data objects in the profiling process. Only data objects with an importance score equal to or greater than this threshold will be included in the profiling. The value should be in the range of 0 - 100.
      • Two separate tabs have been added for APIs and Projects.
      • Previously, the OvalEdge application did not support the Spanish language. Now, the OvalEdge application supports the Spanish language. Navigate to Administration > System Settings > Others, search the key as "ovaledge.locale" and set its value to "Spanish."

      Fixed

      • System Setting 'tags.children.pagination.row.size' has been removed.
      • System Setting 'tags.pagination.row.size' has been removed.
      • System Setting 'is.erd.advancedsettings.enabled' has been removed.
      • System Setting 'catalog.views.setdefault.allow' has been removed.

      Audit Trails

      New & Improved

      • In the Audit Trails, under the Catalog tab and the Terms sub-tab, the action for data objects was previously displayed as Add for both when a term was moved to the draft state and the published state. This caused confusion among users.
        This functionality has now been improved. When a term is moved to the draft or published state, the action is recorded only once. Detailed action information is displayed in the Governance Catalog under Terms in the Action Details column, with the following messages:
        • Term successfully moved to Draft State.
        • Term successfully moved to Published State.

      New Connectors

      Oracle Analytics Server

      • Oracle Analytics Server (OAS) is an on-premises analytics platform offering reporting, data visualization, and advanced analytics capabilities. OvalEdge requires a service account and uses SOAP services to connect to OAS. This integration enables users to crawl data objects, such as reports and report columns, allowing detailed analysis and metadata exploration within OvalEdge.

      New Advanced Jobs

      Name 

      Description

      Migration_JobtoInactivate_Datasets

      This advanced job is used to make the child dataset(s) inactive when their parent dataset is inactive.


      Previously, the child dataset(s) remained active and visible in the Data Catalog under code associations, even when their parent dataset was inactive. However, the child datasets will now become inactive after running this job.


      Note:

      When to run this job:

      This migration job has to run once if users migrate from any release version to R6.3.4.

      DQTAT Execution Overview

      This job analyzes the Data Quality Test Suite, highlighting the status of each Data Quality Rule (DQR) executed in the current release. The job generates a summary of passed and failed rules, listing associated objects for each failed rule. This overview enables swift identification of potential data quality issues and assists teams in pinpointing areas that may require additional focus or remediation.

      Fetching Labels for Synapse Columns

      This job helps fetch the Synapse labels at table level and column level.

      Advance Job for Inserting data into the Lineage table

      This job allows the insertion of data into the Lineage Table to build a Connection Dashboard view.

      FME TO CARTO VISTA Lineage

      This job will establish lineage from FME to Carto Vista based on the FME Components.

      Report Crawl Analysis

      This job facilitates the analysis of activated and inactivated objects during the second crawl of the Power BI server. Upon running the job, a report is generated that provides details about the updated activated and inactivated objects of the Power BI server in OvalEdge, enabling users to track and manage object status effectively.

      New System Settings

      The latest release introduces a new system setting that enhances user control over the application's behavior.

      Key 

      Description

      Impacted Modules in OvalEdge

      dataquality.associatedobjects.tables.limit

      Set the maximum number of objects (tables and table columns) that can be associated with a Data Quality Rule.


      Parameters:

      The default value is set to 1000.


      Enter the value in the field provided.

      Minimum entered value is 1.

      Maximum entered value is 1000.

      Data Quality

      dataquality.associatedobjects.files.limit

      Set the maximum number of objects (files and file columns) that can be associated with a Data Quality Rule.

      Parameters:

      The default value is set to 20.


      Enter the value in the field provided.

      Minimum entered value is 1.

      Maximum entered value is 250.

      Data Quality

      oe.profile.importancescore.threshold

      Configure to define a threshold value for the importance score of data assets in the profiling process. Only assets with an importance score equal to or greater than this threshold will be included in the profiling. 


      Parameters:

      The default value is 0.

      Enter the value in the field provided.

      The value should be in the range of 0-100.

      In Data Catalog > Tables, Table Columns.

      max.character.count.for.text.custom.fields

      Specify the maximum character count allowed for text custom fields.


      Parameters:

      The default value is 1000 characters.

      Accepted value is < 5000.

      Custom fields are available in the Data Catalog, Business Glossary, Tags, Data Quality Recommendations, ROPA Report, and ROPA Processing Activities.

      ai.description.enable

      Configure to show/hide the 'Generate with AI' icon for the Business, Technical, and Detail descriptions.

      Parameters:

      The default value is True.


      If set to True, show the 'Generate with AI' icon for the Business, Technical, and Detail descriptions.

      If set to False, hide the 'Generate with AI' icon for the Business, Technical, and Detail descriptions.
      • Business and Technical Descriptions in Data Catalog.
      • Business and Detail Descriptions in Business Glossary.

      home.lastlogin.enable

      Configure to show/hide the user's last successful login date and the number of unsuccessful login attempts between the current and the previous successful login.


      Parameters:

      The default value is 'False'.


      If set to 'True,' show the last successful login date and the number of unsuccessful login attempts between the current and the previous successful login.

      If set to 'False,' hide the last successful login date and the number of unsuccessful login attempts between the current and the previous successful login.

      Login page

      login.warning.enable

      Configure to show/hide the banner. Upon clicking Okay, users can enter their User ID and Password to proceed with the Login.

      Parameters:

      The default value is 'False'.


      If set to True, show the banner.

      If set to False, hide the banner.

      Login page

      login.warning.description

      The specified description in the Value column shows on the banner if login.warning.enable is set to 'true.'

      The maximum number of characters supported is 2000.


      Parameters:

      The default value is 'Empty'.


      If the Value column contains the content, it shows on the banner.

      If the Value column is 'Empty,' the banner is not shown.

      Login page

      Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA USA