Latest version release notes (7.1.4) may be found below and in the attached pdf along with those for the previous 7.1.x releases.

Overview

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), ISA and Mass Maintenance (formerly dspCompose) must update security roles when upgrading to 7.1. Refer to the Centralized Security Migration Manual for important information about using security in the DSP in version 7.1 and later. Consult this manual BEFORE updating to 7.1, as an analysis of current security assignments must be completed before the DSP can be updated.

NOTE: The following SAP products are compatible with the DSP 7.1.4 release:

• SAP Information Platform Services 4.2 SP6
• SAP Data Services 4.2 SP12
• SAP Information Steward 4.2 SP12

However, these are not compatible with MS SQL Server 2019. For full DSP integration with these products running on MS SQL Server 2019, clients must wait until SAP releases MS SQL Server 2019 compatible versions. This is currently anticipated at the end of Q2 2020.

NOTE: The address for Syniti support has been updated to https://support.syniti.com.

Align Column Encryption State for key Target Source column in Collect Before Upgrade

A new feature was introduced in DSP 7.1.3 whereby the SAP connection settings on a Collect Target Source are moved to a dedicated Data Source Registry record. During upgrade, the following DataGarage dgTargetSource table columns are used to create the new DSPCommon Data Source Registry records. 

As a result of these changes, BEFORE UPGRADING to version 7.1.3 and later, you must review and confirm that the encryption state of these two sets of columns matches. If you do not confirm that the encryption state is identical in these two sets of columns, mixed data could be saved in the column when the DSP is upgraded. Access the Data Source Column Encryption page in System Administration. The Status field indicates issues with encryption that must be corrected before upgrade. 

Enhancements

Advanced Data Migration

Console

When adding a wave to the Wave: Process Areas page, if a Target System (which is on the Vertical View) was not selected prior to saving the record, a warning message displayed. If the user canceled the record at this time, the record still saved and allowed the wave to be further configured. This error caused issues later in the migration process because target reports are not generated until a Target System value is set. To alleviate this issue, the insert method for the Wave: Process Areas page was changed from Horizontal Insert / Switch to Vertical to Horizontal / Switch to Vertical, which requires the Vertical View to be saved in order for the data entered on the Horizontal View to be saved, i.e., requires a user to select a Target System before the wave record can be saved.

Syniti Data Replication

The DSP is now compatible with Syniti Data Replication 9.6.3. When upgrading to DSP 7.1.4, an additional step is required to upgrade Syniti Data Replication to 9.6.3.

Data Stewardship Platform (DSP®)

Collect

The Connection Type field on the Target Sources page now supports a Connection Type of IG Universal Connect as expected. Previously, when IG Universal Connect was selected as the Connection Type, the following error message displayed: “Target Source has Data Services connection type and the Source connection type is not compatible. Correct the Source "Connection Type" or the Source "Data Services Connection Type.” The webTargetSource_ConnectionTypeDataServicesIDVal view was modified to reflect support for the Connection Type of IG Universal Connect.

Online Help

A new topic was added: Create Custom Authentication Plugins.

Updates were made to the following topics to improve clarity:

• Append Utility Columns to All Tables
• Allow Mapping of Utility Columns

Resolved Issues

An issue occurred when performing an import of an .xlsx Excel file: a column with both an Excel format of Number and a defined number of decimal places was sporadically imported with additional decimal places (this was not an issue for .xls Excel files). For instance, an entry of 16.44 on the spreadsheet was imported as 16.44000001 in SQL Server. [DSP70-905]

Advanced Data Migration

Map

• An issue occurred when attempting to auto-generate a full construction page using the Sync to Map functionality on the Targets Validation rules failed to run when the values for the target lookup table did not match the associated values for the target table. The full construction page is now auto-generated without error.
  [DSP70-877]
• Auto-generated list boxes failed to store selected values correctly when the lookup table contained more than one target field. Validation rules run as expected and full construction pages are auto-generated as expected.
  [DSP70-877]

Master Data Management

An issue has been fixed where an “Object reference not set to an instance of an object” error message displayed when the Auto Finish Role checkbox on the Scenario (Role) page was enabled for a role and if the role returned validation messages. A role with Auto Finish Role enabled now works as expected: if enabled and if there are validations returned, the boaStatus icon on the Request Role page is set to validation failed. A user can click the Validate button on the Request Role page to see the validation messages. [DSP70-950]

Data Stewardship Platform (DSP®)

DSP Upgrade Impact:

When upgrading from DSP 7.1.2 or below to 7.1.3 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]

Collect

• An issue occurred with building Data Services packages. When adding a Where Clause to a table in Collect and then building a Data Services RFC package, the Where Clause was not added to the job initially; a second build was required. A similar issue occurred when building an SAP RFC package. The issue has been fixed and these packages now build as expected. [DSP70-837]
• An issue occurred when adding a target source with connection type SAPAPPSERVER on the Target Sources page and attempting to build an RFC package for a table using this target source. The package build failed. The issue has been corrected and the build now completes as expected. [DSP70-962]
• Collect was writing Data Services packages to the incorrect repository. Several changes were made to fix this issue:
  • The Target Sources - DataServices Connection page is now read only. The data services connection information is now retrieved from the Data Source Registry page in Common.
  • A validation rule was added to the Tables and Target Sources pages to ensure that the SAP DataSource is populated on the Target Sources page if one or more RFC packages are registered (on the Tables page).
  • A new Data Services connection type, Oracle12c, was added.
  • An error with the Test Connection button on the Targets page was fixed. Previously, when the Data Source was registered on the Targets page and then renamed or removed from the Data Sources page in System Administration, an error displayed when the user clicked the Test Connection button on the Targets
  • Logging for namespace override options was added to Common. If the SAP Namespace check box on the Data Source Registry page is not checked, DSP checks for a value in the Rfc Name Space Option field on the Parameters-Collect If a value is not set, the DSP overrides the logging configuration settings with “namespace." [DSP70-807]

System Administration

An issue occurred when the Set Password And Notify User button on the Users page was clicked for a UserID that contained spaces. As a result, the following error message displayed when the user tried to log in with the UserID and temporary password: "The website could not finish processing the current request due to an unexpected system error." The issue has been fixed; the error message no longer displays in this scenario if the UserID contains spaces. [DSP70-926]

Information Governance Universal Connect

An issue occurred when attempting to create an Information Governance Universal Connect template. When a user clicked the Boomi Process ID list box on the General tab on the Vertical View of the Template page, the expected list did not display. The issue has been corrected, so the list of Boomi processes generates as expected. [DSP70-787]

Updated 4/9/2020