Configurable cascading in case filters
Case Store and Data Store search screens now support dynamic cascading for code set filter fields.
- All defined
- Filtered and hidden
- Filtered and disabled
This enhancement ensures that users only see relevant filter options based on previously applied criteria, streamlining the filtering process and reducing clutter.
For example, if a user filters by a country and only certain statuses are available for that country, only those statuses will be shown or enabled in the filter drop-down.
This dynamic filtering improves efficiency and helps users quickly find and apply the right filters.
Bulk mass edit for case and data store search screens
The case store and data store search screens now support Bulk actions, starting with the Mass Edit feature. Previously, you needed to select one or more rows to perform actions. With bulk actions, you can apply changes to all rows that match your specified filter criteria. Bulk actions can also be individually hidden from users through the search screen definition.
Rule library with rule priority and enhanced output
The Rule Library has been enhanced to allow the definition of rule attributes and the assignment of priorities to rules. Users can now output these attributes as part of the rule result, and the rule result can be formatted in JSON for easier consumption in JavaScript nodes. This enables workflows where, for example, the highest priority passed rule can be automatically identified and flagged, supporting advanced data quality certification and reconciliation scenarios. The new functionality provides greater transparency and control over rule evaluation and output.
Support for Elastic Beanstalk IMDSv2
The Data360 DQ+ deployed on AWS Elastic Beanstalk now support the use of Instance Metadata Service Version 2 (IMDSv2) for retrieving EC2 instance metadata. This enhancement removes the dependency on IMDSv1, improving security and compatibility with modern AWS best practices.
Ability to delete records from internal database data stores via analysis
A new Data Store Delete Rows node has been introduced in the Inputs/Outputs category for Analysis. This node allows users to delete records from internal database data stores by mapping key fields and providing input rows to be deleted. The node ensures that only records matching the specified keys are removed, and any discrepancies in the number of deleted records are flagged as errors. This enhancement gives you full control over your data, enabling you to keep datasets clean and up-to-date by removing obsolete or unnecessary records as part of you data quality workflows.
Other changes
The following additional improvements and security enhancements are included in this release:
- Addressed a low or certain security finding by ensuring the HTTP Strict-Transport-Security (HSTS) response header is correctly implemented on all relevant resources, improving overall security posture.
Corrected issues
| Issue Summary | Issue Number |
|---|---|
| Resolved an intermittent issue that caused errors for some users when viewing the dashboard from the Case Store screen. | ISX-23259 |
| Resolved file upload failures when creating a new data store from a file, caused by stricter default multipart limits introduced in Tomcat 10.1.x. | ISX-23103 |
| Fixed an issue where the popup window containing the stage picker did not close after clicking Show this stage in pipeline and navigating to the selected stage in the Analysis editor. | ISX-23099 |
| Fixed an issue where the database data store did not display the most recent records after data was modified through the data entry page, causing the list to not reflect changes immediately. | ISX-22958 |
| Resolved an intermittent issue where the Case Screen result grid would not display any records after applying filters, even though the case count was correct. The grid now reliably displays filtered case records without requiring a manual refresh. | ISX-23300 |