This is a multi-tenant, cloud-only release.
New data load range option
When specifying a Data Load Range for input data stores and other executable stages, a new option has been added: Based on File Path Parameter. This setting allows you to work with a specific file, avoiding a file scan and failing if the indicated file does not exist. When you select this option, the specified parameter value must be a sub path to a single file under the data store root path. For example, if the data store root is /bucket/folder, and the file is test.csv in that folder, then the parameter value should be just test.csv. The system will add the root path automatically and will not allow an alternative root path to be used. If the file is not found, processing will fail instead of processing zero records as the Based on File Path Pattern Parameter option does.
Node error behavior
Many analysis nodes do not fail outright upon a problem occurring, instead logging an error and continuing. The analysis only fails when the quantity of logged errors exceeds a defined threshold. Now, you can configure the analysis designer to test values after a node completes and cause the analysis to fail if required values are not present. You can achieve this new behavior by using the new FAILUNLESS function in a computed column's expression. This function throws an error that causes the analysis to fail if required values are not present.
For example, the HTTP status code of a REST API Call node might be checked for a value of 200 to ensure downstream node processing will be correct, and cause the analysis to fail otherwise. This would be done by adding a Compute node and computing a Boolean value using the FAILUNLESS function.
Access via proxy
Previously, if you chose to limit outbound internet connections from the application server or execution engine, you could not fully utilize the Data360 Govern or Spectrum OnDemand integration. Now, you can specify access through a proxy server for both Data360 Govern and Spectrum OnDemand. This allows on-premise or single-tenant customers to establish tighter internet access rules.
Group By node
The Group By node has been enhanced to allow the analysis designer to directly specify aggregation fields on the Group By node Properties panel. This speeds up and simplifies the analysis designer's task compared to using the node sheet actions to add aggregate fields, and then rename them.
Search screen preferences
The system has been enhanced to remember customization's that you have made on each search screen you use, including re-arranging, sizing or hiding fields.
Email information in tooltip
A tooltip with the user's email address is now displayed when listing users to be added to groups or environment groups. This helps to identify the correct user when first and last name information is incomplete or insufficient to identify the desired user.
Download audit trail data
Added the ability to download audit trail data from the audit trail page, and a new GraphQL API queryAuditTrailDetails() for querying audit trail data.
Corrected issues
| Issue Summary | Issue Number |
|---|---|
| Fixed a dashboard issue where not all error messages were shown when there were multiple dashlets with errors. | ISX-21317 |
| Fixed a query error that occurred in the query filter expression of a Case Store when a single argument was used in an IN or NOTIN function. | ISX-21218 |
| Improved permission-related error messages in process models. | ISX-21309 |
| Added validation for work ID in the terminateStageExecution, rerunStageExecution, and rollbackStageExecution GraphQL APIs. | ISX-21197 |
| Fixed an issue in data grids where data store field values were not displayed using the field's display format when specified. | ISX-21355 |
| Fixed an issue that prevented sorting from working in the Audit Trail page. | ISX-21367 |
| Fixed a View Dashboard error which occurred after clicking Cancel on the New Dashboard dialog. | ISX-21469 |
| An error is now shown when viewing or editing a data view if the current storage type is invalid. | ISX-21381 |
| Added a READ permission check on the pipeline item used in the GraphQL APIs createPipelineItemWatchers(), isPipelineItemWatcher(), and deletePipelineItemWatcher(). | ISX-21393 |
| Fixed a chart rendering issue that occurred when dimension series were used. | ISX-21386 |
| When a malformed request URL causes a HTTP error, a custom error page is now shown, rather than the standard Tomcat error page. | ISX-21459 |
| The performance of the execution history screen has been improved. | ISX-21450 |
| A new tab now opens when pressing CTRL and clicking a task in a process model, or when clicking the Go to Selected Stage button in the Show References or Show Usages dialogs. | ISX-21422 |
| Fixed an issue where adding data quality rules on the Profile tab could cause the profiling execution of the data store to fail due to NullPointerExceptions. | ISX-21466 |
| Fixed an issue that prevented low volume data view executions from completing due to exceeding the S3 connection pool limit. | ISX-21370 |
| Fixed an issue where following a hyperlink cell in a dashboard produced an invalid URL and the navigation failed. | ISX-21361 |
| Fixed an issue that prevented context menus from being fully visible on the Pipelines page when the menu was near to the bottom of the screen. | ISX-21318 |