New in 10.0 - Data360_DQ+ - Latest

Custom Security to Offer Readability Extension to Parents

Enhanced pipeline item's Custom Security settings to check selected environment groups for Read permission to parent items, and offered an option to grant Read access to parent items.

Data Catalog for Data Integrity Suite Governance

Previously, when sending metadata to Data360 Govern, DQ+ would always create and send data catalog references. This would cause the "Data Catalog" left navigation item to appear in standalone Data360 Govern systems. In this release, the system will not create reference lists or references for the data catalog unconditionally. It will only create references when the reference lists already exist, as is the case for the DI Suite governance module.

Increased Delimited Field Size

Previously, the system limited delimited field parsing to a maximum field size of 4096 characters. Now, the system will use the maximum length specified for a field definition for parsing that field. This allows customers to have longer fields for situations like a field that will contain an email body used in a process model "Notify from Data Store Task" node.

Enhanced Pipeline item’s custom security settings to offer Readability Extensions to Parents

The pipeline item’s custom security settings are now enhanced to check selected environment groups for Read Permissions to Parent items and offer an option to grant Read access to Parent items.

In this release we have also added the ability to add Read Data permission to the references of a stage in the pipeline Settings->Security tab when custom security is selected. When a security manager is editing the security for a dashboard which references data views and data stores as data sources, the security manager shall be able to quickly see those stages and ensure their Read authorization for anyone able to view the dashboard.

Additional Profile Attributes for Observability

The system now sends additional profile attributes for the profile source (Data360 DQ+), profile series, and profile type (sample or full). The profile series value may be input on the profile tab when the profile results are marked to be sent for governance.

Other Changes

• Improved selected stage location information: Previously, when viewing a stage in the Pipelines, the user may not be able to determine which pipeline and path the stage is within. Similarly, when choosing a stage in a process model or analysis, only the stage name is shown. With this enhancement, the system will now display the full path to the selected stage within the Pipelines screen. A node within a process model or analysis will show the full path to the stage. These changes help the user be aware of where the selected item is located at a glance.
• Preserving filters: Added preserving filters when user switches between Screens and across Sessions.
• Improved permission error message: Improved permission error message in analysis, data view, dashboard, process model, data store and case store screens.
• Define multiple value of filters: Added ability to define multiple initial values for filter fields with defined code sets.
• Case management email notification links: A new function, formatCaseViewURL, is now available when editing the javascript for a case state transition in workflow. This function produces a URL that will route the user to the desired search screen, filtered down to the single case that was transitioned. This improvement increases the productivity of case workers who are working cases via email notifications.
• Change primary stage for a dashboard: Previously, when a dashboard was created and the primary stage was chosen, the primary stage could not be changed. Even when none of the dashlets used the primary stage, the system maintained a reference to the primary stage which prevented that stage from being deleted. Now, when none of the dashlets in the dashboard refer to the primary stage, the user may change the primary stage on the dashboard settings dialog.
• Records tab configuration for case view/edit: Previously, the system chose which data store search to show on the Records tab when viewing a case. With this enhancement, the Case Store builder can edit javascript on the View/Edit screen definition to choose which Data Store to show on the Records tab using any of the fields of the current case. This allows the Case Store builder to choose the most productive default for a case worker.
• Hide or rearrange search screen columns: Currently, a case worker sees the result columns for a case or data store search screen as defined by the case definition. This enhancement allows the case worker to focus their results on the columns they need, in the order that they need them. This improves the productivity of the case worker.
• Restricted search screen visibility: Previously, the system shows search screens for a case store or a data store based upon the overall security settings for the stage. Now, the user defining search screens can define environment groups that can see the search screen. This allows user to control which search screens are available to end users of case stores or data entry within data stores.
• Improved selected stage location information: Previously, when viewing a stage in the Pipelines, the user may not be able to determine which pipeline and path the stage is within. Similarly, when choosing a stage in a process model or analysis, only the stage name is shown. With this enhancement, the system will now display the full path to the selected stage within the Pipelines screen. A node within a process model or analysis will show the full path to the stage. These changes help the user be aware of where the selected item is located at a glance.
• Search filter field initial operator: Previously, the system showed the initial operator for a based upon initial filter values. Now, the user defining the search screen can specify an initial operator appropriate to the type of field without specifying an initial filter value. This ability allows the search screen filter to be optimized for typical usage by the search screen designer.