New in 7.1 - Data360_DQ+ - Latest

What's new

Changes to the UI branding and appearance

The Data360 DQ+ UI and documentation styles and colors have been updated to match the Precisely brand.

Computed fields and calculator fields have been added

Computed fields have been added to case stores, while calculator fields are a new addition to case management and data entry search screens.

Added a locale field to administration settings

A Locale field has been added to administration settings, which affects how data is displayed throughout the system and in the Executions log.

Define individual column widths

You can now specify the column widths of data grids used in a dashboard individually. A dropdown menu, available from the column header, enables you to both specify the column width and sort the order of its content. Clicking on the header will now select the column, instead of sorting it.

View a case directly from the case list

You can now view a case directly from the case list, simply by clicking the hyperlink in the first column, instead of clicking on the row and then clicking View. This also works within the grid on the Records tab of a case view.

New chapter added to the Data360 DQ+ Azure Installation Guide

A new chapter, which provides information about how to change the Microsoft Azure secret has been added to the installation guide.

For more information, see "8. Changing the Microsoft Azure secret".

Maximum allowed storage increased for dedicated AWS instances

The maximum allowed storage for dedicated instances on AWS, has been increased from 10240GB to 16384GB in the execution profile.

Case management page changes

Define the initial view

You can now choose to initially display a dashboard, the queue or the search screen, when the case management page is opened. Previously you could only configure the default dashboard.

Customize the names in the navigation menu

You can now use different names for the Dashboards, Queues, and Search buttons in the navigation menu of the case management page.

Semantic type filtering updates

Semantic type filtering has been updated, based on the latest fast text analysis (FTA) and the locale setting. The semantic type updates have been made to datastore and casestore fields, dataview fields and dataview computer fields, when they are strings. User defined semantic types that start with d3s (case insensitive) are still not allowed.

Other changes

• There is a new home page design, with the ability to add stages to the favorites and recently updated lists.
• Trial support for JWT authentication has been added. This is also applicable for single-tenant cloud and enterprise deployments.
• The case management and data entry search screens now display longer column headers, before they are elided.
• You can now search for null values in the case screen filter fields.
• Support of Protegrity for data tokenization has been added.
• A text filter dashlet has been added to dashboards, which supports the filtering of multiple values.
• SecuPi support for data tokenization has been added.
• Support for reading .gz and .gzip files as data store data sources has been added.
• A prometheus /metrics endpoint has been added, for collecting web requests and stage execution metrics.
• Google Dataproc can now be used for the compute cluster in the enterprise version.
• Support for a generic Spark data source input and output has been added.
• Encryption of the environment-related encrypted properties and the secret key has been improved.
• Descriptions have been added to the dataview field definitions, and custom fields of the dashboard definitions.
• Field descriptions for data and case stores, as well as data views, now display as tooltips, associated with the column headers of a data table, in a dashboard, or within case search screens.
• The ability to add or update the app user in GraphQL API has been added.
• A new Spark Data Source layout has been added to S3 and HDFS/ADLS repository types, called "Spark Data Source".
• Added Google KMS support for key encryption, in an enterprise deployment.
• A new repository type called “Spark Data Source” has been added.
• Support for more security headers for the API and Web pages has been added, leading to an improved security posture.
• The standard log4j Java jar file has been replaced with one that has classes with security vulnerabilities removed.
• Support for multiple SecuPi applications for data protection has been added.

Corrected issues