What's New in Syniti Solutions 7.4.7

Release Date: 11/23/2021

This release contains:

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


NOTE: If psaCollate is installed on the instance you are upgrading, you must uninstall it before upgrading to this version. 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: When upgrading to Stewardship Tier 7.4.5 AND LATER, 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.

NOTE: When upgrading to Stewardship Tier 7.4.6 AND LATER, open a support ticket with Syniti Support to request a new license in order to use Entity Validation and Migration Reports. If using Entity Validation, you must also request a Melissa license.

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.

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 this version. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the Stewardship Tier in this version and later. Consult this manual BEFORE updating to this version, as an analysis of current security assignments must be completed before the Stewardship Tier can be updated.

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.


Master Data Management

  • The Where Used Report is now available at the scenario, role and task level. This report displays the associated business processes, scenarios, roles and tasks for the selected item and provides further insight than the Where Used graphical interface available in previous versions. For more information, refer to View a Role's Scenarios and Tasks, View the Roles and Tasks Assigned to a Scenario and View a Task's Scenarios and Roles.

  • Though the Stewardship Tier runs on a case insensitive database collation, SAP Language is now case sensitive. Changes have been made throughout the Stewardship Tier to reflect this change, including modifying the SAP Language field on the Languages page in System Administration to be case sensitive. Content, custom applications, construction server pages or queries that use any of the following objects may need to be modified to align to the case sensitive collation:

    • webSAPLanguageList view in DSPCommon

    • apiCranSoftLanguageSel view in DSPCommon

    • dspMonitor_AccPak

  • To address queue contention when multiple MDM categories were processing requests concurrently, users can now control the queue (and services) that is used to process each MDM WebApp/category. Set the queue on the Category page's Vertical View in the Posting Job Queue list box. Refer to Set Posting Options at the Category Level for more information.

  • User access to request roles has been updated to tighten security. Users with configured permissions can set a further level of restricted security that affects request role access across MDM. Using Restricted positions, a user can only access a request if that user is assigned to a position with both a role in that request and the business process for that request. Refer to Set Restricted Position Access for more information.

  • The #instance# value can now be added to the subject and body of workflow notification emails allowing recipients to know which system has sent the workflow. The instance is set on the Parameters page within System Administration in the Instance field and must be set on-site. By default, the Instance field is blank. Refer to Use System Values for Dynamic Substitution at Run Time for more information.

  • Use an API procedure now included in the Stewardship Tier to create any parameter with any value required in a workflow. Refer to Use an API Procedure to Create Custom Workflow Parameters and Values for more information.

  • Users can add roles to scenarios more quickly than in previous versions of MDM. Before, all of the role’s associated tasks were set as active and assigned to the scenario, even though many of these tasks were not needed. This required the user to inactivate the unwanted tasks manually. With 7.4.7, when a role is assigned to a scenario, that role’s tasks are inactive by default. The user must activate the role’s associated tasks by enabling the ACTIVE IN SCENARIO ROLE check box on the Scenario Role Task page.

  • Corrected an issue where when users added a role to a scenario, all fields accessed from the role’s tasks via the Link to Page button were added as columns, even though most were not relevant. To decrease the time to configure tasks, after a user activates the task for the scenario role, only relevant task columns are added to the table.

  • We have changed how columns were automatically added to the Content WebApp. By default, if an inactive task is added to a scenario role, the task’s columns are not added. Additionally, when a role is added to a scenario, the columns on all of that role’s tasks are not added by default. The Fetch Columns feature allows users to select a task and retrieve columns. Refer to Fetch All Columns for a Task for more information.

Stewardship Tier

  • AWS RDS is now supported as a database server with certain configurations. Refer to the section Hyperscaler - AWS Hardware Requirements in the Requirements Guide for more information.

    NOTE: For the 7.4.7 version of the Stewardship Tier, the source and target for CTS and Promote must both be RDS or both be non-RDS databases.


  • Users can now import a large number of target source tables using Excel Integration on the Tables page. Refer to Use Excel Integration for more information.

  • The ODBCHANA connection type (on the Source Connection Types page) now supports downloading data from a view. This enhancement enables the users to download views via Collect in order to gather the required metadata for the SAP HANA scanner to run. As a result, the Fetch Tables action that is run for a Collect target source where the Connection Type is ODBCHANA now fetches tables and views on a HANA system.


