What's New in Syniti Solutions 8.0.4

Release Date: 6/14/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

  • When automatically generating tables and tasks, the underlying key ID field has been changed. These fields are now used and required on the tables:

  • To help with potential deadlock issues, the Final Finish process that generates child requests has been updated. Jobs are created to run the On Validate Event on the Content WebApp’s Request page for the child request. This process has been updated to create these jobs with the same Job Group value so that they run serially instead of in parallel.

  • The creation of the Mass Change page components is now being captured in the ttModelLog table.

  • The Vertical View Order field has been removed from the Create Base Table Columns page, as only Horizontal Views can be automatically generated at this time.

  • The Where Clause creation process has been updated as follows:

    • The Mass Change Where Clause page now includes the MassChangeID in the underlying Horizontal view so the drill-down criteria works properly.

    • The generated procedure webRequestMassChange_BuildWhereClauseUpd takes in the MassChangeID as a parameter and then uses it to figure out which ttRequestMassChangeWhereClause records to use to build the Where Clause and which ttRequestMassChange record to update.

    • The Mass Change tables now have the ContentRequestID unique identifier record as a field and have it populated because the ttRequest table in the Content WebApp’s database will have that field as a primary key. The ContentRequestID will help set up a cascading delete when the ttRequest record is deleted during the archiving process.

  • On the Mass Change page, the COLUMN NAME list box has been updated to prevent the selection of boaReserved columns.

  • The Clear All Rejections icon has been added to the Request Review Task Roles page. When a user clicks the icon, the Rejected check box is unchecked and text is cleared from the Rejection Reason field for all records on the Request Review Task Roles page. Use this feature if records have been rejected in error. Refer to Reject All Records in a Request for more information.

  • As part of automatically creating a task that uses partial request rejection, a new stored procedure called webPageDescription_OnValidate_RecurseScenarioFalseUpd is included, where webPageDescription is populated from the Description field on the Create New Task From Existing Table and Create New Task From Integrate Template pages. This procedure sets the Rejected flag to false, but only checks for records in the task’s table. If you have multiple tasks with partial record rejection in the same Scenario, then you must modify this procedure to consider records in those other task tables.

  • The tt[TableName]Compare table must have RequestID as part of the table key.

  • On the Create New Task From Integrate Template page, the INTEGRATE TEMPLATE ID list box includes the Integrate category name.

  • Build options have been added to the process of creating tasks for mass change. When automatically generating tables and tasks, users can also:

  • Some stored procedures incorrectly based what they created on the table name when they should have used the NewTaskID and CategoryID. This caused issues with saving tables with duplicate names in different categories.

  • When creating a base table from an Integrate template, the boaReserved columns (Added On, Added By, etc,) are added automatically. Refer to Create a Task for Mass Maintenance Based on an Integrate BDC Script Template for more information.

  • The fields on the Category page’s Vertical View have been updated to use the words Mass Change instead of Mass Update.

  • When creating a task from a table or an Integrate template, users can now update the VERTICAL VIEW ORDER and the HORIZONTAL VIEW ORDER on the Create Base Table Columns page.

  • The Create Base Table Columns page did not have an assigned OnValidate event, which meant that the Status icon did not work properly. The event has been added to the page, and a validation now runs when a user clicks the Status icon.

  • The apiRoleEdit function has been updated to return a 0 instead of a NULL when the Role and Task input parameters fail to return a result.

  • These columns are now restricted from mass change, and are not available for selection in the Column Name list box on the Mass Change page:

    • RequestID

    • ZCounter

    • ContentRequestID

    • boaStatus

    • AlreadyInSAP

    • PostError

    • PostMessage

    • Rejected

    • RejectionReason

    • ValidationErrorMessage

  • Three new table-valued functions have been added to the DGE database to help with performance issues with existing, delivered API functions. The Stewardship Tier is not delivered with any features that use these functions on installation. Content WebApp designers can use them when creating Content WebApp pages or when resolving page performance issues.

    Two table-valued functions are parallel existing scalar functions:

    • apiRoleEdit_TVF.sql

    • apiSecurityScenarioEdit_TVF

      This single function is a common combination of functions used to determine record editability:

    • apiScenarioRoleUserEdit_TVF.sql

      The general method for using these table-valued functions in a view is to CROSS APPLY or OUTER APPLY them in the view definition. For example: 

      SELECT table.<column1>
      ,table.<column2>
      ,SRU.sruEdit AS <alias_name>
      FROM <table_expression> as table
      CROSS APPLY DGE.dbo.apiScenarioRoleUserEdit_TVF(<RequestID>, 
      <ScenarioID>, <RoleID>, <TaskID>, <UserID>, <AtExists>) as SRU

