This topic provides release information for the latest release of Data360 DQ+. If you are looking for release information for an older version of the product, or for a patch release, see the Release history section.
Latest release - 12.0
This is a multi-tenant cloud release.
Configure branding
Administrators can now establish a tenant or organization-wide branding color scheme for Data360 DQ+. You can import a company logo or favicon, and you can set colors for different components across the application. These settings can be separately exported and imported across different installations such as test and production.
Show stage version history
The system has been enhanced to show a version history of stages that support content versioning. You can generate a JSON text representation of a version of a stage for comparison with another version.
Recon Check analysis node
The Recon Check analysis node has been enhanced to produce additional output fields per recon check match rule. In addition to the boolean result field, the system will now produce "left", "right" and "diff" fields per named rule. The left and right fields contain the accumulated value for the left and right side of the comparison, and the diff field contains the difference between the two values (left - right).
Case management
Case management has been enhanced to allow the case store designer to automatically assign a case to the current user when you are performing a transition action. Additionally, the transition dialog title has been improved to include the state the case is being transitioned to.
Export from the data entry screen
The ability to export data from a data entry search screen has been added. Additionally, the data entry search screen definition has been enhanced for choosing which actions are provided on the search screen.
Other changes
- The system has been enhanced so that the database driver class can refer to an environment or runtime property for either a database data store definition, or an Execute Query in DB analysis node.
- The Environment and Tenant Settings JSON download is now produced in a sorted order to improve external comparison of different versions of the information.
- Case store search screens, data store search screens, and analysis designer data sheets have been enhanced to enable you to freeze a subset of columns so that they remain visible when you scroll horizontally.
Corrected issues
Issue Summary | Issue Number |
---|---|
Fixed an issue in the analysis designer where a rule library node sometimes lost placeholder mappings for its checks when the node was re-connected to an earlier node. | ISX-22572 |
Fixed an issue with the export of Date fields to Microsoft Excel from search screens or dashboards where the exported date was not the same as the date seen in the application. | ISX-22577 |
Fixed an issue where changes could not be saved when a text field filter in a dashboard was edited and the cascading option was turned on. | ISX-22535 |
Fixed an issue where a date filter on a dashboard produced incorrect results when using a custom range filtered to a single date. The system now sets the "To" filter value to the last moment of the chosen date, and uses the organization timezone for criteria values instead of the user's timezone. | ISX-22510 |
Fixed an issue with dashboards where a pivot grid dashlet's content became empty when restored from an invisible state. | ISX-22467 |
Fixed an issue where a blank screen was sometimes displayed after logging in to the application. | ISX-22338 |
Fixed an issue where editing a Join node did not properly display the error message for a problem on the Join Fields tab after switching to the Output Fields tab then back again. | ISX-22573 |
Fixed an issue in the analysis designer with a Union node that caused downstream nodes to require remapping when a field was added to the source. Additionally, an option to add and remove fields has been included for the Union node. | ISX-22473 |
The system no longer appends "_1" to the rule name part of a reason value for rule library nodes when the check is mapped to a single field. | ISX-22513 |
Fixed an issue that prevented users from resetting their password after their account was locked. | ISX-22549 |
Fixed an issue where clearing the value of a prepopulated text field filter in a dashboard did not take effect immediately. | ISX-22550 |
Fixed an issue that prevented process model executions from reflecting the completion status of tasks that followed the first task that failed, showing them on the execution diagram as running when they were not. | ISX-22332 |
Fixed an issue where a uniqueness check, when mapped to multiple fields in a rule library node, produced non-unique failure results. | ISX-22514 |
Fixed an issue where the system was unable to read an XML file during Kafka data store creation unless the chosen file name contained a trailing space. | ISX-22508 |
Fixed an issue where string fields stored in database data stores or case stores were being truncated to no more than 2000 characters. | ISX-22521 |
Fixed an issue with Transformation SQL generation for a hierarchical data source such as JSON where, when the sampled file contained a non-repeating top-level structure, results in data were not being read correctly. For a source where this problem occurs, click Edit Transformations on the Details tab, choose Refresh Schema and click OK. Delete the fields on the Fields tab, then click Generate to regenerate the fields. | ISX-22580 |
Fixed an issue where DateTime field values exported to Microsoft Excel had the wrong cell formatting, rendering them as numbers instead of dates with time. | ISX-22527 |
The system's default configuration has been altered to workaround a potential Apache Spark operation problem when exploding arrays in hierarchical data sources such as JSON or XML. | ISX-22582 |