What's New in Syniti Solutions 7.2.1

Release Date: 6/10/2020

This topic contains:

NOTE: If you are upgrading from 7.0.6 or below, you may need to migrate your security settings to use centralized security. Users of Data Quality (formerly dspMonitor), Master Data Management (formerly dspConduct), and Mass Maintenance (formerly dspCompose) must update security roles when upgrading to 7.2.1. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the DSP in version 7.2.1 and later. Consult this manual BEFORE updating to 7.2.1, as an analysis of current security assignments must be completed before the DSP can be updated.

Refer to the Product Certification Matrix for the versions of third-party products that this release has been certified against.

Enhancements

Advanced Data Migration

Console

Object owners can manually track status for an object’s Relevancy, PreLoad, PostLoad and Program Type. These statuses will be used as input to Migration dashboards in the Knowledge Tier in a future release. Refer to Track Report and Load Program Status for more information.

Master Data Management

The Vertical View of the Scenario (Roles) page has two check boxes that, when both checked, are not compatible:

  • Auto Finish Role
  • User Response Required On Warnings

If a role is auto finished, then there is not a user available to provide the response to any warnings. Therefore, a validation message was added to the Scenario (Roles) page to notify users that when both check boxes are checked, they are not compatible with each other.

Data Quality

A Documentation tab with an External Reference field was added to the Vertical View of the following pages:

The External Reference field displays hyperlinks and supporting commentary that demonstrate the connection from data-related assets in the DSP to external references in other platforms and applications. Syniti recommends a report be linked to a term, rule or data set in the Knowledge Tier.

Data Stewardship Platform (DSP®)

The following improvements were made to security auditing:

  • Security events, which can be viewed on the System Logs page, were updated:
    • The target entity name now displays when adding or removing Security Definition key values to roles and users.
    • The role name now displays for role deletion events.
  • Updates made to security (as in, insertions, deletions, and updates to the RoleWebAppGroup table) as a result of updates in DSP Add-Ons are now logged in the security logs and can be viewed on the System Logs page.

Resolved Issues

Advanced Data Migration

Construct

Corrected an issue that occurred when adding a Full Construction source to a target. The resulting data construction pages and tables included zLegacy<KEY> columns that were added as keys on the construction page and could not be edited. Users were prevented from creating records on these pages. With the fix, the zLegacy<Key> fields are not included in the pages and tables when adding a Full Construction source to a target. As is standard, full construction expects records to be populated with data in values that relate to the target system. If data is being constructed for a record that has not had a target number generated yet, i.e., not loaded, a legacy record number can be used. During the migration process, this value can subsequently be translated to a target value using cross reference tables. [DSP70-949]

Master Data Management

Two issues occurred on the Request Role page where the Finish button was behaving incorrectly. The first issue occurred when a user clicked the Finish button to finish the role. The button became disabled, then enabled again, even though rules registered to the Finish event were still executing. The user could then click the Finish button a second time, executing the rules again, resulting in errors in the data and posting errors. The second issue related to validations running twice, causing performance issues in scenarios that had long running validations. With this fix, once the Finish button has been clicked once, it is either disabled or overlaid with a spinning icon. Users cannot click the Finish button a second time, and current foreground processing and validations only run once. [DSP70-979]

Data Quality

  • When a report was added to a group on the Your Groups page, in order for the user filter to be applied to the report, the report had to be executed and then either the user filter had to be validated or a new user filter had to be created. This issue has been fixed and user filters for a new report added to a group now function as expected: as long as the user filter has been set up, the filter is applied during the first execution of the report. [DSP70-1001]
  • Previously, if there were duplicate records on the Data Quality Score Thresholds page, then duplicate records appeared on the Target Table Threshold and the Target Table Column Threshold pages. This duplication was caused by incorrect join conditions on the webDQSThrewsholdList view. To fix this issue, the view now has joins on the “Name” field. [DSP70-923]

  • The Process and Process For All Users icons on the Your Groups page were always inactive because the Monitor Group Security Definition Events (webSecurity_GroupUserAdd), which inserts records into the ddGroupUser table, did not have the boaStatus field populated. To fix this issue, the webSecurity_GroupUserAdd stored procedure was updated to default an initial value of 0 (New or Dirty) for boaStatus. [DSP70-925]

  • A report can appear multiple times on the Your Object Reports page because it could be assigned to multiple groups, have different filters applied, and be executed independently. To communicate the duplication to users, a Report Warning icon has been added to the Your Object Reports page with the following options:

    • No warnings
    • Report appears multiple times because it has different User filters in different Groups

    [DSP70-930]

  • The Columns button on the Report Target Tables page displayed an incorrect count. The count was the number of target table columns for all reports. The count now displays the correct value: the number of target table columns assigned to the target table for that specific report, i.e., the number of records on the Report Target Table Columns page. [DSP70-1009]

Data Stewardship Platform (DSP®)

DSP Upgrade Impact:

  • When upgrading from DSP 7.0.6 or below to 7.2.1 or above, Collect target sources that include SAP connection details will automatically have the saved connection string details converted into a new Data Source of type SAP Application Server. The newly created SAP Application Server Data Source will then be assigned to the Collect target source. After upgrading, it’s important to review and test all Collect target sources to ensure they function correctly. [DSP70-740]

Enhancement Requests From Users

 

WARNING: Customizations made to any component of the delivered Syniti Solutions will be overwritten in the next upgrade. To preserve customizations, make a copy of the customizations prior to applying any upgrade.

A customization is a change to the underlying source code, which differs from configuration – normal setup of the software, such as setting up workflows and defining parameters via the configuration pages.

Changes in Previous Versions

Previous Versions of Help

Help Build Date:September 17, 2020 04:23:27 PM