What's New in Syniti Solutions 7.1.3

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.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.3 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.

Database

Table

Column

Database

Table

Column

DataGarage

dgTargetSource

SAPPassword

DSPCommon

ttDataSourceRegistry

SAPPassword

DataGarage

dgTargetSource

SAPUserID

DSPCommon

ttDataSourceRegistry

SAPUserID

DataGarage

dgTargetSource

Instance

DSPCommon

ttDataSourceRegistry

SAPSystemID

DataGarage

dgTargetSource

RfcNameSpaceOption

DSPCommon

ttDataSourceRegistry

RfcNameSpaceOption

DataGarage

dgTargetSource

SAPSystemNumber

DSPCommon

ttDataSourceRegistry

SAPSystemNumber

DataGarage

dgTargetSource

Client

DSPCommon

ttDataSourceRegistry

SAPClient

DataGarage

dgTargetSource

SAPServerHost

DSPCommon

ttDataSourceRegistry

SAPApplicationServer

DataGarage

dgTargetSource

Language

DSPCommon

ttDataSourceRegistry

SAPLanguage

DataGarage

dgTargetSource

SAPMsgServerHost

DSPCommon

ttDataSourceRegistry

SAPMessageServer

DataGarage

dgTargetSource

SAPLogonGroup

DSPCommon

ttDataSourceRegistry

SAPLogonGroup

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.

This topic contains:

Enhancements

Data Stewardship Platform (DSP®)

  • Starting with DSP release 7.1.3, the Exclude Client Fields check box on the Vertical View for a system type on the System Type Import page in Common is checked by default. If this check box is not checked and the system type is built with the client included, all target tables and check tables include this field. This means that every lookup table will become a multi-value key value mapping, which diminishes the visibility of true multi-value key lookup tables. Users can uncheck the box to include Client fields if needed.

Collect

  • The AddedOn field on the Job Detail page's Vertical View now displays date and time, so users can review failed records from the Test Connection Service page in time sequence order.
  • The performance of Collect extracts using the SAP RFC and BOA RFC package types has been significantly improved. This performance improvement was achieved through faster data parsing and the use of bulk insert functionality.

Advanced Data Migration

Map

To improve the user experience, the Submit and Submit All events on the Field Mappings page now run in the background instead of in the foreground.

Online Help

  • Added this note to the Validation Rules topic to clarify the use of Warning validations:

    NOTE: When creating an event that will be called indirectly, do not use Warning validations. Use Error validations. Warnings are intended for user interaction. Validations running on events used as business rules of the type WebApp Event or WebApp Event (Private), or as Event Tasks added to a job, are non-interactive. In these cases, validations are only used to stop the business rules of the event from running (or, in the case of a 'Run On Validate Fail' set of rules, to allow the business rules to run). Refer to Set Parameters for a Public WebApp Event, Create a WebApp Event (Private) Business Rule, and the Job Queue Task page for more information.

  • Added topic Track - Changes Per Week.

Mass Maintenance

Syniti Data Replication (formerly DBMoto)

System Administration

Resolved Issues

Data Quality

  • An issue occurred so that the filter criteria set for one report repository altered the Report View selections for another report repository. If the user set Report View filter criteria, for example, of tv*RptSel, for Repository A and then created Report Repository B with a Report View with filter criteria tv*Sel, the view set for Repository B would be applied to Repository A. When a user created a report in Repository A, the view set for Repository B would incorrectly display along with the view set for Repository A. With the fix, only views set for a particular repository display when creating a report for that repository, as expected. [DSP70-874]

  • An issue occurred that caused some user names not to display correctly in two fields when the user was not assigned to the WebApp group. The User ID field on the Group Users page and the Group Owner field on the Report in Groups page were affected. Instead of displaying the User ID concatenated with the User Name, those fields displayed only the User ID, which in many systems is meaningless information. With this fix, the User ID concatenated with the User Name displays in these two fields as expected. [DSP70-815]

Data Stewardship Platform (DSP®)

