What's New in Syniti Solutions 6.6

This topic contains:

New Feature

New installations of the DSP® now create the site and service to run in 64 bit processes. Existing sites and services are not changed with upgrades. Refer to the Syniti Installation and Upgrade Manual to change whether a site or service runs in a 32 or 64 bit process after an installation or upgrade.

Enhancements

dspMigrate™

  • Context switching in dspMigrate™ has been improved. Formerly, while working in dspMigrate™ in any component other than Console, if a user selected a Wave and Process Area in the Context Bar, Console would open and display data for the new context. The user would then have to navigate back to the dspMigrate™ component to continue working in it. For example, if a user was working in Map and selected a different context in the Context Bar, Console would open and the user would have to navigate back to Map. Now, when a user selects a Wave and Process Area in the Context Bar, Console does not open. The current page refreshes with data from the new context.
  • Transform and Integrate are now accessible via the Context Bar.

Console

  • A Map parameter, Reset Field Mapping. has been added. The setting controls the action taken when a user clicks the Reset icon for a field mapping on the Field Mappings page in Map or the Automation SQL Field Mappings page in SQL AutoGen.

    Options are:

    • Reset all Field Mapping Fields – All fields are cleared of values

      NOTE: If the mapping is associated with a field group other than the default field group (* or “All”), the Target Relationship ID field is not updated on a reset.

    • Reset Status Fields only – All fields retain values except for the Mapping Status and Rule Status, which are set to Pending Review.
  • A Migration Developer can compare the target design across Waves, identifying differences between Waves and synchronizing a baseline Wave with one or more child Waves. The Migration Developer can sync target designs at the Process Area, object, target or field level across Waves, making target design a global, efficient and streamlined process. Refer to Synchronize Target Designs Across Waves for more information.
  • The Console WebApp Group, Wavesynchronizer, has been added to grant authorization to Synchronize Waves. All Console users can view and compare Waves; however, a user must be specifically assigned to the Wavesynchronizer Group to access the Sync buttons to make changes to the Waves.

Construct

  • In Construct, when a table is auto-generated for partial or full construction the following system fields are added to the DCS table:
    • boaStatus

    • AddedOn

    • AddedBy

    • AddedVia

    • ChangedOn

    • ChangedBy

    • ChangedVia

    boaStatus is the first column in the page views to allow visibility of record status.

  • When using Target Design with Full Construction, fields with an associated check table or domain value in Map on the Value Mapping (Config) page are now generated with list boxes and the list box format can be configured on the Construct Page page. However, list boxes are not generated for fields with a 'master data' configuration type. Refer to Use Target Design with Full Construction for more information.

  • When using Target Design with Full Construction option, AutogGen now runs in the background so that the sync to Map can complete without the user having to wait for AutoGen to be completed. A message displays when AutoGen finishes building the Construct page.

  • When using Target Design with Full Construction, the following column properties are now automatically generated when a Construct page is created:

    • Indicator fields (fields with a Field Format of Checkbox on the Target Fields page’s Vertical View) are assigned a column property of checkbox with allowed values of 'X' and ' '.
    • Date fields (fields with a Field Format of Date on the Target Fields page’s Vertical View) are assigned a column property of DateTime with a format of Date.

      Refer to Use Target Design with Full Construction.

  • When using Target Design with Full Construction option, fields that are deactivated in Target Design are now hidden on the Construct page with a page view. To prevent the loss of constructed data if a user incorrectly deactivates a field in Target Design, the field remains in the DCS table and any previously constructed data remains in the field. Refer to Use Target Design with Full Construction.

  • When using Target Design with Full Construction, the following basic validations are now automatically generated when a Construct page is created. The validations check the following:

    • Duplicate primary key

    • Invalid lookup values

    • Required field not populated

    Refer to Use Target Design with Full Construction.

  • When using Target Design with Full Construction, on the Target Sources page’s Vertical View, a user can now use the Construct Auto Gen Build View field to specify that the Construct page be built with a Vertical View in cases where editable fields do not all fit on the Horizontal View.

    The tabs on the Construct page’s Vertical View are created and displayed based on the Application Screen, Field Order and Key Field settings on the Target Fields page’s Vertical View:

    • If an application screen is specified, a tab with the Application Screen name is created
    • If no application screen is specified, a tab labeled Not Specified is created.
    • If Vertical Only is selected for Construct Auto Gen Build View, all fields identified as key fields on the Target Fields page’s Vertical View are edited on a tab labeled Required Fields. Key fields are always displayed on the Horizontal View.
    • Fields are sorted based on the Field Order field.

    Refer to Use Target Design with Full Construction for more information.

  • When using Full Construction or Enrichment Construction, required fields from key fields are now configured on the Construct page. The main features of this change are:

    • Key fields are now set as hard required on the Construct page and required fields are set to soft required.

    • If a required indicator is changed in Target Design, the change is reflected on the Construct page.

    • If using Excel Integration from the Construct page, cells in the Excel Integration download file are highlighted for required fields. Refer to Configure the Excel Template Overview in System Administration Help for more information.
    • With Enrichment Construction, the Add option has been removed from the Construct page.
  • In Construct, a user can now control whether AutoGen overwrites a Construct page or not. The Construct Auto Gen Level on Target Design's Target Sources page's Vertical View can be configured to control Construct page update or overwrite.

    Refer to Use Target Design with Full Construction for more information.

