Understanding System Settings
The System Settings allows OE_ADMIN to configure parameters that govern how the application behaves using configurations, ranging from its interaction with other systems to its visual appearance and task execution. These configurations ensure the proper functioning of the application, aligning it with the unique requirements of its users.
The versatility of System Settings is evident in its ability to customize different aspects of various modules within the application. Whether it's the Data Catalog, Business Glossary, Data Quality, Service Desk, or managing Users & Roles, administrators have the flexibility to enable, disable, or modify default values, influencing how each module operates.
|
Note: Careful consideration of these settings is important to guarantee optimal performance and seamless integration with other systems. |
Accessing System Settings
Administrators can access the System Settings within the Administration module of the application. Upon entering the System Settings section, administrators have visibility into a comprehensive list of configurations across multiple tabs in the form of a List View.
List View
The configurations in System Settings are listed in a List View across different tabs of Configuration Groups. The List View provides basic information on each configuration.
|
Field Name |
Description |
|
Configuration Type |
The Configuration Type shows that the configuration is a part of the OvalEdge application. |
|
Key |
Denotes the name or identifier necessary for configuring the system setting. |
|
Value |
The default value is generally for every system setting Key. The value can be a specific numeric or alphanumeric value or set as either true or false, depending on the requirements. |
|
Description |
Brief description outlining the purpose or function of the configuration. |
|
Last Updated By |
Displays the username of the person who made the most recent update to the system setting. |
|
Updated On |
Displays a Timestamp indicating when the last modification to the system setting was made. |
|
History |
Displays the chronological changes and modifications made to the system setting, providing a comprehensive overview of its evolution over time. |
Add Custom Configuration
Organizations can use this option to add custom configurations if the corresponding backend modifications have been implemented by the Technical Team. By utilizing the '+' icon situated in the top right corner of the System Settings, administrators can perform this task. Upon selecting the icon, a pop-up window appears, prompting administrators to provide the following details: Type, Key, Value, Description and Configuration Group. Upon selecting the 'Save' button, the custom configuration will be included in the respective System Setting tab.
Configuration Groups
System Settings are organized based on specific features and conveniently displayed as tabs on the main page for enhanced discoverability. This enables administrators to effortlessly navigate between tabs, simplifying the exploration of various configuration groups.
System Path
System Path Settings are vital for the proper functioning of an OvalEdge application, as they ensure that the application has access to essential resources, links, and tools required for its 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.
|
Key |
Description |
|
ovaledge.base.url |
Specify the OvalEdge application base URL, which helps in hyperlink navigation within the OvalEdge. Parameters:
|
|
ovaledge.license.agreement.link |
Specify the OvalEdge License Agreement link for users reference. Parameters:
|
|
ovaledge.temppath |
To provide the temporary server folder path to store the copy of all the downloaded files. Parameters:
|
|
rpttoxml.executable.path |
Set up an executable tool path to convert the rpt file to XML file format. Parameters:
|
Note: JDBC makes it possible to establish a connection with a data source, send queries, update statements, and process the results.
User & Roles
Users and Roles settings are essential for establishing user access, defining roles and privileges, and ensuring secure administration and effective task management within the OvalEdge application. Notably, critical administrative roles specific to individual modules, such as the Tags Role for managing tags, Project Owner Role for overseeing projects, Connector Creator, and others, can be precisely configured in this section.
|
Key |
Description |
|
ovaledge.admin.principle |
Configure the OvalEdge application default administrator user Id. Restart of the application is required. Parameters:
|
|
ovaledge.admin.credential |
Set the password for the default administrator configured in ovaledge.admin.principle Parameters:
|
|
ovaledge.login.application |
Set up the Self Registration process to allow new users to access or log in to the application site. Parameters:
|
|
ovaledge.role.admin |
Assign admin-level privileges to a Role. Restart of the application is required. Parameters:
|
|
ovaledge.tag.role |
Configure a role to create/manage/delete Tags. Parameters:
|
|
ovaledge.role.public |
Define a default role for the first-time users logging into the application. Parameters:
|
|
ovaledge.connector.creator |
Assign connector creator privileges to a Role. The users associated with the role can establish a connection. Parameters:
|
|
ovaledge.api.role |
Configure a role to execute OvalEdge APIs. Parameters:
|
|
ovaledge.jobs.view.role |
Configure a role to view the job logs. Parameters:
|
|
remote.user.password |
Assign default password to all the Remote users fetched to the OvalEdge application. Parameters:
|
|
ovaledge.username.pattern |
Configure to display the User Id in the format as specified. Username patterns (firstname lastname / lastname firstname). Parameters:
|
|
ovaledge.rdam.userrole |
Assign a default Business Role to the users created in Data Access Management. Parameters:
|
|
ovaledge.domain.creator |
Assign domain creator privileges to a Role. Parameters:
|
|
oe.user&role.admin |
Assign the 'User and Role Creator' privileges to Roles. Parameters:
|
|
project.task.assignee.change |
Configure to add a role as a task assignee who can reassign tasks to project members. Parameters:
|
project.task.object.assignee.permissions |
To check the access permissions a user has on data objects before assigning a task to any member. Parameters:
|
|
project.task.object.visiblity.with.security |
To control the visibility of tasks in the board and list view of a project based on security permission settings Parameters:
|
|
role.project.admin |
Assign 'Project admin' privileges to Roles. Parameters:
|
Lineage
The Lineage Settings in OvalEdge encompass a range of configurations to manage the generation of data lineage diagrams. Each setting serves a specific purpose to tailor data lineage tracking and visualization. Here is the context and purpose of these settings:
|
Key |
Description |
|
shallow.lineage.connection.ids |
Configure to build shallow lineage on selective connectors. Parameters:
|
|
lineage.selfbuild |
Configure to build self-lineage for a table to capture its own data flow by creating replica tables (temp tables). For Example: If self-lineage is built on "customer.enrollment" table, then the temp tables are created for the selected table where the temp tables are denoted as self, followed by the iteration count of the table. like "customer.enrollment_self1", customer.enrollment_self2, customer.enrollment_self3. Parameters:
|
|
lineage.width.nodes |
Set the maximum number of lineage levels to be displayed in the lineage diagram. The configuration applies to both the source and destination objects flowing from left to right or right to left in the lineage. Parameters:
|
|
lineage.height.nodes |
Set the maximum number of nodes to be displayed in the lineage from top to bottom. Each node represents a corresponding object in a data source. The lineage graph becomes too large to display if lineage of all columns in a table is to be shown in one graph. The first level of lineage is exempted from this configuration, and it can show all the nodes present in the lineage. Parameters:
|
|
lineage.debugmode |
Configure debug logs to understand the reason for creating temp tables while building the lineage. The debug logs are captured and saved into the templineagedataset table. Parameters:
|
|
lineage.pick.anytable |
Enable picking a table by its name (first identified) from any connection or schema to build lineage. Parameters:
|
|
connections.order.lineage |
Configure the connection order, which allows the system to pick tables based on the priority set while building lineage. Parameters:
|
|
need.hard.coded.values.in.lineage |
Configure to build lineage on data fields like fixed values or hard-coded values. Parameters:
|
|
process.function.related.lineage |
Configure to process lineage on user-defined functions included in query objects such as Procedures/ Triggers/ Functions. Parameters:
|
|
lineage.report.column.reference |
Enable/disable intermediate objects (datasets) to display in the column lineage between the Report and the source objects. Parameters:
|
|
oe.temp.object.hide |
Configure to show/hide the Temp tables in data catalog. Parameters:
|
|
versioning.for.lineage.connection |
Configure to enable lineage versioning that gives you the ability to store the lineage history of datasets under the configured connections. Currently, it is supported for RDBMS. Parameters:
|
|
informatica.query.dialect |
Configure to parse the Informatica Lineage queries, if any are present in the source code. Example: MySQL, Oracle, PostgreSQL, Microsoft SQL Server etc. Parameters:
|
|
lineage.node.height |
Define the maximum number of source or destination data objects a single node shall display. Too many nodes in the graph make it difficult to track the data flow. Parameters:
|
|
dremio.build.lineage.with.external.sources |
Configure to initiate lineage between actual source tables and dremio (data lake). Parameters:
|
|
is.ovaledge.lab |
Configure to export the failed or parsed queries to the OE Team for validation in zip file format (secured). Parameters:
|
|
ovaledge.lineage.maxquerylines |
Define the maximum number of lines of the query (query rows) to be allowed to process at the time of building lineage. Queries within the specified query row limit are processed and queries exceeding the limit are skipped. Parameters:
|
informatica.param.file.type |
Configure the types of files that are supported to crawl the Informatica connector and allow Lineage Building. File extension values could be like param,txt etc. Parameters: The default value is set to |
|
is.correctquery.required |
Show/hide the correct query screen in Auto Build Lineage Correct Query column in the grid. Parameters:
|
|
lineage.icons.swap |
Configure to display either the object icon and the connector logo in larger size for the nodes in the lineage. Parameters:
|
|
lineage.icons.outer.size |
Configure the diameter of the outer nodes (object icon or connector logo). Parameters:
|
|
lineage.icons.inner.size |
Configure the diameter of the inner nodes (object icon or connector logo). Parameters:
|
|
lineage.icons.inner.position |
Configure to change the position of the external circle of the node to the top or bottom. Parameters:
|
|
Lineage.creation.increase.object importance |
Include/exclude the downstream objects to compute Importance score. Parameters:
|
|
ovaledge.linege.intelligence |
This Configuration is developed for internal purposes. To show/hide the 'Lineage Intelligence' module in Advanced Tools. Parameters:
|
|
adl.supporting.dialects |
It is specific for the Deltalake connector to support different dialects (hive) for building lineage. Parameters:
|
|
lineage.handle.temptable.prefix |
This setting is utilized for managing the creation of temporary tables by adding a unique query name as a suffix for easy identification. Parameters:
|
|
lineage.temptable.prefix.value |
This setting is utilized for managing the creation of temporary tables by adding a unique query name as a suffix for easy identification. Parameters:
|
Notifications
Notifications settings allow users to use SMTP to send notifications via email using different communication mediums including Inbox, Email, Slack, MS Teams, and Google Chat. Users can configure SMTP settings to specify the SMTP server, and port, along with the sender's email address credentials, and configure MS Team, Google Chat, and Slack.
Notification Templates
Administrators can customize Notification Templates to personalize the notifications sent to users. These notification messages can be customized for Inbox, Email, and Slack, MS Teams, and Google Chat. Additionally, the messages can be altered by implementing various variables that correspond to specific events or features. To insert these variables into the message body, administrators can use drag-and-drop functionality.
|
Key |
Description |
|
ovaledge.smtp.server |
Specify the SMTP server URL to send and receive mail messages. Example: google.smtp2go.com Parameters:
|
|
ovaledge.smtp.port |
Specify the SMTP Port number to connect to an SMTP server. For example, Port 25 is a standard SMTP port used for moving messages between mail servers. Parameters:
|
|
ovaledge.smtp.mode |
SMTP can be secured through the enablement of TLS/SSL on your mail server. By enabling TLS/SSL, the SMTP protocol is encrypted on the transport layer by wrapping the SMTP inside of a TLS connection. This effectively secures SMTP and transforms it into SMTPS. Parameters:
|
|
ovaledge.email.username |
Specify the email id for SMTP. Parameters:
|
|
ovaledge.email.password |
Specify the password for SMTP. Parameters:
|
|
ovaledge.email.fromEmail |
Enter the From-email address to send emails from the OvalEdge application to the recipients. Example: notify@ovaledge.com Parameters:
|
|
license.expiry.emails |
Configure to add the email address of the users to send email notifications and notify users when their licenses are due to expire. Parameters:
|
|
slack.app.oauth.token |
Enter the OAuth token to integrate Slack into OvalEdge. Parameters:
|
ovaledge.aws.ses.configset |
To set up a configuration set for Amazon SES (Simple Email Service), which is essentially a named collection of rules and settings used for managing the emails Parameters:
|
|
smtp.oauth2.tenantid |
Enter Client ID for OAuth Token Validation and SMTP Server Authentication. Parameters:
|
|
smtp.oauth2.clientid |
Enter Client ID for OAuth Token Validation and SMTP Server Authentication. Parameters:
|
|
smtp.oauth2.clientsecret |
Enter Client Secret for OAuth Token Validation and SMTP Server Authentication |
|
smtp.oauth2.cloud.name |
Enter Cloud Name for OAuth Token Validation and SMTP Server Authentication. Parameters:
|
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.
|
Key |
Description |
|
saml.role.prefix |
Remove role prefixes defined in SAML that match with 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:
|
|
ovaledge.extauth.authtype |
Set up roles either configured in SAML or OE application. Parameters:
|
|
ldap.allow.Emptyemail |
Set up dummy email IDs for LDAP service accounts that don't have email addresses; Email address is a mandatory field for creating users in OvalEdge. Parameters:
|
|
saml.role.suffix |
Remove role suffixes defined in SAML that match with OvalEdge roles. For Example, if OE_Admin_GLOSKY, OE_Public_GLOSKY_are the roles defined in the SAML instance. Using this configuration, the suffixes _GLOSKY can be removed, and the roles OE_Admin and OE_Public that match with OvalEdge are retrieved. Parameters:
|
|
oeapp.sso.connectorid |
Specify the Connector ID of the SSO connection to sync the SSO platform with OvalEdge. Currently supports OKTA. Parameters:
|
hide.saml.login |
It allows you to choose whether to display the SAML login page with the IDP link or the standard sign-in page when users log-in or log out. Parameters:
|
Proxy
Proxy settings are configured to enable OvalEdge to route its network requests and web service access through a proxy server, enhancing security, privacy, and network performance.
|
Key |
Description |
|
proxy.host |
Specify the IP address of the Proxy. Parameters:
|
|
proxy.port |
Specify the port number of the Proxy. Parameters:
|
|
proxy.protocol |
Specify the protocol of the proxy server, whether http or https. Parameters:
|
|
proxy.username |
Specify the username associated with a proxy server. The purpose is to provide the necessary credentials for authenticating and connecting to the proxy server when making network requests or accessing web services through a proxy. Parameters:
|
|
proxy.password |
To specify the password associated with the proxy server username. Parameters:
|
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, OvalEdge performs an automatic archival of all tables every day at 2:00 AM. 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
To ensure the seamless integration of Splunk, Admins can use the "Test Connection" feature. By clicking on this option, Admins can verify the successful completion of key and value configurations. This step serves as 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 within OvalEdge, providing Admins with a robust solution for log management and analysis.
|
Key |
Description |
|
splunk.tcp_udp.host |
Specify the URL of the Splunk TCP events. (eg: http://splunk.dns.com:9999) Parameters:
|
|
splunk.hec.host |
Specify the URL of the Splunk -HEC. (eg: http://splunk.dns.com:8088) Parameters:
|
|
splunk.hec.token |
Specify the Splunk token to authenticate HEC index. This is mandatory for HEC index logs storing. Parameters:
|
|
splunk.index |
Specify the Splunk index which stores log messages from the HEC (http event collector). Parameters:
|
File Scanner
The File Scanner functionality in OvalEdge 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 OvalEdge's "Upload File or Folder" Advanced Tool.
To ensure the efficacy of the File Scanner, users can utilize the "Validate File Scan" button, enabling them to manually initiate and validate the scanning process, assuring the integrity of the uploaded files within OvalEdge.
|
Key |
Description |
|
fs.system.hostname |
Specify the filescan host address. Parameters:
|
|
fs.system.username |
Specify the data filescan system username. Parameters:
|
|
fs.system.password |
Specify the data filescan system password. Parameters:
|
|
fs.filemanager.enable |
Configure to enable/disable filescan service on File Manager. Parameters:
|
|
fs.loadmetadata.enable |
Configure to enable/disable filescan service on Load Metadata for Files. Parameters:
|
Connector
The Connector tab within the System Settings consolidates all essential configurations dedicated to the connectors used in the OvalEdge Application. It includes configuring Query parameters, RDAM details, or other connector-specific settings, to ensure the smooth operation of OvalEdge's connectivity features.
|
Key |
Description |
|
connector.environment |
Specify the instance of the connector. Example: Development/Staging /Testing/Production. The naming convention of the instance is client specific. Parameters:
|
|
Tablequerylimit |
This setting allows to set the maximum number of table queries that can be fetched in from an external source when performing a crawl. This helps avoid issues with timeouts when fetching a large amount of data. Parameters:
|
|
columnquerylimit |
This setting allows to set the maximum number of column queries that can be fetched in from an external source when performing a crawl. This helps avoid issues with timeouts when fetching a large amount of data. Parameters:
|
|
rdam.query.limit |
This setting allows defining a limit on the number of rows (users and roles) to be retrieved from a remote source (RDAM) during Crawling, helping to prevent timeout problems. For instance, if there are 50,000 users in a remote location that need to be fetched, set the query limit to a specific value, like 10,000, and control the number of users and roles retrieved. Parameters:
|
rdam.addordelete |
To determine how changes in role permissions from a remote source (RDAM) are managed.e, this setting lets you decide whether to manually review and approve permission updates or have them automatically synchronized when changes occur during later crawls. Parameters:
|
|
microstrategy.custom.fields |
To activate or deactivate the custom fields Owner name and Report created date for the Microstrategy connector. When set to Empty they are enabled. The value can be either Empty or Empty.
|
AI
The AI tab of System Settings is dedicated to configuring parameters associated with the AI Recommendations functionality which recommends business glossary erms to unclassified data objects within the Data Classification and Business Glossary modules of OvalEdge. These settings are instrumental in adjusting the smart score to suggest terms for unclassified data objects, establishing thresholds for recommendations, thereby enhancing data object and term relevance recommendations.
|
Key |
Description |
|
ai.match.score |
Define a threshold Smart Score value to display AI Recommendations for the objects that are greater than equal to the Smartscore value entered. Parameters: The default value is 10. Enter any threshold value. |
|
aiterm.maxcolumns |
Specify the maximum number of table columns on which AI Recommendations are run. Parameters:
|
|
ai.recommendation.weightage |
Configure the Name, Data, and Pattern weightage ratio of the Smart Score (nearest match to 100). Example: Name (30):Data (30): Pattern(40). Parameters:
|
|
ai.pattern.match |
This setting enables the consideration of pattern match scores in the calculation of the Smart Score for AI recommendations. Parameters:
|
|
ai.recom.jobrun.rejectednames.delimiter |
Configure the delimiter to separate multiple included/excluded Database names in the Run AI Recommendations pop-up before running AI Recommendation Job Parameters:
|
ai.recom.boost.termmatchescol |
Configure the value to boost or add up the value to the Smart Score if the column name matches the term name for AI Recommendations. Parameters:
|
|
ai.recom.boost.multiplerepeatedcol |
Configure the value to boost up or add up the value to the Smart Score if multiple repeated columns are present on associated data objects. Parameters:
|
|
ai.recom.rejectedscore.weightagepercent |
Configure the rejected score weightage percentage for AI recommendations. The rejected score weightage percentage is a parameter used in AI recommendation systems to control the impact of user feedback on the overall recommendation algorithm. Specifically, it determines how much the smart score of a data object should be influenced if a recommended term is rejected by the user. Parameters:
|
ai.associate.object.threshold.score |
Configure the value of the threshold score to directly associate a term with a data object without having to manually Accept/Reject a Term recommendation on a data object. Parameters:
Best Practices: Set the threshold score to a value that is higher than the AI match score for all recommended data objects, but still low enough to capture a meaningful number of relevant recommendations. This value should be a positive integer, and greater than the AI match score. |
Global Search
The Global Search settings allow administrators to configure the behavior and display of the global search functionality. These settings empower users to tailor their search experience, control the visibility of certain features, and fine-tune the search parameters according to their specific requirements.
|
Key |
Description |
|
globalsearch.objectscore.display |
Show/hide the relevance score for data objects in the Global Search results. Parameters: The default value is False. If set to true, the relevance score is displayed in search results. If set to false, the relevance score will not be displayed. |
|
globalsearch.objectscore.display |
Show/hide the different objects tabs (Tables/Files/Reports/Business Glossary) in the Global search page. Parameters: The default value is set to "ALL,glossary,oetable,oetag,oeschema,oecolumn,oefile,oefilecolumn,oechart,chartchild,oestory,oequery,project'. Enter the selected object names in the field provided. If Left blank then only the All tab is displayed. |
|
globalsearch.es.pagination.count |
Specify the maximum number of records to be displayed on a page while running the advanced job to fetch from local db to elastic search. Supports: Min - 3000, Max - 8000) Parameters: The default value is 10000. Enter the value in the field provided. |
|
globalsearch.es.activedetails |
Show/hide the active/inactive objects in the global search results. Parameters: The default value is Active.
|
|
globalsearch.es.datamovement.display |
To enable search results for source codes (queries) in Global Search results. Parameters: The default value is set to false If set to true, the search results for codes are displayed. If set to False, the search results are not displayed for codes. |
|
elastic.search.highlight.fragments |
Configure the number of highlighted values shown in the search results for a search keyword entered. Parameters: The default value is 15. Enter any value in the field provided. |
|
oe.globalsearch.searchorder |
Control the display of tabs in the Global Search by enabling or disabling them. This applies to both the tabs across the top of the page and the filter left panel. Parameters: Enter the tab names in the field provided. All-ALL, Databases - schema, Tables - oetable, Tags - oetag, Table Columns - one column, Files - oefile, File Columns - oefilecolumn, Reports - oechart, Report Columns - chartchild, Codes - oequery, Business Glossary - glossary, Data Stories - oestory, Projects - project, Service Requests - servicedesk |
|
globalsearch.fulltext.search |
To search for full-text information with or without highlights based on the configured character size. Parameters: If set to True, the full-text search will be performed without highlights. If set to False, the search will consider a character length of 50,000. It will perform the search using highlights for the initial portion of the text and display the search results with highlights. The remaining portion of the text, it will display the search results without highlights. |
|
globalsearch.max.analyzed.offset |
To configure the maximum limit for the preferred value for highlights. Adjusting this value allows users to control the extent of text that can be visually emphasized for easier identification or reference. Parameters: The default setting is 200,000 characters. Enter the desired value in the field provided. |
|
globalsearch.score.use.synonym |
Configure the Synonym (Configure Search Keyword) 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). Parameters: If set to True, the search results calculation includes the Synonym score. If set to False, the search results calculation excludes the Synonym score. Relevance score calculation depends solely on the Elasticsearch score and the settings configured for the Popularity score. |
|
globalsearch.score.use.popularity |
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). Parameters: If set to True, the search results calculation includes the popularity score. If set to False, the search results calculation excludes the popularity score. The relevance score calculation depends solely on the Elasticsearch score and the settings configured for synonym score. |
|
globalSearch.objectMatch.weightage |
Adjust how search results are prioritized and displayed by considering matching search keywords in the names and titles of data objects. This adjustment depends on the "globalSearch.objectDescriptionsMatch.weightage" and "globalSearch.objectOtherAttributesMatch.weightage" system settings, influencing results related to descriptions and other attributes respecively. The displayed search results are determined by the greatest value among the three specified system settings. Parameters: The default weight is set at 2. Enter the value in the field provided. |
|
globalSearch.objectDescriptionsMatch.weightage |
Adjust how search results are prioritized and displayed by considering matching search keywords in the descriptions (Business, Technical and Source Descriptions) of data objects. This adjustment depends on the "globalSearch.objectMatch.weightage" and "globalSearch.objectOtherAttributesMatch.weightage" system settings, influencing results related to Names/Title and other attributes respectively. The displayed search results are determined by the greatest value among the three specified system settings. Parameters: The default weight is set at 3. Enter the value in the field provided. |
|
globalSearch.objectOtherAttributesMatch.weightage |
Adjust how search results are prioritized and displayed by considering other attributes of data objects (Tags, Terms, Custom Fields, etc). This adjustment depends on the "globalSearch.objectMatch.weightage" and "globalSearch.objectOtherAttributesMatch.weightage" system settings, influencing results related to Names/Title and other attributes respectively. The displayed search results are determined by the greatest value among the three specified system settings. Parameters: The default weight is set at 3. Enter the value in the field provided. |
Data Quality
The DQR System Settings tab enables users to configure and customize various parameters related to Data Quality Rules (DQRs) within the OvalEdge application. 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.
|
Key |
Description |
|
ovaledge.dqrule.bg.enforcement |
Configure to execute Data Quality Rules only when the Term is applied. Parameters: The default value is False. If set to True, then a term should be associated with the object to execute the Data Quality rule. If set to False, then a term is not needed to execute the Data Quality Rule. |
ovaledge.dqr.topvalue.separator |
Define a separator to give a set of input fields for the Top Value function>Values field. For Example If / (slash) is used as a separator, then the input values can be separated as red/yellow/blue. Parameters: The default value is comma (,). Enter the value in the field provided. |
|
dqr.databricks |
To process Data Quality Rules for Databricks connection Parameters: The default value is empty. If set to Yes, the DQR is processed for Databricks connection. If set to No, the DQR is not processed for Databricks connection |
dq.dqprinciple.visible |
To show/hide “DQ Principle” column in the Results tab of Custom SQL functions showcasing the entered principle value from the stats query. Parameters: If set to true, the DQ Principle column will be made visible. If set to False, the DQ Principle column will be hidden. |
|
enable.dq.policy |
Show/hide the Data Quality Policies sub-module in the application menu under the Governance Catalog module in Data Quality. Parameters: If set to True, the Data Quality Policies sub-module is displayed in the application menu. If set to False, the Data Quality policies module is hidden. |
overwrite.crawl.additionalinformation |
To overwrite the additional information of an object while crawling. Parameters: The default value is False. If set to True, the overwriting of additional information is enabled. If set to False, the overwriting of additional information is disabled. |
data.quality.provider.type |
To switch the DQR calculation between Internal (OvalEdge) and External (connector) modes. Parameters: The default value is set to internal. If the configuration is set to Internal, then the DQR (Data Quality Rules) performed in the OvalEdge application is displayed in the dashboard under the Data Quality section. If the setting is set to External, then the scores are calculated based on the external connector inputs. |
|
dashboard.dqsb.mode |
To set the DQR mode to DQSB or ALL. Parameters: The default value is ALL. Enter ALL or DQSB in the field provided. |
loadmetadata.dqr.update.dataset |
Configure to enable or disable editing of queries that have been added to the application using Load Metadata from Files. Parameters: The default value is False. If set to True, users can edit the queries that were loaded into the application using Load Metadata from Files. If set to False, users will not be able to edit the queries loaded into the application using Loading Metadata from Files. |
|
dataquality.associatedobjects.additionalcolumns |
To set a limit on the number of parameters that can be configured within Additional Column details for the Data Quality Center. For instance, when set to a value such as 10, it enforces a maximum limit of 10 parameters that can be configured for the additional columns. Parameters: Enter the value in the field provided. The Maximum limit is 20. |
dq.dashboard.dqrscore.weightage |
Configure the weightage of the Data Quality Rule score to calculate the data quality score on data objects. Note: Data Quality Score is the weighted average of three parameters:Data Quality Rule Score, Service Request Score, and Child Score. The total weightage of all three parameters should add up to 100%. Parameters: The default value is set to 50. Enter the ratio percentage in the field provided. |
|
dq.dashboard.srscore.weightage |
Configure the weightage of the Data Quality Rule score to calculate the data quality score on data objects. Note: Data Quality Score is the weighted average of three parameters:Data Quality Rule Score, Service Request Score, and Child Score. The total weightage of all three parameters should add up to 100%. Parameters:
|
|
dq.dashboard.childscore.weightage |
Configure the weightage for the service request score to calculate the data quality score on data objects. Note: Data Quality Score is the weighted average of three parameters: Data Quality Rule Score, Service Request Score, and Child Score. The total weightage of all three parameters should add up to 100%. Parameters: The default value is set to 25. Enter the ratio percentage in the field provided. |
anomaly.detection.analysis.iqr.range |
To set the the threshold percentage of data change (positive or negative), if exceeded, will trigger an anomaly. Parameters: Enter the range in the field provided. |
anomaly.detection.analysis.deviation.threshold |
This value represent threshold percent above or below which anomaly will be generated for rate of change in data series Parameters: Enter the value in the field provided. |
|
dataquality.associatedobjects.max.limit |
Set the maximum number of data objects that can be associated with a DQ Rule. Parameters: The default value is set to 1000. |
|
dataquality.controlcenter.failedrecords.max.limit |
Configure the maximum number of failed results of the DQR (Data Quality Rule) to be displayed in the Control Center Tab. Parameters: The default value is set to 50. Enter the value in the field provided to configure the new maximum limit. |
dq.object.filter.maxlength |
To configure the maximum allowable length for text filters: Parameters: The default is set to 500. Enter the value in the field provided. |
anomaly.detection.analysis.algorithm.selection |
Represents the default algorithm which would be used for Anomaly Detection Parameters: Enter the algorithm that should be considered to identify anomalies. |
anomaly.detection.analysis.algorithm.list |
To configure anomaly detection analysis algorithms. Parameters: Enter the names of the algorithms separated by commas. Currently, we support the 'iqr' and 'deviation' algorithms" |
anomaly.detection.analysis.enabled |
To activate or deactivate the anomaly feature within the application. Parameters: If set to "True", the anomaly feature gets activated allowing it to function as intended If set to "false", the anomaly feature gets deactivated and the connector and data object level anomaly-related settings will appear grayed out. |
|
dataquality.score.optimal.score |
This is a score which is used as a thresold in DQ Speedometer chart Value should be in between 0 and 100 Optimal Score(dataquality.score.optimal.score) should be always greater than or equal to Acceptance score(dataquality.score.accepted.score). |
|
dataquality.score.acceptance.score |
This is a score which is used as a thresold in DQ Speedometer chart Value should be in between 0 and 100 Optimal Score(dataquality.score.optimal.score) should be always greater than or equal to Acceptance score(dataquality.score.accepted.score). |
Dimensions
The Dimensions section in Data Quality serves as a centralized repository, showcasing predefined Data Quality Dimensions like completeness, uniqueness, accuracy, consistency, validity, etc. Additionally, it provides the flexibility to create custom dimensions through a plus icon at the top right.
Administrators can input the name and description for these new dimensions, facilitating the customization of the Data Quality framework to align with specific organizational needs. Furthermore, the tab allows for the modification of descriptions for dimensions already included in the system-defined set, offering a comprehensive tool for managing and adapting Data Quality dimensions.
Service Desk
The Service Desk tab in System Settings allows administrators to tailor service desk related settings functions as an important control center, providing administrators to configure Service Desk functionalities based on the specific requirements of the organization. allows for the customization of external service request templates, approval workflows, field limits, and business operation hours, offering comprehensive control over Service Desk configurations for effective and efficient service management.
|
Key |
Description |
|
servicedesk.custom.templateid |
To set Axiomatic external service request template id. Parameters: The default value is set to 1035. Enter the template id in the field provided. |
|
approvalflow.admin.supersede |
The system setting determines whether admin users can approve or reject service requests regardless of their presence in the configured approval workflow. Parameters: If set to false, only the configured approver designated in the approval workflow can approve or reject the service request. If Set to True, in addition to the configured approver, admin users can exercise approval authority, even if they are not part of the configured workflow, admin users can exercise approval authority. |
|
servicedesk.system.template.edit.enable |
Configure to edit the system-defined templates for the External service request type. Parameters: The default value is False. If set to True, the system-defined External service request |
|
servicedesk.template.fields.limit |
Specify the maximum number of fields that a service desk template can have. Parameters: The default value is 20. Maximum value is 50. Enter the value in the field provided. |
|
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. |
|
servicedesk.approvalworkflow.team.role.limit |
Specify the maximum number of users in the team/role to approve the request if all users. Parameters: The default value is 5. Maximum value is 20. Enter the value in the field provided. |
|
servicedesk.request.bulk.approval.limit |
Specify the maximum number of requests to be approved in bulk from the Service Desk page. Parameters: The default value is 50. Maximum value is 100. Enter the value in the field provided |
|
servicedesk.business.hours |
Specify the Business hours of operation in a day(24hr format) for SLA Calculation. Parameters: Value can be entered within the range of 00:00 - 23:59. |
|
servicedesk.business.days |
Specify the days that are considered as Business Days in a week. This will be used for SLA calculation. Parameters: Value that can be entered are - Mon (Monday), Tue (Tuesday), Wed (Wednesday), Thu (Thursday), Fri (Friday), Sat (Saturday), Sun (Sunday). |
|
servicedesk.holiday.days |
Specify Holiday dates, which will not be considered for SLA calculation. Parameters: Enter dates in dd-mm-yyyy format. The chosen days will not be considered for SLA calculation. |
Others
The Others tab encompasses a diverse list of configurations, each specifically designed to cater to unique use cases and functionalities within OvalEdge. This section offers administrators a versatile toolkit that can be tailored to address their distinct requirements.
Notably, all other modules, including Data Catalog, Business Glossary, Projects, File Manager and Jobs, consolidate their configurations within this tab. Administrators can leverage the Others tab to navigate through module-specific configurations, ensuring a cohesive and efficient approach to customizing OvalEdge based on their organizational nuances.
|
Key |
Description |
|
ovaledge.running.jobs.count |
Specify the maximum number of concurrent jobs that should run at a time in the application. Parameters:
|
|
ovaledge.locale |
Configure the language of the application. OvalEdge supports multiple languages that include Chinese, French, Russian, and English. Parameters:
|
|
ovaledge.log.level |
Configure the Root Log Level to identify the root cause of the issues from the application log files (ovaledge.log). Allowed values - DEBUG, ERROR, WARN, TRACE. Parameters:
|
|
ovaledge.term.policy |
Specify the maximum number of approvers (excluding the admin user) to approve recommendations on a Term. Parameters:
|
|
ovaledge.file size.limit |
Set the maximum file upload size to prevent users from uploading large files to OvalEdge. Parameters:
|
|
pagination.row.limit |
Specify the maximum number of records to be displayed in a page. Parameters:
|
|
nosql.rowcount |
Configure the maximum number of rows to crawl and fetch NoSQL column details from Data (JSON) format. It is for NoSQL Connectors (AWS DyanomoDB, MongoDB, etc). Parameters:
|
|
file.skipfullprofile |
Configure to skip profiling on parquet File types for HDFS. Parameters:
|
|
ovaledge.qlik.iframe |
Show/hide qlik charts in the Data Catalog > Reports presentation. Parameters:
|
ovaledge.fileupload.maxfiles |
Specify the maximum number of files that can be uploaded to the OvalEdge Application. Parameters:
|
|
ordertyperetrieve.default.classification |
To view data object columns for specified Term- Classification. Parameters:
|
|
alternate.file.ext.types |
It helps to read TXT files using CSV file format as an alternative. Parameters:
|
|
ovaledge.session.timeout |
Specify the time (in seconds) a user can remain idle before the session is terminated. Restart is required. Parameters:
|
|
jwt.bearer Token.expiry Time |
Set the expiry time of the bearer token in milliseconds for using JWT authentication for API. Parameters:
|
|
querysheet.row.limit |
Set the maximum number of records to download from Query Sheet Results. Parameters:
|
|
bg.unique.constraint |
Show/hide qlik charts in the Data Catalog > Reports presentation. Parameters:
|
|
reports.crawl.starttime |
Define a Start time to trigger crawling (Server Time Zone). Parameters:
|
|
reports.crawl.endtime |
Define an End time for crawling (Server Time Zone). Parameters:
|
|
application.defaulttheme |
It allows you to customize the global color palette of the application. Parameters:
|
|
ovaledge.skip.instances |
It helps to skip jobs running on unwanted instances. Parameters:
|
|
navigator.row.limit |
Specify the maximum number of rows to be fetched from the Cloudera Navigator Connector. Parameters:
|
|
aj.fileconn.id |
Specify the NFS Connection Id to fetch the files from the File Path defined for the connection. Parameters:
|
|
config.file.types.to.be.cataloged |
Specify the file type format to upload and catalog files from external sources. Parameters:
|
|
exclude.datacatalog.subreport |
Enable/disable the Sub Reports to display in the UI. (Data Catalog > Reports ) Parameters:
|
|
disable.sourcecode.search |
Enable/disable the Source Code search in Global Search. Parameters:
|
|
temporary.object.identification.pattern |
Specify the different patterns to identify internal staging temporary tables in queries. Tables matching this pattern will be prefixed with "Query Name_" to get "Query Name"_Table Name. Parameters:
|
|
bg.showallcf |
To display all the custom fields in the Business Glossary,> View > as separate columns. It is applicable only when the Global custom field definition is defined. Parameters:
|
|
oe.object.search.count |
To specify the number of records to appear on a single page for Jobs. Parameters:
|
|
oe.impact.tr.column.hide |
Hide/Show the T/R Code and T/R Type columns from Impact Analysis. Parameters:
|
|
ovaledge.enable.log4j |
Configure to capture all the job execution logs in the application. Parameters:
|
|
ovaledge.branding.logo |
To upload the brand logo. The standard size of an image is 130 x 26 px. Maximum image size 2 Mb. Supports: jpeg/png file formats. Parameters:
|
|
profiling.configurations |
Configure to enable profiling (in memory and mysql) for Salesforce. Parameters:
|
download.row.limit |
Define the maximum number of rows to be downloaded on a page. (Value should be equal or above 500) Parameters:
|
|
page.refresh.time |
Set the time interval (in seconds) to auto-refresh your pages or tabs. Parameters:
|
|
is.raci.enabled |
Enable/disable RACI functionality to display Responsible/Accountable/Consulted/Informed user in the Business Glossary. Parameters:
|
|
sql server.profile.nolock |
It allows enabling or disabling the NOLOCK while profiling the data objects. Parameters:
|
|
object.terms.maxcount |
Configure the maximum number of auxiliary terms that can be applied to a data object. Parameters:
|
|
aj.fileupload.path |
Specify the file folder or bucket path to upload the backup files from the Data Retention framework. The file path is set for the Connection Id defined in the configuration > Key > aj.fileconn.id. Parameters:
|
|
exclude.report.type |
Configure the Report type to be excluded from the Data Catalog > Reports tab. Parameters:
|
|
enable.file.compare |
Enable/disable the File Compare module in the Advanced Tools. Parameters:
|
|
ovaledge.metric.consumer |
Configure (Prometheus or cloudwatch) to capture performance metrics and monitor the performance of the application. Parameters:
|
|
aws.cloudwatch.region |
Configure the location of the cloudwatch to capture OE Metrics. Parameters:
|
|
aws.cloudwatch.rolearn |
Add ARN Roles from aws to connect to cloud. Parameters:
|
|
ovaledge.sampleprofile.maxcharlength |
Define the maximum character length of the data to be displayed for profiling sample data objects. Parameters:
|
|
use.synonym.without.coninfo |
To pick synonyms without considering connection Id. Parameters:
|
|
rpt.file.size |
Define the maximum size of the RPT file to process files into the OvalEdge application. Parameters:
|
|
max.project.objects.size |
Define the maximum number of data objects that can be added to a single project. Parameters:
|
|
is.erd.advancedsettings.enabled |
To enable/disable Advanced options in Entity Relationships. Parameters:
|
|
last.recent.passwords.count |
To enforce the requirement that a user changing the password be prohibited from using recently used passwords when resetting the password through the self-service password reset form. For Example: If the configuration is set with a default value of 3 and the user resetting the password has already used password@1, password@123, and password@345, then the system prohibits the user from using passwords password@1, password@123, and password@345 while resetting the new password. Parameters:
|
|
ovaledge.governancerolesupdate.isEmpty |
Show/hide the radio button "Cascade when Empty" in the Update Governance Roles Pop-up window. Parameters:
|
|
query sheet.columns.parameterization |
To create Param Queries which helps to edit the column details of the query. Use special characters such as # or $ or ##, $$ to rename the Param columns in the queries. Parameters:
|
|
ovaledge.chart.treeview |
Enable/disable tree view for tableaus to show workbooks, dashboards, or views. Parameters:
|
|
databricks.encrypt.udf |
Define the encrypt UDF name to hide data lake table column data. Parameters:
|
|
databricks.decrypt.udf |
Define the decrypt UDF name for data lake table column data. Parameters:
|
|
oe.internal.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:
|
|
enable.db.performance.metrics |
To capture performance metrics to monitor the performance of the system. Parameters:
|
|
oe.internal.min.query.execution time |
Set a minimum time a query should execute beyond this time, the Query is considered a slow query. This configuration works when the ' enable.db.performance.metrics' configuration is enabled. Parameters:
|
|
oe.logo.url |
Set the logo to display in the notification Email footer. Parameters:
|
|
object.count.cache.enable |
Enable/disable caching of data object counts in the application. Parameters:
|
|
object.count.cache.size |
Set the maximum number of data objects to be cached beyond which the caching is deleted. Set the 'object.count.cache.enable' configuration as True to enable this configuration. Parameters:
|
|
object.count.cache.entry.threshold time |
Define the maximum threshold value (milliseconds) after which the cache is executed. Count will be added to cache only if execution time is greater than the threshold time. Set the 'object.count.cache.enable' configuration as True to enable this configuration. Parameters:
|
|
object.count.cache.update.mode |
To enable asynchronous job to update the data objects count. Parameters:
|
|
throttle.request.limit |
Configure the time limit for executing APIs/URL per user. Parameters:
|
|
throttle.request.duration |
Configure the duration for executing APIs/URL per user. Parameters:
|
|
display.max.top users |
To specify the number of top users to be displayed in the application. Parameters:
|
|
max.cart.objects.size |
Configure the maximum number of data objects that can be added to the Access Cart. Parameters:
|
|
databricks.complete masking.udf |
It helps to mask the entire data in a column in databricks. Parameters:
|
|
databricks.lastfourcharmasking.udf |
It helps to mask the last four characters of a data in a column in databricks. Parameters:
|
|
file.dots.validation |
Configuration option that determines how file formats are handled when they are cataloged, read, or downloaded in an application. Parameters:
|
|
DataGrowth.logs.schedule.time |
Specify the scheduled time to run data growth logs. This configuration works when the ' Data Growth.logs.schedule.enable' configuration is enabled. Parameters:
|
|
Data Growth.logs.schedule.enable |
Capture /recapture the Data Growth scheduled logs that include various mariadb/Mysql variables. Parameters:
|
|
cache count.update.time limit |
Set the minimum length of time (milliseconds) to hold the data objects (current application page) in the cache. It helps to check the time constraint for updating cache object count(in seconds) Parameters:
|
|
enable.access.cart |
Enable/disable the Access cart functionality in the application. Parameters:
|
|
pagination.navigation.lastpage |
Enable/disable the last page navigation in the application, as it takes a lot of time to load all the pages. Parameters:
|
|
hide.embedded.reports |
Configure to display the embedded reports (as displayed in the third-party reporting tools) in the application. Parameters:
|
|
ovaledge.axiomatics.file.persistence |
This parameter is used for writing axiomatics payload to file. Parameters:
|
|
custom.landing.page |
Configure to display the Welcome view / Home view after logging in to the application. Parameters:
|
|
is.dateformat.yyyymmdd |
Enable/disable yyyymmdd as the standard date format across the application. Parameters:
|
|
accesscart.ignoresensitivity.colors |
It helps to configure and ignore selected color codes for api response attributes in the access cart. Parameters:
|
|
filemanager.pagination.row.limit |
Define the maximum number of records of files in the File Manager. Parameters:
|
|
ovaledge.bridge.mode |
Enable/disable bridge functionality in the application. Parameters:
|
|
ovaledge.bridgesoftware.path |
It helps DevOps to specify the path of the bridge software. Parameters:
|
|
oef.enable.siem |
Configure the format for the security information and event management logs in the application. Parameters:
|
|
oef.domain.category |
Specify the format for logs that contain personally identifiable information (PII). Parameters:
|
|
azure.ad.conn.id |
To specify the unique Azure Active Directory (Azure AD) Connection ID. This ID is utilized to retrieve information about external users when submitting a Service Request (SR). Parameters:
|
|
products.registry.url |
Configure the URL to register a new product. Parameters:
|
|
axiomatics.customername |
To specify the name of the customer who are using the app (ex : globe, Mckinsey) Parameters:
|
|
ovaledge.log4j.loglevel |
To view the specified log levels that include ERROR, WARN, INFO, DEBUG, and TRACE that are within the scope of ovaledge db to manage storage space and reduce the amount of data that needs to be processed or analyzed. Parameters:
|
|
oe.internal.slowquery.exclude.log4logs |
To capture the activity logs into the system. Parameters:
|
|
show.payload.audit |
To display the Payload Information in Axiomatics.
|
|
connector.license.groupingpolicy |
To display multiple MSAccess connectors with the same path into one group on the About OvalEdge page. Parameters:
|
|
slqerrors.capture.request |
It controls to show / view request mappings and associated parameters when an error occurs. Parameters:
|
|
sqlerrors.stacktrace.size |
This option allows developers to configure the length of the SQL error character that is stored in a log table when an error occurs. Parameters:
|
|
custom.landing.page.enable |
Enable/Disable the Welcome View / Home View toggle button. Parameters:
|
|
servicedesk.system.template.edit.enable |
Configure to edit the system-defined templates for the External service request type. Parameters:
|
|
bridge.type |
Configure the bridge to Bridge Lite (REST) or NiFi. Parameters:
|
|
display.tree.tagtile |
Show/hide the tree structure inside a tile on Tags > Tiles page. Parameters:
|
|
oe.diagnostics.show |
Show/hide the Log Viewer (OvalEdge Diagnostics ) tab under Ovaledge troubleshooting. It is for internal use. Parameters:
|
|
oe.diagnostics.blockedqueries.show |
Show/hide the Blocked Queries tab under the OvalEdge Diagnostics page. Parameters:
|
|
oe.diagnostics.sqlerrors.show |
Show/hide the SQL Errors tab under the OvalEdge Diagnostics page. Parameters:
|
|
oe.diagnostics.queryperfromance.show |
Show/hide the Query Performance tab under the OvalEdge Diagnostics page. Parameters:
|
|
oe.diagnostics.logs.show |
Show/hide the Logs tab under the OvalEdge Diagnostics page. Parameters:
|
|
dbanalysis.lesscolumns.show |
Configure to show only a few columns in the DB Analysis under Diagnostics. Parameters:
|
|
dbgrowth.lesscolumns.show |
Configure to show only a few columns in the DataGrowth under Diagnostics. Parameters:
|
|
bridge.protocol |
Define the protocol of the bridge, whether http or https. Parameters:
|
|
saas.client.name |
Configure to store secrets/credentials in the secrets manager for saas clients. Parameters:
|
|
registration.valid.domains |
To define a list of valid domains that are used for verifying user IDs during the registration process. Users can input a list of valid domains that should be recognized as acceptable during the user registration process. Parameters:
|
|
throttle.request.urls |
Configure the URLs for which the response rate limit is more. Parameters:
|
|
enable.deep analysis |
To enable/disable, the Deep Analysis sub-module in the Advanced Tools module. Parameters:
|
|
load.reporturl.through9dots |
To show/ hide the SSRS Reports on a separate window in the reports summary page. Parameters:
|
|
ticket.integration.response.read.timeout.seconds |
To specify the ServiceNow connection read the timeout in seconds. Parameters:
|
|
catalog.views.setdefault.allow |
It controls whether or not users can select a default view. Parameters:
|
|
catalog.views.create.public.allow |
To control whether or not non-admin users create a view visible to other users. Parameters:
|
|
term.catalogoption.enable |
To show/hide the display of multiple Term Association options under the "Manage Data Association" section in the Term summary page and Domain- default associations. The default value, "YYYYYYYYYYYY", suggests that all available options are displayed by default. Users can modify the display of these options by entering "Y" or "N" in the respective positions of the configuration string. If "Y" is entered, the corresponding option will be visible, while "N" will make it invisible. The order is as follows:
|
|
min.char.count.for.pattern |
It describes the minimum character count for a value to evaluate pattern while profiling. Example: If this value is 2, all column values which have character length >=2 are considered for pattern evaluation. Parameters:
|
|
max.characters.count.for.data.story |
It defines the maximum character count allowed for a Data Story. Parameters:
|
|
term.association.count |
This configuration allows setting a threshold for term-data object associations during the transition of terms from draft to published status. Its purpose is to enhance system performance, particularly when dealing with terms linked to numerous data objects. For example, if the threshold is set at 30, it triggers an advanced job when a term is moved to Published status with 31 or more data object associations. Conversely, if there are 29 or fewer term-object associations, the system manages status changes conventionally. Parameters:
|
|
tableplugin.pageload.time.display |
Control the display of the table plugin page load popup based on the selected boolean value. Parameters:
|
|
tags.pagination.row.size |
Set the number of tags to be displayed in the Tags List View. Parameters:
|
|
tags.children.pagination.row.size |
Set the number of child tags to be displayed in the Tags detailed page. Parameters:
|
|
health.pagination.row.limit |
Set the pagination limit for displaying the number of health history records in the Connector Heath pop-up. Parameters:
|
|
homepage.welcomestory.fullsize |
Configure how the Welcome story should be displayed on the Home Page by default. Parameters:
|
azuredevops.spoc.message |
Define a standard message in the azure devops > stores > description field. Parameters:
|
glossary.associations.view |
Configure to display either Published Terms or Terms in both Published & Draft status in the drop-down options when associating terms to data objects. Parameters:
|
|
oe.diagnostics.datagrowth.show |
Configure to enable the Data growth tab on the Application Diagnostics page. Parameters:
|
|
show.home.graphicalcount |
To show/hide the display of graphical presentations such as Tables, Files, and Reports on the home page. Parameters:
|
|
oe.diagnostics.slowapi.performance.threshold |
To set a threshold value to determine the maximum duration an API can take to load. The APIs exceeding the specified duration will be displayed in the API Performance tab. Parameters:
|
oe.diagnostics.slowapi.thread.sleep |
This configuration setting is designed for internal use and serves to establish a threshold in milliseconds for evaluating the execution time of a query within a specified timeframe. It plays a crucial role in identifying and monitoring slow-running queries or APIs. Parameters:
|
oe.diagnostics.slowapi.performance.enable |
Configure to enable the API Performance tab on the Application Diagnostics page. Parameters:
|
|
no.of.samplefiles.bucketanalysis |
To set the maximum number of sample file name logs to be displayed in the folder during the Bucket Analysis process. Parameters:
|
|
enable.folder.analysis |
To enable or disable the Folder Analysis tab from the FileManagerr and the File Catalog pages Parameters:
|
|
ovaledge.global.codeparameter.identifier |
This configuration is used to identify a global code parameter. |
oe.diagnostics.dbanalysis.enable |
Configure to enable the DB Analysis tab on the Application Diagnostics page. Parameters:
|
|
oe.diagnostics.activeusersandjobs.enable |
Configure to enable the Active Users And Jobs tab on the Application Diagnostics page. Parameters:
|
|
rows.to.download |
To specify the number of rows for download when utilizing the download option. Parameters: The default value is set to 20000. Enter the value in the field provided. |
|
enable.duckdb |
To profile file connectors using Duckdb.
|
load.data.from.cache |
It setting specifically pertains to the Azure Data Lake connector to control the visibility of file data and file columns when profiling is performed. Parameters:
|
|
enable.project.statusbar |
Enable/disable the Status Bar functionality in the project module. Parameters:
|
bridge.server.host |
To configure the host or URL of the bridge server, allowing the system to establish connections and communication with the specified server Parameters:
|
bridge.server.port |
To specify the port number associated with the bridge server to communicate with the bridge server through the defined port. Parameters:
|
bridge.temppath |
To specify the file system path where temporary or intermediate files related to the bridge functionality are stored. Parameters:
|
|
scroll.pagination.search.limit |
This limit is to display the number of users for each scroll whereever scroll pagination is available Parameters:
|
|
profile.all.files.enable |
To enable or disable the "Catalog and Profile All Files" option in the Data Catalog > Folders accessible through the nine dots icon. Parameters:
|
|
oe.store.source.data |
To configure whether the application should store source data or not. Parameters:
Additional Information:
|
|
status.assignee |
This will enable/disable assignee list in status popup of Processing Activity and Report summary page. |
|
bridge.nifiversion |
To configure the NiFi Bridge version. Parameters:
|
|
bridge.compressed.value |
To control and determine the threshold or size at which data payload compression is applied to any request originating from the bridge side. For Example, if set to 10KB, any data payload exceeding 10 kilobytes in size will be compressed before transmission, whereas payloads smaller than 10KB will not undergo compression Parameters:
|
|
entityrelationip.max.limit |
To configure the maximum limit for the number of nodes displayed in the entity relationship graphs within the Data Catalog. Maximum limit - 100. Parameters: The default setting is 50, which means that initially, up to 50 nodes are shown in these graphs. Enter the value in the field provided. |
pkfk.relation.job.rowcount.check |
To specify the minimum row count that a table must meet to qualify as a primary key. When set to a value like 100, primary key columns will only be identified for those rows that equal or exceed this threshold. Parameters:
|
pkfk.relation.job.max.fk.count |
To specify a limitation on the number of foreign keys that must be identified in order to calculate relationships. When set to a value such as 20, relationships will only be constructed if the count of identified foreign keys is equal to or less than 20. If, for example, 25 foreign keys are identified, relationships will not be established. Parameters:
|
|
relationjob.min.match.count.from.topvalues 1 |
This setting defines the minimum number of matches needed between the top values of two columns to qualify for a potential relationship. For instance, if set to 10, at least 10 matches among the top values of the two columns are required to initiate a relationship. If this threshold is not met, the columns won't be considered for relationship building. Parameters:
|
allreports.pagination.limit |
To specify the number of reports displayed on a single page within the Dashboard > All Reports. Parameters:
|
|
fetch.deltalake.comments |
To control the settings, whether to fetch comments from the remote data source or not, the fetched comments will be displayed in the source description field in the data catalog. Parameters:
|
|
supported.folderanalysis.connectors |
Specify the connector names on which folder analysis can be performed to determine the size and count of folders. Parameters:
|
|
impactanalysis.source.objects.limit |
Specify the maximum number of objects that can be added to a single impact analysis. By specifying this maximum value, a boundary is set for the comprehensiveness of the analysis, adding an excessive number of objects might lead to computational or analytical challenges. Parameters:
|
show.draft.terms.to.viewers |
This setting enables a toggle button in the Business Glossary to toggle and display both Draft / Published terms in the Tree View and List View of the Business Glossary. Parameters:
|
tag.multiple.parent.hierarchy |
This configuration setting provides users with the flexibility to create tags with the same name under different root tags. Parameters:
|
|
dbt.crawl.manifest.size.limit |
To configure the size of the Manifest file content or source code fetched during the crawling of the DBT system. Parameters:
|
|
ovaledge.gov.app.host |
To configure the host server URL for governance apps, allowing the redirection of users to governance apps via email or direct links. Parameters:
|
|
homepage.pagination.limit |
To control the number of domains and terms displayed in the left panel on the homepage. For example, if set it to 20, the panel will initially show 20 domains and retrieve more as you scroll down. Parameters:
|
|
domain.default.color |
To define the default colour of the domain icon in the Business Glossary Dashboard. Parameters:
|
|
domain.icon.max.width |
Specify the maximum width of the domain icon in the business glossary dashboard. Parameters:
|
|
domain.icon.min.width |
Specify the minimum width of the domain icon in the business glossary dashboard. Parameters:
|
|
questions.wall.panel |
To designate stakeholders (users or teams) for the question wall who will receive email notifications when a question is posted. Parameters:
|