# Virtual Machine (VM)

This article provides comprehensive guidance on migrating OvalEdge from Release6.3.4.x to Release7.2.x in a Virtual Machine (VM)-based deployment. It outlines prerequisites, backup steps, migration procedures, and post-migration validation tasks to ensure a smooth and secure upgrade.

## **Prerequisites**

Before initiating the migration, ensure the following:

### **Infrastructure and System Requirements**

* Ensure the operating system and environment support upgraded RAM and SSD space requirements for optimal performance.

### **Database Upgrade**

* OvalEdge Release7.2.x requires **MySQL 8.4.x or higher**.
* ✅ Upgrade MySQL using appropriate guides:
  * [*MySQL Upgrade from 8.0.4 to 8.4.x on RHEL Internet*](https://docs.ovaledge.com/deployment-and-maintenance/upgrade/mysql-upgrade-from-8.0.4-to-8.4.x-rhel-internet)
  * [*MySQL Upgrade from 8.0 to 8.4.x on Azure* ](https://docs.ovaledge.com/deployment-and-maintenance/upgrade/mysql-upgrade-from-8.0-to-8.4.x-azure)
  * [*MySQL Upgrade from 8.0.4 to 8.4.x on AWS*](https://docs.ovaledge.com/deployment-and-maintenance/upgrade/mysql-upgrade-from-8.0.4-to-8.4.x-aws)
  * [*MySQL Upgrade from 8.0.4 to 8.4.x on Windows*](https://docs.ovaledge.com/deployment-and-maintenance/upgrade/mysql-upgrade-to-8.4.x-windows)

⚠️ Ensure the database backup is completed before the upgrade.

### **Java Upgrade**

* OvalEdge Release7.2.x requires **Java 17.x**.
  * Refer to: [*Java Upgrade 17.x on Windows*](https://docs.ovaledge.com/deployment-and-maintenance/upgrade/java-17.x-upgrade-windows)

### **Tomcat Upgrade**

* Recommended upgrade to **Apache Tomcat 9.0.x or higher**.
* Refer to:&#x20;
  * [*Tomcat Upgrade from 9.0.x to 10.1.x on Windows*](https://docs.ovaledge.com/deployment-and-maintenance/upgrade/tomcat-upgrade-from-9.x-to-10.1.x-windows)
  * [*Tomcat Upgrade from 9.0.x to 10.1.x on Linux*](https://docs.ovaledge.com/deployment-and-maintenance/upgrade/tomcat-upgrade-from-9.x-to-10.1.x-linux)

⚠️ After Tomcat upgrade:

* Update `server.xml` to enable compression and verify ports/SSL settings.
* Add `<Resources cacheMaxSize="102400"/>` in `context.xml`.
* Restart Tomcat and review logs for errors.

### **ElasticSearch Upgrade**

* Upgrade to **ElasticSearch 7.17.x**.
* Refer to:
  * [*Elasticsearch Upgrade on Windows*](https://docs.ovaledge.com/deployment-and-maintenance/upgrade/elasticsearch-upgrade-windows)
  * [*Elasticsearch Upgrade on Ubuntu*](https://docs.ovaledge.com/deployment-and-maintenance/upgrade/elasticsearch-upgarde-ubuntu)

### **Configuration Externalization**

* ✅ Externalize `oasis.properties`
  * Refer to:
    * [*Externalize Oasis Properties (Windows)*](https://docs.ovaledge.com/deployment-and-maintenance/configuration/externalize-oasis-properties-for-tomcat-in-windows)
    * [*Externalize Oasis Properties (Linux)*](https://docs.ovaledge.com/deployment-and-maintenance/configuration/externalize-oasis-properties-for-tomcat-in-linux)
* ✅ Externalize `log4j.properties`
  * Refer to:
    * [*Externalize log4j.properties*](https://docs.ovaledge.com/deployment-and-maintenance/configuration/externalize-log4j.properties)

## **Backup Procedures**

Before initiating the migration, perform the following backup steps to safeguard the environment and ensure a smooth recovery in the event of failure.

### **Take a Full Database Backup**

* Use MySQL tools or database management utilities to create a full backup of the OvalEdge database (MySQL or MariaDB).
* Ensure the backup includes all schema, data, triggers, and procedures.
* Store the backup securely in a location with restricted access.
* For detailed instructions, refer to: **\[**[**OvalEdgeDB Backup Process**](https://docs.ovaledge.com/deployment-and-maintenance/backup/ovaledge-db-backup)**]**

### **Table and Row Count Validation**

* Validate and record the row counts of all critical database entities before migration.
* Refer to: [**DB Migration Checklist**](https://docs.ovaledge.com/deployment-and-maintenance/migration/db-migration-checklist).

### **Backup Application WAR Files**

* Navigate to the Tomcat installation directory on your VM.
* Go to the **webapps** folder.
* Copy and save the WAR files (OvalEdge-related deployments) to a secure backup location.
* Verify the integrity of copied files using file hashes or checksums if required.

### **Backup JAR Files (Connectors, Lineage, Advanced Jobs)**

* Navigate to the `External Jars Directory > third_party_jars` location.
* Copy all existing JAR files, including:
  * csplib libraries
  * `Oe-lineage.jar`
  * `Oe-advancejob.jar`
  * Any custom connector JARs (for big data or client-specific connectors)
* Save these files in a backup folder on a secure storage drive.

### **Backup the Shared NFS Repository**

* Identify the location of your shared NFS folder (typically mounted for storing large or shared files).
* Copy the complete contents of this NFS directory to a backup location.
* Validate that all files have been copied successfully.

### **Backup the Tomcat Server Structure**

* Take a copy of the Tomcat installation directory or its key folders.
* Specifically, back up the following subdirectories:
  * **webapps** (ensure WAR files are included)
  * **logs** (retain for troubleshooting if migration fails)
  * **conf** (for Tomcat configuration files)
* Clear the following Tomcat directories (except critical files as noted):
  * **webapps** (clear old deployed apps after backup)
  * **temp** (do not delete JAR files accidentally)
  * **logs** (clean old logs to reduce clutter)

### **Backup System Settings**

* Connect to the OvalEdge database using your preferred DB client.
* Export the system settings table in **XLSX format**.
* Ensure that this export captures all configuration data for the system’s default and custom settings.
* For detailed instructions on exporting database tables, refer to: **\[**[**MySQL Table Backup to CSV/XLSX Guide**](https://docs.ovaledge.com/deployment-and-maintenance/backup/mysql-table-backup)**]**

### **Take a VM Snapshot (Optional)**

* If your virtualization environment allows (e.g., VMware, Hyper-V), create a snapshot of the VM.
* This provides an additional rollback point if system-level recovery is required.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><ul><li>All backups should be labeled with the date and time, as well as the migration version (e.g., <code>pre-7.2-migration-2025-06-13</code>).</li><li>Store backups in secure, access-controlled locations, and verify their integrity before proceeding.</li></ul></div>

## Migration Process

### **WAR Replacement**

* Download WAR files from the link provided via email.
* Replace existing WAR files in **Tomcat/webapps** with the new WAR.

### **JAR Upgrade**

* **Connectors and Lineage JARs**
  * Replace existing JARs in `External Jars Directory/third_party_jars` with:
    * Updated csplib (e.g., `csp-lib-7.2-RELEASE-with-dependencies.jar`)
    * Updated `oe-lineage.jar`
    * Updated big data connector libraries (if client-specific)
* **Advanced Job JAR**
  * Update `oe-advancejob.jar`.

### **Configuration Update**

* **Update `oasis.properties`**
  * Set DB connection, SSO, Elasticsearch, and external dependencies.
  * Ensure proper configuration storage in Key Vaults if applicable.

### **Restart Tomcat Service**

* Restart the Tomcat service to apply changes.

## **Post-Migration Validation**

### **Table and Row Count Validation**

* Validate row counts using provided SQL scripts (refer to: **Tables and Row Count Validation Scripts**).
* Ensure pre- and post-migration counts match.

### **Application Verification**

* Confirm the deployment of the latest features and enhancements.

### **Run Migration Jobs**

* After upgrading to Release7.2.x, it is mandatory to:
  * Execute all migration jobs introduced in Release7.2x to ensure that data structures, configurations, and system components are aligned with the new version.
  * Re-run any migration jobs executed until Release6.3.4.x that are still applicable to ensure data consistency and integrity across the environment.
  * For detailed information about the migration jobs introduced in Release7.2.x, refer to the Release7.2.x Migration Jobs Sheet.&#x20;

{% file src="<https://1813356899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhTnkoJQml0pok9awFDhx%2Fuploads%2F2pIwZDgScwS120uusNsc%2FOvalEdge_Release7.2.x_Migration%20_Jobs_Sheet.xlsx?alt=media&token=0203ff6b-4b74-4ece-a95e-fd90cefe47d0>" %}

### **Run Advanced Jobs**

* After migrating to Release7.2.x, it is essential to:
  * Execute all new advanced jobs introduced in Release7.2.x to ensure the proper functioning of new features and enhancements.
  * Re-run all advanced jobs that were executed until Release6.3.4.x to maintain data integrity and consistency in the upgraded environment.
  * For details on the advanced jobs introduced in Release7.2.x, refer to [**New Advanced Jobs (Release6.3.4.x to Release7.2.x)**](#new-advanced-jobs-release6.3.4.x-to-release7.2.x) in the *Appendix*.

### **Verify System Settings**

* After completing the migration, ensure that all new system settings introduced in Release7.2.x are configured as required to support the latest functionalities and enhancements.
* No changes are needed for existing system settings unless specifically required for your environment.
* For a complete list of new, modified, and deprecated system settings in Release7.2.x, along with guidance on their configuration, refer to [**New System Settings (Release6.3.4.x to Release7.2.x)**](#new-system-settings-release6.3.4.x-to-release7.2.x) in the *Appendix*.

## **Rollback Plan**

If migration fails:

* ✅ Restore the database from backup.
* ✅ Restore WAR/JAR files.
* ✅ Revert configurations (`oasis.properties`, `log4j.properties`).
* ✅ Roll back Tomcat, Java, and ElasticSearch versions if necessary.
* ✅ Restore VM snapshot (if available).

## **Important Notes**

* After the Tomcat upgrade, verify the compression settings, ports, and SSL configuration.
* Confirm `context.xml` cache configuration is applied.
* Always validate Tomcat logs after a restart.

## Appendix

### New Advanced Jobs (Release6.3.4.x to Release7.2.x)

<table><thead><tr><th width="131.666748046875">Version</th><th width="209.333251953125">Advanced Job Name</th><th>Description</th></tr></thead><tbody><tr><td>Release7.2.5</td><td>Process SAP HANA Tables Based on File Differences</td><td>This job will load the SAP HANA table based on the difference between the files generated by the bridge.</td></tr><tr><td>Release7.2.5</td><td>Syncing Views, Procedures, and Functions</td><td><p>This job syncs all Views, Procedures, and Functions available within a schema.</p><ul><li>Attribute1: Provide Connection ID</li><li>Attribute2: Provide Schema Names with Comma(,) separated</li></ul></td></tr><tr><td>Release7.2.5</td><td>Crawl Table Columns</td><td>This job loads table column metadata from files available in the configured folder and updates the corresponding table structures in the system.</td></tr><tr><td>Release7.2.4</td><td>QlikSense Metadata Export Service</td><td>This job exports the metadata of Qlik Sense apps to files.</td></tr><tr><td>Release7.2.4</td><td>ConnectorLevelSemanticMapping</td><td>This job helps migrate temporary lineage schemas by updating their connection reference and replacing "templineage" with the original connection name.</td></tr><tr><td>Release7.2.4</td><td>Business Glossary Associated Count Stats</td><td>This job consolidates and migrates the counts of objects associated with terms into a single unified table for better consistency and reporting.</td></tr><tr><td>Release7.2.4</td><td>Update Project Task Weight Factors in Bulk</td><td>This job calculates and updates task and baseline weight factors for all projects in batches, helping the Advanced project management fields work as intended.</td></tr><tr><td>Release7.2.4</td><td>Migration Data Metrics</td><td>This job captures all the important data metrics from all configured modules.</td></tr><tr><td>Release7.2.3</td><td>Merging Temp Lineage Tables in Bulk</td><td>This job merges temporary lineage tables into their original tables within a specified schema in bulk.</td></tr><tr><td>Release7.2.3</td><td>Fetching Labels for Synapse Columns</td><td>This job helps fetch Synapse labels at both the table and column levels.</td></tr><tr><td>Release7.2.3</td><td>Table Archival</td><td>This job archives data present in the table according to the specified retention period. For example, if the retention period is set to 5 days, the recent 5 days of data will persist, and all other data will be deleted and archived in CSV format into the specified temppath/table_archival/.</td></tr><tr><td>Release7.2.2</td><td>Migrate Descriptions From Alation</td><td><p>This job loads object metadata from the Excel sheets in the given folder path into the stage table. Then it reads descriptions from the OvalEdge database, updating the references from the Alation format to the OvalEdge format.</p><p><strong>Attributes:</strong></p><ol><li>Folder Path: Path of the folder that contains the Excel sheets of object metadata required to identify the related object IDs in the database</li><li><p>Load Excel Data to stage table(true/false)?</p><ol><li>The default value is true.</li><li>If set to True, the job first loads the data into the stage table from the sheets in the given folder path and then updates the references.</li><li>If set to False, the job does not load any data; instead, it updates the references directly. It must be False when the user re-initiates the job on the same folder path, which prevents data duplication.</li></ol></li></ol></td></tr><tr><td>Release7.2.2</td><td>User Favorite Code Migration Job</td><td>This job migrates user favorite codes by matching navigation links to appropriate favobj values. It processes all user favorites in the userfavorite table and updates their favobj column based on the link patterns.</td></tr><tr><td>Release7.2.1</td><td>Update Servicedesk Date columns from UTC to Database time zone</td><td>This job converts ticket creation and SLA (Service Level Agreement) dates from UTC to the database Time Zone. It also processes all tickets created after the first build date for the Release6.3 version.</td></tr><tr><td>Release6.3.4.2</td><td>GDQ Compliance Data Migration</td><td>This job transfers entries from the deprecated GDQ table to the active GDQ table.</td></tr><tr><td>Release7.1</td><td>Advanced Job for Inserting data into the Lineage table</td><td>This job allows the insertion of data into the Lineage Table to build the Connection Dashboard view.</td></tr><tr><td>Release7.1</td><td>Load Axiomatics Policies</td><td>This job will take a folder or file (in JSON format) as input that contains Axiomatics Policies and load them into OvalEdge. This job is also used to reconcile policies if any discrepancies are identified between OvalEdge and Axiomatics.</td></tr><tr><td>Release7.1</td><td>Caching of Business Applications from UPC</td><td>This job will sync business applications from UPC to OE cdr_products. These products will be consumed for raising the Service Requests</td></tr><tr><td>Release7.1</td><td>MetaData Change Report Sync Service</td><td>This job imports all data from an XLSX sheet and inserts it into the database, removing any existing records.</td></tr><tr><td>Release7.1</td><td>DataLake Analysis Second Level</td><td>This is no longer required and can be deleted.</td></tr><tr><td>Release7.1</td><td>Retry Fulfillment for Service Requests</td><td>This job collects Service Requests that are in Fulfillment Error and attempts to re-initiate their fulfillment. It groups the Service Requests by Template ID. If the retry fails for the first request in a group, the entire group is skipped, and the process moves to the next group, assuming the integrated system has not yet recovered.</td></tr><tr><td>Release7.1</td><td>Delete Inactive Users for SSO</td><td>The purpose of this job is to delete inactive users in OvalEdge by verifying their status in Azure Active Directory (Azure AD).</td></tr><tr><td>Release7.1</td><td>Assign Role to Users</td><td>This job takes a role as input and assigns that role to all the users in OvalEdge.</td></tr><tr><td>Release7.1</td><td>Cascade Customfields for Buckets</td><td><p>This job cascades custom fields from buckets to their downstream folders and files. Two attributes need to be specified for this job:</p><p>attribute1: The S3 Connection ID</p><p>attribute2: The bucket name, if only a single bucket is to be processed.</p></td></tr><tr><td>Release7.1</td><td>Cascade tags to the folder and files</td><td><p>This job aims to cascade tags from a bucket to its downstream folders and files. Two attributes need to be specified for this job:</p><p>attribute1: The S3 Connection ID</p><p>attribute2: The bucket name, if only a single bucket is to be processed.</p></td></tr><tr><td>Release7.1</td><td>Update TicketParams For Snowflake</td><td>This job updates the ticket parameters for a Snowflake connection, including field code, field type, and option value.</td></tr><tr><td>Release7.1</td><td>Sync DQ Policy Execution Summary to OE</td><td>This job synchronizes the policy execution summary results to OvalEdge (OE).</td></tr><tr><td>Release7.1</td><td>Cache scopes associated with a Business Application</td><td>This advanced job retrieves the scopes associated with the Business Application and caches them in OvalEdge.</td></tr><tr><td>Release7.1</td><td>Crawl Snowflake Users and Roles</td><td>This job crawls users, roles, and warehouses for a Snowflake connection.</td></tr><tr><td>Release7.1</td><td>Process KAFKA ACLs Dump File For Audit</td><td>This job loads the specified file and processes the ACL's information into the audit table. It is exclusively designed for the Kafka connector. Ensure that both the Crawler ID/Name and File Name (only .xlsx files are supported) are provided.</td></tr><tr><td>Release7.1</td><td>Update SR data for Backward Compatibility</td><td>This job updates the default data for existing tickets by adding new fields.</td></tr><tr><td>Release7.1</td><td>Update Group Info for Service Requests</td><td>This job updates the Group Info for existing Service Requests, excluding API Access Requests.</td></tr><tr><td>Release7.1</td><td>S3 to Snowflake Lineage using DDL Commands</td><td>This job creates a lineage from S3 to Snowflake.</td></tr><tr><td>Release7.1</td><td>Build Lineage from Excel File</td><td>This job will build the lineage from an Excel file.</td></tr><tr><td>Release7.1</td><td>Add connection details to ticketparam2</td><td>This job adds connection details to the ticketparam2 table.</td></tr><tr><td>Release7.1</td><td>Update Fulfillment Detail for Service Requests</td><td>This job updates the Fulfillmentdetailid for pending Service Requests.</td></tr><tr><td>Release7.1</td><td>Remove Access For Inactive Tables</td><td>This job removes access for inactive objects.</td></tr><tr><td>Release7.1</td><td>An advanced Job for Indexing Existing</td><td><p>This advanced job enables the indexing of pre-existing data into Elasticsearch and controls the indexing process based on the specific object types you select.</p><p>Enter the names of the object types that need to be supported in Attribute1, such as 'oetable' or 'oeschema'. The data corresponding to the specified object types will be indexed in Elasticsearch. If multiple object types need to be indexed, separate them with commas. If no object types are provided, data from all object types will be indexed.</p><p>Attributes:</p><p>Comma-separated Object Types - oetable,oecolumn, etc..</p></td></tr><tr><td>Release7.1</td><td>Upgrade Image Avatars</td><td>This job upgrades the image avatars from a circular shape to a square.</td></tr><tr><td>Release7.1</td><td>Generate GUID</td><td>This job will generate GUIDs for existing unassigned catalog objects, tags, and terms. A GUID is a unique identifier for objects within the application. This job will generate and assign the unassigned objects with GUIDs.</td></tr><tr><td>Release7.1</td><td>Tableau columns curated info moving from the report to the Datasource</td><td>This job transfers curated information from the report column to the data source column.</td></tr><tr><td>Release7.1.1</td><td>Migration of Mention and Myaction Comments</td><td><p>This job updates the tab column in the comment table with either "Mention" or "My Action" for existing messages. All pre-existing messages will be marked as Read, except for My Action messages, which will remain pending without requiring any further action.</p><p>This Advanced Job should be executed only once after the migration."</p></td></tr><tr><td>Release7.1.1</td><td>Inconsistent Objects Diagnostic &#x26; Cleanup</td><td>This job identifies and removes inactive objects from OvalEdge to maintain metadata accuracy. When executed, it provides a diagnostic report on the number of inactive parent objects in the job logs. If the cleanup attribute is set to true in Attribute1, the job will proceed to delete these inactive objects while ensuring hierarchical integrity, removing dependent child objects. By default, the cleanup attribute is set to false, allowing admins to review the impact before performing deletions.</td></tr><tr><td>Release7.1.1</td><td>RDAM Deleted Instance Migration</td><td>This job will migrate deleted RDAM instances and their associated records to ensure consistency following the version upgrade.</td></tr><tr><td>Release7.1.1</td><td>Image Upload Security Enhancement</td><td>This job updates the identifiers of previously uploaded images in the Business Description, Technical Description, and other fields in the Froala Editor. Previously, images were stored with sequential IDs, which posed a security risk as users could access other uploaded images by modifying the URL. Running this job after migration replaces all existing image IDs with unique, non-sequential keys, ensuring enhanced security and preventing unauthorized access.</td></tr><tr><td>Release7.1.1</td><td>Advanced job for adding a subject to the comment table</td><td>This job adds subject information for team-related notifications, ensuring that the details appear in the My Recent Notifications widget on the homepage.</td></tr><tr><td>Release7.1.1</td><td>IPC Parameter file processing</td><td>This job copies the parameter file from a remote machine to a local machine and processes the file for configuration details.</td></tr><tr><td>Release7.1.1</td><td>OvalEdge User Licenses AD Verification</td><td><p>This job generates a comparison report that includes users in Active Directory (AD) groups and users with OvalEdge licenses.</p><p>Attributes:</p><p>Attribute1: Compare Azure AD Groups with Author License (comma-separated).</p><p>Attribute2: Compare Azure AD Groups with Viewer License (comma-separated).</p><p>Attribute 3: Notify Users (comma-separated) - Enter the users to notify.</p><p>Attribute4: Notify Team (comma-separated) [The users in the Team will be notified] - Enter the team names.</p><p>Attribute5: Notify Roles (comma-separated) [The users of the given Roles will be notified] - Enter the roles.</p></td></tr><tr><td>Release7.1.1</td><td>Collaboration Message Migration</td><td>This job migrates all collaboration messages older than Release 6.2 and should be executed only once after the migration is complete.</td></tr><tr><td>Release7.1.1</td><td>Compare Axiomatics Policies</td><td>This job compares Axiomatics policies created or updated via API Access Requests from OvalEdge with the existing policies in the Axiomatics application. It identifies and logs any discrepancies in the job logs. An email is sent with an attachment listing the mismatched policies. This process helps in understanding and reconciling any discrepancies.</td></tr><tr><td>Release7.1.1</td><td>Ovalsight Bridge Migration</td><td>This job creates multiple DuckDB files, specific to each connector, from an existing DuckDB file.</td></tr><tr><td>Release7.1.1</td><td>License Issue</td><td>This advanced job, related to migration, aims to add additional attributes to certain existing connectors, fetch unique values for the connectors, and update the license accordingly.</td></tr><tr><td>Release7.1.1</td><td>Advanced job for updating Deltalake custom fields</td><td>This advanced job will update technical and business descriptions for tables in Delta Lake.</td></tr><tr><td>Release7.2</td><td>Curated report column info that maps to the appropriate reporting object based on the connector</td><td>This job enables the movement of curated column-level metadata from higher-level reporting objects to their associated downstream entities, supporting consistent metadata alignment across all connectors.</td></tr><tr><td>Release7.2</td><td>Migrate Tag Role to Master Tag Admin</td><td>This job migrates all users and roles from ovaledge.tag.role to ovaledge.mastertag.admin to align with the new Master Tag-based tag management model. Use this job to ensure continuity in tag administration.</td></tr><tr><td>Release7.2</td><td>Restore archived data</td><td><p>This Job allows users to retrieve historical data related to tags and terms that were previously archived and are no longer visible in the application. It ensures continuous access to past operations for auditing and compliance purposes. Users can restore the archived data into the original or a temporary table, making it easier to track changes, maintain data governance, and meet regulatory requirements even after data has been archived.</p><p><br></p><p>Note: This Job is run based on the client's request</p></td></tr><tr><td>Release7.2</td><td>Reset Time Zones For Schedule</td><td>This job updates the time zones for schedules that do not have a valid time zone associated with them. It will update the time zone to match the server's time zone.</td></tr><tr><td>Release7.2</td><td>Profile By Importance Score</td><td><p>This job allows admins to perform targeted profiling of tables based on their Importance Score. Users can specify a threshold range (e.g., 80-100) to profile only the most critical tables within that range. The job supports filtering by a specific connection and its associated schemas. Attributes:</p><p>Attribute 1: Connection ID (Required) Enter the ID of the connection. Only one connection can be selected per job.</p><p>Attribute 2: Schema IDs (Optional) Provide one or more schema IDs. All schemas must belong to the selected connection.</p><p>Attribute 3: Low Range (Required) Enter the lower limit of the Importance Score range (e.g., 80). The value should be between 0 and 100.</p><p>Attribute 4: High Range (Required) Enter the upper limit of the Importance Score range (e.g., 100). The value must be greater than the Low Range and less than or equal to 100.</p></td></tr><tr><td>Release7.2</td><td>Azure SQL Database Masking Sync</td><td><p>This job is run to fetch details of all the corresponding masked Azure SQL Database columns from the source into OvalEdge.</p><p>Attributes: 1. Connection Id<br><br></p><p>Note: Only Security and Governance admins of the corresponding connection (Defined while creating a connection) and OvalEdge’s super admin (ovaledge.role.admin) can run this job.</p></td></tr><tr><td>Release7.2</td><td>StoryZoneAllowContentEditMigration</td><td>This job is run when migrating from R6.x or R7.2 to allow adding or editing content to Data Story Zones.</td></tr><tr><td>Release7.2</td><td>Migrate Ropa Dropdown Data</td><td>This job migrates data from multiple ROPA tables to a single unified ROPA table.</td></tr><tr><td>Release7.2</td><td>Migrate TCF Text TO Rich Text</td><td>This job converts existing text to rich text format for custom text fields.</td></tr><tr><td>Release7.2</td><td>Migrate Homepage Widgets</td><td>This job migrates the Homepage Widgets layout from 6.3.x and 7.x versions to the 7.2 version.</td></tr><tr><td><br></td><td>Code Custom Fields Options CleanUp</td><td><p>Running this advanced job, the code custom field values will appear beside the custom field level in the same table in the backend.</p><p>Note: No attribute is required to execute this job.</p><p><br></p></td></tr></tbody></table>

### New System Settings (Release6.3.4.x to Release7.2.x)

<table><thead><tr><th width="180">Job Parm Key</th><th width="412.5555419921875">Revised Content</th><th>Impacted Modules</th></tr></thead><tbody><tr><td>qliksense.websocket.timeout</td><td><p>Configures the timeout (in milliseconds) for Qlik Sense WebSocket request–response communication.</p><p>Parameters:</p><ul><li>Specifies the wait time for a response from the Qlik Sense Engine after sending a WebSocket request.</li><li>If the engine does not respond within the configured time, the request is terminated and marked as a timeout error.</li><li>Useful when Qlik apps are large or require additional processing time.</li><li>Increasing the timeout helps avoid “WebSocket response timeout” or “Engine request timeout” errors during crawling.</li><li>If left empty, the application's default WebSocket timeout is used</li></ul></td><td>Connectors</td></tr><tr><td>querysheet.masked.column.security</td><td><p>Determines how the Query Sheet handles tables containing masked or restricted columns.</p><p>Parameters:</p><ul><li>Advanced: Blocks query execution on tables containing masked columns to enhance security.</li><li>Standard: Allows queries to run and applies masking to sensitive columns in the results.</li></ul></td><td>Query Sheet</td></tr><tr><td>sync.mincounttowritetofiles</td><td><p>Controls when objects are written to files based on the total object count.</p><p>Parameters:</p><p>Objects are saved only when their total count exceeds the specified threshold.</p></td><td>Bridge</td></tr><tr><td>sync.mincounttoprocess</td><td><p>Determines when the sync process is executed.</p><p>Parameters:</p><p>The sync process is skipped if the total number of objects exceeds the configured limit.</p></td><td>Bridge</td></tr><tr><td>merge.adf.runs</td><td><p>Controls whether ADF pipeline runs are merged during crawling.</p><p>Parameters:</p><p>When enabled, multiple pipeline runs are consolidated into a single merged run.</p></td><td>Connectors</td></tr><tr><td>adf.runs.app.processing</td><td><p>Determines where ADF pipeline run processing is handled during crawling.</p><p>Parameters:</p><ul><li>When enabled, pipeline runs are processed at the application level.</li><li>When disabled, pipeline runs are processed at the CSP layer.</li></ul></td><td>Connectors</td></tr><tr><td>adf.enable.partitionfiles</td><td><p>Controls whether lineage is built for ADF partition files.</p><p>Parameters:</p><p>When enabled, lineage is generated for partitioned files.</p></td><td>Lineage</td></tr><tr><td>application.font.family</td><td><p>It allows users to select the font displayed in the application interface. The selected font will be applied across the application. Available options: Open Sans, Lufga Regular, Lato, Arial, Roboto</p><p>Parameters: </p><p>The default font is Roboto</p></td><td>All Modules</td></tr><tr><td>openai.base.url</td><td><p>It allows users to specify the base URL for OpenAI if an API gateway is used between the application and OpenAI.</p><p>Parameters:</p><p>The default value is Empty</p><p>Leave this field blank if there is no gateway configured.</p></td><td><br></td></tr><tr><td>openai.timeout</td><td><p>It allows users to set the timeout duration for OpenAI API calls in seconds.</p><p>Parameters:</p><p>The default value is 30 seconds</p></td><td><br></td></tr><tr><td>show.ai.additional.prompt</td><td><p>It allows users to enable or disable the additional prompt text field in the AI generation component while generating descriptions through AI.</p><p>Parameters:</p><p>The default value is True</p><p>If True: Displays the additional prompt text field.</p><p>If False: Hides the additional prompt text field.</p></td><td>Data Catalog, Business Glossary</td></tr><tr><td>ovaledge.upload.tempfile.temppath</td><td><p>Specifies the temporary server folder path used to validate files before uploading.</p><p>Parameters:</p><p>The default value is /home/ovaledge/TempPath</p><p>Enter a valid temporary path in the field provided.</p></td><td>File Manager and My Profile</td></tr><tr><td>dashboard.dataquality.dqscoretrend.maximumvalues</td><td><p>This setting allows users to configure the maximum number of data points displayed for a specific time interval.</p><p>Parameters:</p><p>The default value is 30</p><p>Maximum value: 200</p></td><td><br></td></tr><tr><td>ovaledge.policy.creator</td><td><p>It allows the OE_Admin to assign Policy Creator privileges to specific roles.</p><p>Parameters:</p><p>Default value: OE_ADMIN</p><p>OE_Admin can select one or more roles from the dropdown list.</p></td><td>Policy Manager, Data Catalog</td></tr><tr><td>enable.policy.manager</td><td><p>It allows users to enable or disable the visibility of the Policy Manager module under the Governance App.</p><p>Note: A system restart is required for the changes to take effect.</p><p>Parameters:</p><p>The default value is false</p><p>True: The Policy Manager module is visible to users.</p><p>False: The Policy Manager module is hidden from users.</p></td><td>Policy Manager, Data Catalog</td></tr><tr><td>show.timeout.popup</td><td><p>It allows users to control the visibility of the session timeout pop-up.</p><p>Parameters:</p><p>The default value: true</p><p>If set to true, the timeout popup will be displayed before the session expires.</p><p>If set to false, the timeout popup will not be shown.</p></td><td><br></td></tr><tr><td>restrict.concurrent.logins</td><td><p>It allows administrators to restrict users from logging in concurrently from multiple sessions.</p><p>Parameters:</p><p>Default value: false</p><p>If set to true, Users are restricted from logging in simultaneously from different sessions.</p><p>If set to false, Concurrent logins are allowed.</p></td><td>Login</td></tr><tr><td>dashboard.report.type.restricted</td><td><p>It allows users to restrict certain report types from being added to custom dashboards.</p><p>Parameters:</p><p>The default value is Empty</p><p>Users can enter or select report types from the dropdown to restrict their use in dashboards.</p></td><td>Custom Dashboards</td></tr><tr><td>bulkai.batchapi.outputfile.download.start.delay.minutes</td><td><p>It allows users to set the wait time before the system tries to download the output file metadata from OpenAI during bulk AI Description curation batch processing.</p><p>Parameters:</p><p>The default time is set to 30 minutes</p><p>Users can change the wait time between 0 to 60 minutes.</p></td><td><br></td></tr><tr><td>etl.new.connectorid</td><td><p>It allows users to specify the new connector ID for running ETL jobs.</p><p>Parameters:</p><p>The default value is Empty</p><p>Enter the connector ID on which ETL jobs should be executed.</p></td><td>Connectors, Jobs</td></tr><tr><td>ovaledge.concat.delimeter</td><td><p>It allows users to specify the delimiter used to join multiple values into a single field.</p><p>Parameters:</p><p>The default value is Comma</p><p>Enter a character (e.g., semicolon, #, $ ) to be used as the delimiter.</p></td><td><p>Data Catalog, Business Glossary, DQR, Load Metadata From Files, APIs</p><p>Code Custom Fields</p></td></tr><tr><td>ai.generatedesc.prompt.metadata</td><td><p>It lets users automatically generate descriptions for either Object Metadata or Underlying Attribute Metadata.</p><p>Object Metadata: Uses the object’s hierarchy and existing descriptions.</p><p>Underlying Attribute Metadata: Uses the object’s metadata along with its attributes and relationships.</p><p>Default value: Object Metadata</p></td><td>Data Catalog, Business Glossary</td></tr><tr><td>ai.bulk.description.enable</td><td><p>It allows users to enable or disable the Bulk AI Description generation feature.</p><p>Parameters:</p><p>The default value is True</p><p>If true, enables bulk AI description generation.</p><p>If false, disables the feature.</p></td><td>Data Catalog, Business Glossary</td></tr><tr><td>allowed.file.types.for.file.upload</td><td><p>It allows users to define which file types can be uploaded and cataloged from external sources.</p><p>Parameters:</p><p>The default value is pdf, txt, rtf, docx, odt, xlsx, ods, csv, pptx, odp, jpg, jpeg, png, gif, bmp, tiff, tif, svg, json, xml, log</p><p>Users can choose the allowed file types for uploading in service requests.</p><p>Files not included in the list will be rejected.</p></td><td>Service Desk</td></tr><tr><td>service.desk.file.upload.storage.service</td><td><p>It allows users to configure where files uploaded from Governance Apps are stored.</p><p>Parameters:</p><p>The default value is Empty</p><p>Users can select a storage service (NFS, S3, or Azure) to store files uploaded through the Service Desk.</p><p>If no option is selected, the file storage location remains unconfigured.</p></td><td>Service Desk</td></tr><tr><td><a href="http://service.desk.file.upload.connector.id">service.desk.file.upload.connector.id</a></td><td><p>It allows users to specify the connection ID for the selected storage service.</p><p>Parameters:</p><p>The default value is EmptyUsers must enter the connection ID associated with the chosen storage service.</p></td><td>Service Desk</td></tr><tr><td>service.desk.file.upload.bucketname</td><td><p>It allows users to specify the bucket name for the selected storage service.</p><p>Parameters:</p><p>The default value is Empty</p><p>Enter the bucket name for the storage service. This is mandatory for S3 and Azure.</p></td><td>Service Desk</td></tr><tr><td>candelete.application.diagnostic.data</td><td><p>This setting controls whether users can delete application diagnostic data.</p><p>Parameters:</p><p>The default value is True</p><p>If true, Users can delete diagnostic data.</p><p>If false, Deletion of diagnostic data is restricted.</p></td><td><br></td></tr><tr><td>ovaledge.email.server.type</td><td><p>It allows users to select the type of email server used for sending notifications.</p><p>Parameters:</p><p>The default value is SMTP.</p><p>Users can choose the server type from the dropdown list (SMTP, AWS SES, and Azure Graph API).</p><p>Based on the selection, the relevant configuration fields will be enabled.</p></td><td>Notifications</td></tr><tr><td>ovaledge.azure.graphapi.emailaddress</td><td><p>It allows users to specify the sender email address used for sending notifications through the Azure-authorized application.</p><p>Parameters:</p><p>The default value is EmptyNote: Users must enter a valid and active email address associated with a Microsoft Outlook account within the organization’s environment. The Azure application will use this email to send notifications on the user’s behalf.</p></td><td>Notifications</td></tr><tr><td>ovaledge.azure.graphapi.tenantid</td><td><p>It allows users to specify the Tenant ID from the Azure application registration.</p><p>Parameters:</p><p>The default value is Empty</p><p>Users must enter the Tenant ID associated with your organization's Azure Active Directory.</p></td><td>Notifications</td></tr><tr><td>ovaledge.azure.graphapi.clientid</td><td><p>It allows users to specify the Client ID of the OvalEdge application from Azure application registration.</p><p>Parameters:</p><p>The default value is Empty</p><p>Enter the Client ID assigned during Azure application registration.</p></td><td>Notifications</td></tr><tr><td>ovaledge.azure.graphapi.clientsecret</td><td><p>It allows users to store the Client Secret generated during Azure application registration securely.</p><p>Parameters:</p><p>The default value is EmptyEnter the Client Secret obtained from the Azure portal for the registered application.</p></td><td>Notifications</td></tr><tr><td>ovaledge.awsses.smtp.server</td><td><p>It allows users to specify the AWS SES SMTP Server URL for sending email notifications.</p><p>Parameters:</p><p>The default value is Empty</p><p>Enter the SMTP Server URL provided by AWS SES.</p></td><td>Notifications</td></tr><tr><td>ovaledge.awsses.smtp.port</td><td><p>It allows users to specify the AWS SES SMTP Server Port used for sending email notifications.</p><p>Parameters:</p><p>The default value is Empty</p><p>Enter the port number provided by AWS SES (e.g., 25, 465, or 587).</p></td><td>Notifications</td></tr><tr><td>ovaledge.awsses.smtp.mode</td><td><p>It allows users to specify the mode used by the AWS SES SMTP server for secure communication.</p><p>Parameters:</p><p>The default value is Empty</p><p>Enter the server mode (e.g., TLS, SSL) based on your AWS SES configuration.</p></td><td>Notifications</td></tr><tr><td>ovaledge.awsses.smtp.username</td><td><p>It allows users to specify the username for the AWS SES SMTP server.</p><p>Parameters:</p><p>The default value is Empty</p><p>Enter the SMTP username provided by AWS SES to authenticate and send email notifications.</p></td><td>Notifications</td></tr><tr><td>ovaledge.awsses.smtp.password</td><td><p>It allows users to specify the password for the AWS SES SMTP server.</p><p>Parameters:</p><p>The default value is Empty</p><p>Enter the SMTP password associated with the AWS SES username. This is required for authenticating and sending email notifications.</p></td><td>Notifications</td></tr><tr><td>ovaledge.awsses.smtp.from.address</td><td><p>It allows users to specify the email address used to send notifications through the AWS SES SMTP server.</p><p>Parameters:</p><p>The default value is Empty</p><p>Note: This must be a verified email address in your AWS SES configuration.</p></td><td>Notifications</td></tr><tr><td>project.baseline.limit</td><td><p>It enables users to set the number of baselines for a project, thereby enhancing performance.</p><p>Parameters:</p><p>Default value: 5</p><p>Users can set as many baselines as needed.</p></td><td>Projects</td></tr><tr><td>projects.advanced.mode.enable</td><td><p>It allows users to show or hide specific fields (Plan View, Task Categories, % Complete, Estimated Effort, Time Log, Remaining Effort, and Extended Bulk Update) in the Projects module.</p><p>Parameters:</p><p>The default value is false</p><p>If set to true, Fields will be visible for users to input data.</p><p>If set to false, these fields will be hidden.</p></td><td>Projects</td></tr><tr><td>projects.beta.mode.enable</td><td><p>It allows users to show or hide specific fields (Project Groups, Parent Tasks, Project Audit, Baseline Feature, Dependencies, and Custom Fields) in the Projects module, including Task Shutter and List View.</p><p>Parameters:</p><p>The default value is false</p><p>If true, fields will be visible to users for data input.</p><p>If false, these fields will be hidden.</p></td><td>Projects</td></tr><tr><td>dataquality.rulescore.calculation.method</td><td><p>It allows users to choose how the Data Quality Score is calculated, either Object-Based or Row-Based.</p><p>Parameters:</p><p>The default value is Object-Based</p><p>If Object-Based, the Score is calculated based on how many rules each object passes.</p><p>If Row-Based, the Score is calculated based on how many rows meet the rule conditions.</p></td><td><br>Data Quality</td></tr><tr><td>escape.sequence.regex</td><td><p>This setting uses a regular expression to replace predefined special characters with escape sequences when cloning a Business Glossary Term.</p><p>Parameters:</p><p>The default value is([\^$\.*+?()[\]{}|/&#x26;#])</p><p>Note: Users can add any special characters in the value to replace them with escape sequences.</p></td><td>Business Glossary</td></tr><tr><td>ovaledge.GDQ.admin</td><td><p>It allows OE_Admin to assign GDQ Admin privileges to specific roles.</p><p>Parameters:</p><p>The default value is OE_Admin.</p><p>OE_Admin can select one or more roles from the dropdown list to assign GDQ Admin privileges.</p></td><td>GDQ</td></tr><tr><td>home.lastlogin.enable</td><td><p>It allows users to enable the display of the last successful login date, time, along with the timezone, and displays the number of failed login attempts between the Last successful login and the current login below the header section. </p><p>Parameters:</p><p>The default value is False. If True, enables the last login date along with timestamp and unsuccessful login attempts. If false, it disables the display of the previous login information.</p></td><td>Home Page</td></tr><tr><td>search.es.searchcontext</td><td><p>Configure to view the object types in the Search box drop-down list.</p><p>Parameters:</p><p>Available object types: All, Table, Topic, File, Report, API, Schema, Query, Data Attributes, Business Glossary, Service Request, Help &#x26; Resources, Project, Question Wall.</p><p>The default value is All.</p><p>To add more objects to the Value, select them from the drop-down list. The assigned values appear in the Search drop-down.</p><p>If left blank, "All" is displayed.</p></td><td>Global Search</td></tr><tr><td>search.es.pagination.count</td><td><p>Configure to specify the maximum number of records to be added to an Index while running the advanced job to fetch from the local DB to Elasticsearch.</p><p>Supports: Min - 5000, Max - 10000.</p><p>Parameters:</p><p>The default value is 5000.</p><p>Enter the required value in the field provided. Based on the specified value, the records will be added to an Index.</p></td><td><br>Global Search</td></tr><tr><td>search.es.activedetails</td><td><p>Configure to show the active objects in the search results.</p><p>Parameters:</p><p>The default value is Active.</p><p>If set to Active, active objects are displayed in the search results.</p><p>If set to Inactive, inactive objects are displayed in the search results.</p><p>If set to Empty, then both the active and inactive data object results are displayed in the search results.</p></td><td>Global Search</td></tr><tr><td>search.score.use.synonym</td><td><p>Configure to include the Synonym score in the Relevance score formula to determine the most relevant search results.</p><p>The relevance score is calculated based on three components: the Elasticsearch score, the popularity score, and the synonym score (if configured).</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, the search results calculation includes the Synonym score.</p><p>If set to False, the search results calculation excludes the Synonym score.</p></td><td><br></td></tr><tr><td>search.score.use.popularity</td><td><p>Configure the Popularity Score in the Relevance score formula to determine the most relevant search results. The relevance score is calculated based on three components: the Elasticsearch score, the popularity score, and the synonym score (if configured).</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, the search results calculation includes the popularity score.</p><p>If set to False, the search results calculation excludes the popularity score.</p><p>The relevance score calculation depends solely on the Elasticsearch score and the settings configured for the synonym score.</p></td><td><br></td></tr><tr><td>enable.slack.communication</td><td><p>Configure to enable or disable Slack on the My Profile page.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, the Slack option is enabled.</p><p>If set to False, the Slack option is disabled.</p></td><td>My Profile</td></tr><tr><td>alert.popup.duration</td><td><p>Specify the time in seconds to show the alert.</p><p>Parameters:</p><p>The default value is 3</p><p>Min value - 3</p><p>Max value - 15</p><p>Note: Recommended duration is 5.</p></td><td>All Modules</td></tr><tr><td>ovaledge.font.family</td><td><p>Configure to set the font across the application from the predefined fonts: Lufga, Open Sans, Roboto, Arial, and Lato.</p><p>Parameters:</p><p>The default value is Empty.</p><p>Based on the specified value, the application font will be applied.</p></td><td>All modules</td></tr><tr><td>home.videos.viewall.link</td><td><p>Configure to redirect the specific helpful resources link.</p><p>Enter the particular URL in the Value column.</p></td><td>Home</td></tr><tr><td>ovaledge.main.logo</td><td><p>Configure to upload the primary logo to the top-left black bar.</p><p>Enter the specific image in the Value column.</p></td><td>Application</td></tr><tr><td>ovaledge.login.logo</td><td><p>Configure to upload the logo for display at the login page.</p><p>Enter the specific image in the Value column.</p><p>Allowed image types: png, jpeg, and jpg</p></td><td>Login</td></tr><tr><td>deployment.service.msg</td><td><p>Configure to enable or disable the service message that notifies users about latency information during the deployment process.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, the service message to notify users about latency information in the deployment process is enabled.</p><p>If set to False, the service message that notifies users about latency information during the deployment process is disabled.</p></td><td>Home</td></tr><tr><td>deployment.msg</td><td><p>Configure to customize the deployment message.</p><p>Parameters:</p><p>The default value is blank.</p><p>The message entered in the Value column is displayed as a service message.</p></td><td>Home</td></tr><tr><td>deployment.date</td><td><p>Configure to set the time duration to show the service message.</p><p>Parameters:</p><p>The default value is blank.</p><p>Enter the time in mm/dd/yyyy hh:mm format.</p></td><td>Home</td></tr><tr><td>dataquality.score.external.max.score</td><td>Configure the base score for the Data Quality score calculation.</td><td><br></td></tr><tr><td>enable.user.delete.toggle</td><td><p>Configure to view/hide the Delete and Deactivate options in the Delete/Deactivate drop-down list in the Users&#x26;Roles.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, the Deactivate option will be displayed.</p><p>If set to False, the "Delete" and "Deactivate" options will be displayed.</p></td><td>Users &#x26; Roles</td></tr><tr><td>search.es.active.filters</td><td><p>Configure the specific active filters used on the Global Search page to refine search results. Each filter corresponds to a specific attribute of the search items, allowing users to refine their results based on various criteria. Users can remove filters according to their specific requirements.</p><p>Parameters:</p><p>The default values are Connection, Schema, Business Glossary, Table Type, Folder, Report Group, Term Status, Quality Index, Service Request Status, Question Wall, Additional Information, and Created Date.</p><p>Enter the required value in the field provided. Based on the specified values, filters will be displayed on the Global Search page.</p></td><td>Global Search</td></tr><tr><td>globalsearch.match.type</td><td><p>Configure the Global Search function that analyzes search queries against document fields:</p><p>- best_fields: This type optimizes precision by searching multiple fields and returning the highest score for the best match.</p><p>- most_fields: This type is used to optimize recall, which means it adds the scores of each match across multiple fields to increase overall relevance scores.</p><p>- cross_fields: This type analyzes multiple fields as a single combined field, increasing relevance for queries that span multiple fields. It's beneficial for searches that are expected to have various terms across different fields.</p></td><td>Global Search</td></tr><tr><td>ovaledge.mastertag.creator</td><td><p>Configure to create a Master Tag privilege for the specified role.</p><p>Parameters:</p><p>The default value is OE_ADMIN.</p><p>Choose the specified roles from the drop-down list in the Value column to add more roles.</p></td><td>Tags</td></tr><tr><td>ovaledge.onboarding.widget.enable</td><td><p>Configure to enable or disable the onboarding widget screen.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, the onboarding widget screen is enabled.</p><p>If set to False, the onboarding widget screen is disabled.</p></td><td>Home</td></tr><tr><td>ovaledge.searchbar.enable</td><td><p>Configure to enable or disable the search bar on the home screen.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, the search bar on the home screen is enabled.</p><p>If set to False, the search bar on the home screen is disabled.</p></td><td>Home</td></tr><tr><td>enable.slack.channel</td><td><p>Configure to view the 'Add Slack ID' on the Profile page.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, the Add Slack ID option displays on the Profile page.</p><p>I set it to False, and the Add Slack ID option does not display on the Profile page.</p></td><td>My Profile</td></tr><tr><td>enable.google.chat.channel</td><td><p>Configure to view the 'Add GoogleChat Webhook URL' on the Profile page.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, the 'Add GoogleChat Webhook URL' option displays on the Profile page.</p><p>I set it to False, and the 'Add GoogleChat Webhook URL' option does not display on the Profile page.</p></td><td>My Profile</td></tr><tr><td>enable.ms.teams.channel</td><td><p>Configure to view the 'Add Microsoft Teams Webhook URL' on the Profile page.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, the 'Add Microsoft Teams Webhook URL' option displays on the Profile page.</p><p>I set it to False, and the 'Add Microsoft Teams Webhook URL' option no longer displays on the Profile page.</p></td><td>My Profile</td></tr><tr><td>buildlineage.exclude.jobtypes</td><td><p>Configure job types that need to be excluded from the Build Auto Lineage page.</p><p>Parameters:</p><p>The default value is Empty.</p><p>Enter the job types separated by a comma(,).</p><p>Example:</p><p>Single job type - View</p><p>Multiple job types - View, Trigger</p></td><td>Lineage</td></tr><tr><td>enable.welcome.story</td><td><p>Configure to view if the Data Story can be added to the Home Page or set as a Welcome Story.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, the Data Story can be added to the Home Page or set as the Welcome Story.</p><p>I set it to False; the Data Story should neither be added to the Home Page nor set as Welcome Story.</p></td><td>Home</td></tr><tr><td>issaas.client</td><td><p>Configure to specify if the client is SAAS or not.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, the Credential Manager drop-down displays "OE Credential Manager" on the connection creation page.</p><p>If set to False, the Credential Manager drop-down displays "Database" on the connection creation page.</p></td><td>Connectors</td></tr><tr><td>search.es.governancerole.filters.optional</td><td><p>Configure to view the Governance Roles filters used on the Global Search page to refine search results.</p><p>Parameters:</p><p>Owner, Steward, Custodian, Governance Role 4, Governance Role 5, Governance Role 6</p><p>The default value is Data Owner.</p><p>To add more Governance Roles to the Value, select them from the drop-down list.</p><p>If left blank, "Empty" is displayed.</p></td><td>Global Search</td></tr><tr><td>search.es.dataobjects.filters.optional</td><td><p>Configure to view the additional filters for data objects used on the Global Search page to refine search results.</p><p>Parameters:</p><p>Certification, Rating, API Group, Popularity, Report Type, Metadata Curation Score</p><p>The default value is Certification.</p><p>To add additional filters to the Value, select them from the drop-down list.</p><p>If left blank, "Empty" is displayed.</p></td><td>Global Search</td></tr><tr><td>openai.base.url</td><td><p>Enter the base URL for OpenAI if a gateway is used in between. Leave blank if no gateway is in between.</p><p>Parameters:</p><p>The default value is Empty.</p></td><td><br></td></tr><tr><td>openai.timeout</td><td><p>Enter timeout for OpenAI calls in seconds.</p><p>Parameters:</p><p>The default value is 30 seconds.</p></td><td>Application</td></tr><tr><td>show.ai.additional.prompt</td><td><p>Configure to show or hide the additional prompt text field on the AI generation component.</p><p>Parameters:</p><p>The default value is True.</p><p>If set to True, the additional prompt text field will be displayed on the AI generation component.</p><p>If set to False, the additional prompt text field will not be displayed on the AI generation component.</p></td><td>Data Catalog, Business Glossary</td></tr><tr><td>online.assistance.enable</td><td><p>Configure to enable or disable Online Assistance.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, the Online Assistance option will be enabled.</p><p>If set to False, the Online Assistance option will be disabled.</p></td><td>Data Catalog, Business Glossary</td></tr><tr><td>login.support.enable</td><td><p>Configure to enable or disable support information on the Login page.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, the support information will be displayed on the Login page.</p><p>If set to False, the support information will not be displayed on the Login page.</p></td><td>Login</td></tr><tr><td>ovaledge.login.title</td><td><p>Configure to view the title or tagline for the application on the Login page.</p><p>Parameters:</p><p>The default value is Empty.</p><p>Based on the specified value, the title or tagline will be displayed on the Login page.</p></td><td>Login</td></tr><tr><td>ovaledge.login.description1</td><td><p>Configure to view the application description on the Login page.</p><p>Parameters:</p><p>The default value is Empty.</p><p>Based on the specified value, the description will be displayed on the Login page.</p></td><td>Login</td></tr><tr><td>ovaledge.login.description2</td><td><p>Configure to view the additional description for the application on the Login page.</p><p>Parameters:</p><p>The default value is Empty.</p><p>Based on the specified value, the additional description will be displayed on the Login page.</p></td><td>Login</td></tr><tr><td>login.doc.link</td><td><p>Configure the Login page to display the URL link for the application's documentation and videos.</p><p>Parameters:</p><p>The default value is Empty.</p><p>Based on the specified value, the URL will be displayed on the Login page.</p></td><td>Login</td></tr><tr><td>login.faq.link</td><td><p>Configure the application to display the Frequently Asked Questions URL link on the Login page.</p><p>Parameters:</p><p>The default value is Empty.</p><p>Based on the specified value, the URL will be displayed on the Login page.</p></td><td>Login</td></tr><tr><td>anomaly.detection.default.assignee</td><td><p>Configure the default governance role for anomaly detection if a user wants to assign someone other than the default custodian.</p><p>Parameters:</p><p>Select the role from the specified drop-down list.</p></td><td><br></td></tr><tr><td>application.date.format</td><td><p>Configure to set the default date format to be applied across the application. Users can choose from over 30 formats, with options to use slash or dash separators. Common format parameters include: YYYY for Year, MM for Month, DD for Day, HH for 24-hour format Hour, hh for 12-hour format Hour, mm for Minutes, ss for Seconds, and A for am/pm.</p><p>Parameters</p><p>The default format is set to MM-DD-YYYY hh:mm A.</p><p>Users can choose any available format from the drop-down list.</p></td><td>Application</td></tr><tr><td>enable.time.customfield</td><td><p>Configure to show/hide the time components (hour, minute, second) from the Date Custom Fields across all relevant modules: Data Catalog, Business Glossary, Tags, Data Quality, and ROPA.</p><p>Parameters:</p><p>The default value is True.</p><p>If set to True, the time component will be displayed.</p><p>If set to False, the time component will not be displayed.</p></td><td>Data Catalog, Business Glossary, Tags, Data Quality, and ROPA</td></tr><tr><td>tags.dag.enabled</td><td><p>Configure to show or hide the Data Asset Groups Security tab.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, Data Asset Groups Security will be displayed.</p><p>If set to False, Data Asset Groups Security will not be displayed.</p></td><td>Tags</td></tr><tr><td>index.max.result.window</td><td><p>Configure to return the maximum number of Data Catalog records in a single search request.</p><p>Parameters:</p><p>The default value is 10,000.</p><p>The minimum allowed value is 5000, and the maximum is 10,000.</p></td><td><br></td></tr><tr><td>es.datacatalog.grid.mysql.fallback.force</td><td><p>Configure to fetch data from the Data Catalog using MySQL or Elasticsearch.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, data from the Data Catalog will be fetched from MySQL.</p><p>If set to False, Data Catalog data will be fetched from Elasticsearch.</p></td><td>Data Catalog</td></tr><tr><td>browser.extension.enable.guest</td><td><p>Configure to enable/disable the Browser Extension for non-licensed users.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, enable the Browser Extension.</p><p>If set to False, the Browser Extension is disabled.</p></td><td>Browser Extension</td></tr><tr><td>browser.extension.allowed.email.domains</td><td><p>Configure access for guest users to the browser extension by specifying valid email domains as comma-separated values.</p><p>Parameters:</p><p>The default value is Empty.</p><p>Enter the valid email domains in the specified Value field.</p><p>Example: @ovaledge.come, @google.com</p></td><td>Browser Extension</td></tr><tr><td>businessglossary.term.publish</td><td><p>Configure the roles to publish terms directly through the Term Summary page.</p><p>Parameters:</p><p>The default value is Empty.</p><p>Select the roles from the drop-down list. Selected roles can publish terms through the term Summary page.</p></td><td>Business Glossary</td></tr><tr><td>browser.extension.proxy.user.for.guest</td><td>Specifies the admin user to be associated with data quality service requests raised by guest users through the plugin. The actual email of the guest user will be recorded separately in the service request details.</td><td>Chrome Extension</td></tr><tr><td>es.datacatalog.filter.size</td><td><p>Configure to set the filter size of the catalog objects on a page.</p><p>Parameters:</p><p>The default value is 100.</p><p>The minimum allowed value is 1, and the maximum is 100.</p></td><td>Data Catalog</td></tr><tr><td>catalog.es.oetp.additional.ops.allowed</td><td><p>Configure to enable/disable the Advanced Filter option in the Data Catalog.</p><p>Parameters:</p><p>The default value is True.</p><p>If set to True, the Advanced Filter option will be enabled.</p><p>If set to False, the Advanced Filter option will be disabled.</p><p>Note: This feature is supported only when the Elasticsearch option is enabled for the Data Catalog.</p></td><td>Data Catalog</td></tr><tr><td>ovaledge.instance.name.color</td><td><p>Configure the background color for the environment name displayed in the top header.</p><p>Parameters:</p><p>The default value is Blue.</p><p>Allowed values from the drop-down list: Green, Red, Yellow, and Blue.</p></td><td>All Modules</td></tr><tr><td>ms.teams.integration.type</td><td><p>Configure the Microsoft Teams integration method for sending notifications.</p><p>Parameters:</p><p>The default value is Webhook.</p><p>If you have updated Microsoft Teams to a version that no longer supports Webhooks, switch the integration method to Workflows and set the value to Workflow.</p></td><td>My Profile</td></tr><tr><td>notification.system.administration.user</td><td>Displays the system administration user.</td><td>Notifications</td></tr><tr><td>nudging.cool.off.period</td><td><p>Configure to send the notifications to the approvers via email and In-App alerts.</p><p>Parameters</p><p>The default value is 24.</p><p>The Nudge button is enabled for the specified hours based on the entered value.</p><p>Note: Only numeric values with whole numbers are allowed.</p></td><td>Service Desk, Notifications</td></tr><tr><td>ai.bulk.desc.curation.max.object.count</td><td><p>Configure to support the maximum object count for bulk description curation for data objects via AI.</p><p>Parameters:</p><p>The default value is 10000</p><p>Max allowed value is 1000000000</p></td><td>Data Catalog, Business Glossary</td></tr><tr><td>ai.bulk.desc.curation.batch.threshold</td><td><p>Threshold object count supported for bulk description curation for data objects via BATCH AI APIs.</p><p>Parameters:</p><p>The default value is 1000.</p><p>The minimum allowed value is 0.</p><p>Should not be more than ai.bulk.desc.curation.max.object.count</p></td><td>Data Catalog, Business Glossary</td></tr><tr><td>ai.generatedesc.word.count.limit</td><td><p>Configure to limit the word count for AI-curated descriptions.</p><p>Parameters:</p><p>The default value is 100.</p><p>The minimum allowed value is 10, and the maximum is 250.</p><p>Note: The defined word count limit is an approximate word count limit.</p></td><td>Data Catalog, Business Glossary</td></tr><tr><td>system.url.max.length</td><td><p>Configure to define the maximum allowable length for URLs generated in the application.</p><p>Parameters:</p><p>The default value is 2000 characters.</p><p>Enter any positive integer in the Value field.</p><p>Note: If the URL exceeds the specified length, the system truncates the URL or provides a warning message.</p></td><td>All Modules</td></tr><tr><td>home.actionitems.alert.enable</td><td><p>Configure to enable or disable the alert pop-up functionality.</p><p>Parameters:</p><p>The default value is True.</p><p>If set to True, the alert pop-up functionality will be enabled.</p><p>If set to False, the alert pop-up functionality will be disabled.</p></td><td>Home</td></tr><tr><td>dataquality.associatedobjects.files.limit</td><td><p>Configure to set the maximum number of file objects (files and file columns) that can be associated with a Data Quality Rule.</p><p>Parameters:</p><p>The default value is 20.</p><p>The minimum allowed value is 1, and the maximum is 250.</p><p>Enter the value in the provided field.</p></td><td>Data Catalog, Data Quality Rule</td></tr><tr><td>dataquality.associatedobjects.tables.limit</td><td><p>Configure to set the maximum number of table objects (tables and table columns) that can be associated with a Data Quality Rule.</p><p>Parameters:</p><p>The default value is 1000.</p><p>The minimum allowed value is 1, and the maximum is 1000.</p><p>Enter the value in the provided field.</p></td><td>Data Catalog, Data Quality Rule</td></tr><tr><td>authorised.governance.roles.for.certification</td><td><p>Select the governance roles that have permission to update the certification of Data Catalog objects. Only users with these roles or system administrators can modify certifications. All other users will be restricted.</p><p>Parameters:</p><p>The default Value is Steward and Custodian</p><p>Users can select one or more options from the drop-down list. Options: Owner, Steward, Custodian, Governance Role 4, Governance Role 5, Governance Role 6</p></td><td><br></td></tr><tr><td>api.basic.auth.enabled</td><td><p>This configuration controls whether Basic Authentication is enabled for accessing OvalEdge APIs. Basic Authentication requires API clients to provide a username and password in the HTTP request header for Authentication. A system restart is required for changes to take effect.<br>Parameters:</p><ul><li>The Default value is false (Basic Authentication is disabled)</li><li>Enter the value as true to enable Basic Authentication for APIs, and enter the value as false to disable Basic Authentication for APIs.</li></ul></td><td></td></tr><tr><td>Lineage.build.relationships</td><td><p>This configuration determines whether OvalEdge should build and display data lineage relationships for datasets within the same connection. For datasets with over 100,000 records associated with the same connection, it is recommended to set this parameter to false.</p><p>Parameters:</p><ul><li>The default value is True.</li><li>Set the value to true to enable building lineage relationships for datasets within the connection. Set the value to false to disable building lineage relationships.</li></ul></td><td></td></tr><tr><td>inactive.job.threshold</td><td><p>Configure the time (in minutes) after which a job with no log generation is considered inactive.</p><p>Parameters:</p><p>The default value is 60 minutes.</p><p>Enter the required threshold in minutes.</p></td><td>Jobs &#x26; Notificaion</td></tr><tr><td>inactivejob.notification.timeout</td><td><p>Configure the time (in hours) to identify inactive jobs for notifications.</p><p>Parameters:</p><p>The default value is 24 hours.</p><p>Enter the required timeout in hours.</p></td><td>Jobs &#x26; Notificaion</td></tr><tr><td>lineage.codes.process.limit</td><td><p>Configure the maximum number of codes to be parsed when building lineage for new or changed codes.</p><p>Parameters:</p><p>The default value is Empty (no limit; parses all codes).</p><p>Enter a numeric value (X). Only the first X codes are parsed, and the remaining are skipped.</p><p>Example: If set to 500 and 1500 codes are detected, only 500 are parsed.</p></td><td>Data Catalog</td></tr><tr><td>long.running.job.threshold</td><td><p>Configure the maximum duration (in hours) a job can run before it is considered long-running.</p><p>Parameters:</p><p>The default value is 24 hours.</p><p>Enter the required duration in hours.</p></td><td>Jobs</td></tr><tr><td>nonlocal.user.creation</td><td><p>Configure whether to allow new user creation when authentication is managed through external providers.</p><p>Parameters:</p><p>The default value is False.</p><p>If set to True, new users can be created with non-local authentication.</p><p>If set to False, new user creation is disabled with non-local authentication.</p></td><td>Users</td></tr><tr><td>ovaledge.email.footer.configure</td><td><p>Configure the text to display as a footer in all email notifications.</p><p>Parameters:</p><p>The default value is Empty.</p><p>Enter the required footer text for consistent branding, compliance, or disclaimers.</p></td><td>Notifications &#x26; System Settings > Notification Templates</td></tr><tr><td>ovaledge.email.footer.enable</td><td><p>Configure to enable or disable a global footer in all email notifications.</p><p>Parameters:</p><p>The default value is True.</p><p>If set to True, footer text is displayed.</p><p>If set to False, footer text is disabled.</p></td><td>Notifications &#x26; System Settings > Notification Templates</td></tr><tr><td>stripe.api.key</td><td><p>Configure the Stripe API key.</p><p>Parameters:</p><p>The default value is Empty.</p><p>Enter the required API key.</p></td><td>AI</td></tr><tr><td>stripe.public.key</td><td><p>Configure the Stripe public key.</p><p>Parameters:</p><p>The default value is Empty.</p><p>Enter the required public key.</p></td><td>AI</td></tr><tr><td>stripe.webhook.secret</td><td><p>Configure the Stripe webhook secret.</p><p>Parameters:</p><p>The default value is Empty.</p><p>Enter the required webhook secret.</p></td><td>AI</td></tr><tr><td>askedgi.recipe.marketplace.base.url</td><td>Configure the URL of the recipe marketplace used for editing or generating public/shareable links.<br>Parameters:<br>The default value is Empty.<br>Enter the required marketplace URL</td><td>askEdgi, Recipe</td></tr><tr><td>askedgi.recipe.marketplace.password</td><td>Configure the password used to authenticate with the recipe marketplace APIs.<br>Parameters:<br>The default value is Empty.<br>Enter the required marketplace password.</td><td>askEdgi, Recipe</td></tr><tr><td>askedgi.recipe.marketplace.url</td><td>Configure the base URL of the recipe marketplace for API calls.<br>Parameters:<br>The default value is Empty.<br>Enter the required marketplace URL.</td><td>askEdgi, Recipe</td></tr><tr><td>askedgi.recipe.marketplace.username</td><td>Configure the username used to authenticate with the recipe marketplace APIs.<br>Parameters:<br>The default value is Empty.<br>Enter the required marketplace username.</td><td>askEdgi, Recipe</td></tr><tr><td>askedgi.s3.public.connector</td><td>Configure the S3 public connector ID used for S3-to-S3 copy operations in AskEdgi. When a connection matches this ID, the system uses copy mode instead of download-to-local mode.<br>Parameters:<br>The default value is Empty.<br>Enter the required S3 connector ID.</td><td>askEdgi</td></tr><tr><td>askedgi.workspace.objects.limit</td><td>Configure the maximum number of objects allowed in a workspace.<br>Parameters:<br>The default value is 50.<br>Enter the required workspace object limit.</td><td>askEdgi</td></tr><tr><td>askedgiplus.enable</td><td>Configure to enable or disable AskEdgi Plus.<br>Parameters:<br>The default value is False.<br>If set to True, AskEdgi Plus is enabled.<br>If set to False, AskEdgi Plus is disabled.</td><td>askEdgi</td></tr><tr><td>max.concurrent.bridgeclient.tasks</td><td>Configure the maximum number of client-side data processing tasks allowed to run simultaneously.<br>Parameters:<br>The default value is 5.<br>Enter the required task limit.</td><td>askEdgi</td></tr><tr><td>max.concurrent.bridgeserver.tasks</td><td>Configure the maximum number of server-side data processing tasks allowed to run simultaneously.<br>Parameters:<br>The default value is 3.<br>Enter the required task limit.</td><td>askEdgi</td></tr><tr><td>oe.edgi.free.plan.price.id</td><td>Configure the Stripe price ID for the free plan.<br>Parameters:<br>The default value is Empty.<br>Enter the required Stripe price ID.</td><td>askEdgi, Recipe</td></tr><tr><td>ovaledge.edgi.host.type</td><td>Configure the application hosting type.<br>Parameters:<br>The default value is Empty.<br>Enter the hosting type (e.g., public).</td><td>askEdgi</td></tr><tr><td>askedgi.edition</td><td>This value is used for choosing the askEdgi edition: Catalog Insights or Insights &#x26; Analytics<br>Parameters:<br>Available editions: Catalog Insights / Insights &#x26; Analytics<br>The default value is '.<br>Catalog Insights: Catalog search with metadata analytics across tables and files<br>Insights &#x26; Analytics: Full analytics on top of files and catalog tables for deeper analysis</td><td>askEdgi</td></tr><tr><td>askedgi.ovaledge.recipe.connection.id</td><td>Default OvalEdge recipe connectId</td><td>askEdgi, Recipe</td></tr><tr><td>askedgi.metadata.analytics.role</td><td><p>Define the role permitted to perform metadata analytics in AskEdgi (SaaS v2 and On-Prem variants).<br>A role from any license level can be selected.</p><p>As a best practice, configure a role associated with a limited number of users (ideally 4–5) to ensure stable performance of workspaces.<br>Parameters:<br>The default role is OE_ADMIN</p></td><td>askEdgi</td></tr><tr><td>dcr.object.limit</td><td>Set the maximum number of objects that can be added to the scope of DCR Model.<br>Parameters:<br>Default Value: 20<br>Max Value: 100</td><td>Data Classification Recommendations</td></tr><tr><td>jobs.priority.running.count</td><td>This configuration defines the count of a separate queue for priority jobs, ensuring they can run even if they are stuck in the INIT state due to the ovaledge.running.jobs.count limitation.</td><td>Jobs</td></tr><tr><td>ai.config</td><td>This configuration is used to store the AI config. This opens a popup to configure the AI settings.<br>Parameters :<br>AI Config<br>The default value is standard config without the api keys</td><td>AI</td></tr><tr><td>dashboard.apache.superset.enabled</td><td>This configuration controls the integration of the Apache Superset external application when set to True.<br>Parameters:<br>The default value if false</td><td>Dashboards</td></tr><tr><td>dashboard.apache.superset.base_url</td><td>This configuration allows users to add the required Apache Superset base URL.</td><td>Dashboards</td></tr><tr><td>dashboard.apache.superset.user_name</td><td>This configuration allows users to add the user name for the base URL.</td><td>Dashboards</td></tr><tr><td>dashboard.apache.superset.password</td><td>This configuration allows users to add the password for the base URL.</td><td>Dashboards</td></tr><tr><td>dashboard.external.dashboard.admin</td><td>This configuration defines the user role authorized to access the Apache Superset external application.<br>Parameters:<br>The default value is OE_Admin.</td><td>Dashboards</td></tr><tr><td>notes.relatedobjects</td><td>The notes section will appear in the Related Objects of Business Glossary when the configuration is turned on.</td><td>Business Glossary</td></tr><tr><td>restrict.newuser.saml.login</td><td>This cofiguration is used to restrict/allow new users to login if set to true.<br>Note: A user must be created in advance through the login process or administrative setup.<br>Parameters:<br>The default value is false.</td><td>Login</td></tr><tr><td>db.calls.limit.per.work.unit</td><td><p>This configuration allows setting a limit on DB calls per work unit. </p><p>Parameters:</p><p>The default value is 30.</p></td><td>Jobs</td></tr><tr><td>job.logs.limit.per.work.unit</td><td><p>This configuration allows setting the Job Logs Limit per work unit.</p><p>Parameters:</p><p>The default value is 30.</p></td><td>Jobs</td></tr><tr><td>app.logs.limit.per.work.unit</td><td><p>This configuration allows setting a limit on App logs per work unit.</p><p>Parameters:</p><p>The default value is 30.</p></td><td>Jobs</td></tr><tr><td>job.load.retention.days</td><td><p>This setting helps calculate the date, based on the configured retention period.</p><p>Parameters:</p><p>The default value is 30.</p></td><td>Jobs</td></tr><tr><td>qs.forceselect</td><td><p>This configuration enforces SELECT as the query type when the query type is NULL, OTHER, or DCL. It serves as a workaround to allow query execution when the system fails to identify the query type.</p><p>Parameters:</p><p>The default value is False.</p></td><td>Query Sheet</td></tr><tr><td>lineage.build.transformations</td><td><p>Controls whether transformation logic is extracted and identified during lineage building. It determines whether the specific code segments that contribute to lineage are captured and highlighted in the Data Catalog.</p><p>Parameters:</p><ul><li>When enabled, the system extracts, maps, and highlights transformation code associated with lineage during lineage building.</li><li>When disabled, lineage is generated without extracting or storing details of the transformation code.</li></ul><p><strong>Note</strong>: Enabling this setting may increase lineage build time due to additional code parsing and extraction.</p></td><td>Lineage</td></tr><tr><td>oetp.sort.by.default</td><td><p></p><p>Controls how results are sorted when no explicit ORDER BY clause is defined in a query. It determines whether sorting prioritizes readability or performance by default.</p><p>Parameters:</p><ul><li>The default value is True.</li><li>When enabled, results are sorted alphabetically by name (e.g., column name or table name).</li><li>When disabled, results are sorted based on the primary key to ensure faster performance and consistent ordering.</li></ul></td><td>Others</td></tr><tr><td>data.product.default.relationship.type</td><td><p></p><p>Defines the default relationship type assigned to a data product. It determines how relationships are categorized when they are created for a data product, ensuring consistency in relationship classification.</p><p>Parameters:</p><ul><li>When set, the specified relationship type is automatically applied as the default for data products.</li><li>If not set, no default relationship type is applied, and the relationship type must be defined manually.</li></ul></td><td>Data Products</td></tr><tr><td>ovaledge.datadomain.admin</td><td><p></p><p>Controls which roles are granted permission to create Data Domains. It defines access to Data Domain creation functionality, ensuring that only authorized roles can perform this action.</p><p>Parameters:</p><ul><li>The default value is OE_ADMIN.</li><li>Select one or more roles from the dropdown to grant Data Domain creation privileges.</li></ul></td><td>Data Products</td></tr></tbody></table>

***

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