Map

  • The process to load source values for value mapping has been updated. After loading source values into a lookup table in Map, only those source values that are to be mapped (i.e., only those fields for which a rule has been created) are retained in the lookup table when the target is processed. Unmapped source value fields are deleted.

  • The process for adding a lookup table to a System Type has changed. A lookup table can be added to one field at the System Type Table level. Refer to Add a Lookup Table Manually for more information.
  • The Source Value Tracking page has been added that displays each source table that has a field that has been mapped to a selected lookup table. Refer to View the Source Tables and Fields Mapped to a Lookup Table for more information.

  • The message that displays when a user clicks the Sync from Target Design icon has been improved and provides information about Construct page generation.

Target Design

  • The message that displays when the user clicks the Sync to Map icon has been improved and provides information about Construct page generation.

Transform

SQL AutoGen

  • The Report Auto Gen Level setting on the Automation page’s Vertical View determines if and how business user reports are generated for the target with SQL AutoGen. Options are:
    • On - Drop & Rebuild Report Views and Registrations. Any SQL views previously created for the business user reports in the target are dropped and new SQL views with the same name are added.

    • Off - No Report Generation. AutoGen is not used.

    • New - Add new reports without modifying existing report views or registrations. When autogenerating, only new views are created. Existing views are not updated.

  • A user can now view SQL code presented in error messages in a readable format on the AutoGen SQL Log page.
  • SQL AutoGen for Construct has been enhanced as follows:
    • The Construction rule type now auto-generates a rule that copies the data from a DCS table to a source or target table.

    • The "Mapping Required" flag for Update Row DCS tables defaults to 0.

    • There are no mappings or rules auto-generated on the update row table.

    • The update row DCS source is defaulted to type table and allows the option for view. The import package is auto-generated as well. In the case of a view, no package is generated.

    • Full Construct Tables are mapped as normal (All Copy).

Data Stewardship Platform (DSP)®

The System Administration and DSP Add-Ons sections have been moved to a help system that is accessible through System Administration pages only. Users who cannot access System Administration pages cannot access System Administration help.

Collect

  • Prior to this release, where clauses were only applicable to SAP Data Services package types and not SAP Data Services using RFC package types. With this release, where clause logic can now be used with SAP Data Services using RFC package types. Refer to Manually Register Tables to Source for more information.
  • A synchronous processing option has been added on the Tables page for Data Services package execution. With synchronous execution, the refresh package jobs respect the queue and wait until jobs are finished before starting another job. Refer to Manually Register Tables to Source for more information.
  • When adding a table to a Target Source and selecting the "Manual Data Services" package type, a list of jobs available in the Data Services repository is now available for selection in the Package Name field on the Table page’s Vertical View.

