Release6.2 Migration Process for Container-Based Model

Advance Job Name

Help

Load oereportext table for reporting framework

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, you could view the created reports for OvalEdge DB.

Advance Job for Indexing Existing Data into ElasticSearch

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

Enter the object type names that require support in the 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, please separate them with commas. In case 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

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

This job will Migrate Data To Denormalized(ext) Tables

Servicedesk V1

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 on behalf of multiple users.

Note: No attribute is required to execute this job.

Migrate User License and Connector License to 61

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

Update Schedule Next Execution Date Time

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

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

Custom Field Migration JOB

To migrate custom field to 6.2

Notification Preferences Migration

This job will migrate notification preferences

Enable system dashboards

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

Attributes:

No attributes are needed.

Migrate favourite dashboard to new dashboards flow

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

This job will update the origins for existing objects

Migration Job for Data Quality from R61 to R62

This migration job helps migrate existing DQ Rules to new DQ Rule definitions supporting success and input operators. It also helps migrate the updated changes for DQRC with changes done in Release 6.2

Refresh Has-Lineage

The job refreshes the Has Lineage column present in the Data Catalog list page. The column tells whether the object has lineage or not.

Migrate RDAM Module

To migrate the users, roles, associated permissions on data objects, masking policies from the previous versions to the latest 6.2 version.

Advance Job Name

help

Load oereportext table for reporting framework

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, you could view the created reports for OvalEdge DB.

Advance Job for Indexing Existing Data into ElasticSearch

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

Enter the object type names that require support in the 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, please separate them with commas. In case 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

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

This job will Migrate Data To Denormalized(ext) Tables

Servicedesk V1

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 on behalf of multiple users.

Note: No attribute is required to execute this job.

Migrate User License and Connector License to 61

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

Update Schedule Next Execution Date Time

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

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

Custom Field Migration JOB

To migrate custom field to 6.2

Notification Preferences Migration

This job will migrate notification preferences

Enable system dashboards

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

Attributes:

No attributes are needed.

Migrate favourite dashboard to new dashboards flow

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

This job will update the origins for existing objects

Advance Job Name

Help

Load oereportext table for reporting framework

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, you could view the created reports for OvalEdge DB.

Update User License Type

It updates the user license on the current application version based on the permissions available in the previous version. It is required to migrate the current application version to 6.0.

Advance Job for Indexing Existing Data into ElasticSearch

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

Enter the object type names that require support in the 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, please separate them with commas. In case 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

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

This job will Migrate Data To Denormalized(ext) Tables

Servicedesk V1

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 on behalf of multiple users.

Note: No attribute is required to execute this job.

Migrate User License and Connector License to 61

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

Update Schedule Next Execution Date Time

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

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

Custom Field Migration JOB

To migrate custom field to 6.2

Notification Preferences Migration

This job will migrate notification preferences

Enable system dashboards

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

Attributes:

No attributes are needed.

Migrate favourite dashboard to new dashboards flow

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

This job will update the origins for existing objects

Advance Job Name

Help

Load oereportext table for reporting framework

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, you could view the created reports for OvalEdge DB.

Update User License Type

It updates the user license on the current application version based on the permissions available in the previous version. It is required to migrate the current application version to 6.0.

Advance Job for Indexing Existing Data into ElasticSearch

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

Enter the object type names that require support in the 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, please separate them with commas. In case 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

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

This job will Migrate Data To Denormalized(ext) Tables

Servicedesk V1

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 on behalf of multiple users.

Note: No attribute is required to execute this job.

Migrate User License and Connector License to 61

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

Update Schedule Next Execution Date Time

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.

DQ Score calculation for 61

The primary objective of this job is to ensure that users migrating from the previous version to the 6.1.1 release can access the most up-to-date Data Quality (DQ) score. This is imperative due to recent adjustments made in the score calculation process.

Attributes not needed.

Term Masking Migration JOB

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

Custom Field Migration JOB

To migrate custom field to 6.2

Notification Preferences Migration

This job will migrate notification preferences

Enable system dashboards

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

Attributes:

No attributes are needed.

Migrate favourite dashboard to new dashboards flow

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

This job will update the origins for existing objects