If the password for a data source resulted in an encrypted value longer than 128 characters, the Common Service page "Service - DataServices Status" failed with a message of "Failed to enable constraints. One or more rows contain values violating non-null unique or foreign-key constraints." With the fix, the field length has been updated, and the Service page runs as expected. [DSP70-867]

Collect

  • An issue occurred with the Advanced View Builder tool in Collect where, when a user built views for a given database, the views were created with the where clause on every column whose value related to the SAP Client and/or Language field. This rendered the view unusable. The workaround was to use the View Builder tool in Common. The issue has been corrected, so using the Advanced View Builder tool in Collect builds a view as expected. [DSP70-902]
  • In version 7.1.2, there was a Known Issue with encryption if running SQL Server 2019 with DSP. In some cases, values that were set to encrypted in Collect were not encrypted correctly in the table column. This issue has been corrected, and values are encrypted and decrypted as expected. [DSP70-898]

  • An issue occurred where, when a user tested a connection and the test failed for either a target or a target source, the service page execution ended without testing the remaining connections. The issue has been corrected, so that when a connection fails, service page execution continues and completes testing on all connections. Each record in the dgTarget or dgTargetSource tables updates with the appropriate connection status, depending on the outcome of each connection test. [DSP70-561]

  • The Build View process on the Advanced View Builder page in Collect completes without an error message and drops every SQL Server view in the database for views. DSP is then unable to recreate the views since they no longer exist in the DATABASE FOR TABLES list box. To prevent all views from being deleted, a safety check was added to prevent the DATABASE FOR VIEWS and the DATABASE FOR TABLES fields from being in the same database: a view selected from the DATABASE FOR VIEWS list box is removed as an option from the DATABASE FOR TABLES list box. The same is true for a database selected from the DATABASE FOR TABLES list box. [DSP70-878]
  • With the absence of a NUMERIC data type rule, Collect defaulted to the ANY data type, which uses nvarchar with the same length as the source field. If the source data contained a value that was at the character maximum for numeric and was negative, the value caused an error. To fix this issue, a NUMERIC data type rule was added to the SQLSERVER Source Connection Type page and is formatted the same way as the DECIMAL data type rule. [DSP70-464]

  • In previous versions of DSP, Collect copied and used connection information from the assigned target source into the dgTarget and dgTargetSource tables. If the target source was required to connect to an SAP application (rather than database), the SAP Connection details were also populated on the target source record and stored in the dgTargetSource table. To ensure that connection information is stored in a central location, this release introduced the following changes:
    • Collect no longer copies target and target source connection information into dgTarget and dgTargetSource tables. Instead, Collect uses the connection information stored within the Common Data Source Registry page.
    • The ConnectionString column has been removed from the dgTarget and dgTargetSource tables.
    • Instead of entering the SAP Connection details on the target source record, users must select the Common Data Source Registry connection associated with the relevant SAP application / client.
      • With this change, the following columns within dgTargetSource have been removed or made read-only:
        • Client
        • Instance
        • Language
        • RfcNameSpaceOption
        • SAPLogonGroup
        • SAPMsgServerHost
        • SAPPassword
        • SAPServerHost
        • SAPSystemNumber
        • SAPUserID [DSP70-740

        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]

Integrate

  • An issue has been fixed for 64-bit DSP instances that prevented non-dialog SAP users from creating Integrate BAPI/RFC Templates and posting an Integrate process. With this fix, using SAP non-dialog users/service accounts in Integrate is supported, so long as the user has correct SAP authorizations. [DSP70-915]
  • An issue occurred in 32-bit DSP environment when the same non-dialog SAP user account was used in multiple different data sources, each with different SAP logon languages. This issue occurred when a user posted using one connection ID in language A and then, when that process had completed, attempted to post a second process using a second connection ID in language B. The second post failed, generating an error message: Please logon with a dialog user. This issue has been corrected so that the second background process now completes as expected. [DSP70-872]

Common

  • The View Builder tool in Common has been used as a workaround when the Advanced View Builder tool in Collect does not function properly. The Advanced View Builder tool in Collect now functions properly. [DSP70-902]

Enhancement Requests From Users

As the result of feedback from the online help, the User Template Filter topic was updated to include more detailed information about the VALUE field.

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 11:20:20 AM