Common

  • The process for adding a lookup table to a System Type has changed. A lookup table can be added to one field at the System Type Table level. Refer to Add a Lookup Table Manually for more information.
  • A user can now add a debug log for custom WebApps, including the Content WebApp in dspConduct™. Refer to Add a Debug Log to a Custom WebApp for more information.
  • The DSP® is no longer delivered with a complete SAP or JDE System Type in Common. Instead, Common is now delivered with SAP and JDE models that can be used to import those System Types. Refer to System Types for more information. In addition, the System Type Models page has been improved to ensure a more complete model and to simplify the model building process. Refer to Manage System Types with System Type Models for more information.

  • The DSP® has been enhanced to support HTTPS as a communication method between the DSP® and Data Services applications. Refer to Register a Data Source in Common for more information.

Integrate

  • The Messages page now includes a link on posting errors so that users can log in to Data Services through the Data Services Management Console - Administrator component to view more information about a specific error.
  • On the Templates page Vertical View, the Data Services Job Name field is now a list box that when selected auto-populates the jobs for the selected Data Services repository using the Data Services Web Service API.

Online Help

  • The online help user interface and search results page have been updated. Refer to How to Use Online Help for further information.

  • Added Accessibility Features section under DSP® Navigation.
  • Removed System Administration and DSP Add-Ons sections from User help. This content is now accessible from the System Administration pages of the product.
  • The DSP® Application Development section has been added to System Administration help.

System Administration

  • A System Administrator can now view logged information about access changes made for entities, authentication attempts when users log in to the DSP®, and changes to system configuration on the System Logs pages. Refer to View System Logs for more information.
  • Syniti Solutions now supports the ability to create 3D charts for column and pie charts. Refer to Create a Chart in System Administration help for more information.
  • The Console WebAppGroup Wavesynchronizer has been added to allow users to access buttons and pages related to comparing and synchronizing target designs across Waves.
  • A page Designer can now create a Combination Chart page to combine multiple chart types (pie, column, line, dotted line) on a single chart page. Refer to Create a Combination Chart for more information.

dspConduct™

  • A Designer can auto-generate a Request page and request-related objects (tables, views and stored procedures) in a Content WebApp and database if the objects don’t already exist. Once these objects have been built, users can create and submit a request to dspConduct™ and the Content WebApp can send data to dspConduct™. Refer to Auto-generate Request-related Objects for more information.

  • Charts have been added. Refer to View Charts in dspConduct™ for more information.
  • A Security Administrator now has an option to assign a calendar to a user from the Position User and User Position pages. Refer to Configure Users in a Position and Configure dspConduct™ Positions for a User for more information.

  • The User Response Required on Warnings option is now available on the Role and Scenario (Roles) page. If enabled, after a user clicks Finish for the role, any validation failures require a user response to continue the process.
  • The Update Page List icon on the Task Page page now updates the list of child pages assigned to the selected page and updates all the scenario role tasks to which that task is assigned.
  • When IGC™ roles are imported into dspConduct™, the role conflicts are now imported.

  • Application tasks in IGC™ are automatically added to Review and Post roles in dspConduct™ under certain conditions.
    • When IGC™ tasks are mapped to dspConduct™ tasks
    • When Review or Post roles are added in IGC™ that do not exist in dspConduct™ and are imported into dspConduct™

      Application tasks are added to:

    • All Post roles in any scenario that uses the task
    • All Review roles directly dependent on an application role that uses that task

These application task are added as read-only.

NOTE: When a dspConduct™ task is removed from an IGC™ task at any time after import, associated application tasks are also removed from Review and Post roles.

Resolved Issues

dspMigrate™