Migrate RDAM Module

To migrate RDAM module

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 techincal 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 Assosciation 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

Users & Roles

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

ms.teams.client.id

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

Parameters:

• The default value is Empty.
• impactEnter 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

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

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

This is used to configure anomaly detection analysis algorithms.

Parameters:

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

anomaly.detection.analysis.enabled

This is used 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

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 as 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

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

openai.activation.token

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

Parameters:

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

Others 

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 Processing Activity and Report summary page.

Parameters:

If set to False, it will not display the assignee list.

If set to True, it will display the assignee list.

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 in 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. When the number of calls reaches the configured threshold, the system automatically stops further calls.

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 length.

System Setting Name

Description

tag.multiple.parent.hierarchy

The default value has been altered from true to false for this system setting.

This configuration setting provides users with the flexibility to create tags with the same name under different root tags.

Parameters:

If set to true, users can create tags with the same names under different root tags.

If set to false, it mandates unique tag names, disallowing the use of identical tags or duplicates, need to run the advance job - Update Tag Hierarchy to update the hierarchies for existing tags.

application.defaulttheme

Previously, this system setting was configurable. 

Now, by default, the blue theme is set to be the default theme, which colorizes the entire user interface in blue hues. The default theme cannot be altered in the current version. 

globalsearch.es.objecttabs.display

The search results now include API, API Attributes, Ropareports, processing activity.

ovaledge.jarpath

Configure the jar files path to support crawl/profile. Example: D:\Jars

Parameters:

The default value is /home/ovaledge/third_party_jars.

Enter the path of the jar files in the field provided.

ovaledge.dqrule.bg.enforcement

Configure to execute Data Quality Rules only when the Term is applied.

Parameters:

The default value is False.

If set to True, then a term should be associated with the object to execute the Data Quality rule.

If set to False, then a term is not needed to execute the Data Quality Rule.

ovaledge.dqr.topvalue.separator

Define a separator to give a set of input fields for the Top Value function>Values field. For Example If / (slash) is used as a separator, then the input values can be separated as red/yellow/blue.

Parameters:

The default value is comma (,).

Enter the value in the field provided.

remote.user.password

Assign default password to all the Remote users fetched to the OvalEdge application.

Parameters:

• Enter the password in the field provided.

enable.dq.policy

Show/hide the Data Quality Policies sub-module in the application menu under the Governance Catalog module in Data Quality.

Parameters:

If set to True, the Data Quality Policies sub-module is displayed in the application menu.

If set to False, the Data Quality policies module is hidden.

display.tree.tagtile

Show/hide the tree structure inside a tile on Tags>Tiles page.

Parameters:

The default value is True.

If set to True, the Tags hierarchy is shown for all the Tags on the Tiles page.

If set to False, the Tags hierarchy is disabled.

dashboard.dqsb.mode

To set the DQR mode to DQSB or ALL.

Parameters:

The default value is ALL.

Enter ALL or DQSB in the field provided.

dataquality.catalogobjects.additionalcolumns

To set a limit on the number of parameters that can be configured within Additional Column details for the Data Quality Center. For instance, when set to a value such as 10, it enforces a maximum limit of 10 parameters that can be configured for the additional columns.

Parameters:

Enter the value in the field provided. The Maximum limit is 20.

show.home.graphicalcount 

To show/hide the display of graphical presentations such as Tables, Files, and Reports on the home page.

Parameters:

If set to true, the graphs will be displayed.

If set to false, the bar graph of objects will not be displayed.

tag.multiple.parent.hierarchy

This configuration setting provides users with the flexibility to create tags with the same name under different root tags.

Parameters:

If Set to True: Users can create tags with the same names under different root tags.

If Set to False: It mandates unique tag names, disallowing the use of identical tags or duplicates.

default.term.relationname

Configure the OvalEdge application default term relation name when relating an object to a term.

Parameters:

The default value is related to.

You can pass only 1 relation type name.

questions.wall.notification.email

To control whether the users tagged in the question wall should receive email notifications.

Parameters:

If set to 'Empty, email notifications are sent to the users if the user is tagged in the Questions Wall.

If set to False, email notifications are not received.

sqlserver.profile.columnlength