What's New in Syniti Solutions 7.4.5

Release Date: 08/02/2021

This release contains:

NOTE: If psaCollate is installed on the instance you are upgrading, you must uninstall it before upgrading to 7.4.5. The collation technology is included in the product in 7.4.5 and later. To uninstall psaCollate refer to the Knowledge Base article Uninstalling psaCollate Prior to Upgrade.

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.4.5. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the Stewardship Tier in version 7.4.5and later. Consult this manual BEFORE updating to 7.4.5, as an analysis of current security assignments must be completed before the Stewardship Tier can be updated.
Refer to the Product Certification Matrix for the versions of third-party products that this release has been certified against.

NOTE IF YOU ARE UPGRADING TO 7.4.2 OR HIGHER: Please be aware that any JavaScript content added is stripped away and any remaining, safe HTML is displayed to users. In Stewardship Tier versions 7.4.1 and earlier, users were permitted to enter HTML and have it rendered in the UI or included in file downloads from the UI. There were no restrictions in place on what HTML/JavaScript text was permitted, leading to potentially dangerous cross-site scripting attacks. Refer to the Unsafe HTML/JavaScript removed in Stewardship Tier 7.4.2 Knowledge base article for more information.

NOTE: A new, critical, step has been added to the Post Upgrade section of the Installation process. After an upgrade to Stewardship Tier users must re-create their BAPI templates. Failing to do so will cause the posting of a BAPI template to fail. Refer to Re-create BAPI Templates in the Install Manual for more information.

New Features

Advanced Data Migration (ADM)

ADM is now delivered with a new Collation Aware Migration feature, which simplifies the handling of case-sensitive data through the end-to-end migration process.

The Stewardship Tier runs on MS SQL Server using databases that have a case-insensitive collation (SQL_Latin1_General_CP1_CI_AS). To avoid collation conflicts, Syniti historically required that all project-specific databases use the same case-insensitive collation and for consultants to handle case-sensitive data on a case-by-case basis. This new feature is now delivered with ADM so users can decide at the wave level whether the wave’s data is case insensitive or case sensitive, which makes for a much simpler process.

To aid users through collation decisions, there are several new validation messages where new data sources can be introduced to a wave, such as:

  • Adding a new data object on the Process Area: Object page in Console

  • Adding a new process area on the Wave: Process Areas page in Console

  • Changing a data object’s Data Source ID or Report Cache Data Source ID on the Process Area: Object page in Console

  • Changing a process area’s Target System Data Source ID, Data Source ID or Construction WebApp ID on the Wave: Process Areas page in Console

  • Changing a wave’s Target System on the Waves page in Console

  • Adding a new source data to a target table on the Target Sources page in Collect

  • Changing the Collation Type on the Targets page in Collect if the data source has a Collation Type in the Data Source Registry that is different from the one assigned to the target.


When upgrading to Stewardship Tier 7.4.5, data sources are automatically assigned with the Collation Type of General Latin Case-insensitive. This ensures that the ADM AutoGen continues to create SQL tables whose text columns have a case-insensitive collation.


To support the Collation Aware Migration feature, the following new fields are available on the Waves page to change the collation for a wave:

  • Wave Data Sources—Click to open the Wave Data Source Collation page to view any collation mismatches between the wave and the assigned data sources.

  • Collation Type—Displays the intended collation of data used in the wave. Options are:

    • General Latin Case-insensitive

    • General Latin Case-sensitive

  • Collation Issue—An indicator that displays if there is one or more conflicts between the wave’s Collation Type and the Collation Type of the assigned data source. Navigate to the Wave Data Source Collation page to use the generated report to fix the issues.

  • Toggle Collation—Click to switch the Collation Type between General Latin Case-insensitive and General Latin Case-sensitive.

NOTE: It is recommended that the Collation Type of all data sources assigned to a wave is aligned with the Collation Type of the wave. Refer to Change Collation for a Wave for more information.

