Configuration Groups
System Settings are organized based on specific features and conveniently displayed as tabs on the main page for convenient user accessibility. This enables administrators to effortlessly navigate between tabs, simplifying the exploration of various configuration groups.
All
The All tab in System Settings shows a complete list of all configuration settings used across the application. It combines settings from different modules—like Users & Roles, Notifications, Lineage, Jobs, SSO, Data Catalog, and more—into one place.
This tab makes it easy for administrators to:
View and manage all settings in one view.
See default values, descriptions, and last updated info.
Edit settings quickly without switching tabs.
Use the All tab to review or update system behavior, security, performance, and integrations across the entire platform.
System Path
System Path Settings are important for the proper functioning. They ensure the application can access essential resources, links, and tools required for operations and user interactions.
These settings include defining the OvalEdge application's base URL for hyperlink navigation, setting up the OvalEdge License Agreement link for user reference, configuring the temporary server folder path for file storage, and establishing an executable tool path for converting files to XML format.
Example:
ovaledge.base.url: Specify the OvalEdge application base URL, which helps in hyperlink navigation.
Parameters:
The default value is http://localhost:8080/ovaledge
Enter the valid OvalEdge base URL in the field provided.
Users & Roles
Users and Roles settings are essential for establishing user access, defining roles and privileges, and ensuring secure administration and effective task management. Notably, critical administrative roles specific to individual modules, such as the Tags Role for managing tags, the Project Owner Role for overseeing projects, the Connector Creator, and others, can be precisely configured in this section.
Example:
ovaledge.login.application: Set up the Self Registration process to allow new users to access or log in to the application site.
Parameters:
The default value is True.
If set to Empty, the users can sign up via Self Registration from the application login page.
If set to False, the self-registration process gets disabled.
Lineage
The lineage Settings provide a range of configurations for managing the generation of data lineage diagrams. Each setting serves a specific purpose to customize data lineage tracking and visualization.
Example:
shallow.lineage.connection.ids: Configure to build a shallow lineage on selective connectors.
Parameters:
The default value is Empty.
Enter the Connection IDs separated by a comma.
Notifications
Settings
Administrators use Email Configuration settings to control how OvalEdge sends notification emails. Based on the selected server type (ovaledge.email.server.type), the system activates the required fields for SMTP, AWS SES, or Azure Graph API setup.
System settings also allow administrators to configure notifications across multiple channels, including Email, Inbox, Slack, Microsoft Teams, and Google Chat.
Example:
ovaledge.smtp.server: Specify the SMTP server URL to send and receive mail messages.
Example: google.smtp2go.com
Parameters:
The default value is Empty.
Enter the URL in the field provided.
Notification Templates
Administrators can customize Notification Templates to personalize the notifications sent to users. These notification messages can be customized for Inbox, Email, Slack, MS Teams, and Google Chat. Additionally, the messages can be altered by implementing various variables corresponding to specific events or features. Administrators can use drag-and-drop functionality to insert these variables into the message body.
SSO
The SSO System Settings is crucial for accommodating integration with various SSO technologies such as SAML and LDAP. System admins can configure the system to meet the standards of External SSO options, remove role prefixes and suffixes defined in SAML to the OvalEdge application, set up dummy email IDs for LDAP service accounts that don't have email addresses and others.
Example:
saml.role.prefix: Remove role prefixes defined in SAML that match OvalEdge roles. For Example, if GLOSKY_OE_Admin; GLOSKY_OE_Public are the roles defined in the SAML instance. Using this configuration, the prefix GLOSKY_ can be removed, and the roles OE_Admin and OE_Public that match with OvalEdge are retrieved.
Parameters:
The default value is Empty.
Enter the prefix keyword that should be removed.
Proxy
Proxy settings enable OvalEdge to route its network requests and web service access through a proxy server, enhancing security, privacy, and network performance.
Example:
proxy.host: Specify the IP address of the Proxy.
Parameters:
The default value is Empty.
Enter the IP Address of the host server.
Audit Data Archival
Audit Data Archival is a process designed to transfer older logs, no longer essential for compliance or security, from the OvalEdge database to dedicated storage. The historical logs capturing all application activities accumulate over time, consuming significant storage space and potentially affecting performance. To alleviate this, outdated logs are relocated to mass storage before deletion, freeing up disk space and sustaining optimal application performance.
By default, it automatically archives all tables at 2:00 AM every day. This section allows users to manage and optimize the storage of audit logs within the OvalEdge database.
Users can selectively add specific data objects to the Audit Data Archive by utilizing the "+Add Archival Policy" button in the bottom left. This involves specifying the table name and the desired retention period, followed by saving the settings. The retention period dictates how long logs are archived, ranging from a month to a year. Upon expiration of the retention period, the logs are automatically removed from the OvalEdge database. Users have the flexibility to archive logs in either CSV or SQL format.
Splunk
These settings allow OvalEdge to integrate seamlessly with Splunk for efficient log management and analysis. OvalEdge posts three kinds of Logs to Splunk.
Application/Server Logs
Job/Process Logs
Audit Logs
Admins can use the "Test Connector" feature to ensure the seamless integration of Splunk. By clicking on this option, they can verify the successful completion of key and value configurations. This step is a proactive measure to confirm that the necessary configurations are accurately implemented, ensuring that the logs from OvalEdge are effectively transmitted and captured in Splunk for comprehensive monitoring and analysis. This streamlined process enhances the troubleshooting capabilities, providing Admins with an efficient solution for log management and analysis.
Example:
splunk.tcp_udp.host: Specify the URL of the Splunk TCP events. (eg: http://splunk.dns.com:9999).
Parameters:
The default value is Empty.
Enter the value in the field provided.
File Scanner
The File Scanner functionality is powered by ClamAV, a robust malicious content protection engine employing diverse techniques for detecting malware. The File Scanner section within System Settings allows users to configure the ClamAV - File Scanner settings. This validation occurs when files are uploaded using the "Upload File or Folder" Advanced Tool.
To ensure the efficacy of the File Scanner, users can utilize the "Validate File Scan" button. This button enables them to initiate and validate the scanning process manually.
Example:
fs.system.hostname: Specify the filescan host address.
Parameters:
The default value is Empty.
Enter the value in the field provided.
Connector
The Connector tab within the System Settings consolidates all essential configurations dedicated to the connectors application. It includes configuring Query parameters, RDAM details, or other connector-specific settings to ensure the smooth operation of OvalEdge's connectivity features.
Example:
connector.environment: Specify the instance of the connector.
Example: Development/Staging/Testing/Production. The naming convention of the instance is client-specific.
Parameters:
The default value is Empty.
Enter the names of the instances separated by commas in the field provided. These values are shown as a drop-down for the Environment attribute on the connector creation page.
AI
This feature enables a secure connection between OvalEdge and ChatGPT using a token for seamless integration and communication. It also allows users to configure the visibility of the "Generate with AI" icon for Business, Technical, and Detail descriptions, offering flexibility in how AI assistance is displayed.
Example:
ai.description.enable: Configure to show/hide the Generate with AI icon for the Business, Technical, and Detail descriptions.
Parameters:
The default value is True.
If set to True, show the Generate with AI icon for the Business, Technical, and Detail descriptions.
If set to False, hide the Generate with AI icon for the Business, Technical, and Detail descriptions.
Global Search
The Global Search settings allow administrators to configure the behavior and display of the global search functionality. These settings empower users to customize their search experience, control the visibility of certain features, and fine-tune the search parameters according to their specific requirements.
Example:
search.es.activedetails - Configure to show the active objects in the search results.
Parameters:
The default value is Active.
If set to Active, active objects are displayed in the search results.
If set to Inactive, inactive objects are displayed in the search results.
If set to Empty, then both the active and inactive data object results are displayed in the search results.
Data Quality
Settings
The Data Quality System Settings tab enables users to configure and customize various parameters related to Data Quality Rules (DQRs). Users can define rules for DQR execution, rule execution conditions, algorithm selections, DQR score, set thresholds, and control the behavior of anomaly detection for comprehensive control over data quality assessment. We can also configure the DQ Score Weightage from the 9 dots option at the top right corner.
Example:
Dataquality.associatedobjects.tables.limit - Sets the maximum number of table objects (tables and columns) that can be linked to a Data Quality Rule.
Parameters:
Default value: 1000
Allowed range: 1 to 1000
Dimensions
The Data Quality Dimensions settings allow default admins to define and manage standardized quality metrics (dimensions) used across data quality rules. These dimensions provide a consistent way to categorize and assess data quality, such as Accuracy, Completeness, Uniqueness, and more.
Each dimension can be customized with a label, description, and classification type, and changes are tracked for auditability.
Dimension: Name of the data quality dimension (e.g., Accuracy, Timeliness).
Description: Detailed explanation of what the dimension evaluates.
Dimension Type: Classifies the dimension (e.g., Technical, Business, Operational).
Created By: The user who created the dimension.
Created Date: Timestamp when the dimension was created.
History: Shows modification history for auditing changes over time.
Delete: Option to remove a dimension that is no longer required.
Service Desk
Settings
Service Desk Settings provide a customizable framework for default admins to efficiently manage service request processes. They enable the configuration of various aspects, including setting the external service request template ID, configuring system-defined templates, and defining parameters like maximum field count and approver levels. Team roles can be set, specifying the maximum number of users for request approval. By defining the maximum number of requests to be approved at once, bulk request management is streamlined. Setting business hours can fine-tune SLA calculations.
Example:
servicedesk.template.approvalworkflow.limit: Specify the maximum number of approver levels in the approval workflow for a service desk template.
Parameters:
The default value is 10.
Maximum value is 20.
Enter the value in the field provided.
Workflow Action and Status
The Workflow Action and Status settings in Service Desk allow default admins to define how service request tickets transition through various stages. Default admins can activate or deactivate specific statuses, apply them to selected modules, and track their creation and update history.
Each Workflow Action and Status likely involves the following configurable settings:
Action: The name of the workflow action (e.g., Approve, Reject, Escalate) that a user can perform.
Status: The resulting status of a ticket after the action is executed (e.g., Approved, Rejected, Pending).
Description: A short explanation of what the action or status represents.
Application Defined Description: System-defined description for default workflow behaviors (non-editable).
Color: The label color associated with a status for easy identification in the UI.
Is Active: Indicates whether the action or status is currently active and in use.
Scope: Defines whether the status applies globally or to specific modules (e.g., Data Quality, Request Management).
Created On: The date when the action/status was created.
Updated On: The date of the most recent update made to the action/status.
Bridge
The Bridge system settings enable administrators to configure how the application integrates with external systems or components for data transfer and communication. These configurations are essential for enabling Bridge functionality, selecting the appropriate Bridge type (REST or NiFi), and defining the communication protocol, server, and operational paths.
Example:
ovaledge.bridge.mode: Enable or disable Bridge functionality in the application.
Parameters:
The default value is False
If set to True: The Bridge functionality is enabled
If set to False: The Bridge functionality is disabled
Login and Home
Login and Home settings allow administrators to configure the visual branding and user experience of the login page and home dashboard. These settings help align the application's appearance with organizational standards.
Example:
ovaledge.branding.logo - a custom brand logo for display on the login page and application header.
Parameters:
The default value is Empty
Image Size: Standard dimensions are 130 x 26 pixels
Maximum File Size: 2 MB
Supported Formats: JPEG, PNG
Action: Click on the field to upload the image file
Application Diagnostics
Application diagnostics allows admin users and architects to monitor, analyze, and troubleshoot the OvalEdge application and ensure it functions correctly and efficiently. The main objectives of application diagnostics are to identify performance issues, detect errors, and ensure the application meets its intended goals.
Example:
oe.diagnostics.min.query.cost: To set the maximum cost of a query (performance of a query), which provides a way to identify queries that are consuming excessive resources or taking too long to complete, so that they can be optimized.
Parameters:
The default value is 50.
Enter the value in the field provided.
Browser Extension
The Browser Extension settings allow default admins to manage Browser Extension that enable users to capture metadata, perform data quality actions, and interact with OvalEdge via supported browser plugins. These settings control extension availability for licensed and guest users, enforce domain-based access restrictions, and define proxy user behavior for request attribution.
Example:
Browser.extension.enable.guest: Enable or disable the Browser Extension for non-licensed (guest) users.
Parameters:
The default Value is False
If set to True, guest users are allowed to use the Browser Extension without an OvalEdge license.
If set to False, only licensed users can access the Browser Extension.
This setting ensures controlled access to plugin functionality for users outside the licensed user pool.
Business Glossary
The Business Glossary settings allow administrators to control how glossary terms are created, published, associated, and visually represented. These configurations enable flexible governance of term lifecycle, term-data object associations, relationship types, and UI personalization across domains and categories.
Example:
businessglossary.term.publish: Configure the roles allowed to publish terms without additional approval.
Parameters:
The default value is Empty
Value: Select roles from the drop-down list
Roles selected here will have permission to publish glossary terms directly through the term Summary page.
Relationship Type Settings
The Relationship Type settings define the predefined and custom relationships available between glossary terms. These settings support semantic modelling and improve glossary navigation and understanding.
Example:
Synonym
Antonym
Yes
Custom Defined
Yes
Replaced by
Replaced from
Yes
System Defined
No
Projects
The Projects System Settings tab allows users to define the maximum number of data objects per project, configure roles for task reassignment, and verify user access permissions on data objects before assigning tasks. It also controls task visibility in the board, lists views based on security permissions, assigns project admin privileges to roles, and enables or disables the Status Bar functionality within the project module.
Example:
role.project.admin: Configure to assign Project admin privileges to Roles.
Parameters:
The default value is OE_ADMIN.
Click on the value to select a role to assign as Project Admin.
API
The API System Settings allows users to assign a role to execute Application APIs, authorizing access through system settings such as oe.apirole.read and ovaledge.api.role. It enables granting view access for multiple roles exclusively via the HTTP GET method and provides an option to include or exclude catalog names in the API response.
Example:
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.
Jobs
The Jobs settings enable administrators to manage and optimize job execution. These configurations govern how jobs are scheduled, executed, and monitored, ensuring balanced performance across both internal and external workloads.
Example:
ovaledge.running.jobs.count: Specifies the maximum number of concurrent jobs (external or internal) that can run in the application at a given time.
External Jobs: Data processing activities triggered on source systems such as Crawl, Profile, etc.
Internal Jobs: Tasks executed like Tag Application, Recommendations, and similar background processing jobs.
Parameters:
The default value is 3
Allowed Range: 1 to 10
Value Field: Enter the desired maximum number of concurrent jobs.
Governance App
The Governance App settings manage configurations required to enable, integrate, and secure file uploads and redirection functionalities within the Governance applications. These settings support secure access, storage, and scanning of files, and facilitate seamless navigation for end users.
Example:
assetmanager.storage.connId: Specifies the connection ID used to access the configured storage service.
Parameters:
The default Value is Empty
Value Field: Enter the connection ID corresponding to the storage service.
Data Catalog
The Data Catalog System Settings enable administrators to configure the display, behavior, and metadata handling of Data Catalog objects, query sheets, and embedded content across various data sources. These settings allow greater control over how users interact with the Data Catalog and its associated components.
Example:
Querysheet.columns.parameterization: Enable parameterized queries using supported delimiters. This allows dynamic substitution of values in query columns.
Parameters:
Supported Delimiters: #{, ${, @{, ##, $$
No input field is required; the application automatically recognizes supported formats.
Crawling & Profiling
The Crawling & Profiling settings allow administrators to configure how OvalEdge interacts with data sources during metadata extraction (crawling) and data analysis (profiling). These settings govern aspects such as data volume limits, connector-specific behaviors, time-based execution, and performance optimization.
Example:
Profiling.configurations: Enables profiling configurations specific to Salesforce data sources.
Parameters:
The default value is Empty
By default, profiles 25,000 rows.
File Manager
The File Manager System Settings provide administrators with controls over file uploads, browsing, and ovalsight analysis. These configurations influence how users interact with file-based data sources, ensuring scalability, security, and optimized access to file metadata.
Example:
ovaledge.fileupload.maxfiles: Specify the maximum number of files that can be uploaded to the OvalEdge application at once.
Parameters:
The default value is 10.
Enter the desired number of files in the field provided.
Data Access Management
The Data Access Management System Settings enable administrators to configure how users interact with the Access Cart. These configurations determine which type of data objects can be requested, how many can be added to the cart, and whether only certified data objects can be added, etc. This section is essential for managing secure, scalable, and governed access to data assets.
Example:
enable.access.cart: Enable or disable the Access Cart functionality in the application.
Parameters:
The default value is False.
If set to True, the Access Cart functionality is enabled in the application.
If set to False, the Access Cart functionality is disabled in the application.
Metadata Governance
The Metadata Governance System Settings provide administrators with control over data story limits, entity relationship visualizations, foreign key relationship calculations, and user interface behavior for metadata components. These configurations help enforce metadata consistency, control data volume for visualization, and optimize metadata relationship identification.
Example:
max.characters.count.for.data.story: Define the maximum character count allowed for a Data Story.
Parameters:
The default value is 100000.
Enter a value between 255 and 100000 in the field provided to enforce a character limit on Data Stories.
Others
Other settings allow administrators to customize specific parameters that control the behavior of the application. They can enable, disable, or change default values, which can impact how the application works with other systems, looks, and performs tasks. It's crucial to carefully adjust these settings to ensure the application functions correctly and meets its intended use requirements.
Example:
pagination.row.limit: Specify the maximum number of records to display per page in the application interface.
Parameters:
The default value is 50.
Enter the desired number of records in the field provided.
Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA USA
Last updated
Was this helpful?