New in 11.1 - Data360_DQ+ - Latest

Case assignment for manually created cases

When new cases are created manually, the user who initiates the case can now choose to assign it to themselves. Previously, manually created cases were not assigned an owner during creation.

Case edit and transition rules

The definition of a case store state within its workflow now includes an option to prevent the editing of a case in that state. This allows the case store designer to better ensure compliance with workflow approvals and verification of values.

Additionally, case store designers can establish rules for case transition, ensuring that a case can only be transitioned when certain conditions are met, for example when all fields are completed and the values are within a specified range.

Power User access to Executions menu

Users in the role of Power User can now access the Admin > Executions menu. This makes it easier for Power Users to monitor executions for stages that they are permitted to view without having to navigate to the stage with the Pipeline and then choose Executions.

Executions page Started By column

A new column, Started By, has been added to the Admin > Executions page, containing the user ID of the user who started an execution manually. Previously, only the Admin > Audit Trail page could be used to determine this information. This makes it easier for users to collaborate on resolving issues related to the operation of the system.

Environment Manager access

A user in the role Environment Manager now has access to the Admin > Environments page, where they can maintain certain aspects of the environment. This allows you to provide management responsibilities to users without making them full Administrators.

The Admin > Audit Trail screen is now available to users with the Environment Manager role. This allows designated non-Administrator users to be able to access this information.

Streaming Join node advanced configuration

The Streaming Join node has been enhanced so that you can define more advanced join criteria with conditions such as outer joins with timestamp ranges on watermark fields.

Field code set definition

Defining field code sets has been improved in two ways. A new Add Multiple option allows you to easily specify multiple code set values at one time. Additionally, you can now reference a data store that contains your code set and quickly import or refresh them from that source.

Rename dashboard columns

The header label for all columns in a grid dashlet can now be customized. Previously, only the measures could have their header labels customized. This makes it easier for dashboard designers to lay out grids without impacting other dashlets that use the same underlying data store or data view fields.

Other changes

• The system now imposes a file size limit of 5 MB on the files used for data store creation to reduce the chance of failure during generation of fields.
• The system now generates download file names with more identifying information. Dashlet downloads, for example, are now generated as <dashboard_stage_name>.<dashboard_name>.<dashlet_title>.data_export.csv. This helps you to quickly identify the right downloaded file.

Corrected issues