The Debug Logs page was enhanced to provide a limit to the amount of time that debugging is active along with the start and stop times and the number of hours for retention of this log. This will reduce the risk for system slow downs due to this process running.


  • An error displayed when attempting to use the Structures-Data “Administration-Role” because the Sub Table “RoleWebAppGroup'' only had key fields set up for the comparison process. This Sub Table now includes non-key fields in the comparison process, allowing the “Administration-Role” Data Structure to work as expected.

  • A new setting on the Application Parameters and the Packages page is available, called Default Include dgSAP Views. This check box either includes or excludes objects dependent on SQL objects in databases prefaced with “dgSAP” (such as dgSAP_Dev, dgSAP_QE, etc.) from the transport. While the Parameter configuration is applied to all new packages, this setting can be overridden at the package level.

  • When a package is compared, differences are queued to identify what to transport. If any object within the package failed, all objects in the package were excluded from the transport, which made it impossible to tell which objects failed and which transported successfully. The error process has been improved so that if an object fails to transport, another comparison is run so only objects that failed remain queued to transport.

  • Previously, it was mandatory for a table being compared to have at least one non-key column. However, use cases existed where tables that only contained keys needed to be compared and transported. Now, tables that only have key columns (i.e., the KEYS check box on the Structure - Data Table Columns page is enabled) can be Compared and/or Synced.

  • Users may now transport data within a SQL table to the destination server. This feature allows users to move data in mass by clicking the Send Data Toggle icon on the Package - Object Comparison page.

  • Power Users may now temporarily unprotect a database in order to transport SQL Object changes made to delivered applications for a package. Enable the Allow Delivered Database SQL Changes check box on the Application Parameters page and the same check box becomes available on the Packages page. Both settings must be enabled to transport core modifications.

Syniti Data Replication

This version of the Stewardship Tier is compatible with Syniti Data Replication 9.8.1.

Resolved Issues

Master Data Management

  • In previous versions, when users added a role to a scenario, all fields accessed from the role’s tasks via the Link to Page button were added as columns, even though most were not relevant. To decrease the time to configure tasks, after a user activates the task for the scenario role, only relevant task columns are added to the table. [DSP70-1594]

  • Corrected an issue that allowed requests in the wrong status to display on SLA Summary Notification workflows. Requests in a Cancelled, Deleted, or Duplicate status no longer display on these notifications. [DSP70-1625]

  • Previously, the Auto Extend Display feature did not work. Now, it works correctly. If this check box is checked on the Role page’s Vertical View, the tasks within the role display as read-only to all other users within the scenario not assigned to this role. [DSP70-1623]

  • Corrected an issue that caused the Late Notification workflow to be repeatedly sent in error. Now, when a request is late, the workflow is only sent when the Late Notification Service page is run. [DSP70-1606]

  • Previously, if multiple CalendarIDs were associated with a role, multiple workflow emails were sent. Now, if there are multiple calendars, workflow emails are sent in order of the SLA deadline, starting with the earliest SLA deadline. [DSP70-1422]

  • Previously, an excess number of records in the audit tables prevented workflow emails from being sent. To fix this issue, we added a new field to the Parameters page: Workflow Max Aggregate Records. This field controls the number of records included in the audit workflow emails. The default value is 200. [DSP70-1624]

Stewardship Tier

  • Previously, when directly linking to another page’s Vertical View, and then attempting to filter and select a value from a combo box, instead of populating the filtered results, the page redirected to the Horizontal View of the original linking page. The Filter function on combo boxes in the Vertical View now works as expected. [DSP70-1607]

  • Previously, when a role was assigned to a user with no other roles on the User Roles page, security to that role was not granted until a second role was added. Now, security to the role is immediately granted as expected. [DSP70-1588]

  • Previously, a page rendering with lazy load did not display all records when viewing the screen at a resolution of 100%. Now, a scroll bar is available to allow users to scroll and access all records on the page. [DSP70-1605]


An issue occurred when posting data using a template with an After Post rule. The system always used a default timeout of 30 seconds for processing, regardless of the Command Timeout setting set for the data source. To correct the issue and minimize timeouts, postings that use After Post rule templates now use the timeouts set on the Data Source Registry page for the data source. [DSP70-1587]

Advanced Data Migration (ADM)


Fixed an issue that occurred when adding a new Migration Milestone to the Waves page. While saving the new milestone, if the field NAME was left blank, the system would save the milestone. With the fix, the NAME field is required and the milestone saves as expected. [DSP70-1463]

Enhancement Requests From Users

  • Updated the Password Require Special field on the Parameters page in System Administration to include the special characters.

  • Corrected the description of the Show in Navigation functionality in multiple topics throughout help, including the field description, which was updated to: “If checked, this column displays in the failed records Bulk Execution results. By default, only the first column on the page displays in these results. Refer to View Bulk Execution Results 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 04, 2022 04:21:26 PM