Map

  • An issue occurred in Map during field mapping when the source table name was identical to the target table name but the tables did not contain the same fields. When the source table was selected in the SOURCE TABLE list box on the Field Mappings page, fields from the source table and the target table displayed in the SOURCE FIELD list box. With the fix, the SOURCE FIELD list box does not display target table fields. [DSP-7133]
  • An issue occurred when adding a source to Map that had previously been added to Target Design. When a user attempted to add the source in Map, a warning message displayed after the source was added, and invalid data was added to the source table. With the fix, when a source is added in Target Design and a user attempts to add an identical source in Map, a validation message now displays alerting the user that the target must be synced between Target Design and Map. Invalid data is not added to the source table. [DSP-7096]
  • An issue occurred when upgrading the product from a pre-6.5 release to 6.5 and later that caused zLegacy fields to display in Map that did not display in the pre-6.5 version. The default setting for the Visibility field, which determines whether fields display on the Field Mappings page in Map and can be mapped, was Both. This setting uses values in the Type field, Natural and Utility, as a basis for visibility. The Type field is not available prior to 6.5. With the fix, the default value for the Visibility field for zLegacy fields has been set to None, and the upgrade does not result in extra fields displaying in Map. [DSP-7338]

Target Design

  • An issue occurred in Target Design when importing a System Type. If a field had a description that was longer than 256 characters, an error displayed on import and the target fields were not imported. With the fix, target fields are imported with a System Type and no errors display when the description field contains more than 256 characters. The field is truncated at 256 characters. [DSP-7145]
  • An issue occurred when syncing Target Design and Map. When the number of records to sync was large, the design was complicated (i.e., multiple Update Row sources were used) and the Mapping Required check box was enabled for each Update Row source, the sync process took a long time to complete. With the fix, the sync process completes in a few minutes. [DSP-7325]

Transform

  • An error displayed in Transform when executing a rule or export if the Generate Documentation setting was enabled in Console on the Parameters page and the name of the object and table were long. With the fix, the error no longer displays in this scenario. [DSP-5586]
  • An issue occurred if a target had multiple Add Row source objects from the same source, and a different source report was registered to each source in Transform. On the Source (Info) and Source (Errors) page, duplicate records for each source report displayed. With the fix, duplicate records no longer display on these reports.[DSP-7297]
  • An issue occurred when a data source was named differently than the underlying database name. Rules and reports were not running. With the fix, the data source can be named differently from the underlying database name and rules and reports run as expected. [DSP-7479]

dspConduct™

  • The archive process has been updated to archive the ttReviewRoleAggregate table when the ttRequest table is archived. In addition, when requests are removed from the ttRequest table after archiving, they are also removed from ttReviewRoleAggregate table. [DSP-7602]
  • An issue occurred when the scenario role used the Auto Post feature where workflow notifications were not sent after a posting. With the fix, postings with Auto Post send workflow notifications to the user(s) assigned to the post role in that scenario.
    NOTE: When using Auto Post, the Post Workflow Notification records at the specific Scenario's Post role are used to determine which users receive posting success or failure notifications. [DSP-7604]
  • An issue occurred when a request was set to Auto Post that caused a deadlock during the posting process, caused by the large number of records to be posted. Indexes have been added to tables to improve the performance of the Auto Post process which is expected to reduce the likelihood of a deadlock occurring. [DGE-1024]
  • An issue occurred when a request was set to Auto Post that caused a deadlock during the posting process. A stored procedure which determined the posting user read in all records from the Request table. This issue was corrected when a filter was applied and the deadlock related to this issue no longer occurs.[DGE-1041]
  • An issue occurred when sending workflows to users assigned to a read-only position role. After a role was processed and the user clicked the Submit button, if the next role was a read-only position role, a workflow was sent to the user assigned to the role. Users assigned to a position for this role cannot edit or take action on the org unit data in the Content WebApp so must not receive workflows. With the fix, workflows are not sent to users assigned to the first read-only position role. [DSP-7580]

  • An error displayed when opening the Request Review Task page under certain conditions. If one user had read-only access to a role (through the role position assignment) and another user had unrestricted access to the same role in the request, the error displayed. With the fix, this error no longer displays and the Request Review Task page opens normally. [DSP-7599]

  • An issue occurred when posting using the Group Post method if user credentials were configured for the data source. When the Post role attempted to post a request using the Group Post method, the system credentials, instead of the user credentials, were used for authentication. With the fix, the Group Post uses the data source’s user credentials. [DSP-9071]