Stewardship Tier (formerly Data Stewardship Platform (DSP®)


To support the Collation Aware Migration feature, the following two new fields have been added to the Data Source Registry page:

  • Collation Type—Displays the anticipated collation of text columns of tables in the associated database. It also controls the collation of table text columns that are created by the ADM AutoGen functionality. Options are:

    • General Latin Case-insensitive

    • General Latin Case-sensitive

    This field is available for the following data source types:

    • Migration Object Database (dsw%)

    • Target System Database (dg%)

    • Migration Source Database (sdb%)

    NOTE: The default value is General Latin Case-insensitive, which means the collation uses Latin characters and is case insensitive. Case-sensitive collation is only supported for Advanced Data Migration.

  • Toggle Collation—Click to switch the Collation Type between General Latin Case-insensitive and General Latin Case-sensitive.

    NOTE: It is recommended that the Collation Type of all data sources assigned to a wave is aligned with the Collation Type of the wave. Refer to Change Collation for a Data Source for more information.


Advanced Data Migration (ADM)

Target Design

In previous versions, when Utility fields were appended to tables, they were only identified by their column name, and did not include the corresponding, user-friendly Description field. Users can now add the Utility field’s description on the Append Utility Columns page. When the Append Utility columns are added to the target table, the description is added to the column Display Name. Refer to Append Utility Columns to All Tables for more information.


It is now possible to update empty legacy Description fields to include the description to assist while value mapping. Refer to Include Legacy Value Descriptions for more information.


The Copy Wave process now also copies the wave’s Collation Type.


If a wave and its associated dsw* have a case-sensitive Collation Type, Data Construction table text columns and columns in list boxes are also case sensitive.


With the new ADM Collation Aware Data Migration feature, reports need to be segmented to allow for case sensitivity. Since Windows does not consider case sensitivity, a new Segment Suffix field is available on the following reports so when Transport creates a new folder or reform name, the name is unique:

Mass Maintenance

External Data processing can now use the IMAP email protocol to connect to the account used for both External Request Scenarios and for External Data Processing with an External Data role. By default, the email protocol is POP3. The setting is configured in the new PROTOCOL field on the External Data Email Accounts page.

Stewardship Tier (formerly Data Stewardship Platform (DSP®


With the new addition of category values to Syniti’s REST API, category values can now be:

  • downloaded from data sets, goals, initiatives, missions, policies, rules, systems, terms and visions.

  • uploaded to new rules, terms, systems and data sets.

  • changed on existing rules and terms.

Refer to Integrate the Stewardship Tier with the Knowledge Tier for more information. New use cases and page descriptions are listed in the Online Help section of these release notes.


The Compare event now considers the case sensitivity of data when code is compared across two environments.

Online Help

The following new use cases are available:

The following new use cases are available for Common:

The following new field description topics are available in Common:

Resolved Issues

Advanced Data Migration (ADM)


Corrected an issue on the Load Cycle Execution Plan page that allowed users to enter a higher number in the DEFECT COUNT field (the number of records that failed to load) than in the OPPORTUNITY COUNT field (the total number of records). With the fix, a validation has been added to prevent users from saving this invalid record. [DSP70-1293]

Target Source SQL Automation

Fixed an issue that caused an error to display when a user clicked the Map Source icon on the Automation SQL Target Source page. With the fix, when the user clicks the Map Source icon, Map’s Target Sources page displays with details about the source selected on the Automation SQL Target Source page. [DSP70-1290]


Fixed the hardcoded timeout that caused issues when rules with large amounts of data ran in Transform. The hardcoded value of 9999 has been removed. The stored procedures use the value in the Command Timeout field on the Vertical View of the Data Sources page in System Administration. [DSP70-1461]

NOTE: After upgrading to 7.4.5 and later, clients may need to increase their data source timeouts if there are timeout issues when executing rules in Transform.

Stewardship Tier (formerly Data Stewardship Platform (DSP®))


Corrected an issue when using multi-threading on a source refresh that caused the processing to hang. If the number of records in the CranPort package was large (6 million records) and the package was segmented, sometimes, the segmented table's job never left the job queue. Even though the table's extract completed, the refresh job remained "spinning" in Collect. The cause was Assemble writing logs out of order. With the fix, when Assemble writes logs, it waits until the rest of the log entries, run by background threads for that task, have finished before writing the next log entry. [DSP70-1330]


Corrected an issue introduced in 7.4.4 that caused the DURATION field on the Download Metrics page to always display 0 after a table refresh. The value in this field should be identical to the value in the DURATION field on the Tables page. With the fix, the DURATION field displays the correct amount of time it took to complete the table refresh. [DSP70-1473]


Fixed an issue that caused the Status icon on the System Types page to remain in Processing status after a System Type import, even after the import had completed successfully. Now, the correct status displays when the import is complete. [DSP70-1102]

Enhancement Requests from Users

Online Help

  • In Data Quality corrected the names of the industry-standard Quality Dimensions included with Data Quality on pages where the QUALITY DIMENSION field is described.

  • In Data Quality added links from the Manage Groups page to the Set Up Security page to make finding information about granting users access to reports easier

  • In Integrate updated the Create a Basic Template topic to include BDC Script and GUI Script in the list of template types

  • In Integrate added a note to the Import a BDC Script from a File topic to clarify functionality: "NOTE: The ability to record a BDC script has been removed from the Stewardship Tier 7.3 and later. BDC scripts can be created using the SHDB transaction in SAP and imported as described in this section or copied from an existing BDC script."

  • In Collect clarified functionality for the Table Rename and the Rename Table Template fields. Refer to Register Sources to Target and Manually Register Tables to Source for more information.

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:April 06, 2022 03:02:23 PM