What's New in Syniti Solutions 8.0.3

Release Date: 3/8/23

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 Mass Change feature has been added to MDM, which permits users to update records based on a field and a value on the data entry page using an update statement formed from the settings on the Mass Change page. This page allows users to make mass changes to data on the data entry pages quickly, accurately and without having to move the data out of the Stewardship Tier. Refer to Mass Change Data in MDM for more information.

  • Users can now quickly and easily create tasks and their associated tables, views and pages based on an Integrate BDC Script template or a manually built table for use with mass change scenarios. Refer to Automatically Generate Tasks to Process Mass Maintenance Requests for more information.

  • Users can now add a Rejected and a Rejection Reason column to tasks (pages) for use with partial request rejection. Partial request rejections allows the Review role user to reject only the data that is not correct instead of rejecting all of the records in the request. Refer to Perform a Partial Request Rejection for more information.

  • Users can now add the BDC posting batch size parameter within the Category Process page to limit the batch size during BDC uploads.

  • Scenario types for Mass Maintenance scenarios have been added. Values are:

    • MassBusExtend

    • MassChange

    • MassCreate

    • MassOrgExtend

    Refer to Add a Scenario for more information.

  • Users may now reset a request to In Process on the Request Role page once the status shows as either Posted or Posted with Errors.

  • While processing the validations on the Request Role page, the error messages that are displayed to the user are now captured in a field of the underlying table. If that table is used for multiple pages under a task in the same role, users may see error messages from pages other than the page on which they are viewing the records. If that table is used for multiple tasks in different roles, then only the errors from the last run of the validation process are provided.

  • The Metrics button on the Vertical View of the Scenario page and Business Process page has been updated to include current or all requests made for the scenario or business process based on the chart slice selected.

  • A new parameter, Use Comparison Approval Page, has been added to the Vertical View of the Category page that compares former and new field values. During the auto-generation of objects for a new task, two additional tasks are created (Review and Compare). Each task provides a report of findings. Refer to Use Comparison Approvals in MDM for more information.

Resolved Issues

Stewardship Tier

Collect

Resolved an issue where the SAP Data Services Build Package process for a target table with a key or index was failing during a rebuild if the name of the source exceeded eight characters. This issue was caused by incorrect source connection metadata that truncated some information. The impacted metadata entries have been corrected and the rebuild process now completes as expected. [SST-63]

Common

Fixed an issue for validation on the DataSource Registry page for instances where under certain, rare conditions, leaving the password field blank would not return an error message when testing the connection. The validation now catches this issue so that the user can enter the correct credentials.[SST-1]

Master Data Management

  • An issue occurred involving Post roles in different scenarios where some roles were set to Auto Post and Auto Finish and others were not. The posting completed the Auto Finish process for that Post role in all scenarios if any scenarios had that role marked as Auto Finish. With the fix, the Auto Finish setting on the Post role for the specific scenario determines if it automatically finishes. [SST-61]

  • Fixed an issue with the Description column on the Review Role Audit Details page where the translations were incorrectly associated with the dspConduct WebApp. With the fix, translations on this page are based on the content page in the Content WebApp where the record was added or changed, instead of the translations associated with the dspConduct WebApp. [SST-27]

  • The Metrics button on the Vertical View of either Category Scenario page or Business Process page has been fixed to include current or all requests made for the scenario or business process based on the chart slice selected. [SST-32]

Help Enhancement Requests From Users

At the bottom of every topic in this help system is a Send feedback about this topic button. Users can click this to submit suggestions for the current help topic. The following enhancements were added to the help for this release:

Changes in Previous Versions

Previous Versions of Help

Help Build Date:May 08, 2023 05:27:41 PM