Data Stewardship Platform (DSP)®

An issue occurred when the first linked column on a Header Detail page had an associated business rule event with a link to a different page. The target page for the link displayed instead of the Header Detail page. The columns' links are now skipped by default when the Header Detail page is initially loaded to avoid this error in behavior. [DSP-7825]

Assemble

An issue occurred when adding an Assemble Where Clause that exceeded 128 characters in Map on the Target Sources page’s Vertical View. When the package was built, the Where Clause was truncated in the package. With this fix, the Assemble Where Clause is no longer truncated at 128 characters. NOTE: Assemble affects downstream applications in dspMigrate™ . [DSP-7271]

Collect

  • When upgrading from a version prior to 6.5.3, Collect Packages must be re-built as the naming convention has changed for the Data Services objects (Data Stores, Jobs and Data Flows). The Syniti Solutions Installation and Upgrade Manual has been updated to note that the user must also click Test Connection on the Target Source to recreate the Data Services Data Store. [DSP-7321]
  • An issue occurred when building a package for an ODBC source with a connection type of ODBCDB2, ODBCDB2AIX, or OLEDB2. A typo in the New Data Type Format was corrected, and the package now builds without errors. [DSP-7020]

Common

  • An issue occurred when using the Trace feature in Common. After a data source was traced, if an object was deleted in SQL Server Management Studio in the Trace Object table, running the Trace process again resulted in a Foreign Key error. With the fix, Trace works correctly in this situation (i.e., the deleted object displays as a change in the Trace results) and no error displays. [DSP-7110]
  • An issue occurred when a user was assigned a security role of Analyze in Common. The user was unable to access the Unique Values List icon on the Table Fields (Results) page. With this fix, the Analyze security role now has access to the Unique Values List icon to open the Field Values page. [DSP-7211]
  • An issue occurred where the data source timeout settings from Common were not being sent to Transform, which caused timeout errors when a target was processed. With this fix, the settings are being sent. [DSP-7156]

Integrate

Posting a process based on a User Defined template creates a flat file that is then imported into SAP using a method outside of the DSP®. Because this template type does not require a direct SAP connection, a user name and password are not required when defining a User Defined template. An issue occurred when posting a process based on this template type because SAP Back End Authentication (BEA) ran and failed. With the fix, BEA does not run for a posting based on a User Defined template so there are no longer failures related to BEA. [DSP-7931]

Online Help

  • Updates were made to the topic DSP® Navigation and Menu Options. [DSP-7157]
  • The description of the Refresh Error Aggregate Cache Schema Field was updated on Transform's Targets page, and a typo was fixed on Target Design's Target Fields page. [DSP-7111]
  • The definition of zLegacy field has been updated in the glossary. [DSP-7123]
  • The definition of the Usage field on the Targets page in Target Design has been updated. [DSP-7091]

dspMonitor™

  • Updated the description of the Remove Data From File Path field on the Parameters page in online help.[DSP-6164]

  • An issue was found when processing and generating workflows and the ownership information did not reflect the correct group owner. With this fix, the correct ownership information is displayed. [DSP-6890]

  • An issue was found when a report was removed from one group and added to another, the report process was continuing to process the report metrics in both groups. With this fix, the report metrics are only processed for the correct group. [DSP-6746]

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.Previous Versions

NOTE: 6.5.4 and 6.5.5 versions of Syniti Solutions were not released. The immediately prior release to 6.5.6 was version 6.5.3.

NOTE: A 6.4 version of Syniti Solutions was not released. The immediately prior release to 6.5 was version 6.3.1.

Help Build Date: March 04, 2022 03:26:10 PM