What's New in Syniti Solutions 8.0.1

Release Date: 10/24/2022

This release contains:

Product Certification

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

INSTALLATION NOTES FOR Stewardship Tier 7.4.8 AND LATER

The SAP transports for Stewardship Tier installations are now split into 2 packages and are documented separately.

  • Core—contains the functions and programs required by Stewardship Tier to extract data via RFC and load via BDC. These transports are distributed with the Stewardship Tier installation in versions 7.4.8 and later.

  • Supplementary—miscellaneous functions, programs, and utilities for supporting SAP-based projects. Contact Syniti Support and raise a support ticket to get this transport.

The code in the Core transports has been modernized to adhere to latest ABAP coding standards. Both the Core and Supplementary transports are compatible with SAP installations of EHP 7 FOR SAP ERP 6.0 [SAP_APPL 617] (based on SAP NETWEAVER 740 [SAP_BASIS 740]) or higher.

NOTE: Customers using older versions of SAP can contact Syniti Support who will assist in locating versions of the required programs and functions that are compatible with their SAP Instance.

Refer to Support Article SAP Transports for 7.4.8 and Above for SAP Transports available when running version 7.4.8.

IMPORTANT UPGRADE NOTES

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 psaCollate Incompatible with SST 7.4.5+.

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 Knowledge base article Unsafe HTML/JavaScript removed in Stewardship Tier 7.4.2 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.

Enhancements

Master Data Management

  • The Copy Scenario Role Task Column page now includes the field Skip Inactive Tasks, which when checked skips copying data from inactive tasks and to inactive tasks. When Target tasks are marked as inactive a warning message appears rather than an error message because there could be valid reasons for having inactive tasks.

  • When a user clicks the Notify icon within the Request Role User page for Requests the information message now reads as “This will send an email notification to the highlighted Request Role User.”

  • Using the Quick Finish check box on the Scenario (Roles) page’s Vertical View, users can configure a scenario role to skip the Finish event if the request role’s conditions are not met. This is a reintroduction of the behavior that existed before 7.5.1 of how roles finished if their conditions were not met. Refer to Set a Scenario Role to Skip the Finish Event for more information.

  • Added the Notify event to the Category Workflow Language Message page, which allows users to update the subject, body and email address of ad hoc notifications. Refer to Send Ad Hoc Notifications to Request Role Users of Request Readiness for more information.

  • When generating control tables for scenario roles, the Stewardship Tier now creates tables for inactive tasks. When a user clicks the Create Control Table button or the Update Control Data button on the Scenario Role Task page, a control table is built for all tasks, whether active or inactive in the scenario role.

    As part of this process:

    • All scenario role task column entries for all scenarios that use the same task have their column list updated to the latest set of columns for pages under that task.

    • Columns that were added to a page under the task are added to every scenario role that has that task.

    • Columns that were removed from the page are removed from every scenario role that has that task, regardless of whether or not that task is marked as Inactive in any scenario role.

Resolved Issues

Stewardship Tier

Integrate

Fixed an issue where a Template created using a BAPI was failing due to BAPI download tables having incompatible data type / lengths compared to SAP DATS and TIMS data types. This fix increases the field length of SAP data types DATS and TIMS from 8 characters to 10 characters for (DATS) and from 6 characters to 8 characters for (TIMS). [DSP70-737]

Master Data Management

Mailboxes assigned to a position with a Read Only role (as set on the Position Role page) were erroneously receiving Role Ready workflow emails in their mailboxes. Now, if a Read Only role is assigned to a mailbox, the mailbox no longer receives Role Ready workflow emails. [DSP70-2008]

Changes in Previous Versions

Previous Versions of Help

Help Build Date:October 25, 2022 11:21:36 AM