> For the complete documentation index, see [llms.txt](https://docs.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.collibra.com/data-quality-self-hosted/admin-configuration/admin-console/configuration-settings/application-configuration-settings.md).

# Application Configuration Settings

Application Configuration Settings allows admin users to toggle various platform controls on and off. Admins can also add custom application configuration settings from this page.

![](https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-b8d714660c43c25102735ffdfb8dbe797bfd2d04%2Fdq-app-config-settings.png?alt=media)

## Out-of-the-box application configuration settings

<table><thead><tr><th width="152">Setting</th><th>Description</th><th>Value</th></tr></thead><tbody><tr><td>ACCESSIBILITY_DISPLAY</td><td>Do not use this setting. It is not currently utilized by Data Quality &#x26; Observability (self-hosted).</td><td> </td></tr><tr><td>AI_PLATFORM_PATH</td><td><p>When set to <code>TRUE</code>, SQL Assistant for Data Quality uses the Collibra Platform path and utilizes the Gemini AI model. This is the default and recommended setting.</p><p>When set to <code>FALSE</code>, SQL Assistant for Data Quality uses the path in preview with an encryption key provided by Collibra and utilizes the text-bison-002 AI model.</p></td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>TRUE</strong></p></td></tr><tr><td>AI_TENANT</td><td>Enables <a href="/data-quality-self-hosted/core-concepts/navigation/dataset-overview/sql-assistant-for-data-quality.md">SQL Assistant for Data Quality</a> when set to <code>TRUE</code>.</td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>FALSE</strong></p></td></tr><tr><td>BULK_CATALOG_ON</td><td>When set to <code>TRUE</code>, allows/disallows using the catalog feature from the Wizard in the UI.</td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>TRUE</strong></p></td></tr><tr><td>ENABLE_DELETE_INTEGRATION</td><td><p>When set to <code>TRUE</code>, you can delete integration artifacts, such as assets and domains, when the <strong>Also delete integration for this dataset</strong> option is selected on the <a href="/data-quality-self-hosted/core-concepts/dataset-directory/dataset-manager.md">Dataset Manager</a> delete confirmation dialog box. The <code>/v2/deletedataset</code> API endpoint:</p><ul><li>Removes the data quality rule history</li><li>Sets the integration dataset status to "Disabled"</li><li>Removes the integration table references from the metastore</li><li>Deletes the Collibra Platform rule domains, score domains, and job assets, as well as the data quality rule assets associated with those domains</li></ul></td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>FALSE</strong></p></td></tr><tr><td>ENABLE_STRICT_TAGGING</td><td>The ENABLE_STRICT_TAGGING setting determines how meta tags are managed. When set to TRUE, meta tags must be selected from an Admin-controlled drop-down list. When set to FALSE, meta tags can be entered as free-form text from the <a href="/data-quality-self-hosted/core-concepts/dataset-directory/dataset-manager.md">Dataset Manager</a>.</td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>FALSE</strong></p></td></tr><tr><td>HOST_NAME</td><td><p>Hostname of your URL.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>When you enable <strong>Include Links</strong> on the Alerts Configuration page of the Admin Console, you must also enter your host address in the HOST_NAME input field. For more information, go to <a href="/data-quality-self-hosted/core-concepts/alerts/working-with-the-alert-builder/configuring-alert-emails.md">Configuring alert emails</a>.</p></div></td><td>Enter the hostname in the input field.</td></tr><tr><td>JOB_LOG_RETENTION_HR</td><td>The number of hours that Collibra DQ retains DQ Job logs.</td><td>Enter the number of hours for Collibra DQ to retain DQ Job logs.</td></tr><tr><td>MANDATORY_PRIMARY_RULE_COLUMN</td><td>When set to <code>TRUE</code>, users are required to select a primary column when <a href="/data-quality-self-hosted/core-concepts/dq-rules/rule-builder/working-with-the-rule-workbench/create-a-data-quality-rule.md">creating a rule</a>. This requirement is enforced when a user creates a new rule or saves an existing rule for the first time after the setting is enabled. Existing rules are not affected automatically.</td><td> </td></tr><tr><td>MANDATORY_RULE_DIMENSION</td><td>When set to <code>TRUE</code>, the <strong>DQ Dimension</strong> field on the <a href="/data-quality-self-hosted/core-concepts/dq-rules/rule-builder/working-with-the-rule-workbench/create-a-data-quality-rule.md">Rule Details modal</a> is required for new and edited rules, including when using the API with v3/rule.</td><td> </td></tr><tr><td>MAP_TO_PRIMARY_COLUMN</td><td><p>When set to <code>TRUE</code> and you have an integration with Collibra Platform enabled, you can map a rule to only the Column asset in Collibra Platform that corresponds to the primary column in Data Quality &#x26; Observability (self-hosted).</p><div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p>For more information, go to <a href="/data-quality-self-hosted/integrations/configuring-a-new-integration.md">Configuring a new integration</a>.</p></div></td><td> </td></tr><tr><td>MASK_P_FLAG</td><td>When set to <code>TRUE</code>, sets/unsets <code>-p/-srcp</code> masking in the UI.</td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>TRUE</strong></p></td></tr><tr><td>PLATFORM_LOG_RETENTION_HR</td><td>The number of hours platform logging is retained.</td><td>Enter the number of hours for Collibra DQ to retain platform logs.</td></tr><tr><td>RULE_CONDITION_DISPLAY</td><td>When set to <code>TRUE</code>, the Rules tab and exported XLSX files show "ruleCondition" instead of "ruleValue" for pushdown and pullup datasets.</td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>FALSE</strong></p></td></tr><tr><td>RULE_FILTER</td><td>When set to <code>TRUE</code>, you can use <a href="/data-quality-self-hosted/core-concepts/dq-rules/rule-builder/working-with-the-rule-workbench/filter-a-data-quality-rule.md">filter queries</a> when creating a rule on the Rule Workbench.</td><td> </td></tr><tr><td>SSO_API</td><td><p>When set to <code>TRUE</code>, you can configure single sign-on (SSO) to access Data Quality &#x26; Observability (self-hosted) APIs using authorization bearer tokens.</p><div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p>For more information, go to <a href="/data-quality-self-hosted/admin-configuration/admin-console/user-management/sso-for-api-usage/sso-for-api-usage-overview.md">SSO for API Usage Overview</a>.</p></div></td><td> </td></tr></tbody></table>

## Optional application configuration settings

<table><thead><tr><th width="152">Setting</th><th>Description</th><th>Value</th></tr></thead><tbody><tr><td>AUTO_JOB_ESTIMATION</td><td>The AUTO_JOB_ESTIMATION variable enables the auto-estimation for pullup job reruns or scheduled runs. When set to TRUE, the minimum memory for the driver and executor is set to 2 GB, and the maximum memory is determined by the estimate.</td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>FALSE</strong></p></td></tr><tr><td>DEPRECATED_CROSS_DB_LEGACY_PARSER_ENABLED</td><td>Controls which SQL parser Data Quality &#x26; Observability (self-hosted) uses to extract table names when checking whether a query references tables outside a connection's approved schema. Only has an effect when cross-database schema reference validation is enabled for your environment. When set to TRUE, the legacy, deprecated parser is used. When set to FALSE (recommended), the current dialect-aware parser is used.</td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>FALSE</strong></p></td></tr><tr><td>DEPRECATED_MANUAL_QUERY_AUTO_ESCAPING_ENABLED</td><td>Controls whether a legacy auto-escaping step runs before a manually edited query in Compile Query is sent to the source database. When set to TRUE, the legacy escaping step and the cross-database schema reference validation are run. When set to FALSE, these steps are skipped.</td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>FALSE</strong></p></td></tr><tr><td>CREATE_METRIC_ASSETS</td><td>The CREATE_METRIC_ASSETS variable automatically creates metric assets during integration. When set to TRUE, metric assets, such as <a href="/data-quality-self-hosted/admin-configuration/admin-console/integrations.md">Passing Fraction and Loaded Rows</a>, are automatically created during integration to support the required data quality metrics for your Collibra Platform aggregation path or workflow design. When set to FALSE, metric assets are not created during integration.</td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>TRUE</strong></p></td></tr><tr><td>PUSH_NA_TO_DIP</td><td><p>When set to TRUE, deselected or deactivated Adaptive Rules are pushed to Collibra Platform with a status of "NA" instead of retaining their last synced status. When set to FALSE, deselected or deactivated Adaptive Rules keep their last-known status on Collibra Platform.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>After changing this setting, you must resync the integration for the change to take effect.</p></div></td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>FALSE</strong></p></td></tr><tr><td>RULE_ARCHIVE_RESULTS</td><td>When set to TRUE, Archive Break Records shows and downloads the rule query results for a break record instead of the source row, for jobs where a Link ID is specified. When set to FALSE, the preview and download continue to show the source row retrieved via the Link ID.</td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>FALSE</strong></p></td></tr><tr><td>SCHEDULE_RECOVERY_ENABLED</td><td>The SCHEDULE_RECOVERY_ENABLED variable restarts jobs left in an unfinished state due to an unscheduled server crash. When set to TRUE, the scheduler automatically adds these unfinished jobs to the job execution queue, allowing them to run and complete without user intervention.</td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>FALSE</strong></p></td></tr><tr><td>STRICT_SQL_QUERY_PARSING</td><td><p>You can control the strictness of SQL query validation in the <a href="/data-quality-self-hosted/core-concepts/navigation/dataset-overview.md">Dataset Overview</a> and the <a href="/data-quality-self-hosted/core-concepts/explorer/create-a-dq-job/select-rows.md">SQL View</a> step in Explorer. Use the VALIDATE_QUERIES and STRICT_SQL_QUERY_PARSING settings in the Application Configuration Settings page of the Admin Console to configure this behavior.</p><p>The combination of these settings determines whether query validation is enabled and how strict or simple the validation is:</p><ul><li>Simple validation checks if the query contains any keywords other than <code>SELECT</code>, but it does not perform a full syntax validation.</li><li>Strict validation performs a full syntax check of the query, ensuring it is a valid <code>SELECT</code> statement and that no non-<code>SELECT</code> keywords are present.</li></ul></td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>FALSE</strong></p></td></tr><tr><td>VALIDATE_QUERIES</td><td><p>The VALIDATE_QUERIES setting works in tandem with STRICT_SQL_QUERY_PARSING. The following table explains how these settings interact:</p><p><strong>VALIDATE_QUERIES</strong>: TRUE</p><ul><li><strong>STRICT_SQL_QUERY_PARSING</strong>: TRUE</li><li><strong>Validation behavior</strong>: Strict SQL validation is enabled</li></ul><p><strong>VALIDATE_QUERIES</strong>: TRUE</p><ul><li><strong>STRICT_SQL_QUERY_PARSING</strong>: FALSE</li><li><strong>Validation behavior</strong>: Simple SQL validation is enabled</li></ul><p><strong>VALIDATE_QUERIES</strong>: FALSE</p><ul><li><strong>STRICT_SQL_QUERY_PARSING</strong>: TRUE or FALSE</li><li><strong>Validation behavior</strong>: SQL query validation is disabled</li></ul></td><td><p><strong>TRUE/FALSE</strong></p><p>Default: <strong>FALSE</strong></p></td></tr></tbody></table>