What's New in Syniti Solutions 7.5.1
Release Date: 7/27/22
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: 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
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
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
Stewardship Tier
Collect
Fixed an issue where, when Stewardship Tier was installed or a new data source type was added, users had to change the RAW and VARBINARY data types to convert properly to character fields or the Collect extracts would fail. This issue also occurred when extracting data from SAP using RFC packages. To fix this, we modified source database RAW and VARBINARY data type conversions for ODBCHANA and ODBCOracle database types. We also resolved a problem with extracting binary fields through RFC extracts into VARBINARY fields on the target database.
Master Data Management
-
On the My Positions page, added a link called Position Report that provides display of the User Position Business Processes and User Position Roles pages for a specific position.
-
On the Task Page page, we added a new field ON VALIDATE EVENT CREATED that will provide status of the On Validate Event requirements for that page.
-
Users can now use Excel Integration as a part of the Scenario Role Task Colum page.
-
The Workflow Logging has been changed to run after Audit Detail Reports and after custom rules. This change increases the benefits of the workflow process logging.
-
To streamline request rejection, the Reviewer Workbench feature and the Request Review Task page have been removed. Rejecting a request is now performed on the Request Role Task page. Refer to Reject a Request for more information.
-
Added the ability to quickly and easily access the Scenario Role Task Column page from the Vertical View of the Category, Scenario, Role and Task pages. The Scenario Role Task Column page displays the columns relevant to the selected asset (i.e., when accessed on the Scenario page, all columns in the selected scenario display).
-
Removed the feature to automatically generate control views from the Scenario Role Task Page as the functionality was not implemented correctly and was not used.
-
The Workflow Logging has been changed to run after Audit Detail Reports and after Custom Rules. This change increases the benefits of the workflow process logging.
-
Updated the Scenario Role Task page with icons that allow users to generate and update control tables for all pages in a task. Refer to Generate a Control Table for Content WebApp Pages and Update Control Table Data for more information.
-
On the Request Role page, the Users icon has been moved to the record level. Adding and removing a role owner can now be performed on multiple users at once, as these icons have been moved to the Page toolbar.
-
Designers can now use Navigation tasks to gain finer control of task definitions. Users can now set the tasks that display as buttons on the Request Role Task page quickly and easily using Navigation tasks. Refer to Enable Navigation Tasks for more information.
NOTE: New installations and upgrades of the Stewardship Tier where no scenarios have been created have the Navigation Task parameter enabled by default. Upgrades that already have scenarios defined have this parameter disabled by default.
-
When adding new tasks to a role, the scenario role task records are initially set to Inactive.
-
Users can now run custom business rules when a request is rejected or when a request fails because a conditional dependency is not met. Refer to Add Custom Business Rules for more information.
-
Added a pre and post message when the user clicks the Notify button on the Request Role User page to send an ad hoc message to a user that a role is ready to be worked on. The pre message confirms the message should be sent, and the post message confirms that the Stewardship Tier has sent the message.
-
Added the AddedBy, AddedOn, and AddedVia columns to the ttRequestWorkflowParam table to facilitate request auditing. Additionally, the API stored procedure apiInsertRequestWorkflowParam has two new optional parameters of @RuleName and @boaUserID, which will be used to fill in the AddedVia and AddedBy columns on the ttRequestWorkflowParam table.
-
Added a new field to pages Scenario, Scenario (Roles) and Scenario Role Task that will Copy Column Properties from one scenario to another. The new button links to a new page Copy Scenario Role Task Column that provides fields for Source Scenario and Target Scenario for use in the copy feature.
Resolved Issues
Stewardship Tier
Collect
When filtering the table records in Collect by selecting and right clicking the Duration value and the Filter option in the drop down menu the expected results were not returned. To correct this issue, we have removed the value in the Duration field for all DBMotoMirror Package Types to allow the user to enter the value for the correct filter process. [DSP70-1791]
System Administration
-
On any page that has an object definition, clicking the name of the object leads to the Definition page. The Definition field did not display properly (showed as ??) when the where clause contained Unicode characters such as Japanese or Chinese. This issue has been fixed by changing the format for the Definition field from varchar(max) to Nvarchar(max) so that the correct value displays for all languages. [DSP70-1856]
-
Fixed an issue where when the user clicked on the Vertical view of the WebApps Header page the link may have connected the user to a Vertical view from a different WebApp. If the page names are the same within two or more WebApps, the filter could open the Vertical View of another WebApp page. With this fix, the system filters as expected. [DSP70-1890]
Master Data Management
-
In large MDM environments, the Task Page loading performance showed signs of degradation. To improve performance, a new index has been added to the underlying table. [DSP70-1753]
-
Fixed an issue on the Roles page where if a stored procedure was added to an event, and then the Role Type was changed, it would provide duplicate records for the events. The fix adds a field Clean Scenario Role Event Rules that will activate after the Role Type is changed. This field clears the events from the old Role Type when changed to a new Role Type. [DSP70-1806]
-
Fixed an issue on the Scenario Role Task Column page where all columns across all categories were displayed. With the fix, only columns in the selected category display. [DSP70-1906]
-
Fixed an issue on the Request Role page where the order of rules on the Finish event was preventing the Custom Workflow parameters from being included in the ttWorkflowMessage. With this fix, the order of events is correct and working as expected. [DSP70-1918]
-
Corrected issues that happened in versions 7.1.4 and 7.4.3 when adding a Final Finish table in MDM that used a BOA RFC Collect Package Type. In 7.1.4, the where clause was not formatted correctly and caused an error in the Final Finish download. In 7.4.3, the where clause override was not added to any of the commands in the Final Finish download. With the fix, the Final Finish table in MDM that used a BOA RFC Collect Package Type downloads the data as expected. [DSP70-1851]
-
Fixed an issue where workflow notifications were not sent to roles without any owners when a request had:
-
more than one role ready to be worked on because a dependency was complete, and
-
one of those ready roles had a user marked as an owner.
With the fix, the notifications are sent to all roles in this case as expected. [DSP70-1870]
-
Changes in Previous Versions
Previous Versions of Help
Help Build Date:September 20, 2022 12:14:45 PM
