What's new - Data360_DQ+

Unlock user accounts

The Users page now displays information about whether users are activated or locked. Additionally, administrators can now unlock users without changing their passwords.

Upload a logo

Administrators can now configure a logo image and website icon for their tenant/company within Admin > Settings.

JWT authentication support for APIs

Added OAuth2.0 JWT authentication support for APIs as an alternative to basic authentication.

Key and secrets management

The system now supports access to the AWS Secrets Manager for connection parameters and credentials in Data Store (Database) stages and the Execute Query in DB analysis node. In a single-tenant installation, the Secrets Manager access may be to another AWS account. Secrets are referred to with a value like sec(your_secret_name) or sec(your_secret_name field_in_secret). Execution parameters or environment properties may specify a secret reference, and may themselves be encrypted, when those properties are used in Data Store (Database) stages or in the Execute Query in DB analysis node.

Analysis execution parameters

The analyst defining an Analysis stage can now specify execution parameters that must be supplied when running the analysis. These parameters can also be input when testing the analysis interactively, or accepting changes on the nodes of the analysis. This allows the analyst to avoid using "hard coded" values during analysis design, and ensure that the appropriate execution parameters are supplied when executing the stage.

Encrypt execution parameters

When executing a data stage, you can now specify execution parameters as encrypted values. These values are shown only as a full mask (*****) on the Admin > Executions page. Output parameters defined in process models can also be defined as encrypted values. This enables you to encrypt the credentials that are passed into your process models, and also hides these values from the execution history.

Azure Postgres Flexible Server database

New Azure installations for release 11.2 create a Postgres Flexible Server database. Infrastructure upgrades from earlier releases will migrate the Postgres Single Server database to Flexible server. Review the Azure installation guide for single server backup and flexible server restore steps when upgrading.

Other changes

JVM options to increase the Java stack size have been added to the Enterprise installation to reduce possible errors with the use of certain nodes in the analysis designer.
The AWS single-tenant edition can now be configured to access a separate KMS endpoint for using a customer managed key to encrypt/decrypt data values in Data360 DQ+.
To improve application availability, the Execute Query in DB node now requires a Sample SQL query definition where you must specify a query that will return a modest amount of data for interactive analysis building.
The Analysis Settings dialog has been rearranged to move execution profile settings to a separate tab for greater consistency with the same sorts of settings on other stages, such as Data Views. The System tab of the Data View stage has been renamed to Execution Profile.
Added support of stage UUID as an alternative to stage ID in APIs for querying stage data. The affected APIs include: queryActivityLogData(), queryCaseStoreData(), queryDataStoreData(), and queryDataViewData().
The commons-text library used for enterprise CDP executions has been upgraded to address security concerns.
The size of the KEYDATA column in the CAF_SECDATAKEY table has been increased from 512 characters to 1000 characters to support larger key sizes. See the installation guide for upgrade SQL statements to perform.

Corrected issues

Issue Summary	Issue Number
The `exportServerLogs()` and `exportServerLogsStatus()` APIs are now authorized for admin users only.	ISX-22157
Fixed an issue where rule library regular expression rules, or type conformance rules with a regular expression, failed to execute when the regular expression contained a backslash character. Note: Regular expression rules generated by the new rule library Generate action may begin to fail after this fix is applied. To correct them, edit the regular expression rule, and make any trivial change to the description, then click Accept and Save.	ISX-22261
Fixed an issue where delimited field generation was not generating fields for DateTime values with timezone offsets of either RFC 822 or ISO 8601 type.	ISX-22224
The `exportServerLogs()` API now returns an error when the server does not support exporting server logs, and also returns an error when supplied with invalid start or end times.	ISX-22120
Fixed an issue in the dashlet editor where, when defining a custom field, the Name field was filled with underscores when you entered a white space.	ISX-22167
Fixed an issue where the login prompt was incorrectly displayed after defining a retention schedule based on a CRON expression.	ISX-22054
Fixed an issue encountered in the Gradle `initialize` step when upgrading Data360 DQ+ in a single-tenant deployment.	ISX-22091
Fixed an issue that caused display formatting errors when more than 3 'S's were used in the format string for the millisecond value.	ISX-22227
Fixed an issue where Read permission was not granted when using the Grant permissions to stages used by this stage checkbox in the custom security settings for a stage.	ISX-22222
Fixed an issue that prevented process models from monitoring the execution status of remaining stages after being terminated.	ISX-22332
Fixed an issue that caused an error when exporting dashlet data with custom headers for dimension fields.	ISX-22340
Fixed an issue when performing a mass edit on cases, where the system may incorrectly mark one of the first 10 fields as a field to be changed even though the user did not choose that field.	ISX-22490
Fixed an issue that prevented installation in environments with limited internet access when the download of a Gradle plugin was attempted during deployment.	ISX-22492

What's new - Data360_DQ+ - Latest

Data360 DQ+ Release Notes