> 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/release-notes/data-quality-observability-self-hosted-release-archive/release-2023-03.md). # Release 2023.03 * [Highlights](#highlights) * [New Features](#new-features) * [Enhancements](#enhancements) * [Fixes](#fixes) * [Known Limitations](#known-limitations) * [DQ Security Metrics](#dq-security-metrics) * [Maintenance Updates](#maintenance-updates) ### Highlights * When your Collibra DQ license is about to expire, a counter in a warning banner on the Collibra DQ home page now counts down from 30 days until your license expires. You can [update your license key](/data-quality-self-hosted/admin-configuration/admin-console/license/managing-collibra-dq-licenses.md) at any time to avoid any disruptions. * A message now appears in the Description field of the Jobs activity logs and the Job Exception field of the Jobs log table view when a DQ Job fails because of an expired or invalid license key. * An error message now appears on the Findings page when a job fails because of an expired or invalid license key. * When admin users update a license with a valid license key on the License page of the Admin Console, a success message appears. * When admin users update a license with an invalid license key on the License page of the Admin Console, an error message appears. * DQ Jobs will again run normally once a valid license key is saved.

Any DQ Jobs that run on accounts with expired or invalid license keys will no longer run until a valid license key is saved.

* To improve how Collibra DQ handles Jobs concurrently at lower memory agent configurations, the [default agent batch size](/data-quality-self-hosted/admin-configuration/more-admin-settings/job-management/concurrency/concurrency-sizing.md) for concurrent Jobs is now 5. For example, when you run more than 5 Jobs concurrently, only 5 Jobs run at once. All additional Jobs remain in Staged status until the initial 5 Jobs are complete, which allows new Jobs to continue to enter the queue on the Jobs page. * The following are the default values in the Helm owl-agent-configmap.yaml file: * `DEFAULT_BATCH_ID: ` * `DEFAULT_BATCH_SIZE: 5` * The following are the default values in the Helm values.yaml and values\_test.yaml files: * `agent_batch_id: "default?batchSize=5"` * `agent_batch_size: 5` * It may be necessary to [override the default values](/data-quality-self-hosted/admin-configuration/more-admin-settings/job-management/concurrency/overriding-the-default-batch-size.md) for high concurrency requirements. Increase the `DEFAULT_BATCH_ID` and `DEFAULT_BATCH_SIZE` values and update the corresponding Helm values for DQ Agent configuration accordingly. * You can now [convert log outputs to JSON formatting](/data-quality-self-hosted/core-concepts/explorer/managing-the-jobs-page/logging/convert-log-outputs-to-json-formatting.md) for ingestion by a third-party log consumer. * You can now optionally [include additional fields and hyperlinks](/data-quality-self-hosted/core-concepts/alerts/working-with-the-alert-builder/configuring-alert-emails.md) to the environments from which alerts originate in email alerts. * Admin users can turn this option on or off from the Alerts page within the Admin Console. {% hint style="info" %} If you only install owlweb or owlagent, you need to copy the owlmanage.sh file from the installation package into the bin directory with the following command:`cp $PACKAGE_LOCATION/owlmanage.sh $INSTALL_PATH/bin/owlmanage.sh` {% endhint %} ### New Features #### Platform * Collibra DQ now displays in-app messages about expired, expiring, and invalid licenses, including a banner message on the Collibra DQ home screen that counts down from 30 days until your license expires. * You can update or edit your license from the [License Management](/data-quality-self-hosted/admin-configuration/admin-console/license/managing-collibra-dq-licenses.md) page in the Admin Console. ### Enhancements #### Jobs * The icon for the Jobs page is now the DQ Jobs icon clipboard icon. #### Rules * Export LinkIds now has the same export capabilities as Export and Export with Details. * You can now use keyboard shortcuts on the Rule Builder page to display dataset-level stat rules. #### Alerts * You can now optionally include additional fields and hyperlinks to the environments from which alerts originate in email alerts. #### Agent * To improve how Collibra DQ handles Jobs concurrently at lower memory agent configurations, the default agent batch size for concurrent jobs is now 5. #### Admin * You can now set default values on the Add External Service Configuration form on the Assignment Queues page when you want to override the values for individual finding validate action. #### Security * Collibra DQ now enforces a Spring CSRF token, as well as CORS and SameSite, as standards to mitigate against CSRF attacks. * Any cookie-based auth requests without this token are rejected with a 401 error. * This feature is active by default, but can be deactivated if necessary. Deactivating this feature does not compromise the security of the Collibra DQ app because we have other mitigation standards in place for CSRF. * All non-GET HTTP requests need to carry a CSRF token header when they call the API. This happens automatically when you use the app within Collibra DQ. * This implementation only impacts cookie-based authentication. Additionally, Swagger UI and APIs that use bearer token authentication are not impacted by this change. * Server-side validation for username, first name, last name, and email is now included in the /v2/createlocaljdbcuser internal registration API. #### Platform * New User Request emails now include additional fields and hyperlinks to the environment from which the request originates for easier access. * You can now convert log outputs to JSON formatting for ingestion by a third-party log consumer. #### Snowflake Pushdown (in preview) * You can now scan for exact and fuzzy matches as part of the Dupes check layer. * You can now use the Correlation tab on the Profile page to understand correlation levels between numerical columns. * Minimum and maximum string length profiling is now available. ### Fixes #### Explorer * Fixed an issue where a custom Transform statement was corrupted after running a DQ Job and clicking the Edit button. (ticket #104992) #### Rules * Fixed an issue where custom rules with primary and secondary datasets that shared similar naming conventions failed because of incorrect replacement of @Dataset or @secondary with the name of the dataset by Collibra DQ's replace logic. (tickets #105812, 108490) #### Source * Fixed an issue that resulted in an Authentication error when the source data loaded because both the source and target used the same Kerberos TGT-based connection. (ticket #102639) #### Platform * Fixed an issue where incorrect syntax in the owldq/templates/rbac.yaml manifest caused errors for some Kubernetes deployments on AKS. * Fixed an issue where an upgrade to Release 2023.01 caused errors, which referred to the agent\_displayname column on the agent\_q table when the web pods launched. * Fixed an issue where the Flyway script V188 did not run successfully after an upgrade from Release Version 2022.08 to 2023.01. (ticket #107222) #### Connections * Fixed an issue that prevented Collibra DQ from establishing a connection to Azure Data Lake after an upgrade to Release Version 2022.11. (tickets #104271, 107451) #### Outliers * Fixed an issue where jobs that used union lookback and whose findings were marked as ignored, off-peak, or removed, were incorrectly included in the outlier calculation. (ticket #104746) ### Known Limitations #### Snowflake Pushdown (in preview) * Mixed datatype rules are not supported in Pushdown. #### DQ Connector * There is an issue where Rest API calls from Collibra DGC to Collibra DQ result in a 403 Forbidden Error because Collibra DGC passes a cookie header which causes Collibra DQ to reject the request due to recent updates to CSRF token requirements. This limits Collibra DQ's ability to connect to Collibra Platform. * A possible workaround until a fix is available is to update `export CSRF_TOKEN_ENABLED=false` in the owl-env.sh file for Standalone deployments or update `dq.security.csrf.token.enabled=${CSRF_TOKEN_ENABLED:false}` in the Web ConfigMap for Kubernetes deployments. ### DQ Security Metrics ![Security vulnerabilities over 5 months](https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-3c58d106c5d3fb3e54742b3a2bee74df1db4e3c4%2Fvulns-over-time-2023-03.png?alt=media) ![Critical security vulnerabilities table over five months](https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-b8dd41c4bbc73a4bcee5653625ea891a27185c49%2Fcritical-table-2023-03.png?alt=media) ### Maintenance updates * External users can now successfully run Jobs that include alert links. * The email address of the owner of a Job with alert links is no longer included in alert emails for both local and external users.