Stewardship Tier

  • When downloading the data on a page to a file using the Download option on the More Actions (small gear) menu, the default format has been updated from XLS to XSLX.

  • Setting a column on a page to Soft Required on the Page Columns page now adds a validation to the OnValidate event for that page. The message that displays when a user leaves a field blank that has been set as soft required has also been updated. This validation is now an Error message of “FieldX should have a value,” where FieldX is the translated field name, if there is a translation at the time the field is set to soft required. Validations created prior to this release from this process are not changed.

  • To avoid issues with license expiration, the expiration date for the version of Syniti Data Replication installed with the Stewardship Tier is now set to 10/15/2031.

Promote

Once a package group has been sent for approval, changes cannot be made nor can packages be compared; the only option is to transport the package. With this change, users can now:

Resolved Issues

Stewardship Tier

Fixed an issue with the Recompile Objects functionality, accessed in System Administration on the Data Sources page. If users had created any table-valued functions in a database registered as a data source, the Recompile Objects process did not complete and displayed a Compile error. Now, the Recompile Object event properly handles table-valued functions. [SST-82]

Integrate

Fixed issues with Integrate caused by simultaneous postings with processes that used the same BAPI template. One of the postings completed while the other did not. The issue was observed in Master Data Management, when multiple requests for the same scenario were simultaneously completed when AutoPost was set on the scenario’s Post role. With debugging enabled, one of the following errors would occur from this resource conflict:

  • [CranSoft.DSP.Integrate.PostAdapter] The given key was not present in the dictionary.

  • [CranSoft.DSP.Integrate.PostAdapter] An item with the same key has already been added.

Now, simultaneous BAPI posting with processes that use the same template do not fail from a resource conflict. [SST-150]

Master Data Management

  • When generating a task based on an existing table, the only field that was ever assigned as a key field was the ID field, even though the tables had other key fields. With the fix, the key fields are captured correctly by this process. [SST-97]

  • Fixed an issue that caused Reset workflow notifications to be incorrectly sent to users with Read Only roles. With the fix, Reset notifications are no longer sent to these users. [SST-60]

  • Fixed an issue that occurred during the request review process. If a Review role rejected the request but did not complete the Reason field, a validation did not display. The Reason field is now required when rejecting a request, and a message displays if the user attempts to save without completing the field. [SST-59]

  • Fixed an issue that occurred if a user entered a single quote as part of an update in a record entered on the Mass Change page. This type of change was not updated when the record was processed. With the fix, creating a new Mass Change page for a Content WebApp includes the SQL objects that can properly handle single quote marks in the update value. Mass Change pages that were created prior to this version are not updated. [SST-193]

  • The boaStatus column must be added to any table that is used to create a task. If you attempt to create a task based on a table that does not contain this column, it is added automatically. [SST-203]

Known Issues

Promote

Promote does not support the comparison of tables that contain columns with different collations. As a result, the logic that serializes the record that needs to be transported to the destination server fails. If a comparison is run, the error displays in the Job Queue in System Admin, not the Debug Log in Promote.

The workaround for this issue is to alter the source table so that all columns are case sensitive and once the data has been transported, revert back the columns that aren’t supposed to be case sensitive.

Changes in Previous Versions

Previous Versions of Help

Help Build Date:June 14, 2023 07:09:54 AM