Changes in Previous Versions

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: 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 toRe-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

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 Reportthat 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 Headerpage 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]

What's New in Syniti Solutions 7.5.0

This release contains:

Enhancements

Stewardship Tier

Assemble

The following security definitions and associated keys have been created to further define security rights in Assemble:

  • Assemble.DataSources—limits users to creating packages with the specified data sources as targets.

  • Assemble.WorkingDataSources—allows users to create packages with all working (non-delivered application) data sources.

  • Assemble.ApplicationDataSources—displays delivered application data sources. Packages that read from or write to tables in the delivered databases are not standard nor recommended and can cause functional issues. This key allows Power Users to access existing packages created with delivered application data sources.

NOTE: If a security role exists and has an Assemble WebApp group assigned, the Assemble.WorkingDataSources security key is assigned by default in a post-install step. The other two keys must be configured by administrators, depending on what database access the user needs. Refer to Set Up Security for Assemble for more information.

Promote

In order to accommodate users' ability to provide a variety of information related to the review/approval Package Groups, the following field names were updated:

Master Data Management

  • Messages sent along with MDM workflows are now logged for analysis later. The logs can be accessed in Common on the Vertical View of Debug Log page. Refer to View Workflow Messages for more information.

  • Shared mailboxes can now be used to receive request-based email notifications. Administrators can register mailboxes and then assign the mailbox to one or more positions. If a new request is created or a subsequent request role to which the position has access becomes ready, then an email is sent to the mailbox address. Refer to Set up a Mailbox for Position-Based Workflow Notifications for more information.

  • Using position-based assignment, users and administrators can quickly set how users receive workflow notifications for request events, such as when a request is ready for review or when a request is late. Users receive the notifications based on the positions they have access to through their request roles. Users can select to receive notifications through email, popup, or both. Users can also choose to receive no notifications. Refer to Set User Workflow Receipt Preferences by Position for more information.

  • Users can update the workflow receipt preferences for multiple positions for multiple users either manually or through Excel integration on the new All User Positions page. Refer to Edit Workflow Receipt Preferences in Bulk for more information.
  • A role owner can now be assigned easily to a request role, either directly on the Request Role page, or using API procedures delivered with MDM. Role owners receive notifications when a request they own is canceled, deleted, posted, posted with errors, rejected, reset, and finished. Role owners also receive all SLA notifications. Refer to Add Role Owners for more information.
  • A user who finishes a request role is set as the role owner automatically. Owners receive email workflow notifications about request events during request processing. Refer to Set Workflow Notification by Position for more information.

  • Users can update the workflow receipt preferences for multiple positions for multiple users either manually or through Excel integration on the new All User Positions page. Refer to Edit Workflow Receipt Preferences in Bulk for more information.

  • Users can now view all users assigned to a request role on the Request Role Users page, and send a user an email from that page notifying them that a request is ready to be worked on. Refer to View a Request’s Roles, Tasks and Users and Send Ad Hoc Notifications to Request Role Users of Request Readiness for more information.

  • Users can now use views to create custom Audit reports to generate the audit details, and can use this custom report instead of the delivered Audit report. These reports are sent in the notification email as an Excel spreadsheet attachment, and they provide more opportunities to show drop down values, and other validation features. Refer to Assign a Custom Audit Report for more information.

  • Users can add two columns, one containing the role owner and the other the SLA minutes late for the request roles, to the Requests page in the Content WebApp using an API view included with the Stewardship Tier. Include the view apiRequestAllOwnersMinutesLateSel.sql using an outer join in the Content WebApp’s Request page view to show Minutes Late and Role Owner for each request.

  • Auto Post and Auto Finish roles no longer receive Role Ready or Reset/Reject workflow notifications when preceding roles are reset or rejected.

  • Added another level of escalation for SLAs at the category level with SLA Late Cycles, which are the number of cycles a request can be late before escalation notifications are sent. The SLA Late Cycles value ranges from 1 to N, where the number indicates how many multiples of the role's SLA level pass before an Escalation notification is sent.

    For example, a role with an SLA of 1 day and 6 hours in a category where this SLA Late Cycles value is set to 5 would result in SLA notifications being sent:

    • At 1 day and 6 hours for the Late SLA notification

    • At 5 days and 30 hours for the Escalation notification

    If this value is 1, the Late SLA notification and the Escalation notification are sent at the same time.

    All users assigned to the role that have the workflow notification settings set for ESCALATION on the My Settings and User Settings pages are notified on the escalation date.

Resolved Issues

Stewardship Tier

Promote

Fixed an issue with the way Pass Through tables worked. A rule runs to set all data in a Pass Through table to ignore the Sync action. However, this rule did not work correctly for Not in Host records, causing values that only existed on the Destination system to be marked for deletion. The rule now works as expected where Not In Host records in Pass Through tables on the Destination system are no longer marked for deletion. Users still need to use caution with Pass Through tables because child records of Not In Host records can still be marked for deletion. [DSP70-1548]

Master Data Management

  • Fixed an issue where a non-key Column was selected as “Include in Record Key” that caused the Audit Details import to fail. With the fix, for new record creations and deletions, the field marked as “Include in Record Key” displays as part of the concatenated key. Also, for changes, due to the way the #AuditColumn table stores the updated data, the value for a non-key field is only available if that field is changed. [DSP70-1745]

  • Fixed an issue that occurred when a user clicked the Validate or Finish button for a role from the Request Role page. The validation message that displayed had the incorrect role name in the title bar. This role name was always the first role name in the request by priority order, instead of the role name that validated or finished the role. With the fix, the validation message displays the name of the role that validated or finished the role in the title bar. [DSP70-1754]

  • Fixed an issue related to auditing data that was imported into MDM using Excel integration. If a user enabled auditing for a category, created and submitted a new request, and designed the content page to use Excel integration, any records imported using this method did not display on the Review Role Audit Details page as they should have. With this fix, records added using Excel integration are tracked for auditing as expected. [DSP70-948]

What's New in Syniti Solutions 7.4.9

Release Date: 3/17/22

This version of the Stewardship Tier includes important architectural changes that provide the foundation for tighter integration with the Syniti Knowledge Platform.

It also resolves this issue:

Fixed a problem that occurred when the Stewardship Tier was communicating with S/4 HANA 2021 application via RFC. This issue impacted data extracts and integrate BAPI template creation and postings. With this fix, the Stewardship Tier is able to integrate with S/4 HANA 2021 applications as expected. [DSP70-1792]

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 toRe-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.

Changes in Previous Versions

Previous Versions of Help

What's New in Syniti Solutions 7.4.8

Release Date: 1/24/2022

This release contains:

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

Enhancements

Add-Ons

Previously, when assigning a WebApp group to a role, the ROLE ID list box on the Security Roles page only displayed the description of each role. Now, the ROLE ID list box includes both the role name and the role description.

Common

Connection to SAP systems using SAP Router with and without the usage of a Message Server is now supported. When SAP router is used with SAP Message Server, the SAP Gateway Host and SAP Gateway Service attributes must also be populated.

SQL Auto Gen

While viewing the Automation tab in the Quick Panel, if the Create Target Table icon is clicked, a Target Table is created within SQL Server. If one or more columns are considered "Utility," this action would fail with an Incorrect syntax error due to missing column formatting. The automation process is updated, and the target tables will create as expected without error.

Master Data Management

  • To better capture workflow message auditing information, all procedures that create workflows now capture data in the AddedOn, AddedBy and AddedVia columns in the ttWorkflowMessage table. Refer to Set up SLA Notifications for more information.

  • Date timestamps generally display in Stewardship Tier based on the time zone of the database server. Based upon client feedback, there are certain instances where users / auditors could benefit from viewing the dates / times based upon their time zone. Therefore, the following pages / field support date/time display based upon a user’s time zone:

To support this functionality, additional parameters have been added to the Stewardship Tier to store time zone settings:

  • Parameters page contains a field - Server Time Zone to hold the database server’s time zone.

  • User Settings page contains a field - User Time Zone to store the user’s default time zone (defaults to database server time zone if blank).

In conjunction with standard MS SQL function, these parameters determine the specific date/time for the pages specified above.

System Administration

This version contains updates to improve how the Stewardship Tier displays information about column encryption for a data source. The Stewardship Tier indicates when data is in a state of mixed encryption on a single column, and sends an email notification with details on these columns.

These updates include:

  • To track a table’s unencrypted columns, the columns NOT ENCRYPTED COUNT (the total number of unencrypted columns in the table) and TOTAL COUNT (the total number of columns in the table) have been added to the following pages:

  • If the values in the NOT ENCRYPTED COUNT and TOTAL COUNT are not equal, indicating that there is a mix of encrypted and unencrypted data in the column, the Stewardship Tier sends the Data Source Table Column Encryption Report workflow email to the relevant user(s).

  • The Status field on these three pages displays a warning icon when both encrypted and decrypted records exist in a column. The tooltip for this icon has the message Mixed Encryption.

  • In the Data Source Table Column Encryption Report workflow email, the Email From and Email To values were the same in previous versions. The Email From value name now displays the system instance, taken from the Instance field on the Parameters page.

  • The email includes the tables and columns that have mixed encryption and the mixed state indicator.

  • In cases when a column has data in a mixed state, and the encryption state is Not Encrypted, additional steps must be taken to encrypt these unencrypted records. Refer to Resolve Columns with Data in a Mixed State of Encryption for more information.

Resolved Issues

Advanced Data Migration (ADM)

  • Fixed an issue within ADM where the key columns of the Error Aggregate tables were exceeding the max length of 500 characters causing the process to fail due to a truncation on the SQL statement. With the fix, the key columns are now set to NVARCHAR(MAX) and the tables are created without issues. [DSP70-1643]

  • Previously, when multiple users attempted to import target fields in Design concurrently, there was the possibility that lookup tables were not added. With this fix, clicking Execute Import on theSystem Types Import page allows one import to run at a time, ensuring lookup tables are added. [DSP70-1665]

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

Integrate

  • Fixed an issue that occurred when attempting to create certain BAPIs (known examples include RCP301_RECIPES_SAVE and RCP301_RECIPES_WRITE) on the Template page within Integrate. After clicking the Create BAPI Template button, the button would remain in a processing mode and the BAPI template would not be created. With the fix, the template is now created as expected. [DSP70-1703]

  • Fixed an issue that occurred with Integrate processes using conditionals when running the Stewardship Tier on an application server using antivirus software that calls the Windows Antimalware Scan Interface (AMSI). The posting was running at over ten times the time of the same template on a system where the AMSI scan was not running. With the fix, the posting of an Integrate process with conditionals now completes in roughly the same amount of time regardless of whether antivirus software calls the Windows Antimalware Scan Interface (AMSI). [DSP70-1608]

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.

What's New in Syniti Solutions 7.4.7

Release Date: 11/23/2021

This release contains:

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

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 Uninstalling psaCollate Prior to Upgrade.

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

Enhancements

Master Data Management

  • The Where Used Report is now available at the scenario, role and task level. This report displays the associated business processes, scenarios, roles and tasks for the selected item and provides further insight than the Where Used graphical interface available in previous versions. For more information, refer to View a Role's Scenarios and Tasks, View the Roles and Tasks Assigned to a Scenario and View a Task's Scenarios and Roles.

  • Though the Stewardship Tier runs on a case insensitive database collation, SAP Language is now case sensitive. Changes have been made throughout the Stewardship Tier to reflect this change, including modifying the SAP Language field on the Languages page in System Administration to be case sensitive. Content, custom applications, construction server pages or queries that use any of the following objects may need to be modified to align to the case sensitive collation:

    • webSAPLanguageList view in DSPCommon

    • apiCranSoftLanguageSel view in DSPCommon

    • dspMonitor_AccPak

  • To address queue contention when multiple MDM categories were processing requests concurrently, users can now control the queue (and services) that is used to process each MDM WebApp/category. Set the queue on the Category page's Vertical View in the Posting Job Queue list box. Refer to Set Posting Options at the Category Level for more information.

  • User access to request roles has been updated to tighten security. Users with configured permissions can set a further level of restricted security that affects request role access across MDM. Using Restricted positions, a user can only access a request if that user is assigned to a position with both a role in that request and the business process for that request. Refer to Set Restricted Position Access for more information.

  • The #instance# value can now be added to the subject and body of workflow notification emails allowing recipients to know which system has sent the workflow. The instance is set on the Parameters page within System Administration in the Instance field and must be set on-site. By default, the Instance field is blank. Refer to Use System Values for Dynamic Substitution at Run Time for more information.

  • Use an API procedure now included in the Stewardship Tier to create any parameter with any value required in a workflow. Refer to Use an API Procedure to Create Custom Workflow Parameters and Values for more information.

  • Users can add roles to scenarios more quickly than in previous versions of MDM. Before, all of the role’s associated tasks were set as active and assigned to the scenario, even though many of these tasks were not needed. This required the user to inactivate the unwanted tasks manually. With 7.4.7, when a role is assigned to a scenario, that role’s tasks are inactive by default. The user must activate the role’s associated tasks by enabling the ACTIVE IN SCENARIO ROLE check box on the Scenario Role Task page.

  • Corrected an issue where when users added a role to a scenario, all fields accessed from the role’s tasks via the Link to Page button were added as columns, even though most were not relevant. To decrease the time to configure tasks, after a user activates the task for the scenario role, only relevant task columns are added to the table.

  • We have changed how columns were automatically added to the Content WebApp. By default, if an inactive task is added to a scenario role, the task’s columns are not added. Additionally, when a role is added to a scenario, the columns on all of that role’s tasks are not added by default. The Fetch Columns feature allows users to select a task and retrieve columns. Refer to Fetch All Columns for a Task for more information.

Stewardship Tier

  • AWS RDS is now supported as a database server with certain configurations. Refer to the section Hyperscaler - AWS Hardware Requirements in the Requirements Guide for more information.

    NOTE: For the 8.0.0 version of the Stewardship Tier, the source and target for CTS and Promote must both be RDS or both be non-RDS databases.

Collect

  • Users can now import a large number of target source tables using Excel Integration on the Tables page. Refer to Use Excel Integration for more information.

  • The ODBCHANA connection type (on the Source Connection Types page) now supports downloading data from a view. This enhancement enables the users to download views via Collect in order to gather the required metadata for the SAP HANA scanner to run. As a result, the Fetch Tables action that is run for a Collect target source where the Connection Type is ODBCHANA now fetches tables and views on a HANA system.

Common

TheDebug Logs page was enhanced to provide a limit to the amount of time that debugging is active along with the start and stop times and the number of hours for retention of this log. This will reduce the risk for system slow downs due to this process running.

Promote

  • An error displayed when attempting to use the Structures-Data “Administration-Role” because the Sub Table “RoleWebAppGroup'' only had key fields set up for the comparison process. This Sub Table now includes non-key fields in the comparison process, allowing the “Administration-Role” Data Structure to work as expected.

  • A new setting on theApplication Parameters and the Packages page is available, called Default Include dgSAP Views. This check box either includes or excludes objects dependent on SQL objects in databases prefaced with “dgSAP” (such as dgSAP_Dev, dgSAP_QE, etc.) from the transport. While the Parameter configuration is applied to all new packages, this setting can be overridden at the package level.

  • When a package is compared, differences are queued to identify what to transport. If any object within the package failed, all objects in the package were excluded from the transport, which made it impossible to tell which objects failed and which transported successfully. The error process has been improved so that if an object fails to transport, another comparison is run so only objects that failed remain queued to transport.

  • Previously, it was mandatory for a table being compared to have at least one non-key column. However, use cases existed where tables that only contained keys needed to be compared and transported. Now, tables that only have key columns (i.e., the KEYS check box on the Structure - Data Table Columns page is enabled) can be Compared and/or Synced.

  • Users may now transport data within a SQL table to the destination server. This feature allows users to move data in mass by clicking the Send Data Toggle icon on the Package - Object Comparison page.

  • Power Users may now temporarily unprotect a database in order to transport SQL Object changes made to delivered applications for a package. Enable the Allow Delivered Database SQL Changes check box on the Application Parameters page and the same check box becomes available on the Packages page. Both settings must be enabled to transport core modifications.

Syniti Data Replication

This version of the Stewardship Tier is compatible with Syniti Data Replication 9.8.1.

Resolved Issues

Master Data Management

  • In previous versions, when users added a role to a scenario, all fields accessed from the role’s tasks via the Link to Page button were added as columns, even though most were not relevant. To decrease the time to configure tasks, after a user activates the task for the scenario role, only relevant task columns are added to the table. [DSP70-1594]

  • Corrected an issue that allowed requests in the wrong status to display on SLA Summary Notification workflows. Requests in a Cancelled, Deleted, or Duplicate status no longer display on these notifications. [DSP70-1625]

  • Previously, the Auto Extend Display feature did not work. Now, it works correctly. If this check box is checked on the Role page’s Vertical View, the tasks within the role display as read-only to all other users within the scenario not assigned to this role. [DSP70-1623]

  • Corrected an issue that caused the Late Notification workflow to be repeatedly sent in error. Now, when a request is late, the workflow is only sent when the Late Notification Service page is run. [DSP70-1606]

  • Previously, if multiple CalendarIDs were associated with a role, multiple workflow emails were sent. Now, if there are multiple calendars, workflow emails are sent in order of the SLA deadline, starting with the earliest SLA deadline. [DSP70-1422]

  • Previously, an excess number of records in the audit tables prevented workflow emails from being sent. To fix this issue, we added a new field to the Parameters page: Workflow Max Aggregate Records. This field controls the number of records included in the audit workflow emails. The default value is 200. [DSP70-1624]

Stewardship Tier

  • Previously, when directly linking to another page’s Vertical View, and then attempting to filter and select a value from a combo box, instead of populating the filtered results, the page redirected to the Horizontal View of the original linking page. The Filter function on combo boxes in the Vertical View now works as expected. [DSP70-1607]

  • Previously, when a role was assigned to a user with no other roles on the User Roles page, security to that role was not granted until a second role was added. Now, security to the role is immediately granted as expected. [DSP70-1588]

  • Previously, a page rendering with lazy load did not display all records when viewing the screen at a resolution of 100%. Now, a scroll bar is available to allow users to scroll and access all records on the page. [DSP70-1605]

Integrate

An issue occurred when posting data using a template with an After Post rule. The system always used a default timeout of 30 seconds for processing, regardless of the Command Timeout setting set for the data source. To correct the issue and minimize timeouts, postings that use After Post rule templates now use the timeouts set on the Data Source Registry page for the data source. [DSP70-1587]

Advanced Data Migration (ADM)

Console

Fixed an issue that occurred when adding a new Migration Milestone to the Waves page. While saving the new milestone, if the field NAME was left blank, the system would save the milestone. With the fix, the NAME field is required and the milestone saves as expected. [DSP70-1463]

Enhancement Requests From Users

  • Updated the Password Require Special field on the Parameters page in System Administration to include the special characters.

  • Corrected the description of the Show in Navigation functionality in multiple topics throughout help, including the field description, which was updated to: “If checked, this column displays in the failed records Bulk Execution results. By default, only the first column on the page displays in these results. Refer to View Bulk Execution Results 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.

What's New in Syniti Solutions 7.4.6

Release Date: 9/16/21

This release contains:

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

IMPORTANT UPGRADE NOTES

NOTE: If psaCollate is installed on the instance you are upgrading, you must uninstall it before upgrading to 7.4.6. The collation technology is included in the product in 7.4.5 and later. To uninstall psaCollate refer to the Knowledge Base article Uninstalling psaCollate Prior to Upgrade.

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 7.4.6. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the Stewardship Tier in version 7.4.6 and later. Consult this manual BEFORE updating to 7.4.6, as an analysis of current security assignments must be completed before the Stewardship Tier can be updated.

New Features

Entity Validation

Stewardship Tier 7.4.6 introduces Entity Validation - a new platform component that provides a way to standardize data. This initial release currently supports address verification using Melissa. Utilize the component to manually add and verify addresses or adapt the tables to any address cleansing solution.

Refer to the online help for more information about this new component.

NOTE: To use Entity Validation, users must have a valid Melissa license and must obtain a new Stewardship Tier license. Request a new Stewardship Tier license and/or a Melissa license by opening a support ticket with Syniti Support.

Migration Reports

The Migration Reports WebApp provides a simplified and improved version of Report Delivery. Report Delivery in Transform allows users to access reports for objects in the currently selected wave and process area in the Context bar. The new Migration Reports WebApp allows users to access reports across all objects. Using this WebApp, Business Contacts can quickly navigate to reports and drill down and select reports to add to their Favorite Reports page using a variety of methods. Administrators can easily grant user access to reports by object. Refer to View Migration Reports for more information.

Enhancements

AWS RDS is now supported as a database server with certain configurations. Refer to the section Hyperscaler - AWS Hardware Requirements in the Requirements Guide for more information.

NOTE: For the 7.4.6 version of the Stewardship Tier, the source and target for CTS and Promote must both be RDS or both be non-RDS databases.

Syniti Data Replication

The 7.4.6 version of the Stewardship Tier is compatible with Syniti Data Replication 9.8.

Advanced Data Migration (ADM)

Console

Transform

On the Target Reports and Target Source Reports pages, on the Vertical View, on the Business User Settings Tab, the Sensitive check box and the Business Users Assignment icon are no longer hidden until the report is published. Report administrators can now use these settings to configure granular user access to a report before publishing it. Refer to Grant Users Access to Reports and Sensitive Data for more information.

System Administration

To better support decryption of encrypted data, on the Decrypt page of System Administration, the field Encrypted Data has been increased from 255 characters to 1024 characters.

Resolved Issues

Master Data Management

  • Corrected an issue that occurred after validation message phrases were added to a catalog in a language other than English. These phrases were not translated when the validation message displayed. Now, these phrases display using the correct phrases. The phrases can either be translated:

  • Fixed an issue that occurred when downloading data on the Request Role Audit Details page. When the Review role attempted to download the request data, the CreatedOn and CreatedBy fields were not included in the download. With the fix, these two fields are included in the download as expected. [DSP70-1475]

  • Fixed an issue for pages that required scrolling in the grid to view additional information. If these pages allowed download, no download occurred when the user clicked the Download button. With the fix, these pages now properly download, as expected. [DSP70-1476]

Advanced Data Migration (ADM)

Console

  • Several metrics related to Field Mapping were returning incorrect statistics when a target had multiple target sources including inactive ones. The metrics views did not exclude inactive target sources. Incorrect statistics were also returned when there were multiple target sources for the same source. These issues have been fixed and the metrics are now calculated correctly. [DSP70-1480]

  • Fixed an issue where creating a new wave as a copy of two different source waves that contained segmented target reports was failing to complete the background job. With this fix, both waves are copied correctly and the status in the source wave shows as Procedures Completed as expected. [DSP70-1482]

Integrate

To support copying of a template or a process on the Copy page, the lengths of the following fields were updated. The Copy To Template Name field had a length of 50 which has been updated to 150. The Copy To Process field had a length of 50 which has been increased to 255 characters. [DSP70-901]

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

  • Fixed an issue with RFC extracts running on an SAP HANA database that caused the extract to duplicate data. This happened because HANA databases do not sort data in the same way as typical databases. To fix this, a Transport has been added that sorts the order of the records based on primary key once the selection is complete. This new Transport is included in the Stewardship Tier installation. [DSP70-1519]

  • An error message displayed erroneously when creating a Service message for a Service page. The error was "Please ensure that the Service User ID listed below has permission to access this page." The requirement for a Service User to have access to the Service page is no longer in the Stewardship Tier and the error message no longer displays. [DSP70-1429]

  • Fixed an issue where multiple clicks on a page link in the site menu caused the links on the displayed page to not respond. With the fix, the links function as expected. [DSP70-1339]

 

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.

What's New in Syniti Solutions 7.4.5

Release Date: 08/02/2021

This release contains:

NOTE: If psaCollate is installed on the instance you are upgrading, you must uninstall it before upgrading to 7.4.5. The collation technology is included in the product in 7.4.5 and later. To uninstall psaCollate refer to the Knowledge Base article Uninstalling psaCollate Prior to Upgrade.

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 7.4.5. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the Stewardship Tier in version 7.4.5 and later. Consult this manual BEFORE updating to 7.4.5, as an analysis of current security assignments must be completed before the Stewardship Tier can be updated.

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

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.

New Features

Advanced Data Migration (ADM)

ADM is now delivered with a new Collation Aware Migration feature, which simplifies the handling of case-sensitive data through the end-to-end migration process.

The Stewardship Tier runs on MS SQL Server using databases that have a case-insensitive collation (SQL_Latin1_General_CP1_CI_AS). To avoid collation conflicts, Syniti historically required that all project-specific databases use the same case-insensitive collation and for consultants to handle case-sensitive data on a case-by-case basis. This new feature is now delivered with ADM so users can decide at the wave level whether the wave’s data is case insensitive or case sensitive, which makes for a much simpler process.

To aid users through collation decisions, there are several new validation messages where new data sources can be introduced to a wave, such as:

  • Adding a new data object on the Process Area: Object page in Console

  • Adding a new process area on the Wave: Process Areas page in Console

  • Changing a data object’s Data Source ID or Report Cache Data Source ID on the Process Area: Object page in Console

  • Changing a process area’s Target System Data Source ID, Data Source ID or Construction WebApp ID on the Wave: Process Areas page in Console

  • Changing a wave’s Target System on the Waves page in Console

  • Adding a new source data to a target table on the Target Sources page in Collect

  • Changing the Collation Type on the Targets page in Collect if the data source has a Collation Type in the Data Source Registry that is different from the one assigned to the target.

IMPORTANT UPGRADE NOTE

When upgrading to Stewardship Tier 7.4.5, 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.

Console

To support the Collation Aware Migration feature, the following new fields are available on the Waves page to change the collation for a wave:

  • Wave Data Sources—Click to open the Wave Data Source Collation page to view any collation mismatches between the wave and the assigned data sources.

  • Collation Type—Displays the intended collation of data used in the wave. Options are:

    • General Latin Case-insensitive

    • General Latin Case-sensitive

  • Collation Issue—An indicator that displays if there is one or more conflicts between the wave’s Collation Type and the Collation Type of the assigned data source. Navigate to the Wave Data Source Collation page to use the generated report to fix the issues.

  • Toggle Collation—Click to switch the Collation Type between General Latin Case-insensitive and General Latin Case-sensitive.

NOTE: It is recommended that the Collation Type of all data sources assigned to a wave is aligned with the Collation Type of the wave. Refer to Change Collation for a Wave for more information.

Stewardship Tier (formerly Data Stewardship Platform (DSP®)

Common

To support the Collation Aware Migration feature, the following two new fields have been added to the Data Source Registry page:

  • Collation Type—Displays the anticipated collation of text columns of tables in the associated database. It also controls the collation of table text columns that are created by the ADM AutoGen functionality. Options are:

    • General Latin Case-insensitive

    • General Latin Case-sensitive

    This field is available for the following data source types:

    • Migration Object Database (dsw%)

    • Target System Database (dg%)

    • Migration Source Database (sdb%)

    NOTE: The default value is General Latin Case-insensitive, which means the collation uses Latin characters and is case insensitive. Case-sensitive collation is only supported for Advanced Data Migration.

  • Toggle Collation—Click to switch the Collation Type between General Latin Case-insensitive and General Latin Case-sensitive.

    NOTE: It is recommended that the Collation Type of all data sources assigned to a wave is aligned with the Collation Type of the wave. Refer to Change Collation for a Data Source for more information.

Enhancements

Advanced Data Migration (ADM)

Target Design

In previous versions, when Utility fields were appended to tables, they were only identified by their column name, and did not include the corresponding, user-friendly Description field. Users can now add the Utility field’s description on the Append Utility Columns page. When the Append Utility columns are added to the target table, the description is added to the column Display Name. Refer to Append Utility Columns to All Tables for more information.

Map

It is now possible to update empty legacy Description fields to include the description to assist while value mapping. Refer to Include Legacy Value Descriptions for more information.

Console

The Copy Wave process now also copies the wave’s Collation Type.

Construct

If a wave and its associated dsw* have a case-sensitive Collation Type, Data Construction table text columns and columns in list boxes are also case sensitive.

Transform

With the new ADM Collation Aware Data Migration feature, reports need to be segmented to allow for case sensitivity. Since Windows does not consider case sensitivity, a new Segment Suffix field is available on the following reports so when Transport creates a new folder or reform name, the name is unique:

Mass Maintenance

External Data processing can now use the IMAP email protocol to connect to the account used for both External Request Scenarios and for External Data Processing with an External Data role. By default, the email protocol is POP3. The setting is configured in the new PROTOCOL field on the External Data Email Accounts page.

Stewardship Tier (formerly Data Stewardship Platform (DSP®

Common

With the new addition of category values to Syniti’s REST API, category values can now be:

  • downloaded from data sets, goals, initiatives, missions, policies, rules, systems, terms and visions.

  • uploaded to new rules, terms, systems and data sets.

  • changed on existing rules and terms.

Refer to Integrate the Stewardship Tier with the Knowledge Tier for more information. New use cases and page descriptions are listed in the Online Help section of these release notes.

Promote

The Compare event now considers the case sensitivity of data when code is compared across two environments.

Online Help

The following new use cases are available:

The following new use cases are available for Common:

  • Add or Change Category Values for a Rule

  • Add or Change Category Values for a Term

  • Add or Change Category Values for a Data Set

  • Add Category Values for a System

The following new field description topics are available in Common:

Resolved Issues

Advanced Data Migration (ADM)

Console

Corrected an issue on the Load Cycle Execution Plan page that allowed users to enter a higher number in the DEFECT COUNT field (the number of records that failed to load) than in the OPPORTUNITY COUNT field (the total number of records). With the fix, a validation has been added to prevent users from saving this invalid record. [DSP70-1293]

Target Source SQL Automation

Fixed an issue that caused an error to display when a user clicked the Map Source icon on the Automation SQL Target Source page. With the fix, when the user clicks the Map Source icon, Map’s Target Sources page displays with details about the source selected on the Automation SQL Target Source page. [DSP70-1290]

Transform

Fixed the hardcoded timeout that caused issues when rules with large amounts of data ran in Transform. The hardcoded value of 9999 has been removed. The stored procedures use the value in the Command Timeout field on the Vertical View of the Data Sources page in System Administration. [DSP70-1461]

NOTE: After upgrading to 7.4.5 and later, clients may need to increase their data source timeouts if there are timeout issues when executing rules in Transform.

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

Assemble

Corrected an issue when using multi-threading on a source refresh that caused the processing to hang. If the number of records in the CranPort package was large (6 million records) and the package was segmented, sometimes, the segmented table's job never left the job queue. Even though the table's extract completed, the refresh job remained "spinning" in Collect. The cause was Assemble writing logs out of order. With the fix, when Assemble writes logs, it waits until the rest of the log entries, run by background threads for that task, have finished before writing the next log entry. [DSP70-1330]

Collect

Corrected an issue introduced in 7.4.4 that caused the DURATION field on the Download Metrics page to always display 0 after a table refresh. The value in this field should be identical to the value in the DURATION field on the Tables page. With the fix, the DURATION field displays the correct amount of time it took to complete the table refresh. [DSP70-1473]

Common

Fixed an issue that caused the Status icon on the System Types page to remain in Processing status after a System Type import, even after the import had completed successfully. Now, the correct status displays when the import is complete. [DSP70-1102]

Enhancement Requests from Users

Online Help

  • In Data Quality corrected the names of the industry-standard Quality Dimensions included with Data Quality on pages where the QUALITY DIMENSION field is described.

  • In Data Quality added links from the Manage Groups page to the Set Up Security page to make finding information about granting users access to reports easier

  • In Integrate updated the Create a Basic Template topic to include BDC Script and GUI Script in the list of template types

  • In Integrate added a note to the Import a BDC Script from a File topic to clarify functionality: "NOTE: The ability to record a BDC script has been removed from the Stewardship Tier 7.3 and later. BDC scripts can be created using the SHDB transaction in SAP and imported as described in this section or copied from an existing BDC script."

  • In Collect clarified functionality for the Table Rename and the Rename Table Template fields. Refer to Register Sources to Target and Manually Register Tables to Source 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.

What's New in Syniti Solutions 7.4.4

Release Date: 06/08/2021

This release contains Enhancements.

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 7.4.4. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the Stewardship Tier in version 7.4.4 and later. Consult this manual BEFORE updating to 7.4.4, as an analysis of current security assignments must be completed before the Stewardship Tier can be updated.

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

NOTE: A new, critical, step has been added to the Post Upgrade section of the Installation process. After an upgrade to Stewardship Tier 7.4.4 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.

Enhancements

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

Collect

When packages with package types BOA RFC or SAP RFC are extracted, the Stewardship Tier now removes all trailing empty spaces in columns by default. The Remove Trailing Spaces option has been added to the Vertical View of the Tables page in Collect to allow users to select the desired behavior. When upgrading, extracts using BOA RFC or SAP RFC package types will have Remove Trailing Spaces set to false. This will ensure that extracts continue to function as before the upgrade.

Common

Online Help

Added the topic Add a Custom Message to the Login Page.

What's New in Syniti Solutions 7.4.3

Release Date: 04/27/2021

This topic contains:

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 7.4.3. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the Stewardship Tier in version 7.4.3 and later. Consult this manual BEFORE updating to 7.4.3, as an analysis of current security assignments must be completed before the Stewardship Tier can be updated.

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

NOTE: A new, critical, step has been added to the Post Upgrade section of the Installation process. After an upgrade to Stewardship Tier 7.4.3, 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.

Enhancements

Advanced Data Migration

Target Design

The processing time when importing fields related to Lookup tables has been improved with the addition of a WHERE clause specifying wave, process area and object.

Construct Source Relevancy Pages

Source Relevancy pages are installed as part of new installations of the Stewardship Tier. These pages, available in Construct, support a common approach to implement data relevancy within an Advanced Data Migration project. Essentially, the pages allow consultants to document the criteria used in their relevancy rules and to then drive the transformation rules they create from this data. For further information about the Source Relevancy pages, including how upgrading customers can obtain these pages refer to the article Advanced Data Migration Source Relevancy in the Knowledge Base.

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

Promote

A new check box, Large Data, is available on theStructures - Data Table Column page to allow columns with large amounts of data (e.g., 1 MB) to work with the comparison process. If checked, the text “Large Data” displays for the Large Data column on thePackage - Data Comparison Records page instead of attempting to display the field’s content. If unchecked and a column being compared contains large amounts of data, thePackage - Data Comparison Records page will fail to load.

Collect

  • The structure of the dgTargetSouceTable has changed. The key fields for this table were previously Target, Source and Table. Starting with version 7.4.3, the table uses a key field that has a unique ID and the table now has a unique constraint for Target, Source, Table and TableRename. All child tables that have foreign key relationships to the dgTargetSourceTable have been updated to use the new unique id.

    Using Table Rename functionality, users can register multiple tables with large data sets (for example, BSEG) but with different Table Renames (for example Company Code). This allows users to extract data from target sources on a more granular level, pulling the correct data into tables named, for example, for BSEG_Company One, BSEG_Company Two, and so on.

    NOTE: These changes to table structure will cause CTS packages, DBVT packages or any scripts used to populate the target source tables built on previous versions to fail. To fix the CTS issue, upgrade, then rebuild the package. Scripts and DBVT packages will need to be modified to use the updated key fields and table structures.

  • On the Target Source Table Index Columns page, the page is now sorted by the Index ID.

  • On the Data Source Table Columns page, the page is now sorted by the Column Order

  • On the Copy Targets page, the “Target To” list box excludes the target in the “Target From” list box, as this scenario is not valid .

  • On the Table Errors page, added a link to the TABLE column to the Table page.

  • The following changes have been made to the Collect Tables page:

    • The Table Rename column was added to the Horizontal View.

    • The page order was changed to the updated key field, Target-Source-Table-Table Rename.

    • The Package Type field and the Table Rename field were moved from the Advanced Settings tab to the General tab on the Vertical View

    • The Build and Refresh and “Build Package” buttons will now be disabled if the selected table is marked as inactive

Common

  • SAP Application Server data sources allow available RFC Enabled Functions to be extracted. This extract process ran a foreground process that had the potential to timeout. To prevent this, the extract process has been updated to run in the background.

  • The following user experience improvements were made to the Knowledge Tier Connect pages:

    • A Record Count field now displays on theKnowledge Tier Download page to show the number of assets downloaded.

    • Record Counts are now included on all relationships, sponsors, contacts, supporting documentation and field icons to clearly display the number of asset details assigned to the asset.

    • The ID list box on the asset relationship upload pages now includes a friendly description of the relationship.

    • Previously, in order to use Excel integration to add system fields on the System Field Upload page, users must have first manually entered a system field before the Excel Upload icon was available. The functionality on this page has been streamlined where a system field does not have to be manually added before Excel integration can be used.

    • Many fields in the Knowledge Tier Connect were imported from the API and did not meet design standards. To align these fields to Syniti design standards, various field names were updated by adding capitalization and spaces, and removing underscores

    • For UI consistency, the Asset Support Documentation page was renamed toAsset Supporting Documentation.

    • Various fixes were made to column length issues and validations, including:

      • The Definition field on the Policy page is now set to nvarchar(max) to account for the 30,000 character limit allowed by the API.

      • The Value field for supporting documentation across all assets is now set to nvarchar(max) to account for the lack of a character limit in the API.

      • The Classification field on the Data Set Field Upload page is now hard required.

  • The following functionality enhancements were made to the Knowledge Tier Connect:

    • Users may now change existing rules and terms, and change fields on existing data sets, and publish them to the Knowledge Tier. For rules and terms, the latest draft version of the asset is updated. For data sets, this feature copies data from the Knowledge Tier; it does not consider endorsement status of the asset.

    • Users may now add fields to existing systems and data sets that were downloaded from the Knowledge Tier and add fields in order to expand the system’s and data set’s definition.

    • Users may now download system fields by utilizing the Download System Fields icon added to the System page. Be aware that systems with a large amount of fields can take a long time to download.

    • The menu links under Knowledge Tier Upload have been renamed to allow for a distinction between creating and changing rules, terms and data sets:

      • Rule > Create Rule

      • Term > Create Term

      • System > Create System and Fields

      • Dataset > Create Data Set and Fields

    • The Asset Mapping field on theSKT Sub Assets Mapping page has been updated to include the action (GET, PUT or POST) along with the asset name to clarify the action being performed on the asset.

    • An Asset URL icon is available on the asset download pages. Click the icon to launch the Knowledge Tier and view the downloaded asset is linked to the asset in the Knowledge Tier.

    • The following new pages are available in Common:

      • Select Existing System for Adding New Fields

      • Select Existing Data Set for Adding New Fields

      • Select Existing Rule for Change

      • Change Rule Relationship

      • Change Rule Sponsor

      • Change Rule Supporting Documentation

      • Select Existing Term for Change

      • Change Term Relationship

      • Change Term Sponsor

      • Change Term Supporting Documentation

      • Change Rule

      • Change Term

      • Select Existing Data Set for Change

      • Change Data Set

      • Change Data Set Field

      • Change Data Set Relationship

      • Change Data Set Contact

      • Change Data Set Supporting Documentation

  • In this release, it is not possible to add or change category values on new or existing rules and terms. If you need to do this, please contact Syniti Support who will advise how this can be done.

  • Syniti is now delivered with API stored procedures to post assets. Refer to Use API Stored Procedures to Post Assets for more information.

Syniti Data Replication

The 7.4.3 version of the Stewardship Tier is compatible with Syniti Data Replication 9.7.3.3.

Resolved Issues

Advanced Data Migration

SQL AutoGen

The Rebuild – Alter Table and Drop & Rebuild Views And Stored Procedures option for the AutoGen Level on the Automation page has been updated (and renamed) to no longer drop and alter the source table and target tables. Only views and stored procedures are dropped and rebuilt. [DSP70-1218]

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

Fixed issues that caused slow Excel Import performance when inserting and updating records on a page with a large number of records already added to the page. For example, before the fix, an Excel import to update 10k records over a table with 20k records took 2 mins 28 secs. With the fixes, this import process now takes 23 secs. [DSP70-1281]

Integrate

Fixed an issue that caused a posting to fail and a Timeout error to display when posting large data sets. The error occurred if:

  • The process post’s underlying view contained a number of records that took longer than 30 seconds to process, and

  • The process post’s WHERE clause did not limit the maximum posting time to 30 seconds

With the fix, the Timeout error does not display in this situation and large data sets can be posted. [DSP70-1278]

System Administration

When a report is executed in Transform with the Publish option enabled, .xlsx files are generated in the Transform directory and in the C:\Windows\Temp folder on the application server. Previously, these files were not deleted, which caused the system to run out of space quickly. Now, these temporary .xlsx files are deleted from the C:\Windows\Temp folder after the report is generated. [DSP70-1229]

Known Issue

In Collect, on the Tables page, the Package Type of Syniti Connect displays as IG Universal Connect in the Package Type list box. This option will be updated in a future release.

What's New in Syniti Solutions 7.4.2

Release Date: 2/25/21

This topic contains:

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 7.4.2. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the Stewardship Tier in version 7.4.2 and later. Consult this manual BEFORE updating to 7.4.2, as an analysis of current security assignments must be completed before the Stewardship Tier can be updated.

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

NOTE: The Stewardship Tier is now certified with MS SQL 2019 with Transparent Data Encryption (TDE) activated. Note that enabling TDE has a measurable performance impact. According to Microsoft, TDE has an estimated performance impact of 3-5% (https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/security/transparent-data-encryption). Syniti testing has confirmed this, and in some cases an even higher impact on performance.

New Features

S/4 HANA Right Sizing Analysis

SAP S/4 HANA is revolutionary. Its in-memory platform, real-time analytics and applications deliver unrivaled speed, efficiency, and scale leading to significant business benefits. Without effective data management, the potential benefits of migrating to S/4 HANA can be reduced or even lost. Right Sizing for SAP S/4 HANA streamlines the data you put into S/4 HANA, to ensure it runs simply, powerfully, and efficiently. In this release, Syniti is delivering analysis software that will help customers to right size their data prior to migration.

Our S/4 HANA Right Sizing Analysis software will help you to:

  • Evaluate all your Business Suite data Identify old or infrequently accessed data for archiving

  • Test ‘what if’ scenarios to confirm what data can be safely delete

  • Accurately specify your S/4 HANA appliance requirements

By streamlining your data:

  • The cost of migrating to S/4 HANA will be reduced

  • Ongoing hardware costs will be significantly lower

Integrate the Knowledge Tier and the Stewardship Tier

With the aid of Synit’s REST API, the Stewardship Tier and the Knowledge Tier can be integrated. Integration between these two tiers could be very useful on a project, such as to:

  • Jump start Data Quality. Download Jump Start Rules into the Stewardship Tier and tie the implementation of the rule in Transform to the Knowledge Tier rule.

  • Migration Harvesting. Upload systems, data sets, terms, rules, etc from a migration initiative run on the Stewardship Tier into the Knowledge Tier to seed data governance initiatives moving forward or moving from a migration project to business-as-usual initiatives.

  • Data Catalog Population. Systems and data sets produced on the Stewardship Tier can be ingested into the Knowledge Tier to seed the catalog for Data Governance-based initiatives.

Common is now delivered with a new set Knowledge Tier Connect pages used to:

  • Configure a connection to a Knowledge Tier tenant

  • View asset mappings that detail how the SwaggerHub endpoint definitions are linked to the object structure

  • Download assets from the Knowledge Tier

  • Create and upload assets to the Knowledge Tier

For detailed information, refer to Integrate the Stewardship Tier with the Knowledge Tier.

Enhancements

Advanced Data Migration

Map

The process for removing unused source values when value mapping has been improved. A user can now access a Remove Values button at the wave, check table and wave / check table / source level to quickly remove all source values that have:

Refer to Remove Unmapped Source Values for more information.

Stewardship Tier Advanced Data Migration Content

To help accelerate migration projects, Syniti is focused on bringing its experience to every project. One of the ways Syniti does this is through the deployment of content via Knowledge Packs.

This content is shipped with Stewardship Tier 7.4.2 and above.

ADM Process Areas and Objects

From Stewardship Tier 7.4.2 and above, Advanced Data Migration (ADM) is delivered with a set of process areas and objects that are most commonly used across the migration projects that Syniti works on. This list of objects is independent of target systems and is based on decades of experience across a wide range of systems.

The specific process areas and objects that are delivered are listed in the following sections.

Process Areas

The following process areas are included in new installations (not upgrades) of the Stewardship Tier version 7.4.2 and above:

  • SAM01CF - Cross Functional

  • SAM01CRM - Customer Relationship Management

  • SAM01EHS - Environmental Health & Safety

  • SAM01FM - Financial Management

  • SAM01GTS - Global Trade System

  • SAM01HCM - Human Capital Management

  • SAM01JVM - Joint Venture Management

  • SAM01MM - Material Management

  • SAM01P2P - Procurement

  • SAM01PLM - Product Lifecycle Management

  • SAM01PM - Plant Maintenance

  • SAM01PP - Production Planning

  • SAM01PRA - Production Revenue Accounting

  • SAM01PROJ - Project Management

  • SAM01QM - Quality Management

  • SAM01RE - Real Estate Management

  • SAM01SD - Sales & Distribution

  • SAM01SM - Service Management

  • SAM01TM - Transportation Management

  • SAM01WM - Warehouse Management

Objects

The following objects are included in new installations (not upgrades) of the Stewardship Tier version 7.4.2 and above:

  • CF0020: Classification

  • CF0030: Business Partners

  • CF0040: Customer Master

  • CF0050: Business Partner Contacts

  • CF0060: Site Master

  • CF0080: Vendor Master

  • CRM0010: Customer Relationship Management

  • EHS0010: Phrase Master

  • EHS0020: Substances

  • EHS0030: Hazardous Substance Master

  • EHS0040: Dangerous Goods Master

  • EHS0050: MSDS

  • EHS0060: Specification Management

  • FM0010: G/L Account

  • FM0020: Cost Elements

  • FM0040: Credit Management (BP)

  • FM0070: Internal Order

  • FM0080: Bank Master

  • FM0120: GL Balances

  • FM0130: GL Open Items

  • FM0140: Open Accounts Payable

  • FM0150: Open Accounts Receivable

  • FM0160: Allocation Cycles

  • FM0300: Asset Management

  • FM0410: Cost Centre

  • FM0420: Profit Centre

  • FM0430: Activity Type

  • FM0450: Cost Centre Group

  • FM0460: Profit Centre Group

  • FM0470: Statistical Key Figures

  • FM0600: Treasury Managment

  • FM0700: Grant Managment

  • GTS0100: ECCN Assignments

  • GTS0200: GTC Assignments

  • GTS0300: HTS Assignments

  • GTS0400: Schedule B Assignments

  • HCM010: Organizational Management

  • HCM020: Personnel Administration

  • HCM030: Recruitment

  • HCM040: Payroll

  • HCM050: Travel Management

  • HCM060: Personnel Management

  • HCM070: Time Management

  • HCM080: Compensation Management

  • HCM090: Training & Event Management

  • HCM100: Wages

  • HCM110: Personnel Development

  • HCM120: Workforce Administration

  • JVM100: Joint Venture Management

  • MM0010: Material Master

  • MM0020: Article Master

  • MM0030: Batch Masters

  • MM0040: Batch Strategy

  • MM0050: Article Brands

  • MM0060: Article Listing

  • MM0070: Article Merchandise Category

  • P2P0030: Purchases Info Record

  • P2P0080: Purchase Order

  • P2P0090: Scheduling Agreements

  • P2P0120: Outline Agreement

  • P2P0130: Purchasing Pricing Agreements

  • P2P0150: Receipts

  • P2P0350: Source Lists

  • P2P0360: Conditions for MM Output Determination

  • P2P0370: Quota Arrangements

  • P2P0380: Purchasing Contracts

  • PLM0010: Material Master

  • PLM0030: DIR

  • PLM0040: Material Classification

  • PLM0050: Equipment Master

  • PLM0070: Interchangeability

  • PM0400: Work Centers

  • PM0410: Functional Locations

  • PM0420: Equipment Master

  • PM0430: Equipment BOMs

  • PM0440: Maintenance Catalog Codes

  • PM0450: Task Lists

  • PM0470: Maintenance Plans

  • PM0480: Open PM Orders

  • PM0490: Measuring Point

  • PP0210: Manufacturing Work Centers

  • PP0220: Bills of Material

  • PP0230: Routing

  • PP0240: Production Versions

  • PP0250: Planned Independent Requirements

  • PP0260: Recipes

  • PP0270: Open Production Orders

  • PRA0010: Production

  • PRA0020: Ownership

  • PRA0030: Contractual Allocations

  • PRA0040: Revenue Accounting

  • PROJ0010: Project Planning

  • PROJ0020: Project Preparation

  • PROJ0030: Project Tracking

  • PROJ0040: Project Reporting

  • PROJ0050: Project Costs

  • PROJ0060: WBS Elements

  • PROJ0070: Project

  • PROJ0080: Project Artists

  • QM0010: Inspection Methods

  • QM0020: Inspection Plans

  • QM0030: Master Inspection Characteristics

  • QM0040: Info Records

  • QM0050: Catalog Codes

  • QM0060: Inspection Setting

  • QM0070: Quality Notifications

  • QM0080: Quality Level

  • RE0010: Real Estate Management

  • SD0010: Customer Contacts

  • SD0020: Billing Output Conditions

  • SD0030: Sales Contract

  • SD0040: Open Sales Orders

  • SD0050: Open Quotations

  • SD0060: Scheduling Agreements

  • SD0070: Customer Material Info Record

  • SD0080: Price Conditions

  • SD0090: Rebate Agreements

  • SD0110: Material Determination

  • SD0120: Listing & Exclusion

  • SD0150: Open Quantity Contract

  • SD0160: Service Plans

  • SD0180: Batch Determination

  • SD0190: Unloading Points

  • SM0010: Repair Orders

  • SM0020: Service Contracts

  • SM0030: Service Notifications

  • SM0040: Service Orders

  • SM0050: Service Quotations

  • SM0060: Warranties

  • TM0020: Freight Order Management

  • TM0030: Freight Settelment

  • TM0040: Org Management

  • TM0050: Planning

  • TM0060: Transportation Network

  • WM0020: Distributed Order Management

  • WM0030: Inbound Management

  • WM0040: International Trade & Customs

  • WM0060: Outbound Management

  • WM0070: Pick to Sequence

  • WM0080: Warehouse Tasking

  • WM0100: MM Ext to EWM

  • WM0110: Storage Bins

  • WM0120: Control Cycles

  • WM0130: Production Supply Areas

  • WM0140: Control Cycles IM

  • WM0150: Packaging Instructions

  • WM0160: Inventory Balances

  • WM0170: Last Bin Count Date

  • WM0190: Supersession

  • WM0200: Reference Product

  • WM0210: Handling Units

  • WM0220: Inbound Deliveries

S/4 HANA Target Design Knowledge Pack

Refer to the section S/4 HANA Target Design Knowledge Pack in the Installation and Upgrade Manual for information about the S/4 HANA Target Design Knowledge Pack.

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

The executionTimeout property has been updated to 300 seconds in the web.config file. In 7.4.1, it was set to a 90 second default. This update will cause all foreground events to timeout after 300 seconds. For more information about this setting, refer to the Knowledge Base article Foreground Events Time Out After 300 Seconds.

Promote

  • Syniti has added Promote configuration (Structure Data, Structure Objects and Package Templates) to support the comparing and transporting of Integrate code. With this change, users are now able to easily transport Integrate Categories, Templates and Processes across their Stewardship Tier landscape.

  • There were two SQL field data types that could not be transported due to limitations in Promote: varbinary and image. A new field was added to the Structures - Data Table Columns page, BINARY DATA, which if checked, signifies that binary data exists in the designated column within the source database and Promote applies specific logic to convert these binary columns to an encoded format that is able to be transported to the target. Specifically, this new field fixes an issue in Integrate where some BAPI connection data is stored in an image column.

Syniti Data Replication

The 7.4.2 version of the Stewardship Tier is compatible with Syniti Data Replication 9.7.2.28.

Online Help

The Installation and Upgrade Manual and the Software Requirements and Hardware Sizing Guide been moved online.

The following new use cases are available for Common:

  • Integrate the Stewardship Tier with the Knowledge Tier

  • Set Up Security for Stewardship Tier and Knowledge Tier Integration

  • Download and View Assets from the Knowledge Tier

  • Upload Rules to the Knowledge Tier

  • Upload Terms to the Knowledge Tier

  • Upload Systems to the Knowledge Tier

  • Upload Datasets to the Knowledge Tier

  • Plugin Troubleshooting

The following new field descriptions topics are available in Common:

  • Asset Contact

  • Asset Relationship

  • Asset Sponsor

  • Asset Support Documentation

  • Category

  • Category Value

  • Dataset

  • Dataset Contact Upload

  • Dataset Field

  • Dataset Field Upload

  • Dataset Relationship Upload

  • Dataset Supporting Documentation Upload

  • Dataset Upload

  • Goal

  • Initiative

  • Knowledge Tier Download

  • Knowledge Tier Tenant

  • Mission

  • Policy

  • Program

  • Rule

  • Rule Relationship Upload

  • Rule Sponsor Upload

  • Rule Supporting Documentation Upload

  • Rule Upload

  • Knowledge Tier Asset Mapping

  • Knowledge Tier Asset Mapping Fields

  • Knowledge Tier Sub Assets Mapping

  • System

  • System Contact Upload

  • System Field Excel Upload

  • System Field Range Value Upload

  • System Field Tags Upload

  • System Field Upload

  • System Information

  • System Relationship Upload

  • System Supporting Documentation Upload

  • System Upload

  • Term

  • Term Relationship Upload

  • Term Sponsor Upload

  • Term Supporting Documentation Upload

  • Term Upload

  • User

  • Vision

Data Quality

Lingering references to “dspMonitor” in workflow messages, SQL statement and stored procedures have been updated to “Data Quality.”

Resolved Issues

Master Data Management

In large Master Data Management implementations, there is a tendency that the processes determining user access to request roles to suffer from performance problems. In this release, Syniti has made several important changes to the process to prevent issues from occurring and to give users a better experience. The most notable change made involves pushing the main SQL stored procedure (webRequest_SecurityIns) that rebuilds request security into a job that runs in the background. This change has been implemented everywhere except in the apiFinalizeRequest procedure. To reduce the frequency that the webRequest_SecurityIns procedure runs, logic has been added to the process that creates the backgrounds so that a job is added only if there is not another job that would result in the same security rebuild waiting in the job queue. Additionally, there has been some optimization of SQL code to ensure better overall performance and significantly reduce the occurrence of deadlocks.

Since the request security update process is now moved to the background, a control parameter Security Job Queue (on the MDM Parameterspage) has been added to the Master Data Management application to allow customers to select which job queue and ultimately which Windows services are used to process the jobs that update request security. The default job queue is ‘General’; however, since other jobs run on this queue, Syniti recommends that customers monitor the queue traffic and time taken for security updates to run to ensure the updates are not queued to run for too long. If there are delays, customers can create a dedicated queue with a higher priority than other queues. The number of allowable parallel running request security updates processes can also be set using the Master Data Management parameter (Security Job Threads, also set on the Parameters page). The recommendation is to use the default value of 2, but this can be raised if there is often a backlog of entries that take time to run. Increasing this too far could result in deadlock, so any increases should be monitored.

Summary of Important Changes

  1. Direct calls of procedure webRequest_SecurityIns now result in the creation of background jobs. Previously, this procedure was run as a foreground event. Refer to the Knowledge Base article Stewardship Tier 7.4.2 MDM Request Security Changes for more information.

  1. Adding / removing of Position Category Org Units may result in a background job being created that updates Read Only status of Role Level Org Units.

  2. Two new Parameters have been added to control the processing of MDM background security jobs:

    • Security Job Queue

    • Security Job Threads

  3. Multirow action has been removed from the Assign All Org Units on the Category Org Units for Position page.

IMPORTANT! If any local, core modifications have been made to the way any of the MDM Security related procedures run, it’s recommended that the changes are reviewed BEFORE upgrading. [DSP70-731]

Advanced Data Migration

Transform

Corrected an issue that occurred when the Generate Documentation check box was checked on the Transform tab of theParameterspage in Console and a target with a long table or object name was processed in Transform. An error displayed: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. EndTargetSource: 7d602a5d-2b69-4069-9fbe-12183d17045e failed to execute." The field length was updated, and this error no longer displays. [DSP70-1190]

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

System Administration

Corrected an issue with Excel import functionality when importing more than 10k records. Prior to the fix, the Excel Results panel failed to appear at the end of the import. With this change, the import runs to completion, and the Excel Results panel appears and includes the counts of the number of inserted and updated records.

NOTE: For performance reasons, if more than 10k records are inserted and updated, the counts display on the Excel Results panel, but the individual record's changes do not display.

NOTE: Two other scenarios can cause the Excel import to fail:

  • If the Excel import takes longer than the foreground event timeout set in the web.config file, the Excel import will hang. If this happens, the "Thread is aborted" error displays on the Messages page or “The request has been aborted” displays in the Windows Event logs. The foreground event timeout can be changed via these instructions in the Knowledge Base: Foreground Events Time Out After 90 Seconds

  • If the Excel import exceeds the record count configured on the Excel Import Record Limit setting (currently defaulted to 100k) on the Parameters page, under the Page Parameters tab in System Administration, an error displays during the upload. [DSP70-1245]

Common

Previously, fields (used to determine whether records were in sync) that were encrypted on the Data Sources page in System Administration and on the Data Source Registry page in Common would cause the Out of Sync indicator to be populated on the Data Source Registry page. This occurred because the encryption process generates different hashed values even if the unencrypted values are identical on both pages. Since Passwords and Connection Strings are now delivered as encrypted, the Out of Sync indicator is shown after installation. To resolve this issue, Passwords and Connection Strings fields are now excluded when determining whether or not data sources are out of sync. [DSP70-1103]

Enhancement Requests From Users

What's New in Syniti Solutions 7.4.1

Release Date: 12/10/2020

This topic contains:

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 7.4.1. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the Stewardship Tier in version 7.4.1 and later. Consult this manual BEFORE updating to 7.4.1, as an analysis of current security assignments must be completed before the Stewardship Tier can be updated.

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

Enhancements

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

A change has been made in version 7.4.1 and later to improve performance. In previous versions, the compilation debug setting in the web.config file on the Stewardship Tier Installation directory (Program files (x86)\BOA\DSP\Web) was set to true. In some situations, this setting resulted in noticeable degradation of Stewardship Tier performance. It also allowed foreground events to potentially run for extended periods of time.

For 7.4.1 and later, the compilation debug setting is set to false. This update will cause all foreground events to timeout after 1 minute and 30 seconds. (A message displays in the Quick Panel on the right of the Stewardship Tier if a foreground event times out). In previous versions, foreground events would not time out unless the user session expired.

NOTE: In large Stewardship Tier installations, there is a possibility that foreground events that previously took more than 1 minute 30 seconds will now terminate before they complete.

To prevent this from happening, a new property (executionTimeout) has been added to the web.config file. To override the default 90 seconds timeout, users can provide their own value. Syniti recommends changing this value to 300 seconds. In the case of a custom application, users could also choose to change specific foreground events to run in the background.

Another update to the web.config file was added to help ensure the proper permissions are applied. The new tempDirectory setting is located after the compilation debug setting in the web.config file. In previous versions the temp directory was in the OS .NET folder structure and not guaranteed to have the correct permissions for the web site to operate. By defining the temp directory, the user can ensure the appropriate Stewardship Tier site permissions are applied. By default, this setting is set to the installation directory, but can be updated.

Collect

  • A new source connection type called ODBCPostGreSQL is available to help set up a PostgreSQL connection for data extraction.

  • If the WHERE clause for a SAP RFC or a BOA RFC is greater than 72 characters, the WHERE clause is now broken down into several lines based on the last white space character before the 72-character limit on each line. If there are no white spaces, a new WHERE clause line after the 72 characters is created. In addition, a validation error has been added to the Tables page to warn the user if they have a WHERE clause with 72 adjacent characters and no spaces. To troubleshoot, enable debug logging for Collect to see how the WHERE clause was split into several lines.

  • In order to better support the extraction of large datasets, changes have been made to the Stewardship Tier platform to ensure that datasets in excess of 2.1 billion records can be handled correctly. Notable changes to the product to support this change include the use of BIGINT (instead of INT) data types for fields containing record counts and the use of COUNT_BIG (instead of COUNT) to get table record counts.

Promote

  • New Structure Data, Structure Objects and Template Groups are now delivered for Data Quality and Custom WebApps. In addition, the following updates have been made to existing configurations:
    • Structure - Data:

      • Administration—Data Source: DataSourceName is now a Simple Selection value for DataSource

      • Assemble—Package: PackageName is now a Simple Selection value for the CPPPackage table

    • Template Groups: <ADM Configuration>
      • Common—System Type is now part of this Template Group

  • A new security role for Promote has been added, called Promote User. This role can perform basic functions within Promote, such as create, compare and transport packages, but does not have any administrative permissions. Refer to Set Up Security for Promote for more information on security roles.

  • A new service page, called Remove Temp Host Dest Records, is available for Promote. When a Package Group or a Package is deleted, this service page deletes the data in the following tables:
    • PackageObjectDependent_TempDest
    • PackageObjectDependent_TempHost
    • PackageStructureData_TempDest
    • PackageStructureData_TempHost

    This new service page (and all Stewardship Tier service pages) can be viewed from the Services Pages page in System Administration.

  • The Structure Object Focus Database field was removed from the Packages Template page because it was obsolete.

  • Several unused or duplicate pages were removed:
  • Two updates were made to the Structures - Data page:
    • The Vertical View was removed because the associated fields had no functional use.
    • The Packages icon was updated to solely a record count because the previous icon was not linked to an underlying page nor did it need to be linked.
  • To separate application settings by functions that are only performed by a Promote Code Promotion Manager, various fields were moved from the Application Parameterspage to a new page, called Advanced Promote Actions. In addition, this new page also contains a new field: Transform Object Template. This field allows users to select a custom template to be used when the Crawl All Transform Objects button is clicked. The Advanced Promote Actions page is available to Promote Code Promotion Managers and Promote Users; the Application Parameters page is only available to Promote Code Promotion Managers.

Online Help

We have added video tutorials for the following Promote topics:

Advanced Data Migration

Console

A status indicator has been added to the Vertical View of the Process Area: Object page to track the Unit Test status of objects. This indicator will be used in a future release of the Migration dashboards. Refer to Track Report and Load Program Status for more information.

Master Data Management

RFC-based extracts for final finish tables have been added to MDM. Finish Type CranPort has been renamed Collect and users can now use the Collect Finish Type to extract data using SAP RFC or BOA RFC. These new extract methods support the passing of a WHERE clause to reduce data extraction times. The Collect Finish Type continues to support extraction using CranPort.

Resolved Issues

Master Data Management

In scenarios where Stewardship Tier users are logged in using Windows Authentication and Managed Pipeline Mode is set to Integrated in IIS manager, users experienced failures when a request containing validation error was Finished. This issue has been fixed by including an updated version of the RazorEngine.dll in the software installation package. [DSP70-454]

Mass Maintenance

Previously, users received an error message when trying to save an electronic signature record if the Comment exceeded 200 characters. The record was saved when the error was disregarded, but the Comment itself was not saved. Now, a validation message displays when the record is saved if the comment exceeds 200 characters. Users must reduce the Comment to fewer than 200 characters in order to save the record. [DSP70-1189]

Advanced Data Migration

Map

  • An error occurred when syncing from Target Design to Map if the user followed this particular navigation path:

  1. Click Design in the context bar.

  2. Click the Sources icon for a target.

  3. Click the Mapping icon for a source.

  4. Click the Sync from Target Design icon in the Page toolbar.

    The issue has been corrected and the sync process runs as expected when the user follows this navigation path. [DSP70-1101]

  • An issue occurred in Map and a validation warning was thrown when:

  1. Target Design had been completed for a table and a source was added to the table in Target Design.

  2. The target was then synced to Map.

  3. In Map, the user selected a source table from the assigned source to assign to the target on the Target Sources page.

NOTE: The selected sources table had at least 1 primary key and was not currently in the source System Type.

  1. The user saved the record.

NOTE: The validation warning “No key was found for this Source Database Object” displayed.

With the fix, the record saves successfully in this scenario. [DSP70-1177]

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

Fixed an issue that occurred when adding a translation to a page in a custom WebApp that had no custom catalogs registered to it. The issue occurred for a user who was not using a Design license. Previously, when the user clicked the Edit Page Help icon for a column on the Pages page, a record could not be added, as the Stewardship Tier required the user to select a catalog from the Catalog ID list box. Because the custom WebApp did not have any catalogs registered to it, the list box was empty. With the fix, users can add a translation to a column property on a page in a custom WebApp by clicking the Edit Page Help icon on the Pages page. [DSP70-365]

Stewardship Tier Upgrade Impact:

  • When upgrading from DSP 7.0.6 or below to Stewardship Tier 7.4.1 or above, Collect target sources that include SAP connection details will automatically have the saved connection string details converted into a new Data Source of type SAP Application Server. The newly created SAP Application Server Data Source will then be assigned to the Collect target source. After upgrading, it’s important to review and test all Collect target sources to ensure they function correctly. [DSP70-740]

Collect

  • Fixed an issue in Collect when adding new tables (on the Tables page) to a Target Source that was configured to use the SAPAPPSERVER Source Connection type. If the default Collect Package Type was set to BOA RFC, newly added tables were being incorrectly created with the "SAP Data Services using RFC" package type. With the fix, the correct "default" package type is used when adding new tables to SAPAPPSERVER Target Sources. [DSP70-1188]

  • Fixed an issue when using SAP RFC or BOA RFC package types to download tables. Even though the Refresh was marked as successful in Collect and in the Job Queue, the process ended with errors that were not displayed. The value in the Record Count field on the General Information tab on the Vertical View of the Tables page and the number of records in the Table in SQL did not match the record count that should have been extracted when the Refresh process successfully completed. With this fix, if there is a failure during the extraction, the extract will terminate and the reason for error will be available. [DSP70-1226]

Promote

  • The comparison functionality failed when comparing a table with 40 or more columns. With this fix:

Enhancement Requests From Users

What's New in Syniti Solutions 7.4

Release Date: 11/02/2020

This topic contains:

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 7.4. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the Stewardship Tier in version 7.4 and later. Consult this manual BEFORE updating to 7.4, as an analysis of current security assignments must be completed before the Stewardship Tier can be updated.

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

New Feature

Stewardship Tier 7.4 introduces Promote - a new platform module that enables Stewardship Tier solutions to be promoted through a multi-tier landscape. Promote works by comparing the data held within Stewardship Tier application tables and SQL objects created by users between host and destination Stewardship Tier instances and informs users of the differences. Users are then able to selectively transport the changes they require. Promote directly replaces the psaTransport tool and will eventually replace the embedded CTS functionality. Refer to the article Top Benefits of using Promote Over CTS for more information. In 7.4, Promote is delivered with configurations to support the Transport of Advanced Data Migration solutions. Refer to the Advanced Data Migration Code Promotion standard operating procedure for more information. Configurations for other solutions will be added in upcoming releases.

NOTE: To use Promote, a new Stewardship Tier license must be installed. Request a new license by opening a support ticket with Syniti support.

Enhancements

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

The Stewardship Tier is now compatible with Syniti Data Replication 9.7.1.

Online Help

Resolved Issues

Collect

  • Fixed an issue related to downloading BOA RFC package types. In version 7.1.3, performance improvements were introduced and these improvements were maintained through version 7.3.0. These improvements were lost in version 7.3.1. For example, a table download of 23K records, with an RFC Records per Call value of 5000 (the default value) takes 42 minutes in 7.3.1, while on previous versions (7.1.3 and later) it takes a consistent 57 seconds. With the fix, the download speed is consistent with the RFC download improvements that were implemented in 7.1.3, and persisted through all versions up to 7.3.0. [DSP70-1197]

    NOTE: Do not set the Trace Level for Collect to Debug on the Debug Logs page in Common. This option generates detailed messages and can slow performance.

  • The table rename option did not work for DBMoto and Data Services package types; the issue has been resolved and table rename now works as expected. In addition, the Table Rename field was removed from the Tables page for Syniti Connect, Excel Import and SAP Text packages because the field was not applicable to those package types. [DSP70-1054]

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

Stewardship Tier Upgrade Impact:

  • When upgrading from DSP 7.0.6 or below to Stewardship Tier 7.4 or above, Collect target sources that include SAP connection details will automatically have the saved connection string details converted into a new Data Source of type SAP Application Server. The newly created SAP Application Server Data Source will then be assigned to the Collect target source. After upgrading, it’s important to review and test all Collect target sources to ensure they function correctly. [DSP70-740]

Enhancement Requests From Users

  • Updated the Collect topic Encrypt CranSoft® DataSource Password with a link to the System Administration topic Encrypt Password for CranSoft® DataSource.
  • Clarified the Page Design Guidelines topic with this note: "A custom page built in the Stewardship Tier will not operate correctly when the framework can’t determine the page’s primary key(s). The framework can determine the key(s) automatically when the page is built based on a table with a primary key defined. The platform cannot determine the key(s) automatically when the page is built on a view or on a table with no primary key. In this case, a key must be assigned to the page."

What's New in Syniti Solutions 7.3.1

Release Date: 8/31/2020

This topic contains:

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 7.3.1. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the Stewardship Tier in version 7.3.1 and later. Consult this manual BEFORE updating to 7.3.1, as an analysis of current security assignments must be completed before the Stewardship Tier can be updated.

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

7.3.1 Enhancements

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

A new check box format called INFOR LN (Yes or No) has been added. This format is used for pages developed in custom WebApps that integrate with INFOR technology. This check box passes 1 for True and 2 for False.

Syniti Connect (formerly IG Universal Connect)

As part of the continued rebranding effort, “IG Universal Connect” list box options have been renamed to “Syniti Connect” for the following fields:

Collect

To clean up unused columns and to resolve duplicate columns between the Data Source Tables and the Tables pages, the Data Source Tables page was removed. The Columns and SQL Commands icons from the Data Source Tables page were added to the Tables page under the General tab.

7.3.1 Resolved Issues

Advanced Data Migration

Console

  • Wave Load Cycles and Milestones are copied as part of the Wave Copy process. However; the copied Milestone used the wave / load cycle GUID from the original wave instead of the new wave. This issue has been fixed; the copied Milestone now uses the GUID from the new wave. [DSP70-1074]
  • Corrected an issue when processing multiple records on the Load Cycle Execution Plan page that had Warning messages. Accepting the Warning message only updated the status of the record on which the warning was accepted. The other records had an unknown status. In this fix, the associated validations have been changed to Messages ensuring that all records have the correct status. [DSP70-1086]
  • The behavior of the View Notice Indicator on the Load Cycle Execution Plan page has been updated to improve the user experience. Previously, the indicator displayed after the user clicked the Run Count Views icon, and only under certain situations. In this version, the icon displays with the tool tip "Opportunity and Defect Views Not Configured" after the user clicks the Update From Template icon. The user then clicks the Run Count Views icon, and the indicator displays tool tips if the views fail to run or if there are missing or changed configurations. [DSP70-1087]

Map

Corrected an issue that caused the generated SQL for the Xref mapping to use an incorrect value for the join when using a look up table with multiple keys. With the fix, the SQL generated for validation reports related to multi value key lookup tables includes the correct table join criteria. [DSP70-1092]

AutoGen

The AutoGen.dbo.boaGetCranPortSelectColumnList scalar function did not work with sources that had spaces in the key field names. The function has been modified and now works as expected. [DSP70-1096]

Master Data Management

Corrected an issue in how due dates for SLAs were calculated when a Begin Date came after a Finish Date on the same day. For example, if a work day on the calendar was from 9:00 to 17:00, then a role started on the same day after 17:00, the Due Date was set to the same day at 17:00, which was in the past. With the fix, the Due Date for the SLA is calculated correctly. [DSP70-1097]

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

In this release, Excel Integration functionality in conjunction with field controls has been updated so that the appearance and behavior of the Excel spreadsheet columns are aligned with the page columns on which they are based. Additionally, when using Excel templates that were not created by the Stewardship Tier, under some circumstances, users were able to add or change data in error.

The key changes that have been made are:

  • Fields hidden by Page Control Views were previously available in Excel Integration templates and could, in certain circumstances, permit data to be updated when a template was imported into the Stewardship Tier. With this update, hidden fields that are not primary keys are excluded from the Excel Template.
  • Under certain circumstances, fields disabled by Page Control Views could update data when a template was imported into the Stewardship Tier. With this update, disabled fields no longer allow update or addition when a template is imported.
  • When using Excel integration, in cases where a Horizontal view included fields that did not belong to the underlying table, the fields were not included in the spreadsheet. With this change, these fields are now included in the Excel template but cannot be edited. The import process also excludes these fields.

NOTE: Pages developed in custom WebApps including MDM (previously dspConduct) and Mass Maintenance (previously dspCompose) that use Excel Integration may now function slightly differently. Therefore, when upgrading to this release or above, all such pages should be thoroughly tested and adjusted accordingly. Refer to Exclude Columns from Excel Integration for more information. [DSP70-1068]

Stewardship Tier Upgrade Impact:

  • When upgrading from DSP 7.0.6 or below to Stewardship Tier 7.3.1 or above, Collect target sources that include SAP connection details will automatically have the saved connection string details converted into a new Data Source of type SAP Application Server. The newly created SAP Application Server Data Source will then be assigned to the Collect target source. After upgrading, it’s important to review and test all Collect target sources to ensure they function correctly. [DSP70-740]

7.3.1 Enhancement Request From Users

The Maximum Retry Interval description throughout Automate was updated to be clearer with a concise example.

What's New in Syniti Solutions 7.3

Release Date: 8/12/2020

This topic contains:

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 7.3. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the Stewardship Tier in version 7.3 and later. Consult this manual BEFORE updating to 7.3, as an analysis of current security assignments must be completed before the Stewardship Tier can be updated.

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

7.3 Enhancements

  • The Stewardship Tier now supports Windows Server 2016 and Windows Server 2019; Windows Server 2012 is no longer supported. Refer to the Installation & Upgrade Manual for more information.
  • The Stewardship Tier no longer supports 32-bit mode services. Clients running the Stewardship Tier in 32-bit mode are recommended to switch to 64-bit mode prior to upgrading to version 7.3 to allow sufficient testing before upgrading. If issues occur during the switch to 64-bit mode, it is easier to roll back the architecture switch than the entire upgrade. As a result of this change, any clients that need to extract from systems using 32-bit drivers need to contact Syniti Support in order to obtain a 32-bit version of Syniti Data Replication. This tool enables continued extraction from systems that rely on 32-bit drivers. Refer to the Installation & Upgrade Manual and the 32-Bit Support Dropped for Stewardship Tier 7.3 knowledge base article for more information.

  • The Knowledge and DSP Connectors are now included in the Stewardship Tier installation files instead of being separately provided by Syniti Support. Refer to the Installation & Upgrade Manual for more information.

  • The Stewardship Tier is now certified to run the Microsoft Edge (Chromium) browser while certification against IE 11 has been discontinued. Due to browser technology constraints, functionality to create BDC Script Integrate templates directly from the Stewardship Tier (Integrate and Mass Maintenance) has been deprecated; however, BDC recordings can still be recorded in SAP and imported into the Stewardship Tier to use this functionality. Additionally, support for the creation of new SAP GUI Integrate templates has been deprecated. Existing GUI Script Integrate templates will continue to work. Refer to the Integrate and Mass Maintenance release notes for more information.

Advanced Data Migration

Console

  • A Load Cycle can now have an associated instance assigned to it to tie data in Migration and Data Quality dashboards in the Knowledge Tier to the correct instance in the Stewardship Tier for multi-tier implementations. Refer to Manage Load Cycles for more information.
  • The following items associated with Load Cycle Execution Reporting can now be used by the CTS process:

    • Console—Execution Group

    • Console—Wave Execution Group Values

    • Transform—Execution Plan Template

  • Migration Execution Levels have been added to allow users to define, by object, at what level they want to perform execution-related tasks. For example, for some objects, all target tables are processed and loaded together. For other objects individual target tables may be processed and loaded one by one. Refer to Migration Execution Levels and View Migration Execution Levels for more information.
  • Migration Execution Groups have been added to allow users to specify how execution tasks need to be tracked and recorded to provide the required management insight. For example, a project may want load statistics to be captured by country or business unit. Refer to Add Migration Execution Groups for more information.
  • The Wave Execution Groups and Wave Execution Values pages have been added to manage execution data for an object.
  • The Load Cycle Execution Plan page was added to view Load Cycle Execution Plan load statistics and significant dates for an object’s Migration Execution Groups within an instance’s Load Cycle.

Transform

The Object Execution Template page was added to configure Migration Execution Plan Templates to record load statistics for Migration Execution Groups.

SQL AutoGen

In previous versions, if the user clicked the Create All Objects or Create All Rules icons on the Automation page’s Page toolbar, mappings with an Action of Manual Rule or Manual Construction were built and their rule status was set to Complete. Mappings for source rules with this Action must be manually built by developers. When a rule with this Action is saved in Map, the Generate Rule check box on the Field Mappings page’s Vertical View is unchecked by default, and the rules are no longer built by SQL AutoGen.

Online Help

Mass Maintenance

Mass Maintenance templates can no longer be created from a BDC Script or GUI Script recording. Custom templates can be created, as well as templates based on Integrate templates. Refer to Create Templates for more information.

Data Quality

These features have been added to improve Opportunity Views. Users can:

  • View an Opportunity View’s SQL definition
  • View an Opportunity View’s assigned Error reports, providing insight into Data Quality percent calculations
  • Add a Description to an Opportunity View

Refer to View an Opportunity View’s Definition and Error Reports for more information.

Stewardship Tier (formerly Data Stewardship Platform (DSP®))

Collect

  • Removed the Target User Access page as it has been deprecated.
  • To simplify page design and make changing the schema of target source tables easier, the following changes have been made:
    • Navigation from the Target Source Group page to the Tables page is now direct, and no longer via the Target Source Tables page.
    • The Target Source Tables page has been removed.
    • The Vertical View has been removed from the Table Errors page, and the Package Built check box, and Indices and Rules icons have been removed from the Horizontal View.

    Integrate

    • Recording a BDC script to use as the basis for an Integrate template has been removed from the Stewardship Tier. This functionality depended on Internet Explorer 11, which is no longer supported. To create a BDC script to use as the basis for BDC Script template in Stewardship Tier 7.3, users can:
      • Create a BDC script using the SHDB transaction in SAP and import the script into Integrate. Refer to Import a BDC Script from a File for more information.
      • Copy an existing BDC script. Refer to Copy a Template for more information.
      • Use a BDC script created in a previous version.
    • Recording a GUI script to use as the basis for an Integrate template has also been removed from the Stewardship Tier, as this functionality also depended on Internet Explorer 11 support. New templates based on GUI recordings cannot be created in version 7.3 and later, but GUI templates created in previous versions of the Stewardship Tier can be used, as well as copies of GUI templates. Refer to Copy a Template for more information.

7.3 Resolved Issues

Advanced Data Migration

Transform

Fixed an issue that caused a timeout when a view was registered as a target source and it took longer than 30 seconds to execute. With the fix, the timeout does not occur and the execution completes as expected. [DSP70-1039]

Stewardship Tier (formerly Data Stewardship Platform (DSP®)))

Stewardship Tier Upgrade Impact:

  • When upgrading from DSP 7.0.6 or below to Stewardship Tier 7.3 or above, Collect target sources that include SAP connection details will automatically have the saved connection string details converted into a new Data Source of type SAP Application Server. The newly created SAP Application Server Data Source will then be assigned to the Collect target source. After upgrading, it’s important to review and test all Collect target sources to ensure they function correctly. [DSP70-740]

7.3 Enhancement Request From Users

What's New in Syniti Solutions 7.2.1

Release Date: 6/10/2020

This topic contains:

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 7.2.1. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the DSP in version 7.2.1 and later. Consult this manual BEFORE updating to 7.2.1, as an analysis of current security assignments must be completed before the DSP can be updated.

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

7.2.1 Enhancements

Advanced Data Migration

Console

Object owners can manually track status for an object’s Relevancy, PreLoad, PostLoad and Program Type. These statuses will be used as input to Migration dashboards in the Knowledge Tier in a future release. Refer to Track Report and Load Program Status for more information.

Master Data Management

The Vertical View of the Scenario (Roles) page has two check boxes that, when both checked, are not compatible:

  • Auto Finish Role
  • User Response Required On Warnings

If a role is auto finished, then there is not a user available to provide the response to any warnings. Therefore, a validation message was added to the Scenario (Roles) page to notify users that when both check boxes are checked, they are not compatible with each other.

Data Quality

A Documentation tab with an External Reference field was added to the Vertical View of the following pages:

The External Reference field displays hyperlinks and supporting commentary that demonstrate the connection from data-related assets in the DSP to external references in other platforms and applications. Syniti recommends a report be linked to a term, rule or data set in the Knowledge Tier.

Data Stewardship Platform (DSP®)

The following improvements were made to security auditing:

  • Security events, which can be viewed on the System Logs page, were updated:
    • The target entity name now displays when adding or removing Security Definition key values to roles and users.
    • The role name now displays for role deletion events.
  • Updates made to security (as in, insertions, deletions, and updates to the RoleWebAppGroup table) as a result of updates in DSP Add-Ons are now logged in the security logs and can be viewed on the System Logs page.

7.2.1 Resolved Issues

Advanced Data Migration

Construct

Corrected an issue that occurred when adding a Full Construction source to a target. The resulting data construction pages and tables included zLegacy<KEY> columns that were added as keys on the construction page and could not be edited. Users were prevented from creating records on these pages. With the fix, the zLegacy<Key> fields are not included in the pages and tables when adding a Full Construction source to a target. As is standard, full construction expects records to be populated with data in values that relate to the target system. If data is being constructed for a record that has not had a target number generated yet, i.e., not loaded, a legacy record number can be used. During the migration process, this value can subsequently be translated to a target value using cross reference tables. [DSP70-949]

Master Data Management

Two issues occurred on the Request Role page where the Finish button was behaving incorrectly. The first issue occurred when a user clicked the Finish button to finish the role. The button became disabled, then enabled again, even though rules registered to the Finish event were still executing. The user could then click the Finish button a second time, executing the rules again, resulting in errors in the data and posting errors. The second issue related to validations running twice, causing performance issues in scenarios that had long running validations. With this fix, once the Finish button has been clicked once, it is either disabled or overlaid with a spinning icon. Users cannot click the Finish button a second time, and current foreground processing and validations only run once. [DSP70-979]

Data Quality

  • When a report was added to a group on the Your Groups page, in order for the user filter to be applied to the report, the report had to be executed and then either the user filter had to be validated or a new user filter had to be created. This issue has been fixed and user filters for a new report added to a group now function as expected: as long as the user filter has been set up, the filter is applied during the first execution of the report. [DSP70-1001]
  • Previously, if there were duplicate records on the Data Quality Score Thresholds page, then duplicate records appeared on the Target Table Threshold and the Target Table Column Threshold pages. This duplication was caused by incorrect join conditions on the webDQSThrewsholdList view. To fix this issue, the view now has joins on the “Name” field. [DSP70-923]

  • The Process and Process For All Users icons on the Your Groups page were always inactive because the Monitor Group Security Definition Events (webSecurity_GroupUserAdd), which inserts records into the ddGroupUser table, did not have the boaStatus field populated. To fix this issue, the webSecurity_GroupUserAdd stored procedure was updated to default an initial value of 0 (New or Dirty) for boaStatus. [DSP70-925]

  • A report can appear multiple times on the Your Object Reports page because it could be assigned to multiple groups, have different filters applied, and be executed independently. To communicate the duplication to users, a Report Warning icon has been added to the Your Object Reports page with the following options:

    • No warnings
    • Report appears multiple times because it has different User filters in different Groups

    [DSP70-930]

  • The Columns button on the Report Target Tables page displayed an incorrect count. The count was the number of target table columns for all reports. The count now displays the correct value: the number of target table columns assigned to the target table for that specific report, i.e., the number of records on the Report Target Table Columns page. [DSP70-1009]

Data Stewardship Platform (DSP®)

DSP Upgrade Impact:

  • When upgrading from DSP 7.0.6 or below to 7.2.1 or above, Collect target sources that include SAP connection details will automatically have the saved connection string details converted into a new Data Source of type SAP Application Server. The newly created SAP Application Server Data Source will then be assigned to the Collect target source. After upgrading, it’s important to review and test all Collect target sources to ensure they function correctly. [DSP70-740]

7.2.1 Enhancement Requests From Users

What's New in Syniti Solutions 7.2

Release Date: 5/19/2020

This topic contains:

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 7.2. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the DSP in version 7.2 and later. Consult this manual BEFORE updating to 7.2, as an analysis of current security assignments must be completed before the DSP can be updated.

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

7.2 New Feature

Data Migration Dashboards

Project Managers can gain insight into migration project statuses using the Data Migration Cloud Dashboards accessible in the Knowledge Tier. Configuring and using the dashboards:

  • Allows Design / Mapping and Build Status to be tracked against plan by Wave / Process Area, Object or Target Table
  • Allows for project milestones related to design, mapping and build activities to be set and tracked against using near real-time status information.
  • Provides improved metric reporting and dashboarding, giving project stakeholders better visibility of project status using fact based information.

The dashboards provide the following:

  • An Executive Summary of the migration project, including:
    • Development Status to Plan
    • Target Design Percent Complete
    • Field Mapping Percent Complete
    • Field Mapping & Rule Backlog
    • Field Mapping % Populated
    • Rule Build % Complete
    • Complete Mapping Rule Build % Complete
  • Milestone Reporting including:
    • Project Milestones
    • Target Design % Complete
    • Field Mapping % Complete
    • Rule Build % Complete
    • Number of Objects
  • Object Status
    • Data Object Development Status to Plan
    • Target Design % Complete
    • Field Mapping % Complete
    • Field Mapping Backlog
    • Field Mapping % Populated
    • Rule Build % Complete
    • Complete Mapping Rule Build % Complete

Additionally, there are a series of reports that allow project managers and consultants to drill into status information at Object / Target and Target Source level.

This Data Migration dashboarding capability is supported by the following new DSP features:

  • Planning Groups
  • Milestones
  • Load Cycles
  • Object Planning Data

Refer to Configure Data Migration Cloud Dashboards for more information.

7.2 Enhancements

Advanced Data Migration

Target Design

The Visibility field on the Target Fields page defaulted to “Both - Mapping for Source and Target” for Natural fields, which meant that every active target field required two mappings: one for the source rule and one for the target rule. This default value caused a duplication maintenance effort because a field typically has either a source or a target rule; not both. To alleviate this duplication, the default value has been changed from “Both - Mapping for Source and Target” to “Source - Source only mapping.”

Data Quality

The WHERE CLAUSE MANUAL field on the User (Reports) page was limited to 2000 characters, which often was not enough characters and led to the generated WHERE clause to be truncated. To accommodate larger WHERE clauses, two changes were made:

  • The WHERE CLAUSE MANUAL field was extended from NVARCHAR(2000) to NVARCHAR(MAX).
  • The associated stored procedures that construct the WHERE clause were updated to ensure the resultant where clause supported NVARCHAR(MAX).

Online Help

Added a topic to the online help explaining how to Populate the Bulk Update Tables to Publish Rules and Terms to the Knowledge Tier.

7.2 Resolved Issues

Data Stewardship Platform (DSP®)

DSP Upgrade Impact:

  • When upgrading from DSP 7.0.6 or below to 7.2 or above, Collect target sources that include SAP connection details will automatically have the saved connection string details converted into a new Data Source of type SAP Application Server. The newly created SAP Application Server Data Source will then be assigned to the Collect target source. After upgrading, it’s important to review and test all Collect target sources to ensure they function correctly. [DSP70-740]

What's New in Syniti Solutions 7.1.4

Release Date: 5/4/2020

This topic contains:

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 7.1.4. Refer to the Syniti Solutions Centralized Security Migration Manual for important information about using security in the DSP in version 7.1.4 and later. Consult this manual BEFORE updating to 7.1.4, as an analysis of current security assignments must be completed before the DSP can be updated.

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

Align Column Encryption State for key Target Source column in Collect Before Upgrade

A new feature was introduced in DSP 7.1.4 whereby the SAP connection settings on a Collect Target Source are moved to a dedicated Data Source Registry record. During upgrade, the following DataGarage dgTargetSource table columns are used to create the new DSPCommon Data Source Registry records.

Database

Table

Column

Database

Table

Column

DataGarage

dgTargetSource

SAPPassword

DSPCommon

ttDataSourceRegistry

SAPPassword

DataGarage

dgTargetSource

SAPUserID

DSPCommon

ttDataSourceRegistry

SAPUserID

DataGarage

dgTargetSource

Instance

DSPCommon

ttDataSourceRegistry

SAPSystemID

DataGarage

dgTargetSource

RfcNameSpaceOption

DSPCommon

ttDataSourceRegistry

RfcNameSpaceOption

DataGarage

dgTargetSource

SAPSystemNumber

DSPCommon

ttDataSourceRegistry

SAPSystemNumber

DataGarage

dgTargetSource

Client

DSPCommon

ttDataSourceRegistry

SAPClient

DataGarage

dgTargetSource

SAPServerHost

DSPCommon

ttDataSourceRegistry

SAPApplicationServer

DataGarage

dgTargetSource

Language

DSPCommon

ttDataSourceRegistry

SAPLanguage

DataGarage

dgTargetSource

SAPMsgServerHost

DSPCommon

ttDataSourceRegistry

SAPMessageServer

DataGarage

dgTargetSource

SAPLogonGroup

DSPCommon

ttDataSourceRegistry

SAPLogonGroup

As a result of these changes, BEFORE UPGRADING to version 7.1.4, you must review and confirm that the encryption state of these two sets of columns matches. If you do not confirm that the encryption state is identical in these two sets of columns, mixed data could be saved in the column when the DSP is upgraded. Access the Data Source Column Encryption page in System Administration. The Status field indicates issues with encryption that must be corrected before upgrade.

7.1.4 New Feature

Enhanced Migration Reporting

Data Quality is the analytical component of the DSP® that facilitates enhanced migration reporting on the target data staged in preparation for loading into the target system. It allows business users to:

  • Establish data quality thresholds and view data quality scores and status
  • Organize and display quality metric reports via web access or other formats for process improvement
  • Identify and send errors (via workflow notifications) to business users for remediation prior to loading to the target system

Data Quality is delivered with a standard set of reports. Users can also create custom reports to fit their business needs. Refer to Use Enhanced Migration Reporting for more information.

7.1.4 Enhancements

Advanced Data Migration

Console

When adding a wave to the Wave: Process Areas page, if a Target System (which is on the Vertical View) was not selected prior to saving the record, a warning message displayed. If the user canceled the record at this time, the record still saved and allowed the wave to be further configured. This error caused issues later in the migration process because target reports are not generated until a Target System value is set. To alleviate this issue, the insert method for the Wave: Process Areas page was changed from Horizontal Insert / Switch to Vertical to Horizontal / Switch to Vertical, which requires the Vertical View to be saved in order for the data entered on the Horizontal View to be saved, i.e., requires a user to select a Target System before the wave record can be saved.

Syniti Data Replication

  • The DSP is now compatible with Syniti Data Replication 9.6.3. When upgrading to DSP 7.1.4, an additional step is required to upgrade Syniti Data Replication to 9.6.3.

Collect

  • The Connection Type field on the Target Sources page now supports a Connection Type of IG Universal Connect as expected. Previously, when IG Universal Connect was selected as the Connection Type, the following error message displayed: “Target Source has Data Services connection type and the Source connection type is not compatible. Correct the Source "Connection Type" or the Source "Data Services Connection Type.” The webTargetSource_ConnectionTypeDataServicesIDVal view was modified to reflect support for the Connection Type of IG Universal Connect.

Online Help

7.1.4 Resolved Issues

  • An issue occurred when performing an import of an .xlsx Excel file: a column with both an Excel format of Number and a defined number of decimal places was sporadically imported with additional decimal places (this was not an issue for .xls Excel files). For instance, an entry of 16.44 on the spreadsheet was imported as 16.44000001 in SQL Server. This issue was resolved by updating the third party library (ExcelDataReader) used by Assemble.[DSP70-905]

Advanced Data Migration

Map

  • An issue occurred when attempting to auto-generate a full construction page using the Sync to Map functionality on the Targets page. Validation rules failed to run when the values for the target lookup table did not match the associated values for the target table. The full construction page is now auto-generated without error. [DSP70-877]
  • Auto-generated list boxes failed to store selected values correctly when the lookup table contained more than one target field. Validation rules run as expected and full construction pages are auto-generated as expected. [DSP70-877]

Master Data Management

An issue has been fixed where an “Object reference not set to an instance of an object” error message displayed when the Auto Finish Role check box on theScenario (Role)page was enabled for a role and if the role returned validation messages. A role with Auto Finish Role enabled now works as expected: if enabled and if there are validations returned, the boaStatus icon on the Request Role page is set to validation failed. A user can click the Validate button on the Request Role page to see the validation messages. [DSP70-950]

Data Stewardship Platform (DSP®)

DSP Upgrade Impact:

  • When upgrading from DSP 7.0.6 or below to 7.1.4 or above, Collect target sources that include SAP connection details will automatically have the saved connection string details converted into a new Data Source of type SAP Application Server. The newly created SAP Application Server Data Source will then be assigned to the Collect target source. After upgrading, it’s important to review and test all Collect target sources to ensure they function correctly. [DSP70-740]

Collect

  • An issue occurred with building Data Services packages. When adding a Where Clause to a table in Collect and then building a Data Services RFC package, the Where Clause was not added to the job initially; a second build was required. A similar issue occurred when building an SAP RFC package. The issue has been fixed and these packages now build as expected. [DSP70-837]
  • An issue occurred when adding a target source with connection type SAPAPPSERVER on the Target Sources page and attempting to build an RFC package for a table using this target source. The package build failed. The issue has been corrected and the build now completes as expected. [DSP70-962]

  • Collect was writing Data Services packages to the incorrect repository. Several changes were made to fix this issue:
    • The Target Sources - DataServices Connection page is now read only. The data services connection information is now retrieved from the Data Source Registry page in Common.

    • A validation rule was added to the Tables and Target Sources pages to ensure that the SAP DataSource is populated on the Target Sources page if one or more RFC packages are registered (on the Tables page).

    • A new Data Services connection type, Oracle12c, was added.

    • An error with the Test Connection button on the Targets page was fixed. Previously, when the Data Source was registered on the Targets page and then renamed or removed from the Data Sources page in System Administration, an error displayed when the user clicked the Test Connection button on the Targets page.

    • Logging for namespace override options was added to Common. If the SAP Namespace check box on the Data Source Registry page is not checked, DSP checks for a value in the Rfc Name Space Option field on the Parameters-Collect page. If a value is not set, the DSP overrides the logging configuration settings with “namespace." [DSP70-807]

System Administration

  • An issue occurred when the Set Password And Notify User button on the Users page was clicked for a UserID that contained spaces. As a result, the following error message displayed when the user tried to log in with the UserID and temporary password: "The website could not finish processing the current request due to an unexpected system error." The issue has been fixed; the error message no longer displays in this scenario if the UserID contains spaces. [DSP70-926]

Information Governance Universal Connect

An issue occurred when attempting to create an Information Governance Universal Connect template. When a user clicked the Boomi Process ID list box on the General tab on the Vertical View of the Template page, the expected list did not display. The issue has been corrected, so the list of Boomi processes generates as expected. [DSP70-787]

What's New in Syniti Solutions 7.1.3

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 7.1. Refer to the Centralized Security Migration Manual for important information about using security in the DSP in version 7.1 and later. Consult this manual BEFORE updating to 7.1, as an analysis of current security assignments must be completed before the DSP can be updated.

NOTE:The following SAP products are compatible with the DSP 7.1.3 release:

  • SAP Information Platform Services 4.2 SP6
  • SAP Data Services 4.2 SP12
  • SAP Information Steward 4.2 SP12

However, these are not compatible with MS SQL Server 2019. For full DSP integration with these products running on MS SQL Server 2019, clients must wait until SAP releases MS SQL Server 2019 compatible versions. This is currently anticipated at the end of Q2 2020.

NOTE: The address for Syniti support has been updated to https://support.syniti.com.

Align Column Encryption State for key Target Source column in Collect Before Upgrade

A new feature was introduced in DSP 7.1.3 whereby the SAP connection settings on a Collect Target Source are moved to a dedicated Data Source Registry record. During upgrade, the following DataGarage dgTargetSource table columns are used to create the new DSPCommon Data Source Registry records.

Database

Table

Column

Database

Table

Column

DataGarage

dgTargetSource

SAPPassword

DSPCommon

ttDataSourceRegistry

SAPPassword

DataGarage

dgTargetSource

SAPUserID

DSPCommon

ttDataSourceRegistry

SAPUserID

DataGarage

dgTargetSource

Instance

DSPCommon

ttDataSourceRegistry

SAPSystemID

DataGarage

dgTargetSource

RfcNameSpaceOption

DSPCommon

ttDataSourceRegistry

RfcNameSpaceOption

DataGarage

dgTargetSource

SAPSystemNumber

DSPCommon

ttDataSourceRegistry

SAPSystemNumber

DataGarage

dgTargetSource

Client

DSPCommon

ttDataSourceRegistry

SAPClient

DataGarage

dgTargetSource

SAPServerHost

DSPCommon

ttDataSourceRegistry

SAPApplicationServer

DataGarage

dgTargetSource

Language

DSPCommon

ttDataSourceRegistry

SAPLanguage

DataGarage

dgTargetSource

SAPMsgServerHost

DSPCommon

ttDataSourceRegistry

SAPMessageServer

DataGarage

dgTargetSource

SAPLogonGroup

DSPCommon

ttDataSourceRegistry

SAPLogonGroup

As a result of these changes, BEFORE UPGRADING to version 7.1.3 and later, you must review and confirm that the encryption state of these two sets of columns matches. If you do not confirm that the encryption state is identical in these two sets of columns, mixed data could be saved in the column when the DSP is upgraded. Access the Data Source Column Encryption page in System Administration. The Status field indicates issues with encryption that must be corrected before upgrade.

This topic contains:

7.1.3 Enhancements

Data Stewardship Platform (DSP®)

  • Starting with DSP release 7.1.3, the Exclude Client Fields check box on the Vertical View for a system type on the System Type Import page in Common is checked by default. If this check box is not checked and the system type is built with the client included, all target tables and check tables include this field. This means that every lookup table will become a multi-value key value mapping, which diminishes the visibility of true multi-value key lookup tables. Users can uncheck the box to include Client fields if needed.

Collect

  • The AddedOn field on the Job Detailpage's Vertical View now displays date and time, so users can review failed records from the Test Connection Service page in time sequence order.
  • The performance of Collect extracts using the SAP RFC and BOA RFC package types has been significantly improved. This performance improvement was achieved through faster data parsing and the use of bulk insert functionality.

Advanced Data Migration

Map

To improve the user experience, the Submit and Submit All events on the Field Mappings page now run in the background instead of in the foreground.

Online Help

  • Added this note to the Validation Rules topic to clarify the use of Warning validations:

    NOTE: When creating an event that will be called indirectly, do not use Warning validations. Use Error validations. Warnings are intended for user interaction. Validations running on events used as business rules of the type WebApp Event or WebApp Event (Private), or as Event Tasks added to a job, are non-interactive. In these cases, validations are only used to stop the business rules of the event from running (or, in the case of a 'Run On Validate Fail' set of rules, to allow the business rules to run). Refer to Set Parameters for a Public WebApp Event, Create a WebApp Event (Private) Business Rule, and the Job Queue Task page for more information.

  • Added topic Track - Changes Per Week.

System Administration

7.1.3 Resolved Issues

Data Quality

  • An issue occurred so that the filter criteria set for one report repository altered the Report View selections for another report repository. If the user set Report View filter criteria, for example, of tv*RptSel, for Repository A and then created Report Repository B with a Report View with filter criteria tv*Sel, the view set for Repository B would be applied to Repository A. When a user created a report in Repository A, the view set for Repository B would incorrectly display along with the view set for Repository A. With the fix, only views set for a particular repository display when creating a report for that repository, as expected. [DSP70-874]

  • An issue occurred that caused some user names not to display correctly in two fields when the user was not assigned to the WebApp group. The User ID field on the Group Users page and the Group Owner field on the Report in Groups page were affected. Instead of displaying the User ID concatenated with the User Name, those fields displayed only the User ID, which in many systems is meaningless information. With this fix, the User ID concatenated with the User Name displays in these two fields as expected. [DSP70-815]

Data Stewardship Platform (DSP®)

If the password for a data source resulted in an encrypted value longer than 128 characters, the Common Service page "Service - DataServices Status" failed with a message of "Failed to enable constraints. One or more rows contain values violating non-null unique or foreign-key constraints." With the fix, the field length has been updated, and the Service page runs as expected. [DSP70-867]

Collect

  • An issue occurred with the Advanced View Builder tool in Collect where, when a user built views for a given database, the views were created with the where clause on every column whose value related to the SAP Client and/or Language field. This rendered the view unusable. The workaround was to use the View Builder tool in Common. The issue has been corrected, so using the Advanced View Builder tool in Collect builds a view as expected. [DSP70-902]
  • In version 7.1.2, there was a Known Issue with encryption if running SQL Server 2019 with DSP. In some cases, values that were set to encrypted in Collect were not encrypted correctly in the table column. This issue has been corrected, and values are encrypted and decrypted as expected. [DSP70-898]

  • An issue occurred where, when a user tested a connection and the test failed for either a target or a target source, the service page execution ended without testing the remaining connections. The issue has been corrected, so that when a connection fails, service page execution continues and completes testing on all connections. Each record in the dgTarget or dgTargetSource tables updates with the appropriate connection status, depending on the outcome of each connection test. [DSP70-561]

  • The Build View process on the Advanced View Builder page in Collect completes without an error message and drops every SQL Server view in the database for views. DSP is then unable to recreate the views since they no longer exist in the DATABASE FOR TABLES list box. To prevent all views from being deleted, a safety check was added to prevent the DATABASE FOR VIEWS and the DATABASE FOR TABLES fields from being in the same database: a view selected from the DATABASE FOR VIEWS list box is removed as an option from the DATABASE FOR TABLES list box. The same is true for a database selected from the DATABASE FOR TABLES list box. [DSP70-878]
  • With the absence of a NUMERIC data type rule, Collect defaulted to the ANY data type, which uses nvarchar with the same length as the source field. If the source data contained a value that was at the character maximum for numeric and was negative, the value caused an error. To fix this issue, a NUMERIC data type rule was added to the SQLSERVERSource Connection Type page and is formatted the same way as the DECIMAL data type rule. [DSP70-464]

  • In previous versions of DSP, Collect copied and used connection information from the assigned target source into the dgTarget and dgTargetSource tables. If the target source was required to connect to an SAP application (rather than database), the SAP Connection details were also populated on the target source record and stored in the dgTargetSource table. To ensure that connection information is stored in a central location, this release introduced the following changes:
    • Collect no longer copies target and target source connection information into dgTarget and dgTargetSource tables. Instead, Collect uses the connection information stored within the Common Data Source Registry page.
    • The ConnectionString column has been removed from the dgTarget and dgTargetSource tables.
    • Instead of entering the SAP Connection details on the target source record, users must select the Common Data Source Registry connection associated with the relevant SAP application / client.
      • With this change, the following columns within dgTargetSource have been removed or made read-only:
        • Client
        • Instance
        • Language
        • RfcNameSpaceOption
        • SAPLogonGroup
        • SAPMsgServerHost
        • SAPPassword
        • SAPServerHost
        • SAPSystemNumber
        • SAPUserID [DSP70-740

        DSP Upgrade Impact:

        When upgrading from DSP 7.1.2 or below to 7.1.3 or above, Collect target sources that include SAP connection details will automatically have the saved connection string details converted into a new Data Source of type SAP Application Server. The newly created SAP Application Server Data Source will then be assigned to the Collect target source.

        After upgrading, it’s important to review and test all Collect target sources to ensure they function correctly. [DSP70-740]

Integrate

  • An issue has been fixed for 64-bit DSP instances that prevented non-dialog SAP users from creating Integrate BAPI/RFC Templates and posting an Integrate process. With this fix, using SAP non-dialog users/service accounts in Integrate is supported, so long as the user has correct SAP authorizations. [DSP70-915]
  • An issue occurred in 32-bit DSP environment when the same non-dialog SAP user account was used in multiple different data sources, each with different SAP logon languages. This issue occurred when a user posted using one connection ID in language A and then, when that process had completed, attempted to post a second process using a second connection ID in language B. The second post failed, generating an error message: Please logon with a dialog user. This issue has been corrected so that the second background process now completes as expected. [DSP70-872]

Common

  • The View Builder tool in Common has been used as a workaround when the Advanced View Builder tool in Collect does not function properly. The Advanced View Builder tool in Collect now functions properly. [DSP70-902]

7.1.3 Enhancement Requests From Users

As the result of feedback from the online help, the User Template Filter topic was updated to include more detailed information about the VALUE field.

What's New in Syniti Solutions 7.1.2

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 7.1. Refer to the Centralized Security Migration Manual for important information about using security in the DSP in version 7.1 and later. Consult this manual BEFORE updating to 7.1, as an analysis of current security assignments must be completed before the DSP can be updated.

NOTE:The following SAP products are compatible with the DSP 7.1.2 release:

  • SAP Information Platform Services 4.2 SP6
  • SAP Data Services 4.2 SP12
  • SAP Information Steward 4.2 SP12

However, these are not compatible with MS SQL Server 2019. For full DSP integration with these products running on MS SQL Server 2019, clients will need to wait until SAP releases MS SQL Server 2019 compatible versions. This is currently anticipated at the end of Q2 2020.

NOTE: The address for Syniti support has been updated to https://support.syniti.com.

This topic contains:

7.1.2 Enhancements

Data Stewardship Platform (DSP®)

  • The DSP, including SSIS, is now compatible to run on MS SQL Server 2019. Additionally, MS SQL Server 2014 is no longer a supported platform for the DSP.

    NOTE: If running the DSP on SQL Server 2019, be aware of the Known Issue.

  • If SSIS packages are used in Collect on a SQL Server 2019 environment, SQL Server Data Tools for Visual Studio 2017 (SSDT for VS 2017) must be installed.

  • The delivered Security Role Governance Developer has had the System Administration JobMonitoring WebApp group added to it. This provides users assigned to this Security role with comprehensive access to DSP Monitoring pages.
  •  Electronic Signature authentication enhancements include:
    • The logic for deciding when to render the Electronic Signature panel has been updated so that the panel always appears if custom authentication is enabled, regardless of whether the user has a basic authentication password.
    • When determining whether to accept the credentials entered on the Electronic Signature panel, the logic first checks if the password matches the basic credentials password. Otherwise, it checks for custom authentication, if enabled.

Collect

  • Custom Source Connection Types added in Collect are no longer deleted on upgrade.

    To support this functionality, the DSP Supplied check box has been added to the following pages in Collect to indicate those items that are delivered with the DSP and cannot be deleted:

  • Previously, the Collect Target Source Data Services test connection process sometimes failed when the Target Source type was SAPAPPSERVER. The following features were added to prevent failure of the connection test for this Target Source type:

    • The Connection Settings button on the Vertical View of the Target Sources page is disabled when the Data Services connection type is SAP Application.

    • A validation error displays on the Target Sources page if the source connection type and Data Services connection type do not align (for example, if the source connection type is SAPAPPSERVER, then the Data Services connection type must be SAP Application).

    • A validation error displays on the Target Sources page if the source connection type does not align with the Data Services package types registered for that Target Source (for example, if the source connection type is ORACLE, the Data Services package type cannot be DataServicesRFC).

  • The Collect Parameter option Maximum Connections on the SDR Settings tab (Common > Configuration > Modules > Parameters-Collect > SDR Settings) has been deprecated:

Mass Maintenance

The Mass Maintenance Navigation pane displays as expected after a user expands the Navigation pane and later performs a page refresh.

Syniti Data Replication (formerly DBMoto)

  • The DSP is now compatible with and installed with Syniti Data Replication 9.6.2.0.
  • To more tightly integrate Syniti Data Replication functionality into the DSP, the following updates have been made:
    • DSP functionality has been updated so that the Syniti Data Replicator Service no longer stops and then restarts when building and refreshing packages. The application now builds and refreshes packages without starting and stopping.
    • Where Clause functionality has been updated for the DBMoto Download package type so that running Syniti Data Replication filters records as expected. Previously, the Where Clause Override field in the DSP was not passed into the Syniti Data Replication replication Where Clause. Now, both the Where Clause Override and the Client fields are added to the Replication.

      NOTE: The DBMoto Mirror package type only filters based on SAP Client. Other filters must be manually added within the Syniti Data Replication Management Center as a Visual Basic script.

    • When a user clicks the Build package button on the Tables page in Collect, Syniti Data Replication creates the replication but does not run it.
    • Refreshing a DBMoto Download package type runs the package without also rebuilding it.

System Administration

To show unencrypted columns that needed to be reviewed, the DSP sent a daily email and a pop-up message displayed within the DSP. The pop-up message was superfluous and therefore has been removed.

7.1.2 Resolved Issues

Data Quality

An issue occurred that caused the wrong reports to display on a user's Your Object Reports page. If the user had a filter applied, the UserReportFilePath for the Your Object Reports page included the wrong user name in the file path. With the fix, the reports that display on the Your Object Reports page are now associated with the correct user name and the UserReportFilePath includes the correct user name. [DSP70-556]

Data Stewardship Platform (DSP®)

  • The following issues with Electronic Signature authentication have been corrected:
    • Upon proper configuration, Electronic Signature now works with Integrated Authentication. Refer to Use Electronic Signature with Integrated Authentication for more information.

    • Custom authentication no longer allows locked users to log in to the DSP (for example, previously, they could make unlimited guesses at the custom login credentials).

    • The login attempt count is now correct when basic and custom authentication are both enabled.

    • Users are no longer forced to reset their passwords when they do not already have a password to reset.

    • The Integrated Authentication Variable Name option was removed from the Parameters page, resolving potential security issues. [DSP70-771]

  • A DSP-delivered CTS configuration for the DSPCommon WebApp has been updated. In a previous release, the System Type table ztSystemTypeTableFieldCheckTable was deprecated. In this release, this table has been removed from the CTS configuration. [DSP70-861]
  • A DSP-delivered CTS configuration for the Transform WebApp has been updated. The Relationship of ttWaveProcessAreaObject to ttWaveProcessAreaObjectTarget now has the EnableCTS setting checked. [DSP70-861]
  • An issue occurred when importing a System Type using a System Type Model where if there were duplicate data type mappings for the conversion from the data type used in the model to SQL Server then the import created duplicated records in the ztSystemTypeTableField table. With this fix, duplicate records are no longer created in the System Type. [DSP70-830]
  • An issue occurred in several System Type tables, including ztSystemTypeJoin and ztSystemTypeJoinField, where the tables did not have primary keys or foreign key relationships. This caused performance impacts and prevented records from being deleted when a System Type was deleted. With this fix, all ztSystemType* tables have the required primary keys and foreign key relationships, and System Type deletion cascades successfully. [DSP70-851]

Collect

  • An issue occurred with the DBMoto Download package type where, when users clicked Refresh on Collect Source, the job timed out. The code for this package type has been rewritten to prevent parallel sessions, which was the issue that caused the timeouts. With this fix, DBMoto Download jobs build as expected. [DSP70-790]

  • An issue occurred when a Schedule Services service page executed during a CranPort package refresh. If the target contained both Syniti Data Replication and CranPort tables, the service page job failed because the service page process was not able to access the CranPort tables specified in the underlying view.

  • The service page table view has been altered so that the deadlock no longer occurs. Running a Schedule Services job simultaneously with a CranPort package refresh no longer causes the Schedule Services job to fail. The concurrently running jobs now execute as expected. [DSP70-791]

7.1.2 Known Issue

If running SQL Server 2019 with DSP, there is a known issue with encryption. In some cases, values that are set to encrypted in Collect are not encrypted correctly in the table column. To resolve this issue, upgrade to 7.1.3 or request the 7.1.3 version of stored procedure DataGarage..webService_EncryptColumns.sql from support by opening a ticket at Syniti Support.

7.1.2 Enhancement Request From Users

As the result of feedback from the online help, the SQL Server Health Charts topic was updated to include more detailed information about the Memory Overview Chart.

What's New in Syniti Solutions 7.1.1

NOTE: If you are upgrading from 7.0.6 or below to 7.1 or above, 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 7.1. Refer to the Centralized Security Migration Manual for important information about using security in the DSP in version 7.1 and later. Consult this manual BEFORE updating to 7.1, as an analysis of current security assignments must be completed before the DSP can be updated.

This topic contains:

7.1.1 Enhancements

As part of the Syniti rebranding effort, the temporary license email, which is sent to users who request a temporary license to log in to the DSP, has been updated from no-reply@boaweb.com to no-reply@syniti.com.

Data Stewardship Platform (DSP®)

System Administration

  • To help streamline user management security, User Management was added to delivered security roles. The User Management role includes access to the UserManagement and ContentKeySecurity WebApp Groups. Users assigned to this role can create security roles with a Role Type of Content. They can also assign security definition key values to users and to security roles with Role Types of Standard and Content. The role restricts access to security, only allowing access to the pages used to create users and assign them to Application roles. Refer to Delivered Security Roles for more information.

  • To improve security, the following columns were hidden for the FieldAndValueMapper WebApp Group:

    • Refresh
    • ExportFieldMappings
    • ImportFieldMappings
    • SyncFromTargetDesign
    • UserColumnNotDefined
    • RemoveValues
    • Process
    • Build Reports
    • BuildReportsWithRemediation
    • Create
    • CreateAllRules
    • TargetTableImport

    Additionally, hard-coded UCVs were replaced with a generic webUserSecurityUcv that points to the cMap ztPageGroupColumnStatus table. If entries for AutoGen pages' columns are included in the cMap ztPageGroupColumnStatus table, the generic webUserSecurityUcv will provide correct results. All cMap page-specific UCV registrations were replaced with webUserSecurityUcv, which checks against all aspects of user security.

Syniti Data Replication (formerly DBMoto)

  • The DSP is now compatible with Syniti Data Replication version 9.6.1.
  • New DSP installations now default to the 64-bit version of Syniti Data Replication; the 32-bit version of Syniti Data Replication has been removed from the DSP installer.

7.1.1 Resolved Issues

With Google Chrome version 78, check boxes on Horizontal pages did not work properly; the check box was made invisible and an image rendered on top. Therefore, users were unable to update the check box. This issue has been fixed where check boxes work as expected in Google Chrome version 78. [DSP70-834]

Mass Maintenance (formerly dspCompose)

The User Template Role Access page in Mass Maintenance has been updated to remove functionality to grant and deny users access to templates at a global level as this method of assigning security is not compatible with the centralized security management introduced in 7.1. [DSP70-799]

Master Data Management (formerly dspConduct)

  • Fixed an error that caused a process to fail when the user clicked the Create Control Table button on the Scenario Role Task page under certain conditions. If another ScenarioRoleTask with the “Active In Scenario Role” flag unchecked is associated to the same Task as the ScenarioRoleTaskPage being processed, Invalid column name 'FieldName' errors displayed and the process failed. The failure occurred because the Control Table was created with only the key fields, missing all the non-key fields. With the fix, the Create Control Table button creates and populates the control table including both key fields and non-key fields and the process ends successfully. [DSP70-813]
  • In previous versions, when copying a position, that position’s users could be copied to the new position. Since 7.1, users are assigned to positions using centralized security, and can no longer be assigned to positions as part of the position copy process. [DSP70-823]

Data Stewardship Platform (DSP®)

  • An issue occurred where the DSP displayed a red “service stopped” icon even when all services were running. This issue occurred when the database and app servers were not located in the same time zone. With the fix, this difference in time zones no longer triggers the “service stopped” icon to display. [DSP70-831]
  • Collect

    • An issue occurred in the Vertical view of the Target Sources page when users populated the SAP Settings with data that included the string 'PWD'. When a user clicked the Test SAP Connection button, this error displayed:
    • Test SAP Logon Failed: Argument Length must be greater than zero.

      With this fix, including the string 'PWD' in the SAP connection information no longer triggers the Test SAP Logon Failed: Argument Length must be greater than zero error message. [DSP70-844]

    • An issue occurred with the Test Connection process on the Collect Targets page where, when more than one Cransoft Service was running in the General Queue and the user clicked Test Connection for a target, an error message displayed:
    • Internal Error - Object reference not set to an instance of an object. An unhandled exception occurred during the execution of the plugin.

      Supporting views have been changed to prevent the issue. With this fix, the exception no longer occurs and the Test Connection process completes as expected. [DSP70-500]

  • System Administration

    • The Role Content Access Download report displays the friendly name of the key assigned to a role. However, the table joined in this report is SecurityDefinitionKeyValue, which has a two-column key for some components, such as Mass Maintenance. The view used to create this report was modified to de-duplicate the values for multi-column key assignments. [DSP70-814]
    • An issue occurred on the Security Role Compare page where the page and group comparisons were displaying incorrect results. With this fix:

      • The Role Page Comparison Dynamic SQL determines the Access Matches based upon the page’s inclusion in both roles, and based upon the Allow Select/Insert/Update and Delete indicators. If the page is not found in one of the roles, then the Access Matches field is set to NO.

      • The Role Group Comparison Dynamic SQL determines the Access Matches based upon the page’s inclusion in both groups. If the group is not found in one of the roles, then the Access Matches field is set to NO. [DSP70-816]

    What's New in Syniti Solutions 7.1

    NOTE: If you are upgrading from 7.0.6 or below to 7.1 or above, you may need to migrate your security settings to use centralized security. Users of dspMonitor, dspConduct,and dspCompose must update security roles when upgrading to 7.1. Refer to the Centralized Security Migration Manual for important information about using security in the DSP in version 7.1 and later. Consult this manual BEFORE updating to 7.1, as an analysis of current security assignments must be completed before the DSP can be updated.

    This topic contains:

    7.1 Enhancements

    Data Stewardship Platform (DSP®)

    System Administration

    Centralized Security

    In DSP releases of 7.0.6 and below, the management of a user’s access to different application functionality and content is done from within System Administration and the individual applications. For example, to grant a user access to dspCompose, administrative tasks were required in both dspCompose and System Administration. This fragmented approach resulted in these challenges:

    • New-user onboarding and change of user access was not efficient.
    • Users responsible for user onboarding needed training in all DSP applications that were being used.
    • Integration of DSP with third-party identity management tools was limited and, without extensive customization, would still require actions to be performed within DSP.

    With the centralized security model introduced with 7.1, a user’s access to both application functionality and content is managed in System Administration.

    Refer to Set Security for an overview of the updated process.

    Role Types Drive User Access

    To support this functionality, 7.1 also introduces a Role Type concept. There are three role types:

    • Standard roles allow access to both application functionality via WebApp Groups AND Content via Security Definition Key Value assignments.
    • Application roles only allow access to application functionality via WebApp Group assignment.
    • Content roles only allow access to Content via Security Definition Key Value assignment.

    As in previous versions, users are given access to applications through assignment to WebApp groups. In 7.1, users are assigned to WebApp groups directly, or are assigned to Standard or Application security role that has the WebApp group assigned.

    Separate User Provisioning Tasks

    Syniti recommends that Application and Content access is provisioned through separate security roles. With 7.1, it is now possible to create security roles that ONLY permit application functionality access to be granted. This offers the most efficient method by which to maintain security. Users who administer content can be assigned to the System Administration ContentKeySecurity WebApp group. Users who administer application access can be assigned to the System Administration User Management WebApp group.

    Security Definitions Restrict Access to Content and Run Rules

    Security definitions have been added to the platform that restrict access to content and that run rules when certain security-related events occur. Use a security definition to:

    • Assign a key to limit a user’s access to content.

      NOTE: Security definitions are assigned to content roles. When a user is assigned to a role, the key value(s) assigned to the role’s security definition(s) restrict the user’s access to that content only.

    • Tie rules to events, so that for example, when a user is removed from a security role, the user is removed from associated template roles in dspCompose.

    Delivered security definitions cannot be updated, but users can register custom security definitions for custom WebApps. Refer to Delivered Security Definitions and Register Custom Security Definitions for more information.

    Automatic Updates to User Access to Content with Security Definition Events

    Security definition events provide the capability to assign users to application content that previously required direct application maintenance. When a specific security-related task is performed in DSP, these events run stored procedures that insert, update or delete data specific to a user and piece of application content. For example, when a user is deleted from a security role, the user is also unassigned from the relevant application content items as a result of the security definition event rules.

    The DSP is delivered with security definition events. Refer to Delivered Security Definitions for more information.

    NOTE: There is no change to the existing security definition functionality that allows security definitions to be assigned to a WebApp page and for the data on the page to be filtered based upon the user Security Definition Key value assignments.

    New WebApp Groups

    The following WebApp groups have been added. For a complete list of delivered WebApp Groups, refer to Delivered WebApp Groups.

    WebApp

    WebApp Group

    Assemble

    • PowerUserLite — Enables users to create, change, delete and execute CranPort Packages. Users cannot change any Assemble configuration-related settings.
    • ExecutionOnly — Enables users to execute CranPort packages only, not to create or edit them.

    Automate

    • PowerUserLite — Enables users to add tables to Target Sources and to build and run packages.
    • ExecutionOnly — Enables users to execute Automate Interfaces only. Users cannot create or edit them. 

    Common

    • AdvancedDeveloper — Intended to be used for Migration Advanced Developers. It enables users to maintain module-specific settings, maintain data sources, and add automation engine tasks.
    • AnalyzeLite — Enables users to execute profiling, tracing and duplicate detection activities.
    • UserCredentials — Designed to be used by Integrate Roles, allowing users to maintain their user-specific application credentials.

    dspConduct™

    • UserManager — Access to the User Settings page in dspConduct to update a user’s workflow notification settings and back up user information.

    Integrate

    • ExecutionOnly — Ability to post in Integrate, but not to activate or deactivate templates or processes

    Map

    • FieldAndValueMapper — Enables users to maintain Field and Value Mapping. Intended for use by non-migration developer resources who are responsible for documenting mappings requirements.
    • PowerUserLite — Enables users to perform all Field and Value Mapping activities needed to build a data object end to end. It's recommended for use by Migration Developers. Users with this Group cannot change any Map configuration-related settings.

    System Administration

    • ContentKeySecurity — Provides restricted access to a type of security user, usually a SME or Data Steward, that can:
      • Create security roles with a Role Type of Content and
      • Assign security definition key values to users, and to security roles with Role Types of Standard and Content 
    • DesignerPlus — Provides experienced DSP users with access to some advanced System Admin setup and configuration tasks.
    • JobMonitoring — Provides users with comprehensive access to DSP Monitoring pages.
    • UserManagement — Provides restricted access to security, only allowing access to  the pages used to create users and assign them to roles.

    Target Design

    • PowerUserLite — Enables users to perform all Data Design activities needed to build a data object end to end. It's recommended for use by Migration Developers. Users cannot change any Console or Target Design configuration-related settings and cannot create Waves, Process Areas, or Objects.

    Transform

    • ExecutionOnly — Designed to be used by:
      • A user whose role is to only process data objects or 
      • Users that are running migration load cycles from within non-development environments. Users in this WebApp group can:
        • Execute Objects, Targets, Sources, Rules and Reports
        • Publish / Unpublish Objects / Targets / Sources and Reports
        • Segment Reports 
        • Assign users to reports or report segments.
    New Security Roles
    • The following security roles have been added to the platform:

      • Governance Business User—users assigned this role can be added to WebApp groups that allow them to submit requests and process roles in dspCompose and dspConduct and to receive reports and remediate failures with dspMonitor. Users with the Governance Business User have access to all DSP Data Governance Application functionality intended for use by end users. Depending upon which applications are in scope for a project, this role will need to be tailored to meet project requirements.
      • Governance Developer—users assigned this role can be added to WebApp groups that allow them to register data sources, add system types, configure templates, and perform other development and configuration tasks in Collect, Common, Construct, Assemble, dspCompose, dspConduct, dspMonitor, Integrate, Sys Admin. Users with the Governance Developer role have PowerUser access across all the DSP Data Governance Applications and most shared cross application components (Common, Collect and Integrate). They also have wide access to System Administration functionality. They do not have access to maintain DSP Security. Depending upon which applications are in scope for a project, this role will need to be tailored to meet project requirements.
      • Migration Business User—users assigned this role can be added to WebApp groups that allow them to maintain data design and field / value mapping. They should also be able to view the migration reports to which they have been assigned.
      • Migration Developer Advanced—users assigned this role can be added to WebApp groups that allow them to have access to all waves, process areas, objects, targets and sources and can set up security for dspMigrate. Users with the Migration Developer Advanced role are senior resources on a project and are responsible for not only designing, developing and executing data objects from start to finish, but also for troubleshooting, supporting other consultants and managing some platform level settings that control DSP’s behavior. Users with this access must have a deep understanding of the DSP platform and associated implementation methodology.
      • Migration Developer Lite—users assigned this role can be added to WebApp groups that allow them to configure dspMigrate but cannot set up security. Users with the Migration Developer Lite role are developers on a project that are responsible for designing, developing and executing data objects from start to finish. This role should permit them to perform all tasks required to design, build and execute the data objects they are responsible for. Users assigned this role should have limited access to any setup / configuration areas of DSP, including Console where they are not permitted to alter the Wave setup, because such changes impact project scope and should be determined by the project lead.
      • Migration Executer—users assigned this role can be added to WebApp groups that allow them to have limited access to perform tasks within a designated wave and process area. Users with the Migration Executer role can view data design, field/value mappings and execute Transform / Integrate processes. This role is intended for use on projects that have a multi-tier DSP environment where changes made in the development environment are transported into the Quality / Production instances. This role is also intended for use by projects that have a team that is responsible solely for executing the migration process.
      • Security Administrator—users assigned this role can be added to WebApp groups that allow them to either manage security and users or manage DSP Addons. Users with the Security Administrator role can maintain all aspects of the DSP security layer. They can create roles, security definitions and custom webapp groups. They can also create users and assign them roles. This is a privileged role and must be assigned to only a few select users.
    • The Security Role Compare page has been added so that users can compare security roles to determine the groups and pages to which certain security roles have access. Refer to Compare Security Roles for more information.
    Security Reports

    User Security reports have been added to System Administration to provide details about how centralized security is configured, including:

    • All users in the platform
    • All security roles in the platform
    • WebApp Groups assigned to security roles
    • The pages and content security roles can access
    • The pages and content users can access
    • Security roles assigned to users
    • The Security Administration Reconciliation with Governance Applications report has been added to show instances where a user’s security is out of sync between a WebApp and security settings set in System Administration. The report compares a user’s access to dspConduct Positions,dspMonitor Groups and dspCompose Template Roles within the individual applications with the expected access based upon user assignment to security roles that have associated Security Definition Key Values and User Specific Security Definition Key Valus. Refer to Compare User Access to Content Between WebApps and System Administration for more information.

      To access the reports, select Admin > Security > Security Management > User Security Reports

    • A new set of report pages are available under Security Management, called Security Pages, to allow Security Administrators to see what pages are assigned to which WebApp groups, Security roles and Security Definitions. This new set of reports enables users to effectively and efficiently create new custom security roles and to grant security access to appropriate security roles. Refer to View Security by Page for more information.
    Add Multiple Users Quickly with User Role Staging
    • The User Roles Staging page has been added so that Administrators can stage user role assignments, either manually or using Excel Integration. Staging user roles allows a user to add multiple user role assignments in one process.Processing the records in this staging table adds and removes role assignments for selected users. If the roles have any security definition key values with associated events, these events will be run. Refer to Stage User Roles for more information.

    Additional Enhancements

    The following tasks that were once performed in Common are now performed in System Administration:

    NOTE: The ability update the text in the password reset email has been removed. Additionally, the View Log In History icon has been removed from the Users page. This information is now accessible in System Administration Logs.

    • The DSP is now delivered with a set of encrypted columns, such as passwords and connection strings. This feature allows Security and Data Source Administrators to monitor columns where encryption is either required or suggested for encrypted. Refer to Monitor Columns for Encryption for more information.
    • To maintain consistency across DSP pages, the E Mail Address field on the Users page now displays as Email Address.
    • The Excel Integration feature for mass user creation on the Users page now has additional fields available, facilitating the completing of users’ profiles.

      Previous fields available: UserID, Name, Password, Anonymous and Language ID

      New fields available: UserID, Name, WindowsUserName, ExpirationDate, Anonymous, Telephone, TelephoneExtension, EMailAddress, LanguageID, DefaultPageID, StyleID and LocaleID

    • The Security Definition menu and all sub-pages are now nested under a new menu option, titled Security Management. Under this menu, Security Administrators are now able to better manage security related to the platform and individual applications. They are also able to gain deeper insights into the overall DSP security setup.

    • The following pages have been modernized by utilizing fly-out pages, enabling users to access the pages with fewer clicks:

    DSP Add-ons

    • When creating custom WebApp groups with DSP Add-ons, an Administrator user can use two new methods to quickly add pages and page permissions to it:
      • Copy a WebApp group to use the pages and page permissions (the ability to view, add, update or delete records on a page) as the basis for the new WebApp group.
      • Use Excel Integration on the Group Pages page to import a spreadsheet of pages and permissions for the new WebApp group.
        Refer to Customize Security Using DSP Add-Ons for more information.
    • Custom WebApp groups created using DSP Add-Ons can now be updated after they are published. After the group is published, the Administrator user can:
      • Assign new pages to the WebApp group
      • Delete pages from the WebApp group
      • Change page permissions
      • Change security roles assigned to the WebApp group
      • Rename the WebApp group
      • Delete the WebApp group
    • WebApp groups added in DSP Add-ons are no longer deleted on upgrade. In previous versions, users were required to republish any WebApp Groups created in DSP Add-ons after upgrade.
    • Users can now CTS custom WebApp groups added to delivered WebApps that were created in DSP Add-ons.

    Common

    • The JDE System Type model is no longer delivered with the product.
    • The trace level setting is used to indicate when the DSP should log information about DSP processes. This severity is now set to Debugging Disabled (0) for Common and dspCompose debug logs. Refer to Configure Debug Logs Settings for more information.
    • The new User Calendar page allows users to view and change the calendar for a user, either individually or in bulk by utilizing Excel Integration pages. In dspConduct the pages that use that use Calendar ID (for example, the Position User, User Position and My Positions pages) were updated to continue to work.

    dspMigrate™

    Transform

    Users can now purge inactive target report segments that do not have records returned on all reports. The segments with no records display on the All Business Reports (All Waves and Process Areas) page until they are manually purged. Refer to Purge Inactive Segments for more information.

    dspCompose

    • From DSP release 7.1 onwards, users will no longer be able to be assigned to a Template or Template Roles from directly within dspCompose. It will still be possible to view user assignments to Positions. It will also no longer be possible to copy a user's template role assignment, this functionality. Instead, users will have to be assigned the corresponding Security Definition Key Value, either directly to their user, or via the assignment of their user to a Role that contains the key value.

      Watch the video for an overview of changes do dspCompose template roles for 7.1.

    • The order of items in the dspCompose Navigation menu has changed. The Configuration menu in dspCompose contains:
      • Roles
      • Org Units
      • Users
      • Change Request Status
      • Archives
    • The Setup menu contains:
      • Parameters
      • External Data Email Accounts
      • Workflow Message
      • Email Validation
      • Request Status
      • Mass Change Exclude Column
    • The Troubleshooting menu contains
      • Request Role (Finish Download)
      • Roles (Execute)
      • Data Services Job Executor
    • When a user is copied in dspCompose, the user no longer inherits dspCompose Template Roles from the user selected in the 'Copy User ID' field. Only org unit assignments are copied to the new user. Refer to Copy Org Unit Assignments for more information.

    dspMonitor

    • Users will no longer be able to be assigned to Monitor Groups from directly within dspMonitor. It will still be possible to view user assignments to Groups. Instead, users will have to be assigned the corresponding Security Definition Key Value, either directly to their user, or via the assignment of their user to a Role that contains the key value.

      Watch the video for an overview of changes to dspMonitor groups for 7.1.

    • The Data Quality Score Thresholds page is now accessible via dspMonitor > Configuration > Data Quality Score Thresholds.

    dspConduct

    • Permissions on pages assigned to the dspConduct Read Only WebApp group have been updated so that read only access is applied correctly.
    • From DSP release 7.1 onwards, users will no longer be able to be assigned to a Position from directly within dspConduct. It will still be possible to view user assignments to Positions. Instead, users will have to be assigned the corresponding Security Definition Key Value, either directly to their user, or via the assignment of their user to a Role that contains the key value.

      Watch the video for an overview of changes to dspConduct positions for 7.1.

    7.1 Resolved Issues

    dspMigrate™

    Transform

    Fixed an issue where a target report, target source report, or target Data Services report did not display on the All Business Reports (All Waves and Process Areas) page in certain cases. If the report had segments, but there were no records returned for the segments, the segments were deleted in error. With the fix, when a segment is added and users are assigned to it, even if a report has no records for a segment, the segment is not removed. Additionally, segmented reports display on the All Business Reports (All Waves and Process Areas) page, even if the target report segment contains no records. Segments with no records must be purged to be removed. Refer to Purge Inactive Segments for more information. [DSP70-552]

    Map

    • Previously, when a duplicate source table was added to the Target Sourcespage, the validation rule should have prompted the user to override the source table name. Instead, the validation rule failed. The validation rule has been fixed to properly prompt the user to override the duplicate source table name. [DSP70-776]

    dspCompose™

    • When using comparison approvals, the Approve page did not display all changes to the data entry page in certain cases. If the data entry page contained a list box, and the list box was updated to the value None, the Approve page did not display an arrow next to the list box, indicating that a change had been made. With the fix, an arrow displays next to list boxes with this update on the Approve page. [DSP70-696]

    dspConduct™

    • There were several dspConduct dashboards that did not include archived data. The impacted charts referenced the views webDashboard_RequestMinStartTimeSel and webDashboard_RequestMaxFinishedOnSel. This issue has been fixed by replacing the table ttRequestRoleLog (active requests) with apiRequestRoleLogAllSel (active and archived) in these two views. [DSP70-698]
    • An issue occurred where the Count Metrics displayed week counts that did not take the year into consideration, so two years with week x would both display, causing each year’s Count Metrics to display a different week count. With this fix, the dashboard shows the correct number of week / year records. [DSP70-707]

    Data Stewardship Platform (DSP®)

    An issue occurred where, when users enabled page logging for a data source and performed concurrent actions that produced log files, a concurrency error caused those log files to be written to a fallback file path. This frequently produced a logging file path error message. With this fix, the NLog versions were replaced in the library, which stabilized the concurrency error that was forcing the logging files to write to the fallback file path. [DSP70-759]

    System Administration

    An issue occurred when users registered a security definition and added more than one key column for a multi-part key. In these instances, the system created duplicate entries in the SecurityDefinitionKeyValue table and incorrectly processed the multi-part keys. Old values for multi-part keys are now properly removed when the security definition's key columns are modified.

    In addition to this fix, a System Provided flag has been added to delivered security definitions. Security definitions with this flag cannot be changed by users. Refer to Register Security Definitions for more information. [DSP70-743]

    Integrate

    In previous versions, if multiple background posts were executed from Integrate, they ran single threaded (one at a time). These postings worked this way because they were saved with a JobQueue GroupName of 'Integrate - Post,' which indicated to DSP that they should be run single threaded. With this fix, the Integrate 'Process Name' is used for the JobQueue GroupName, and now posts related to different processes run in parallel. [DSP70-671]

    dspTrack

    With User Management being moved from Common to System Administration, a new method to default a calendar to dspTrack users was designed by creating new the security definition events Plan Role and Project Role. Now, when a user is assigned to a role containing a Security Definition Key Value that belongs to one of these security definitions, or when a Security Definition Key Value that belongs to one of these security definitions is added to the user, the calendar defined by the Default Plan Calendar field on the Parameters page in dspTrack is assigned to users with no calendar set.

    What's New in Syniti Solutions 7.0.6

    This topic contains:

    7.0.6 Enhancements

    dspMigrate™

    Map

    To facilitate the mapping process, two changes have been made:

    1. The SOURCE DATABASE OBJECT field on the following pages now includes the description along with the table name:
    1. The SOURCE TABLE and the SOURCE FIELD fields on the Field Mappings page now include the descriptions along with their names.

      NOTE:For the name and description fields to display in the format NAME (DESCRIPTION) (for example, ITEM(MATERIAL NUMBER)), a user must define the description fields. In the System Type assigned to the data source, set the description field for the source table on the System Type Tables page, and the description for the source field on the System Type Table Fields page. If a description field is not defined, the Source ID displays the table or field name only.

    Data Stewardship Platform (DSP®)

    Collect

    • To prevent processing backlogs and inefficient DSP usage during the execution of large Collect refreshes, the queue ID can be set at the target, target source or table level. Adding a queue ID prevents processing backlogs. By assigning Collect refresh jobs to different queues, you can distribute the jobs across multiple processing threads that can run in parallel. Refer to Assign a Queue to a Refresh for more information.

    Integrate

    • Previously, Integrate postings did not support the usage of an SAP Message Server. This meant that posting processes could not take advantage of load balancing across available application servers. With this change, users can now use a Message server via Integrate postings and thus make use of load balancing capability. Refer to Establish a Connection to a Target System and Establish a Connection via a Message Server for more information.
    • SAP GUI version 7.4.3 Patch Level 8, 7.5.2 Patch Level 10, and 7.6.1 Patch Level 1 are now supported.

    Online Help

    dspConduct

    A page designer can streamline request processing by allowing users with the Review role to reject requests from inside a Content WebApp page, instead of rejecting them on the Reviewer Workbench in dspConduct. Refer to Reject Requests from a Content WebApp Page for more information.

    7.0.6 Resolved Issues

    dspMigrate™

    SQL AutoGen

    Corrected an issue in SQL AutoGen that prevented rules from being dropped and rebuilt for a target. With the fix, when the user sets the Report AutoGen Level to New Reports, then clicks the Create All Reports button on the Automation page, rules already generated for the target are dropped and rebuilt. [DSP70-578]

    dspConduct™

    An issue occurred where theTask page did not open when users added a button or toolbar that linked a task back to its parent page in order to avoid clicking the browser back button multiple times to return to the parent page. The LinkToPageID function has been fixed so that the Task page no longer gets looped and opens as expected when users add a button or a toolbar to return back to the parent page.[DSP70-684]

    Data Stewardship Platform (DSP®)

    System Administration

    • CTS components for dspConduct Role Level and Category Role Type event rules are now included. [DSP70-628]

    • Fixed an issue when installing Integrate archives using the CTS process. If records in the archive updated records in the target system, the following fields with a blank value were converted to a NULL value:
      • ProcessTemplateLoop.LoopName
      • ttBAPIField.LoopName
      • ttBDCScreen.LoopName
      • ttBDCScreen.ScreenTitle
      • ttBDCScreenField.LoopName
      • ttBDCScreenField.Fval

    With the fix, blank values remain blank when the archive is installed. [DSP70-161]

    7.0.6 Known Issue

    When viewing fields that are HTML area controls on Vertical views with tabbed layouts, the display of buttons on the tab is left aligned. This occurs if the user clicks Edit on the Vertical View with a tabbed layout, then clicks the tab containing the field that is an HTML area. The External Reference field, which displays on multiple DSP pages, is an example. To correct the display, click the tab containing the HTML area control field before clicking Edit. [DSP-8202]

    What's New in Syniti Solutions 7.0.5

    This topic contains:

    7.0.5 Enhancements

    dspConduct

    • The Request Post Workflow Notification page allowed Name fields to remain NULL and when the notification emails were sent, a blank email was sent to any user on the Request Post Workflow Notification page that had the Name field populated with NULL. Now, users must enter an appropriate value in the Name field when adding users to the Request Post Workflow Notification page.
    • The Count Metrics Chart was not considering the year when determining the week, so if dspConduct had requests from previous years, all years were combined into the respective week. Now, the year is included in the chart label with its corresponding week.
    • Archived requests are now included in the calculations in the following charts:

      • Category Request Duration

      • Business Process Request Duration

      • Scenario Business Process Request Duration

      • Role Scenario Request Duration

      • Category SLA Percent On Time

      • Category, Business Process SLA Percent On Time

      • Business Process, Scenario SLA Percent On Time

      • Scenario, Role SLA Percent On Time

      • Business Process Predictive
      • Request Predictive
    • The calculation for the charts Category Request Duration, Business Process Request Duration, and Scenario Business Process Request Duration has been updated to use the average request duration, and not the average request role duration as in previous versions. Additionally, the baseline used in the request duration considers completed requests from the active and archived request table. The request start for the calculation is the earliest start time of all roles. The average duration calculation uses a rolling history that is set by the dspConduct parameter Preceding Weeks Count.

    • A page designer can call the public events Validate and PreFinish from the dspConduct Request Role page from any event on dynamic pages in the Content WebApp. This allows users to run these events via a button on Content WebApp pages. Refer to Add Validate and PreFinish Events to Content WebApp Pages for more information.
    • A new Completed column was added to the Request Status page to indicate which statuses relate to completed requests.

    Data Stewardship Platform (DSP®)

    • The following usability improvements have been made to the UI:

      • Font sizes are now consistent across Horizontal and Vertical views

      • Line spacing has been reduced to allow more information to be available on the page without scrolling

    • The DSP is now packaged with both versions of DBMoto: 32-bit and 64-bit. Previously, only the 32-bit version of DBMoto was packaged with the DSP and clients had to request the 64-bit version from Support. Refer to the Syniti Installation and Update Manual for DBMoto installation and upgrade instructions.

    System Administration

    • A new site parameter called Support Workflow Authentication is available on the Parameters page to allow site administrators to enable/disable the ability for users to be automatically logged in to the DSP when they click a link in a workflow email. By default, this parameter is enabled.

      If Support Workflow Authentication is enabled:

      • Users are automatically logged in to the DSP when the workflow link is clicked.
      • The following disclaimer text appears in workflow emails:

        "Any user who clicks the workflow link in this email will be automatically authenticated based upon your user account. Any actions performed in the DSP will be tied to your user account, and any information associated with your account is accessible to that user."

      If Support Workflow Authentication is disabled, users who click the workflow link must log in to the DSP to access the DSP page. If a user forwards their workflow email to another user, this new site parameter prevents the recipient of the email forward from automatically being logged in to the DSP when the workflow link is clicked.

    • The DSP User Interface (specifically, menu links) can now be easily customized to support language-specific requirements without the need for a DSP design license. This is done by creating a custom catalog, adding the phrases that need to be translated, and assigning the new catalog to the System Catalog ID field on the Language support tab of the Parameters page.

    Common

    • Business Rules are now included by default in the bulk execution processing capability on the User Management page. Users on this page now have an option to execute validations and business rules after executing Excel uploads for users. Refer to Use Bulk Execution for more information.

      NOTE: The User Management page was removed with 7.1.

    • To prevent incomplete System Types or those of a poor quality from being sent to the Entota Cloud, an 'ENTOTA Cloud Ready' check box has been added to the ztSystemType table and the associated Vertical view of the System Types page. This check box is unchecked by default, and can be updated by users.

    • To support the transfer of metadata from registered systems in the DSP to the cloud, and to maintain the original data types to describe the system in its original format, the table ztSystemTypeTableField now includes the following fields:

      • Original Data Type
      • Original Length
      • Original Decimals

      These three new fields have also been added to the Vertical View of the System Types Table Fields page.

    • The newly added Source Metadata fields, Original Data Type, Original Length, and Original Precision, are now included in the System Type Model Import process.
    • Now all fields will be included in a SAP System Type Model Import, even fields that do not have descriptions in table DD04T.

    Online Help

    Added the topics:

    7.0.5 Resolved Issues

    dspConduct

    • dspConduct has a process that scans the Content Application Database Audit Tables to produce a Review Role Audit Details report. This process selects a table's keys and other configured fields with a pipe delimiter into a single Key To Record field in the Report. When any of those fields used a different database collation, an error would occur. To resolve this issue, the aggregation process now converts the results of the select into the database_default collation. [DSP70-510]
    • Previously, incomplete development of dspConduct Tasks (missing child pages and audit tables) prevented request data from being added to the ttReviewRoleAggretate table. This in turn prevented Review Role Audit data from displaying on theReview Role Audit Details page, resulting in time-consuming analysis work to identify the problem. To help consultants identify tasks that may have pending development work, the TASK PAGE LIST UPDATED field has been added to the Taskpage to identify tasks that have missing child task pages. Additionally, the AUDIT TABLE CREATED field has been added to the Task Page page to identify pages that do not have auditing set up. [DSP70-478]

    dspMigrate™

    Map

    Previously, after installing a full Wave CTS package in another DSP landscape, the wave registration was not available on the Wave Lookup Table Refresh page. This meant that users were not able to refresh Target Values. Additionally, after installing a CTS package containing Wave Process Area Object Target Mappings or the Wave Process Area Object, users were unable to view mappings on the Field Mappings page. These issues could be worked around by syncing a target table to Map.

    These issues were resolved by making the following changes to the CTS configuration:

    • Added a new shippable item: cMap - Wave Service Check Table
    • Added new SQL Object Relationships from table ttTarget to ttTargetField [DSP70-563]

    dspCompose™

    In dspCompose, when the Force Reject Severity list box was set to Warning or Message at the template level, the Reject check box on the Reject page was not automatically checked for rows that failed both the Error and Warning/Message validations. With this fix, the Reject check box is checked for every row that fails the Error validation including rows that also fail Warning/Message validations when the Force Reject Severity list box is set to Warning or Message. [DSP70-519]

    Data Stewardship Platform (DSP®)

    • Corrected an issue with the delivered CTS configuration for Integrate. The CTS process now includes custom fields assigned to the template when building the archive. [DSP70-477]
    • Syniti Transport RD2K9A00XW is not compatible with S/4HANA version 1809. Clients that are running this version of S/4HANA will need to contact Syniti Supportto obtain a compatible version of the transport. [DSP70-458]

    Collect

    • The contents of ztTargetSourceConnectionType conversion table and ztTargetSourceConnectionTypeDataConversion table have been modified to allow DB2 and Oracle tables to be downloaded correctly and to allow DB2 BIGINT values to be downloaded correctly. [DSP70-580]
    • Previously, the Collect build of tables with more than 1 column failed with a primary key error when using an ODBCTERADATA source. This issue has been resolved by modifying the delivered Download SQL field for the ODBCTERADATA source connection type (on the Source Connection Types page). [DSP70-434]
    • When users would select to build packages or refresh Oracle tables, they received duplicate column errors because of hidden or virtual system columns. With this fix, users can build packages or refresh Oracle tables without errors. [DSP70-553]

    System Administration

    • Previously, when a user forwarded a workflow email to a second user, the second user could click the link and be automatically logged in to the DSP as the first user. A site parameter, Support Workflow Authentication, was added to the Parameters page to allow site administrators to enable/disable the ability for users to be automatically authenticated when they click a link inside a workflow email. Support Workflow Authentication works for both Basic and Integrated Authentication. [DSP70-448]
    • An issue with header detail pages that only had a Vertical View with tabs has been fixed. Previously, with this specific page setup, despite the tab the user was trying to edit, once in edit mode, the page would automatically jump to the first tab and inactivate the remaining tabs. [DSP70-528]

    7.0.5 Enhancement Requests from Users

    dspConduct

    In dspConduct, when users clicked the Finish icon (or Validate button) on the Request Role page, the validation pop-up did not bind on the current UserID and the validations sometimes displayed duplicates. With this fix, the pop-up binds on the current UserID so that duplicate validations are never displayed.

    Online Help

    • The Enable Required Validation documentation in dspCompose has been clarified to state that validations are not run on required fields with data types other than nvarchar.
    • The dspCompose topic,Create Teams was clarified to indicate that a user must be added to dspCompose before being added to a team.

    What's New in Syniti® Solutions 7.0.4

    This topic contains:

    7.0.4 Enhancements

    Data Stewardship Platform (DSP®)

    • The DSP® assists clients with corporate or regulatory compliance by logging all events related to processing personal data in a data source identified at the client site. The logs are created daily as .CSV files. The DSP creates a log entry every time an event executes in DSP in any application, including each page load. A log retention period has been added to the Logging Options tab on the Parameters page in System Administration. Using this field, a user can set a date by which these logs are deleted. Refer to Log Events and Access to Personal Data for more information.

    • When connecting to a HANA data source, the DSP now creates a session variable called APPLICATION and sets the value to VBR_DSP_HDI.
    • A Previous Password field has been added to the My Profile page. When users reset their passwords, they must enter their current password into this field, along with the new password and a confirmation, to reset it.
    • The DSP installation package now includes a user prompt to create and confirm the administrator password as part of the installation and users do not need to change the password immediately after installation as part of the configuration of the application.

      NOTE: This enhancement does not apply to upgrades as the administrator account password will already be set and known.

    Collect

    Since all tables in DSP are required to have primary keys, if the Download Keys Indexes field on the Target Sources page's Vertical View was not checked during registration of the source, many tables got created without primary keys and had to be rebuilt and refreshed later. Now, the Download Keys Indexes field is checked by default.

    Online Help

    Added the topic Extraction Methods for End-to-End Integration Solution.

    7.0.4 Resolved Issues

    dspMigrate™

    Transform

    Fixed an issue where Target and Source reports were failing because they were being executed against the Migration Object Database Data Source Name instead of the Migration Object Database Data Source Database Name. [DSP70-498]

    dspCompose™

    • Corrected an issue where, when archiving requests, the Posted On, Posted By and Post Start Time were not included in the archived record. With the fix, these values are captured so that the archived request's data is complete. [DSP70-509]
    • Fixed an issue where the X and Y axis on the Request Time Taken chart in dashboards overlapped at a 200% font zoom. To fix this issue, the following text changes were made to increase space on the axes and therefore avoid overlapping:
      • Renamed the page from Request Time Taken to Active Requests Time Taken (Days).
      • Renamed columns from Longest Days Active, Shortest Days Active and Average Days Active to Longest, Shortest and Average.
      • Changed the date to a numeric format, e.g., 01/2018 instead of Jan 1, 2018. [DSP70-411]

    Data Stewardship Platform (DSP®)

    • The CSV download/export feature assumes files are opened by a spreadsheet program that allows formulas (such as Excel). When not opened by a spreadsheet program, an issue occurred with CSV files where formulas that should be displayed as text were being executed, and therefore displayed warnings to the user. To resolve this issue, an apostrophe was prefixed to the first character of cells that start with an equal (=), plus (+), minus (-) or “at” sign (@). [DSP70-476]
    • DSP user email addresses have historically been limited to 50 characters. This limitation has been removed in this release. With this fix, user email addresses used to access the DSP can be up to 255 characters in length. [DSP70-480]

    Assemble

    Fixed an issue with file delimited CranPort packages (of any Target data source with a text delimiter defined) where the last column displayed as NULL under the following conditions:

    • At least 1 column other than the last column was delimited by the defined text delimiter
    • The last column did not have a text delimiter
    • The last column was a single character (such as A or 1)

    All rows now populate as expected: with values and with the text delimiters dropped from the delimited values. [DSP70-506]

    Collect

    • Fixed an issue where Data Services package builds failed with the error “The maximum message size quota for incoming messages (65536) has been exceeded." A large number of jobs being built in a single Data Services repository caused the issue. To correct it, target sources can now have a Data Services repository assigned. In prior versions, the repository could only be assigned at the target level. Data Services jobs for different source systems can be registered and created in separate repositories, and the issue that causes the error no longer occurs. Consider creating and registering an additional repository for separate target sources to minimize the chance of overloading the communication between Collect and Data Services. Refer to Configure Source for SAP Data Services for more information. [DSP70-453]
    • Fixed an issue where if the data in the Connection String field at the target source level was encrypted, any refresh would result in the data being decrypted. Now, whether the refresh is at the target or target source table level, manual or scheduled, the data in the Connection String field remains encrypted.[DSP70-538]
    • An issue occurred on the Target Source (Tables) page where builds failed with a PRIMARY KEY error when trying to build a package for a table that existed twice in the source for two different schemas. With this fix, the schema owner is included when pulling the table definitions, allowing packages to build successfully. [DSP70-430]

    • An issue occurred on the Job Detail page where scheduled refreshes that had successfully completed were recorded as having a Cancelled status. With this fix, successful refreshes are now recorded as having a Completed status. [DSP70-433]

    What's New in Syniti Solutions 7.0.3

    This topic contains:

    7.0.3 Enhancements

    Data Stewardship Platform (DSP®)

    • Session ID values no longer appear in any URL string created as part of navigation around the DSP and are no longer visible in IIS logs, decreasing session handling vulnerabilities and improving security.
    • To improve accessibility, the Messages in the Quick Panel now display READ and UNREAD to indicate the status of the message rather than an R.

    Online Help

    Added the topics:

    7.0.3 Resolved Issues

    dspMigrate™

    Target Design

    An issue occurred on the Target Source Full Construct page where the Drop and Build Construct Page button was hidden instead of dimmed until the Target Source was synced to Map. With this fix, the Drop And Build Construct Page button is dimmed until the Target Source is synced to Map. [DSP70-490]

    Map

    • For charts that displayed mapping status, the metrics displayed incorrectly in some cases. If a target had more than one source, and one of the sources was inactive, the mapping would display 0 on the charts, even though mappings had been completed. With this fix, charts display mapped fields correctly when a target has an inactive source. [DSP70-320]
    • The following charts did not display data under certain conditions:
      • Process Areas were missing from the Field Mapping by Wave & Process Area chart when no targets in that process area had any completed mappings.
      • Objects were missing from the Field Mapping Summary by Object chart for a process area when no targets in an object had any completed mappings.
      • Targets were missing from the Field Mapping Summary by Target chart for an object when a target did not have completed mappings.

      With this fix, these objects now display on dashboards, though they still show no data (as the target mapping has not been started). [DSP70-323]

    • An issue occurred when users submitted mappings for approval; the Mapping Status icon turned green in Map but dimmed in Automation. With this fix, mappings submitted for approval cause the Mapping Status icon to turn green in Automation as well, correctly representing the mapping status in Map. [DSP70-431]

    dspConduct™

    • When importing data from IGC into dspConduct, the cloud import failed if the DSP password was encrypted. With this fix, the cloud import does not fail in this situation. [DSP70-493]

      NOTE: This feature was deprecated in a later version.

    • Corrected an issue that caused Late Summary emails to be sent to roles even though the Late Summary workflow message was disabled for the category. [DSP70-200]
    • Corrected an issue where the ability to activate and deactivate the Late Summary workflow in dspConduct for a specific category did not work. The Late Summary workflow can now be set as active or inactive for individual categories. [DSP70-487]
    • In dspConduct, the Request Post Workflow Notification page allowed Name fields to remain blank and when the notification emails were sent, a blank email was sent to any user on the Request Post Workflow Notification page that didn’t have the Name field populated. With this fix, users will be required to enter values in the Name, Email Address, and Language fields when adding users to the Request Post Workflow Notification page. [DSP70-452]
    • An issue occurred where when users added Scenarios to Business Processes and Roles to Scenarios, the drop-down links for SCENARIO ID and ROLE ID opened to pages with all Categories displayed. With this fix, the drop-down links open pages filtered by the Category in which the user is working. [DSP70-432]

    dspCompose™

    When adding a Request to dspCompose, the Vertical View displayed both the Template and Template Name fields until the record was saved at which point the Template list box was removed and only Template Name was visible. Furthermore, when using keyboard navigation, the Template Name field took focus even though no entry was possible. With this update, only the Template field is displayed at the point of creation and this field remains displayed and editable on the page once saved. [DSP70-440]

    dspMonitor™

    In dspMonitor, on the Your Groups page, if all of the reports were Info reports, the status displayed yellow with an exclamation mark and a tool tip of "Report Configuration Incomplete". With this fix, if all reports are Info reports, there is no check for an Opportunity View and the status at the group level is green with a tool tip of “Complete”. [DSP70-460]

    Data Stewardship Platform (DSP®)

    • Fixed an issue where users who logged in to the DSP were not given unique session IDs. Now, these IDs are generated for each user per session. [DSP70-456]
    • The sort order was corrected throughout various charts in the DSP. As a result, the order of values on some chart pages has been updated. [DSP70-405]
    • Fixed an issue with the focus on the Close button in the Quick Panel. The user can now tab and back-tab through the items on the Quick Panel, and close the window by pressing the Enter key when the Close button is in focus. [DSP70-438]

    • Corrected the border color of non-required list boxes when they are in focus across pages in the DSP. List boxes now have the same border color as other focused fields. [DSP70-439]
    • Fixed an issue that prevented tool tips from displaying on the Edit, Status, Vertical, Audit and Delete icons on the Horizontal View on DSP pages. Tool tips display for these icons in all supported browsers. [DSP70-443]

    • The header bar did not change when different high contrast styles were applied as it was a fixed image. With this update, the header bar image has been replaced with the base color of the style applied to the Navigation pane, and a light or dark version of the DSP logo is applied to the header bar. Furthermore, the text color for context menu items displayed in the header bar as well as the up / down navigation arrows follow the coloring of the Navigation pane text. [DSP70-442]
    • When users opened the online help by clicking on the “?” icon on a page, any subsequent navigation to the help from the DSP in the same session would open a new tab. With this update, after users have opened the online help in a tab, any subsequent navigation to the help from the DSP in the same session re-uses the open tab displaying the help. [DSP70-369]

    • When downloading an Excel template through Excel Integration with the Data Type in the header, the data type DECIMAL displayed the length in bytes of the field in the header. This was confusing as most users are more familiar with precision and scale when working with this data type. With this fix, only char-based data types display length. Fixed length data types including decimal, numeric, money and smallmoney, display the data type and the number of whole digits and decimals, for example decimal (10,4). [DSP70-450]

    Collect

    • Fixed an issue where Data Services package builds failed with the error "The maximum message size quota for incoming messages (65536) has been exceeded." A large number of jobs being built in a single Data Services repository caused the issue. To correct it, target sources can now have a Data Services repository assigned. In prior versions, the repository could only be assigned at the target level. Data Services jobs for different source systems can be registered and created in separate repositories, and the issue that causes the error no longer occurs. Consider creating and registering an additional repository for separate target sources to minimize the chance of overloading the communication between Collect and Data Services. [DSP70-453]
    • When setting up data type conversions using a source connection type of ODBCDB2, ODBCDB2AIX, ODBCDB2AS400, OLEDB2, OLEDB2AS400 and ODBCIM, the BIGINT data type was converted to INT. The data type is now converted correctly. [DSP70-435]

    System Administration

    • On the Vertical View of the System Administration > WebApps > Pages > General tab, when a user hovered over the Vertical View field, there was a typo in the Hover View Pane text. With this fix, the typo has been corrected. [DSP70-451]
    • An issue occurred on the Customization Review page where it failed to load on SQL Server 2017. With this fix, changing the CranSoft database compatibility level from 140 to 130 is no longer needed as a workaround. [DSP70-475]
    • Required text boxes had a blue border for On Focus while the border for On Display was green. With this fix, the border of required text fields when On Focus is now green, making the color for all required fields the same when On Display and On Focus. [DSP70-491]

    Integrate

    Automate

    Fixed an issue where duplicate interface instances were sometimes created by Automate when queues were full. [DSP70-412]

    7.0.3 Enhancement Requests from Users

    What's New in Syniti Solutions 7.0.2

    This topic contains:

    7.0.2 Enhancements

    dspMigrate™

    Construct

    The process for building tables, views, pages and objects for Full Construction sources has been updated. For a Full Construction target source, the Construction table, view and page are built when the Full Construction target source is synced to Map, not when it is saved. For Enrichment Construction, the table, view and page are built when the Construction mapping is submitted, not when it is saved.

    Data Stewardship Platform (DSP®)

    • Users can now generate a URL to link to a specific page in the DSP by using the Copy URL to Clipboard option in the Settings menu. The URL takes them to the page where it was generated with the same drill through and the same filters applied. Refer to DSP® Navigation and Menu Options for more information.

      NOTE: The Copy URL to Clipboard option uses the value that is set on the System Administration > Configuration >Parameters page, in the Web Site Root field to generate the correct URL.

    Online Help

    Updated these topics for clarity:

    Added the topics:

    7.02 Resolved Issues

    The default Email From address for workflow notifications has been updated in Console (for dspMigrate), dspCompose, dspMonitor, dspConduct, and Common (for Collect) to replaceme@entota.com. This address must be replaced with a valid email address at the client's site. [DSP70-428]

    dspMigrate™

    AutoGen

    An issue occurred that prevented AutoGen from creating rules for Xref actions in Map in certain cases. When a target was synced with Map, then a lookup table was added to the target in Target Design that had not been used in other mappings in the source, then the mapping was reset and submitted again, AutoGen did not create the xt views in the database when the user clicked the Create and Complete icon for the rule in AutoGen. AutoGen displayed a message that it had completed successfully. The rule was not created as it was not validated. With the fix, when the user clicks Submit in Map for an Xref mapping, the record is validated and AutoGen can then generate the xt view. [DSP70-444]

    Target Design

    Fixed an issue that caused duplicate icons to display on the Targets page. [DSP70-429]

    Map

    • Fixed an error that occurred ("The service was unable to evaluate the non-query statement.") when the user clicked the Submit button on the Field Mappings page when mapping a target source field with the Construction action. [DSP70-338]
    • Fixed an issue that caused duplicate icons to display on the Wave Lookup Table Refresh page and the Value Mapping page. [DSP70-429]
    • The Value Mapping by Wave & Process Area chart showed a bar for each Process Area in the Wave, but all of the bars displayed the same values for the selected Process Area. With this fix, only one bar displays with the correct selected Process Area values. [DSP70-321]
    • An issue occurred that caused an error to display when setting the Source Database Object on the Target Sources page in Map. If a source used a System Type that had a table with multiple joins, and the source was added to a target in Target Design and then synced to Map, attempting to add the source database object in Map resulted in a Primary Key Constraint error. With the fix, this error no longer displays, and source database objects can be added to the target source in Map. [DSP70-388]
    • An issue occurred that caused validating or adding a source based on a system type on the Target Sources page in Map to take over a minute in certain cases. When there was a large amount of data (for example, over six million fields and over one million joins), the performance was slow. A stored procedure that was no longer needed was removed from the OnValidate event for the Target Source record, which greatly reduced the time it takes to add or validate a target source. [DSP70-389]

    Transform

    • Fixed an issue where, when generating documentation for target source reports in Transform, an error occurred if the report Description was longer than 50 characters. [DSP70-280]
    • Fixed an issue that prevented multiple target sources from being executed at the same time in certain situations. If two targets used the same source ID, the Process icon on the Target Sources page was dimmed for one of targets while the other target was being processed. With the fix, target sources of this type can both be processed at the same time. [DSP70-406]

    dspConduct™

    • When multiple Final Finishes were run, sometimes the Final Finish and the Business Create Processes failed. With this fix, users can run multiple Final Finishes without failures. [DSP70-279]
    • The finish process used to be able to create multiple Finish Packages and refresh tables multiple times per request. With this release, tables refresh once per unique WHERE clause regardless of the number of Tasks that they are registered to. For example, if LFA1 (Vendor General Data) is registered to 2 tasks that are in the same request with the same WHERE clause, then LFA1 only refreshes once during the Finish process.[DSP70-142]

    dspMonitor™

    • When users clicked View on a report, the report displayed with a Report Name column that repeated the same information for each row. With this fix, this extraneous column has been removed from the page. [DSP70-371]
    • Am error displayed when running a report that had the Order By field populated that also used a File Delimited output type. With the fix, the report executes successfully under these conditions. [DSP70-385]

    Data Stewardship Platform (DSP®)

    Collect

    • RAW Data Type conversions often produced errors in delivered Connection Types. With this fix, RAW Data Type conversions work as expected. [DSP70-408]
    • An issue occurred on the Tables page where CranPort packages no longer appeared in the Package Name list box. With this fix, the CranPort package names appear for the Target Source tables.[DSP70-186]

    Common

    • When an SAP System Type was imported using the model views included in Common (DSPCommon.dbo.tvDataBaseModel_%), tables with a TABCLASS of "POOL" in DD02L were not imported into the System Type. With this fix, tables are imported as expected. [DSP70-386]
    • The Add option on the Debug Log page was not supported for custom WebApps, so users were not able to create a Debug Log. With this fix, users can create a Debug Log for custom WebApps. [DSP70-384]
    • A service page has been created in Common to automatically delete dspCommon.dbo.ttMonitor records based on the retention days configuration on the Monitor Overview page. [DSP70-277]

    Integrate

    The No Data Symbol, which represents no data in a post, did not display when posting a BDC process in the background using the BDC Post Method BOAFileCreation. With the fix, if the field is blank, Integrate uses the symbol correctly to represent no data in the posting record. [DSP70-361]

    7.0.2 Known Issue

    There is a known issue with SQL Server 2017 running at Compatibility Level of 140. Dynamic views that have SQL and reference functions that return tables can cause the SqlDataAdapter.FillSchema method to fail to return the schema. If WebApp Customization > Page Customization is used, the Compatibility Level must be lowered to 130 for the Cransoft databas. In SSMS, execute the following statement:

    ALTER DATABASE [CranSoft] SET COMPATIBILITY_LEVEL = 130

    7.0.2 Enhancement Requests from Users

    • When Excel Integration was enabled, the dynamic column help was written into a row of the Excel sheet and due to the length of the help text this could contain, it was not an ideal way of providing the information to the user. Now, users can choose whether the help text goes into a header row of the sheet or is attached as a comment. When the Excel Help Text as Comment check box is checked on the Excel tab of the Vertical View of the Pages page, the column help text is displayed in comments when hovering over the second row in the downloaded Excel template.
    • When users select Download from the More Actions menu on a DSP page, the default value selected is Microsoft Excel Document (XLS)
    • A note was added to the field description for the Rule field on the Scenario Role Event Rule page: "NOTE: When adding a custom business rule, the Designer selects the rule from a list of stored procedures from the selected data source. These stored procedures can only accept the inputs RequestID and RoleID.

    What's New in Syniti Solutions 7.0.1

    This topic contains:

    7.0.1 New Feature

    Use the Agent Interface to Configure the Migration Dashboard

    The Migration dashboard, visible in Syniti, provides visibility into progress and status associated with enterprise Data Migration efforts by giving you access to the most important migration project metrics.

    Using this dashboard you can:

    • Understand the current status of migration waves
    • Identify any waves that are running behind schedule
    • Ascertain go-live readiness for a wave

    Before waves, milestones and threshold data can display on the Migration dashboard, each must be configured in the DSP. Refer to Configure the Migration Dashboard for more information.

    NOTE: You need an additional license to access the Agent Interface and the Migration dashboard. Contact your Syniti Sales contact for more information. If you do not have contact information, then submit a request in the Product Support site.

    7.0.1 Enhancements

    Data Stewardship Platform (DSP®)

    Online Help

    The help now has an enhanced feedback section at the bottom of every page, where users can indicate whether a page's content was helpful. The Documentation team uses this feedback to monitor and improve the quality of the help.

    The Online Help now features video use cases for the following topics:

    7.0.1 Resolved Issues

    dspMigrate

    Target Design

    Fixed an issue that caused an error to display when a user clicked the Drop and Build Data Construction Table and Page icon on the Target Sources page’s Vertical View. [DSP70-395]

    dspConduct™

    • Users used to be able to run Finish Packages even when the package generated without a WHERE clause, which resulted in a full target system table refresh. With this release, the DSP prevents Finish Packages from running if they generate without a WHERE clause to prevent the full target system table refresh. [DSP70-141]
    • An issue occurred on the Request Roles page where the Finish button was behaving incorrectly. When a user clicked the Finish button to finish the role, the button became disabled, then enabled again, even though rules registered to the Finish event were still executing. The user could then click the Finish button a second time, executing the rules again, which would result in errors in the data and posting errors. With this fix, once the Finish button has been clicked once, it is either disabled or overlaid with a spinning icon that indicates current foreground processing. [DSP70-144]

    dspMonitor™

    An error occurred in dspMonitor, on the Workflow Parameters tab of the Parameters page, where the Registered Sign was displayed incorrectly as a unicode fallback value in the Email Attachment Body text. With this fix, the Registered Sign displays correctly. [DSP70-398]

    Data Stewardship Platform (DSP)®

    The following related issues were resolved involving the reliability of the DSP site after an extended idle period. The problems found were related to the erroneous generation of records in the LogEntry and Setting tables for background events and multiple licensing concurrency errors being unhandled. [DSP70-154, 155, 156, and 157]

    System Administration

    An issue occurred in CTS where unresolved aliases that existed in SQL Objects were causing builds to fail. With this fix, CTS packages are created for the SQL objects ignoring unresolved aliases and the builds complete successfully. [DSP70-374]

    Common

    An issue occurred where the Common Service page Data Services Status produced failures due to a RunID that could not be found as a Job in Data Services. With this fix, the Common Service page Data Services Status no longer produces these failures if there is a RunID referenced in DSP that does not exist in Data Services. [DSP70-281]

    What's New in Syniti Solutions 7.0

    This topic contains:

    WARNING: Any additions or changes users have made to CTS configuration (Admin > CTS >Configuration) may be lost when upgrading from DSP 6.6.x or earlier.

    Prior to any upgrade backups should be taken of all databases. Once the upgrade is complete, if any custom CTS configurations are found to be missing, then the backup of the CranSoft database should be restored to a new database (DO NOT restore it to the CranSoft database). The missing custom configurations can be merged into the CranSoft.dbo.CTSConfig% tables from the restored backup.

    Please contact Syniti Support if you would like assistance with this activity.

    7.0 New Features

    Updated User Interface

    • The look and feel of the DSP® has been updated for 7.0. All pages and functionality are still available. Refer to DSP® Navigation for more information.
    • The Styles page in System Administration has been updated with additional options. After upgrading to 7.0, custom styles may have to be updated by an Administrator. Refer to Add a Style in System Administration for more information.
    • Images in the DSP have been updated to svg format. Refer to Add or Update Custom Icons for Custom WebApps for more information about working with svg images.

    Updated Online Help Interface

    • The look and feel of the online help has been updated. Refer to How to Use Online Help for more information.
    • The online help is now hosted and accessible via a URL, instead of being installed on site with the DSP. This allows for updates and improvements to help to be made independent of a product release.

    7.0 Enhancements

    Data Stewardship Platform (DSP®)

    The DSP now supports SQL Server 2017.

    System Administration

    • Administrators now have an avatar icon in the Site toolbar that displays the Administrator’s initials and has a service light. The service light continuously displays the current status of background jobs. When admin users click the avatar, depending on the service light color, the icon directs the user to different linked pages. The service light colors indicate:
      • Red — Service down; links to Resources page
      • Yellow — Service job failed; links to Jobs (Failed) page
      • Green — Nothing in failed job queue; links to Resources page
    • The Styles page has been updated to reflect the additional interface elements that can be styled with 7.0. Elements that are no longer styled have been removed.

      NOTE: Custom styles may need to be adjusted after an upgrade to 7.0. Refer to the Styles page for information about each option.

    Online Help

    7.0 Resolved Issues

    dspConduct™

    • Corrected an issue where the request status displayed in the Content WebApp incorrectly. When a request displayed the “Scheduled” request status in dspConduct, it displayed the “Request in Process” status in the Content WebApp. With the fix, the request status displays correctly in the Content WebApp, and users can view which requests are scheduled to post in the future. [DSP70-185]
    • Fixed an issue where, under certain conditions, records were not written to a log table when a role was not used in any of the later dependencies in a request. For example, if role 1 had roles 2, A, B, and C dependent on it, and role 2 had roles B, C, and D dependent on it, when role 2 completed, no log entry was created for role D. Additionally, if role D was dependent on any other role, no log entry was created. Now, records are written to the log table without issues. [DSP70-202]
    • Fixed an issue when using the Group Post feature where the user ID of the person triggering the posting process was not recorded correctly against each of the posting steps. The user ID stored as the request's Posted By value is now used for the individual posting processes in that request. [DSP70-203]

    dspMigrate™

    Map

    Deadlock errors occurred and duplicate fields displayed on the Target Source Schema page in Map when a user selected multiple fields and clicked the Reset button. With the fix, the Reset icon is active when one field is selected, and is dimmed when multiple fields are selected. [DSP70-198]

    SQL AutoGen

    Fixed an issue where, in certain situations, DSP did not map the correct SQL Server data type to a System Type field’s data type when building tables using AutoGen. With the fix, all relevant data types can now be mapped for System Type field’s data types, and tables are built correctly. [DSP70-201]

    Transform

    An issue occurred and users could not execute target reports that had key field names that contained special characters. With this fix, users can execute target reports in Transform, even if the key field names contain special characters. [DSP-6552]

    dspMonitor™

    Postal code formats for validations used in dspMonitor™ have been updated as a result of SAP OSS number 1381564. [DSP70-199].

    Data Stewardship Platform (DSP)®

    An issue occurred where SSIS packages took too long to process. With this fix, the code for processing SSIS packages was changed back to OleDB.net and is processing quickly; users no longer need to use the ManualSSIS Package workaround. [DSP70-270]

    Common

    An issue occurred where Lookup Table values were not being populated when System Types were imported into Common. With this fix, System Type Import populates Lookup Table values for System Types Table Fields as expected. [DSP70-282]

    Online Help

    • The navigation for the field description topic describing the Target Source Copy To page in the DSP was improved. Also, both a field description and use case topic were added to the help that explains the Target Rule Copy To page in the DSP. [DSP-9544]
    • Improved the RANGE LOW and RANGE HIGH field descriptions on the Sample Sizes (Setup) page in Transform.

    IG Universal Connect

    Fixed an issue with the plugin used by Integrate and Collect to call Boomi that caused an error when the number of processes in a single account was greater than 400. [DSP70-87]

    What's New in Syniti Solutions 6.7.1

    This topic contains:

    WARNING: Any additions or changes users have made to CTS configuration (Admin > CTS >Configuration) may be lost when upgrading from DSP 6.6.x or earlier.

    Prior to any upgrade backups should be taken of all databases. Once the upgrade is complete, if any custom CTS configurations are found to be missing, then the backup of the CranSoft database should be restored to a new database (DO NOT restore it to the CranSoft database). The missing custom configurations can be merged into the CranSoft.dbo.CTSConfig% tables from the restored backup.

    Please contact Syniti Support if you would like assistance with this activity.

    6.7.1 New Feature

    In dspMonitor™, the Business Value dashboard has been added to track the costs of data quality issues. Users configure the Business Value dashboard by entering the Cost Per Failure for each report, and, if needed, setting the currency to a value other than US dollars. Refer to View the Business Value Dashboard for more information.

    6.7.1 Enhancements

    dspConduct™

    The Final Finish Admin WebApp group has been added to dspConduct. Users in this group receive workflow notifications when a final finish package is created but fails to run successfully. Refer to Send Workflow Notifications when a Final Finish Package Fails for more information.

    Data Stewardship Platform (DSP®)

  • The Description field was added to the Archive Manifest Keys page in System Administration.
  • Online Help

    • The Report Delivery section in Transform has been updated and restructured for accuracy and clarity.
    • Various topics in Console were renamed and combined for clarity.

    6.7.1 Resolved Issues

    dspConduct™

    The Disable and Enable icons were removed from the Page toolbar of the Category Workflow Message page. The functionality around these icons is redundant. The same icons are available on the Category Workflow Language Message page and are used to enable or disable messages. [DSP-10234]

    dspMonitor™

    • Data displayed incorrectly on the Your Metrics page for users in existing groups with historical data when a new user was added to the group. The page displayed the same number of duplicate records as there were group members. For example, a group had 4 members and reports were processed. A new user was then added to the group. The Your Metrics page displayed correctly for new users, but displayed 5 duplicate records for existing users. With the fix, the Your Metrics page displays the correct number of records for all users in the group.

      NOTE: The resolution of this issue also corrected an issue with the amount of data that displayed on the Your Group Metrics chart. In previous versions, this chart did not use the Display Metrics Duration parameter to determine the number of days to display on the chart. The value was hard coded in the chart as 8 days. With the fix, the chart uses the correct parameter, and the chart is now aligned with Your Report Metrics and Your Metric Reports pages and charts. [DSP-10321]

    • An issue occurred that prevented users who only belonged to the dspMonitor User WebApp Group from accessing dspMonitor. Security settings were updated for the Data Quality dashboard, and users in the User WebApp Group can now access dspMonitor. [DSP-10228]

    • The data on the Your Report Metrics chart did not display correctly for users assigned to existing groups with historical data. The chart displayed duplicate records and did not display records in chronological order after reports were processed. Users who belonged to the group when it was created and before reports were initially processed were not affected by this issue. With the fix, the Your Report Metrics chart displays data as expected for users added to existing groups. [DSP-10361]

    dspMigrate™

    Map

    • While mapping a field with the Default action, depending on the data type length of the field, users creating a placeholder to create output values for empty and null values got the error, "Default Value exceeds the length allowed for Target Field." With this fix, users can create Default rules when adding empty or null as the value for the field, regardless of the data type length. [DSP-9495]
    • An issue occurred when adding System Type joins that caused Target Sources with over 500,000 records to take over a minute to save. With this fix, Target Sources with System Type joins save quickly. [DSP-9807]

    Target Design

    When users marked Append Utility Columns as Target Append only (as in, Source Append is unchecked), these columns would still appear in the Target Source Schema and on the auto-generated Target Source table. With this fix, Append Utility Columns marked Target Append only do not appear in the Target Source Schema or on the auto-generated Target Source table. [DSP-9587]

    Transform

    • An issue occurred with Target reports, Target Source reports and Target Data Services reports where pages with high record volumes required 10 or more seconds to load. With this fix, pages with high record volumes load quickly. [DSP-9289]
    • Page performance has been greatly improved on the Transform reports and charts accessed when a user clicks My Reports in the Navigation pane. Page load times that took 2 minutes or more now take a few seconds. [DSP-9190]

    Data Stewardship Platform (DSP®)

    • The Data Source ID for the object has been added to the CTS Packing List By Config Item page. [DSP-10306]
    • An issue occurred in Excel Integration where the AddedBy, AddedOn, and AddedVia fields were being updated when an Excel import changed an existing row. With this fix, these columns are populated when the Excel import creates rows, not when it updates rows. [DSP-9380]

    Collect

    • When users would create a Target registered with a Data Services repository against the Target, then add a Target Source with a connection type of SAPAPPSERVER and add a Table to the Target Source choosing the "Manual Data Services" package type, they would receive an error when they clicked Refresh for the Table. With this fix, in the same situation, users can refresh the selected Table/DS job without errors. [DSP-9030]
    • The Synchronous setting at the package level was only being applied for the SAP Data Services package type, and it was not being applied in the SAP Data Services using RFC or Manual SAP Data Services package types. With this fix, the Collect / DS integration now uses the Synchronous setting for all Data Services package types including: SAP Data Services, SAP Data Services using RFC and Manual SAP Data Services. [DSP-9658]

    Common

    An issue occurred when users added a multitude of data sources to the DSP causing processing times to be adversely affected. The cause of the issue was the SourceTrack - Auto Activate DataSource service page running every 15 minutes. This would duplicate jobs that did not finish running within 15 minutes and overload the system. With this fix, this stored procedure runs every 15 minutes, as before, but now checks to see if the previous execution is still running. If it is, no action is performed and the service page will check again at its next scheduled execution. [DSP-6893]

    dspCompose™

    Certain validations in dspCompose took over three hours to run. The issue has been corrected by an updated stored procedure, and the validations now run in a few seconds. [DSP-9543]

    What's New in Syniti Solutions 6.7

    This topic contains:

    WARNING: Any additions or changes users have made to CTS configuration (Admin > CTS >Configuration) may be lost when upgrading from DSP 6.6.x or earlier.

    Prior to any upgrade backups should be taken of all databases. Once the upgrade is complete, if any custom CTS configurations are found to be missing, then the backup of the CranSoft database should be restored to a new database (DO NOT restore it to the CranSoft database). The missing custom configurations can be merged into the CranSoft.dbo.CTSConfig% tables from the restored backup.

    Please contact Syniti Supportif you would like assistance with this activity.

    6.7 Enhancements

    CTS Process

    • A user can build a CTS Package by selecting that wave only in the packing list. The package contains all of the items required to successfully promote the entirety of a Migration Wave (and all its dependents) to another environment.
    • The CTS Packing List Summary and the CTS Packing List by Config Item pages have been added to streamline the process of excluding items from the packing list. Refer to Review Packing List to Exclude Specific Items in the System Administration help for more information.
    • A package can contain objects from multiple data sources.
    • The DSP now uses a crawler to set up object dependencies and installation order automatically, based on the configuration on the pages accessed in Admin > CTS > Configuration.

    NOTE: CTS configurations for delivered WebApps must not be updated. If CTS’ing a custom WebApp, the baseline configuration must be set on these pages. Refer to Set a Baseline Configuration for Shippable Items in Custom WebApps.

    dspMigrate™

    Map

    • Value Mapping values can now be entered outside of the DSP® and imported into Map. The Value Mapping (Legacy to Target) page now has Excel Integration and Bulk Execution enabled by default. This allows a user to download a template spreadsheet for data entry completion outside of the DSP®. The value mapping values can then be imported into Map from the spreadsheet. Refer to Perform Value Mapping, Use Excel Integration andUse Bulk Execution for more information.

    SQL AutoGen

    • It was difficult for migration developers to know whether the SQL AutoGen logs they were looking at had just been written or were historical and therefore from an execution prior to changes they had just made. Now, the Added On and Added By dates are displayed on the Horizontal View of the AutoGen SQL Log page to improve clarity.
    • In previous versions, fields with a zLegacy prefix were automatically excluded from the auto-generated CranPort package, which imports data from sdbConstruct to the dsw databases. In some instances, these fields could be required downstream and removing them would not produce a desired effect. With this release, all fields (including fields that start with zLegacy) in the dcs page table are included in the CranPort packages and are imported into both the sdb source table and the dsw source table.

    dspMonitor™

    • The Implication and Comment fields on the Vertical View of the Repository Reports page have been changed from text boxes to text areas so that users can enter more information in these fields.
    • When a user received a workflow email with a link to view the report in the DSP®, the link opened the Your Reports page, not the report itself. With this update, the report displays when a user clicks the link.

    dspConduct™

    • Roles that are set to auto-finish no longer receive notifications. Auto-finishing a role is useful when a request must pass through a role with no action required from a user assigned to the role.
    • The Business Value dashboard can now be populated with any missing metrics for all finished but unarchived requests and all missing metrics for all finished archived requests. On the Vertical View of the Business Process page, when the user clicks the Calculate Archived Request Working Hours button, the underlying tables are populated with the data.
      NOTE: You must enter the Baseline Hours and Avg. Cost Per Hour values and click Save before the Calculate Archived Request Working Hours button displays.

    • Users not belonging to the UserManager delivered WebApp Group used to be able to see all the users on the User Settings page. With this release, users in other dspConduct™ WebApps have their own My Settings page that only displays the current user's information. Users can edit all of the information on this page, but they cannot add or remove their own position on the User Position page.

    Data Stewardship Platform (DSP®)

    • When the installation license Hardware IDs did not match the currently licensed Hardware ID, it caused users to be denied access to the DSP®. With this release, users can continue to access the DSP® for 14 days while waiting to receive an updated license.
    • Many client sites required the use of an SAP Message Server when communicating with SAP via RFC. On these sites, DSP® was previously unable to extract tables or load data properly. With this release, SAP Message Server Connections in Collect, Common and Integrate are now supported.
    • Users could not easily check to see which job queue a job had run on. So, the Queue Name has been added to the Horizontal Views of the All Jobs and Jobs (Failed) pages under Admin > Resources.
    • On the CTS Items, CTS Item Keys, and CTS Packing List pages, the Description field displays the text description so that users can easily identify those items in the Packing List.
    • Previously on the WebApp Customization page, no count appeared on the Catalogs, Custom Links, or Pages icons. With this release, counts appear for the underlying elements and users can easily identify web applications where customizations have taken place.
    • Added the help topic Add Phrases to Catalogs.
    • The icons on the CTS Configure page now display counts of the number of records on the underlying pages to assist users while navigating and evaluating data.

    Collect

    In Collect, for IGUC package types, a warning message now displays if the specified table does not exist in the target database.

    Online Help

    • Added documentation for the Vertical View of the WebApps page.
    • Added documentation for the Database Types page.
    • Added documentation for CTS Configuration pages.

    6.7 Resolved Issues

    dspMigrate™

    An issue occurred when users copied an object from the Process Area : Object page, and only one target of the copied object was shown in the destination wave in Map. The rest of the targets were inserted in cMap.dbo.ttTarget without a DataSourceID, and on the source wave instead of the destination wave. With this fix, all targets belonging to the copied object appear in the new Wave, across Console, Design, Map and Transform. [DSP-9540]

    Map

    • An issue occurred when adding System Type joins that caused target sources with over 500,000 records to take over a minute to save. With this fix, target sources with System Type joins save quickly. [DSP-9807]
    • When users mapped a field as Construction, a Construct page was automatically generated with the key fields disabled by default. As a result, key fields usually required for populating data were excluded from Excel Integration download files. With this fix, key fields are no longer excluded from the Excel Template even if they are not editable. [DSP-9417]

    Target Design

    • A stored procedure used in Map that automatically generated validation views for Construct pages assumed there was a single key for the lookup table. This assumption meant that any validation view generated for a multi-key lookup table had to be manually corrected in SSMS before the associated Construct page could be used (without the user receiving a warning). With this fix, only invalid records prompt a warning message when a multi-key lookup table is associated with a Construct page. [DSP-9227]
    • An issue occurred that prevented users from saving records on the Target Lookup Table page. When attempting to add lookup tables with a multipart key, the Multi Value Field Lookup Table Value Column field was required, but the values in that list box did not display until the record was initially saved. In other words, it was not possible to save the record because it was not possible to update the field on the Horizontal View. Instead, an error message displayed and the record that was being added no longer displayed. To correct the issue, the Target Lookup Table page switches to the Vertical View when the user clicks Save. The Multi Value Field Lookup Table Value Column field can then be updated from the Vertical View, and the record can be saved. [DSP-9509]

    Transform

    • If there were line feeds in one of the fields in the results of a view, a new row was created when downloaded in Excel format. With this fix, the downloaded Excel file has one row for each record in the view result. [DSP-7311]
    • In Transform, when downloading a report to Excel, if the Report Column Delimiter field was set to Comma and Report Column Qualifier field was set to DoubleQuote in the Report Settings section of the Transform tab on the Parameters page, and the value contained a comma, the value would then be split into two columns. With this fix, if there is a comma contained in a value wrapped in double quotes, and the Report Column Delimiter is set to Comma and Report Text Delimiter is set to DoubleQuote, the comma is not used as a column delimiter. [DSP-7526]
    • An issue occurred where reports with fields that had a double quote (") character in the first column produced a MaxBufferSize data parsing error. With this fix, the reports generate without issues. [DSP-9052]
    • An issue occurred where reports with fields that had a ž character produced a MaxBufferSize data parsing error. With this fix, the reports generate without issues. [DSP-9233]

    SQL AutoGen

    • There was an issue where Data Services reports were not registered in Transform with the correct naming convention. They were created in SQL with underscores, and users had to change the registrations of these reports on the table every time they were generated to get them to process properly. With this fix, when AutoGen creates all Data Services report views in SQL, it registers those reports in Transform, and reconciles the names to the SQL view names. [DSP-9421]
    • In AutoGen, the [WaveProcessAreaID] datatype was set to NVARCHAR, which led to lengthier processing times when conducting Transform target execution. By changing the [WaveProcessAreaID] datatype to the appropriate UNIQUEIDENTIFIER (in all the st% tables), users are now able to conduct Transform target execution more efficiently. [DSP-9465]

    dspConduct™

    • The request status "Cancelled - will not be Posted" no longer has role access enabled. This change ensures that request roles for a canceled request cannot be finished or reset, and request role tasks may not be accessed. The request role and request role task data control views were enhanced to include controlling request status of "Duplicate Request." [DSP-9056]
    • On the Audit Table Column Registration page, the Include in Record Key check box has to be checked in order for the field to display on the Review Role Audit Detail page. Refer to Register Tables and Columns to be Audited or more information. [DSP-9830]
    • Fixed an issue that caused table data downloads for the Finish process to include tables for inactive tasks. Now, tables with inactive tasks are not downloaded during the Finish process. [DSP-9076]
    • The process for creating control tables for dspConduct™ Content WebApps has been updated. When building a list of scenarios > roles > tasks to update when generating control tables, the rules that build the control tables look for every task that has the same page and updates the column information and inserts data for every scenario and role that have any of those tasks. When building control views for Content WebApps, dspConduct™ checks to see if that page is used in any task that has an active variant. [DSP-7597]
    • In a scenario where multiple roles used the same task, and a user updated the columns for one role and attempted to recreate the control table on the Scenario Role Task Page page, the table would not include the newly added columns. The stored procedure to create the control table on the Scenario Role Task Page page was not passing the correct keys to its events. With this fix, when users click the Create Control Table icon in the Page toolbar on the Scenario Role Task Page page, the procedure checks the Key check boxes on the ScenarioID and RoleID column properties of the Scenario Role Task Page page and any newly added columns are added for the correct roles. [DSP-9234]

    dspMonitor™

    • On the Repository Reports page, the field "Title" was renamed to "Data Quality Rule" to match the rest of the application. [DSP-9607]
    • An issue occurred that prevented users who only belonged to the dspMonitor™ User WebApp Group from accessing dspMonitor™. Security settings were updated for the Data Quality Dashboard, and users in the User group can now access dspMonitor™. [DSP-10228]
    • When users would add a Group Report in dspMonitor™, the Reports list box was not filtering the reports to display only those reports registered to the Repository. Now, the necessary Where Clause has been added to display only the registered items, so only the reports registered to the Repository display when users click the Reports list box. [DSP-9457]

    dspCompose™

    Any dspCompose™ Archive Compare tables - rtxxxCompare - that were created prior to 6.6 have ArchiveID defined as an Identity field. In 6.6, the Compare tables do not have the ArchiveID as an Identity field. As a result, when Requests for these templates were posted, the stored procedure that moved data into rtxxxCompare table during the Posting process would error out when attempting to move data into rtxxxCompare tables.

    The stored procedure that moves data into rtxxxCompare tables has been modified to detect if the rtxxxCompare table still has ArchiveID defined as an Identity field and accommodates that table definition so data is successfully moved into the rtxxxCompare table and posting completes successfully.

    NOTE: A separate, stand-alone stored procedure webTemplate_OneTime_FixComparisonApprovalArchiveTableUpd is provided with 6.7 (but not inside the standard DSP® setup) along with instructions for the stored procedure. This stored procedure may be manually executed for individual templates to correct the schema definition of pre-6.6 Template rtxxxCompare tables.

    If the Template was created in 6.5.6, a unique nonclustered index will have been created on the ID field of the rtxxxCompare table. Either drop that unique nonclustered index and create a nonunique nonclustered index, or execute the separate stand-alone stored procedure webTemplate_OneTime_FixComparisonApprovalArchiveTableUpd to correct that issue. [DSP-9336]

    Data Stewardship Platform (DSP)®

    An issue occurred that caused the DSP® to crash when users tried to build an SSIS package after installing a new version of SQL Client Tools on their application server. With this fix, all currently supported versions of SQL Server work with their associated SQL Client Tools and SSIS packages build without issues. [DSP-9412]

    Collect

    • An issue occurred in Collect while using any RFC Connection type with an SAP Message Server where the package would not get built. With this fix, RFC type packages build with or without using a message server. [DSP-6070]
    • An issue occurred in Collect where the SSIS option was not populating in the Package Type list box for Target Source tables. With this fix, SSIS appears in the Package Type list box. [DSP-9497]
    • An issue occurred that caused an error when trying to build SSIS packages using ODBC data source types. With this fix, a dedicated ODBC connection object has been created and users can successfully build SSIS Packages with the DSP®, configured in either 32-bit or 64-bit mode. [DSP-9270]
    • In Collect documentation, the security required for a user to receive a workflow notification when a table failed to download was described incorrectly. A user must be assigned to a security role that has the Collect WebApp group WorkFlowFailureAll or WorkFlowFailureByTargetAccess assigned to receive these emails. [DSP-9717]

    Common

    • An issue occurred on the Data Source Registry page when users set up a connection to SAP Message Servers. The connection failed and produced a configuration parameters error. With this fix, users can connect to the SAP Message Server without issues. [DSP-8008]

    Integrate

    The process template connection for Integrate is now a shippable item and can be CTS'ed independently of process templates. [DSP-10240]

    6.7 Enhancement Request from Users

    In dspMonitor™, the Implication and Comment fields on the Vertical View of the Repository Reports page have been changed to Text Areas so that users can record all necessary information. [DSP-6078]

    Online Help

    On the Data Sources page in System Administration, the Server Address field has been revised to inform users to avoid using the IP address of the server as the Server Address property. For the CranSoft data source, the Server Address property must be the host name of the database instance and cannot be the IP address. Although the IP address may test successfully, if the IP address is used for the CranSoft data source, then Collect downloads do not return the Record Count and the rules registered to the Collect table will not execute. [DSP-9586]

    What's New in Syniti Solutions 6.6.4

    This release contains resolved issues.

    6.6.4 Resolved Issues

    dspCompose™

    • An issue occurred when adding the delivered function cMass.dbo.boaFormLegacyComparyHTML to the Horizontal View of a dspCompose-generated data entry or approval page in dspCompose_Data. When both parameters were NULL, the function returned '&amp;nbsp;' to an HTML Area column property, which displayed as-is, without converting to a blank space. With this fix, when both parameters are NULL, the function returns a blank space ('&nbsp;') to the HTML Area column property. [DSP-9077]
    • An issue occurred where numeric (int, bigint, decimal, float, etc.) data type columns were not displaying on the Comparison Approval page in dspCompose. With this fix, all columns, regardless of datat ype, display as expected. [DSP-9791]
    • An issue occurred on the Requests page when users tried to add a new Request without entering a name in the Template field. Because the Template field was not hard required, a user could save a Request with no Template name. The Request was created, but did not display on the Requests page when saved. With this fix, the Template field is now hard required. Requests will fail to save and produce an error when users do not populate the Template field. [DSP-9742]
    • Fixed an issue on the Request (Post) page that allowed a user to edit the Posted On and Posted By fields. [DSP-9743]

    Data Stewardship Platform (DSP)®

    • An issue occurred where the behavior for the "Support Direct Update" option allowed editing the value of a check box regardless of the boaEdit value. With this fix, the "Support Direct Update" option allows editing the value of a check box only if the Data Control View(DCV) allows editing the row. [DSP-9714]
    • An issue occurred in the framework on pages with a Data Control View that resulted in primary key columns with a value of 2 being incorrectly hidden. With this fix, the DCV no long incorrectly hides these values. [DSP-9194]

    Common

    An issue occurred when the correct table listing was changed in the ztDatabaseModelSystemTypeTable Configuration. As a result, entries for DD03T and DD04L remained in the ztDatabaseModelSystemTypeTable table after new installations. This fix removes the entries for DD03T and DD04L from the ztDatabaseModelSystemTypeTable table for both new installs and for upgrades.

    The correct list for both new installs and upgrades is:

    • DD02L
    • DD02T
    • DD03L
    • DD04T
    • DD05S
    • DD07T
    • DD08L

    [DSP-9799]

    Online Help

    Updated the description of the Connection ID field throughout dspCompose™ help with this note:

    NOTE: If a user adds a request based on this template and does not select a connection ID, the default connection assigned to the Integrate Template is used for the request. [DSP-9744]

    What's New in Syniti Solutions 6.6.3

    This topic contains resolved issues.

    6.6.3 Resolved Issues

    dspMigrate™

    Console

    • When administrators would set up a custom Security Role that only provided access to a single Wave Process Area and limited Objects within, assigning the new Security Role did not prevent users from seeing additional Process Areas and Objects. This occurred because the Wave Process Areas and Process Area : Object pages did not have the appropriate security checks applied. With this fix, the appropriate security checks have been added, and users assigned to limited custom Security Roles have access to only what the Administrator has assigned to that role. [DSP-7927]
    • An issue occurred where copying a Wave containing field groups would fail with a duplicate primary key error. With this fix, Waves with field groups can be copied without error. [DSP-9504]

    Construct

    In previous versions, when administrators granted business users access to the Construct WebApp, the user still wasn't able to access the tool. The Administrator had to add the Construct Launch and Construct Page pages to the user's security definitions. Now, these pages are provided under the Construct WebApp User Group security role by default. [DSP-6398]

    Map

    An error displayed when resetting XRef or RuleXref rules when value mapping was also configured to reset during the reset process. If the value in the Reset Value Mapping field (Console>Advanced Configuration>Parameters>Map tab) was set to Delete Value Mappings, the DSP displayed an error, even though the mapping reset was successful. With the fix, the reset process completes without error. [DSP-7419]

    Target Design

    When importing a System Type, the column SystemTypeTableID was populated with the default value “88888888-8888-8888-8888-888888888888” in the target table on import. With the fix, the SystemTypeTableID is populated with a GUID pulled from the Common tables for System Types. [DSP-9261]

    Transform

    An issue occurred on the All Reports page where Sources with multiple tables registered in Transform displayed duplicate reports for multiple Source tables. With this fix, reports on the All Reports page display only for the appropriate Source tables. [DSP-9211]

    SQL AutoGen

    An issue occurred when the data source was a {Target Rules} data source and users clicked the Create All Objects icon in AutoGen that caused a duplicate key error. With this fix, users no longer receive an error when the data source is a {Target Rules} data source and they click the Create All Objects icon in AutoGen. [DSP-9503]

    dspCompose™

    • An error occurred when creating a template in dspCompose™ from an existing Integrate template. If the Transaction Code was greater than 10 characters, an error displayed in the DSP, and the template could not be created. The column length of the column in dspCompose™ was 10, while the field length for this same field in Integrate is 50. With the fix, the length of the Transaction Code column is the same in dspCompose™ and Integrate, and the template can be created successfully. [DSP-9018]
    • An issue occurred that prevented a data role from finishing in certain situations. Two users were assigned the data role, and the request data failed a validation. User 1 clicked the Validate button on the Request (Roles) page and could view the errors to correct them. However, when User 2 clicked the Validate button, the failed validations did not display. The validation was tied to the User ID, so that only User 1 could view and correct the issues. With the fix, existing validation messages for all users are first cleared as part of the validation process. When a user clicks the Validate button, only valid failures for the request display and the role can be finished. [DSP-6681]
    • An issue occurred that prevented a request from posting in certain situations. When the user saved the request, a default connection required to post the request was not populated. To set the connections, the user had to click the Connections icon on the Request page’s Vertical View to pull in the defaults. No warning message displayed to ensure compliance with this added step. With the fix, default connections are added automatically as the request is created. The extra step is no longer required and the request can be posted. [DSP-9546]

    dspConduct™

    • An issue occurred where the boaWorkDaysForecastDateCalculation function ignored breaks in work hours and miscalculated the number of hours worked in a day. With this fix, the function recognizes breaks in work hours and correctly calculates the number of hours worked in a day. [DSP-8989]

      NOTE: The function depends on a Calendar having Work Hours Start Time and Finish Time blocks for each Work Day. If there are no Work Hours for the Calendar, the function will return ‘Jan 1 1900 12:00AM’.

    • dspConduct™ sent a duplicate email to roles in certain situations. If the SLA date had passed, and the user received the workflow email, the user would then receive the same email when the role was finished. With the fix, the duplicate email is no longer sent. [DSP-8047]

    Data Stewardship Platform (DSP)®

    • When users would navigate to the Technical Help by the Settings menu on a dynamic page in the product, like the Your Object Reports page, they would receive the following error, 'Internal Error. The website could not finish processing the current request due to an unexpected system error.' Now, when users access the Technical Help by the Settings menu on a dynamic page in the product, they do not receive that error and the Technical Help pane displays as expected. [DSP-9348]
    • An issue occurred when upgrading to 6.6. In some cases, the upgrade failed with a Duplicate Key error. With this fix, the upgrade to 6.6 runs as expected. [DSP-9185]
    • When editing five or more rows at once on a page with auditing set up, the Audit Information popup did not display the correct information. One row, or multiple rows, showed that a change was made. However, no information displayed about the nature of the change. With the fix, audit information displays correctly when multiple rows are edited at once. [DSP-9520]

    Common

    • An issue occurred on the System Types Model Tables page where an incorrect table list was supplied for the delivered SAP System Type Model that led to unnecessary table extraction. With this fix, the SAP System Type Model table contains the correct list of tables required to support the delivered views used to define the System Type Model. [DSP-9291]
    • If a user account was added in System Administration then updated in Common, the Changed On field did not update for that user’s account, which had a direct impact on the auditing process. With this fix, the Changed On field is updated for the user account every time a change is made in Common. [DSP-8981]

    Online Help

    • Clarified description of the Data Quality Rule on dspMonitor's Your Favorite Reports page. [DSP-9562]
    • Clarified description of the Data Quality Rule on dspMonitor's Your Group Reports and Your Favorite Reports pages. [DSP-9562]

    What's New in Syniti Solutions 6.6.2

    This topic contains:

    6.6.2 New Features

    Regulatory Compliance

    The DSP assists clients with regulatory and corporate compliance by:

    • Restricting access to personal data (any data that can be used to identify a person), handled through DSP security and through purging data after a retention date has passed. Purging data is configured in Common and Collect.
    • Tracking and logging user access to this data throughout the product, which is configured in System Administration.

    Settings must be configured before compliance can begin.

    • An Administrator must enable the logging feature in System Administration. By default, the DSP tracks access to all pages; however, an Administrator can control which pages are tracked. Refer to Disable and Enable Logging for Pages in System Administration help for more information.
    • At the client site, an Administrator must also set up auditing for these specific tables in the DataSource named DataGarage:
      • dgTarget
      • dgTargetSource
      • dgTargetSourceTable

    When a Data Controller updates any retention expiration date, an e-signature is required and captured in the audit records. Refer to Enable Auditing for Tables with Personal Information in the System Administration help for more information.

    • At the client site, an Administrator should also set up auditing for any tables that contain regulated data. Refer to Enable Auditing for Tables with Personal Information in System Administration help for more information.
    • A Collect Administrator must configure data protection for Targets, Sources and Tables.

    Refer to Support Regulatory Compliance and Log Events and Access to Personal Data. for more information.

    dspConduct™

    • A Director of Data Governance can now view the new Business Value Dashboard charts to evaluate the cost and time saving associated with automating business processes with dspConduct™. Refer to View Business Value Dashboard for more information.
    • dspConduct™ now allows an Administrator to set the currency label on the Parameters page that is displayed for the Average Cost Per Hour field on the Business Process page’s Vertical View. An Administrator may also set the default calendar used for working hours calculations on the new Business Value Dashboard. Refer to Set Currency Display Label and Set Calendar Used For Business Value Calculations for more information.
    • dspConduct™ now allows a Process Designer to configure business value parameters on the Business Process page’s Vertical View. A Designer can set the Baseline Hours and Average Cost Per Hour values that are used to calculate the information displayed on the new Business Value Dashboard. Refer to Configure Business Value Parameters for more information.
    • A Process Designer can now access the Business Value Dashboard from the Business Process page’s Vertical View for the specific Business Process. Refer to View Business Value Dashboard for more information.

    dspMonitor™

    The Monitor Dashboard released as beta in 6.6.1 is now live. Once dspMonitor™ is configured and reports are processed, the dashboard is displayed automatically when dspMonitor™ is accessed. You can also access the Monitor dashboard by selecting DQS Dashboard in the Navigation pane. Users will not see any data in their dashboard after initial upgrade. The update introduces a layer of tables that will only be populated on new execution of reports. Most of these are scheduled to run daily, so users will be begin to see updates either the next day, or they can manually process some reports, and groups and data will come in as they complete their execution. Refer to Use Data Quality Dashboard for more information.

    6.6.2 Enhancements

    Data Stewardship Platform (DSP)®

    An issue occurred where a user's security definitions were not deleted when the user account was deleted. It was possible that if a user with specific security definitions was deleted, and later a new user with the same user ID was added to the system, that user would inherit the deleted user's security definitions automatically. Now when a user account is deleted, even if a new user is created with the same user ID, the new user does not inherit the deleted user's security definitions automatically. [DSP-6408]

    Common

    Client fields can now be excluded when importing a System Types Model by checking the Exclude Client Fields checkboxes on the System Types Import page. Refer to Import a Model for more information.

    Automate

    Previously, the Comment, Message Success and Message Failure fields on the Contact Info tab on the Vertical View of the Interfaces page displayed as text boxes. With this release, the text boxes are now larger text areas that can display the 2000 characters that the fields can contain.

    6.6.2 Resolved Issues

    dspMigrate™

    In previous versions, users with specific security definitions may have had access to pages not included in their security definitions when navigating to the Context Select pages in Target Design, Map, Construct, and Transform. Now, the Context Select pages in Target Design, Map, Construct, and Transform have the correct Security Definitions configured. [DSP-9342]

    Console

    • An issue occurred where if a user was deleted while using a specific Wave and Process Area, that Wave and Process Area could not be deleted. With this fix, if a user is deleted while using a specific Wave and Process Area, that Wave and Process Area can be deleted. [DSP-1866]
    • In previous versions, when adding the Target System to a Wave in Console, users were given the option to Click to add a new item and also the option to Use this value when typing a value in the text box. It was possible that users would use the Use this value method, causing an error if the Target System name was not properly formatted. Now, users only have the option to add a new item by clicking the link. [DSP-5155]

    Map

    An issue occurred where the External Source ID field on the Vertical View of the Field Mappings page was hidden. With this fix, the External Source ID field is visible again. [DSP-9395]

    Target Design

    An issue occurred where the Import Fields process returned two rows displaying the same Target table for Targets added with an incorrect Target name. With this fix, the Import Fields process only returns one row for the added Targets. [DSP-6471]

    dspConduct™

    • An issue that caused expired users to display on the dspConduct Position User page and User Settings page has been corrected.[DSP-9464]
    • When Reviewers reset their Roles, the Roles dependent upon the Reviewers would get emails as if the Reviewers had finished their tasks. Now the Reviewers must complete their tasks before emails are sent. [DSP-9159]
    • An issue occurred in dspConduct when a user added a Role to a Scenario. The newly created Role would not appear on the Business Processes (Scenario Roles) page. Now, when a user creates a Role on the Scenario (Roles) page, it displays when the user clicks the Roles SLA icon for a Business Process Scenario. [DSP-9212]
    • An issue occurred in dspConduct when a user deleted a Role from a Scenario. The deleted Role would still appear on the Business Processes (Scenario Roles) page. Now, when a user deletes a Role on the Scenario (Roles) page, it does not display when the user clicks the Roles SLA icon for a Business Process Scenario. [DSP-9213]
    • In previous versions of dspConduct where a linear role flow was created, users could reject roles even when the role dependency was not complete. Now, users are not able to reject these roles. They do not display on the Request Review Task and Request Review Task Roles pages until the role dependencies have been completed. [DSP-9223]
    • An issue occurred when using the CTS process to move a dspConduct role, scenario, or business process under certain conditions. If multiple roles contained the same task, and each of these role task combinations had multiple variants, the CTS process failed. The process attempted to move variants from role-task combinations unrelated to the current role task. The default configuration for dspConduct CTS has been updated and the CTS process now moves roles to the Target as expected. [DSP-9106]

    Syniti Integration

    • An issue occurred where the Scenario Role Task Level for Review and Post Roles contained application tasks that were not relevant for the Scenario but were relevant for other Scenarios, such as application tasks for the reused Post and Review Role from another Scenario. With this fix, only the relevant application tasks are included at the Scenario Role Tasks level for the Review and Post roles. [DSP-9295]
    • An issue occurred where the Scenario Role Task level did not produce a record of the Post task; therefore, it did not show up in the Request (Request Role Task) page, and the Post event could not be initiated. With this fix, the Post Role at the Scenario Role Task level produces records for the Post task and the Post event initiates. [DSP-9294]

    • An issue occurred where the Scenario Role Task level did not produce a record of the Role task. With this fix, the Role at the Scenario Role Task level produces a record for the Role task. [DSP-9189]

    Scenario

    An issue occurred where all the tasks in the Review and Post Roles appear at the Scenario Role Task level. With this fix, the Review and Post Roles only show Application Tasks that are in the application Roles on which those Review and Post roles are directly dependent. [DSP-9215]

    Data Stewardship Platform (DSP)®

    Collect

    An issue occurred where removing users’ Collect Target access from the User Specific Security Definitions in System Administration did not remove all references to those users’ access to the Target. With this fix, removing users from a Collect Target fully removes their access to that Target. [DSP-9376]

    Common

    In version 6.6.1, when users clicked the Create Source Table icon on the Automation SQL Target Source page, the view was not being created, failing with an invalid column name '#AutoDropReport#'. Now when users click the Create Source Table icon, the view is created without error. [DSP-9512]

    Online Help

    • The title of the Collect Target Monthly Summary Chart page has been updated from "Monthly" to "Target Monthly Summary," to be consistent with the title conventions of the Weekly and Daily summary chart pages. [DSP-7270]
    • Previously, the Sync Data Sources in Common and System Administration topic described the Out of Sync icon in the OUT OF SYNC column on the Data Source Registry page as being a clickable icon that syncs the changes made in Common to System Administration. With this fix, the documentation has been updated to reflect that the Out of Sync icon displays to indicate that changes have been made to a data source that must be updated by validating or saving the record in Common. [DSP-9529]

    6.6.2 Enhancement Request From the User Base

    Online Help

    A note was added to the Excel Integration Import Data topic clarifying when duplicate primary key errors occur. [DSP-9555}

    What's New in Syniti Solutions 6.6.1

    This topic contains:

    6.6.1 New Feature

    IG Universal Connect

    IG Universal Connect uses the DSP® combined with Dell Boomi, an Integration Platform as a Service (IPaaS) solution. Boomi’s connectors allow the DSP® to extract and load data in systems that do not use a database connection, such as Workday, Salesforce or SAP SuccessFactors. The Boomi Process also has an associated atom, the default execution environment (for example, Dev, QA and Prod).

    In Boomi, a DSP® Implementer creates Processes using the IG Universal Connect Template, then registers the Processes in Common, Collect or Integrate.

    In Collect, a Boomi Process can be registered as a Target Source allowing the Process to execute and pull data into Target tables. A new package type of IG Universal Connect has been added. Refer to Extract Data using IG Universal Connect in Collect.

    In Integrate, the new Template type of IG Universal Connect allows a user to create a Process Template that uses a Boomi Process to post data. Refer to Post Data Using IG Universal Connect for more information.

    A WebApp developer can also register a Boomi Process from a custom page. Refer to execute a Boomi process from a custom page.

    Refer to IG Universal Connect for general information.

    Access to IG Universal Connect is by subscription. Contact Syniti Sales for more information.

    dspMonitor™

    A Business Data Owner or Director of Data Governance can now view the Monitor Dashboard page to evaluate the quality of data and drill down into areas of data quality concern. The Monitor Dashboard is only available in beta and must be enabled to gain access. To enable the Monitor Dashboard go to the Parameters page, and then on the Metrics Parameters tab, click Enable DQS Dashboard (Beta). Once enabled, the dashboard is accessible from the DQS Dashboard (Beta) option in the Navigation pane. To provide feedback on this beta version of the Monitor Dashboard, contact support (http://support.boaweb.com) to enter a support ticket. Known issues with Monitor Dashboard beta are performance issues in large deployments and inaccurate report counts in summary row under certain situations.

    6.6.1 Enhancements

    dspMigrate™

    Target Design

    A warning message has been added when deactivating a key field in Target Design. The KEY FIELD check box must be unchecked before the field can be deactivated.

    dspMonitor™

    • dspMonitor™ now allows a Data Quality Steward to register a Collect target to a report repository. With this improvement, a Collect target provides access to the application, table, and column a report rule evaluates. This allows a Data Quality Steward to view data quality scores at the application, table and column levels. Refer to Register Collect Targets to a Report Repository and View Your Applications for more information.

    • dspMonitor™ now allows a Data Quality Steward to set data quality scoring thresholds to determine what custom or sigma level threshold is considered Green, Yellow and Red. Refer to Register Data Quality Score Thresholds for more information.
    • dspMonitor™ now allows a Data Quality Steward to configure custom data quality scoring thresholds or to use the sigma level delivered with the product to set thresholds. Refer to Register Data Quality Score Thresholds for more information.

    • dspMonitor™ now allows a Data Quality Steward to register logic that determines the variables required to calculate a data quality score. The Data Quality Steward is able to register an Opportunity View that contains the full set of possible records that could potentially fail (an Opportunity Count) in its associated error report. Refer to Register Report Repositories in dspMonitor™ and Register Reports to a Report Repository for more information.
    • dspMonitor™ now automatically determines the Defects Per Million Opportunities (DPMO) of the Data Quality Scoring once the opportunity logic is configured for reports. Refer to Register Report Repositories in dspMonitor™ and Register Reports to a Report Repository for more information.

    • dspMonitor™ now supports summary notification workflows for items with data quality scores that are below the configured threshold. Refer to Customize User Settings for more information.
    • dspMonitor™ now supports configuration of summary threshold notifications, which can be sent at a specific time interval (Daily, monthly, weekly... etc.). Refer to Customize User Settings for more information.
    • The Data Sources Page has been renamed to Report Repositories and the Data Source ID field has been renamed to Repository throughout the application and documentation.
    • The Quality Dimension page is now accessible from dspMonitor > Administrative > Configuration > Quality Dimension.
    • Quality dimension configuration has been enhanced. The user can now prioritize, activate and deactivate quality dimensions. In addition, when upgrading to 6.6.1, the quality dimensions Conformity and Integrity are changed to Consistency and Validity, respectively. Refer to Register Quality Dimensions for more information.
    • A user can profile the target table using the profile functionality in Common. Refer to Profile a Target Table in dspMonitor™ for more information.

    Online Help

    • Added field description for Calendar ID to User Management page's Vertical View in Common.

      NOTE: The User Management page was removed in 7.1.

    • To improve clarity, a note instructing users on how to allow business users to see the results of the Duplicate Detection process was added to the topics Find Duplicates Overview and View Results in Common.
    • The Add a System Type Model topic has been updated for clarity.

    • A search filter has been added to restrict search results by component. Refer to Online Help Search Tips.
    • The following pages are no longer accessible in dspMonitor™, so they have been removed from the help:
      • Material Types
      • Customer Account Groups
      • Vendor Account Groups
      • Informal Words
      • Unit of Measure
      • Special Characters
      • Postal Code Formats
      • Inspection Types
    • Additionally, the follow topics related to those pages have been removed from the help:
      • Add Material Types
      • Create Customer Account Groups
      • Create Vendor Account Groups
      • Register Informal Words
      • Register Units of Measure
      • Register Special Characters
      • Register Postal Code Formats
      • Register Inspection Types

    Data Stewardship Platform (DSP)®

    Common

    Excel Integration has been enhanced on the User Management page to allow an Administrator to add and manage user accounts. Fields required for account maintenance were added to the Excel spreadsheet downloaded from the User Management page. Refer to Create and Manage User Accounts in Common for more information.

    NOTE: This functionality was removed in 7.1. User accounts are created in System Administration in 7.1 and later versions.

    dspCompose™

    A Template Administrator can now set the target system connection for each process template in a request or external request scenario by clicking the Connections Icon on the following pages:

    The connections set for process templates associated with a request can also be viewed by clicking the Connections icon on the Request (Post) page.

    The following pages have been added for use with this setting:

    dspConduct™

    In dspConduct™, the Configuration and Security menus have been updated.

    The Category Objects page has been removed from the Configuration menu and is accessible via:

    1. Select dspConduct > Design in the Navigation pane.
    2. Click Vertical View for a category.
    3. Click the Org Unit Types icon.
    4. Click Add.
    5. Click Click to add a new item in the OBJECT NAME list box.

    The Configuration menu structure is:

    The Security menu structure is:

    • Security (opens User Settings page. In previous versions, opened the Position page)
      • User Settings (Opens User Settings page)
      • Positions (Opens Position page)
      • Common: User Management (Opens User Management page in Common)

    6.6.1 Resolved Issues

    dspMigrate™

    Console

    An issue occurred when selecting the Report Column Qualifier setting while configuring Transform parameters in Console. The qualifier is used to delineate column data containing spaces or special characters. When the user selected a pipe (|) for the qualifier, the downloaded report data used a comma as a delimiter instead of a pipe. With the fix, the pipe character is used correctly as a delimiter in the downloaded .txt file. [DSP-7531]

    SQL AutoGen

    An error that prevented a user from rebuilding a Full Construction source table and page has been corrected. [DSP-9183]

    Transform

    • An issue occurred in Transform where the Instruction column was not formatted correctly. With this fix, the Rule Book report in Transform has been improved by removing the improperly formatted Instruction column and adding the Rule SQL and Rule Where Clause columns. In addition, the Rule Book report on the Target Source Rule Book page in Map has been improved by adding the Rule SQL and Rule Where Clause columns. [DSP-7362]
    • An issue occurred in Transform with cached reports that used the Report Order By setting. The reports were not sorted correctly. With the fix, reports sort as configured in the Report Order By field. [DSP-6498]

    • The field description for the Source Rule Table field on the Target Source Rules page has been improved with a note that informs users that the Source Rule Table field must be blank to insert or delete rules. [DSP-9439]

    dspConduct™

    • An issue caused users with expired logins to the DSP® to continue to receive workflow emails. With this fix, users with expired logins no longer receive workflow emails. [DSP-9027]
    • An issue occurred when CTS'ing dspConduct™ Positions that had users assigned to them. Users were included in the CTS Archive. Users are not moved with the CTS process, as user IDs in a Source instance may not exist in a Target instance, and security settings in a Source instance may not be properly applied in a Target instance. With the fix, a Position's users are not included in the CTS Archive, and must be manually added to Positions in the Target instance. [DSP-7587]

    dspMonitor™

    A typo in the description for the dspMonitor Service page Send Notifications WorkFlow has been corrected. [DSP-9156]

    Data Stewardship Platform (DSP)®

    • An issue occurred with the location of the Admin item in the Navigation pane. It displayed incorrectly below Reports. With the fix, the Admin item displays below the System item. [DSP-9174]
    • When the user clicked the help icon in DSP Add Ons, the product help opened, which did not contain help for DSP Add Ons. With the fix, the DSP Add Ons help displays correctly when the user clicks the help icon on any DSP Add Ons page. [DSP-9055]
    • An issue occurred in the DSP Platform where custom authentication would fail with passwords that contained uppercase letters. With this fix, custom authentication allows passwords with uppercase letters. Refer to the BOA Solutions Configuration Authentication Manual for Windows Server 2008 and 2012 for more information about authentication methods.[DSP-8166]
    • An issue occurred in System Administration when installing 6.6 where the Audit Table Exists service page failed because of invalid records in the CranSoft.dbo.Audit table. With this fix for 6.6.1, the invalid records have been removed and the service page runs as expected.[DSP-9402]

    Collect

    • An issue occurred in Collect with table refresh when the Recycle Job Max parameter was set to 0 on the Parameters – Collect page in Common. The Recycle Job Max parameter controls the number of times the download process is recycled. If the job fails, the table is recycled into the job queue at the end of the current cycle. With this fix, any working table registrations are refreshed as expected. If Recycle Job Max is set to 0, the job isn’t recycled, as expected. [DSP-9170]
    • On the Parameters - Collectpage, DBMoto Settings tab, the field name Server Address has been updated to Server Name for clarity.[DSP-9217]
    • An issue occurred in Collect where the default column delimiters for ODBCSYBASE connection types were not automatically configured in the Left Column Delimiter and Right Column Delimiter values on Source Connection Types page's Vertical View. With this fix, the correct values are defaulted on the Vertical View. [DSP-9154]

    • An issue occurred in Collect on the Tables page where an error would display when a user accessed the page's Vertical View if many (in excess of 300) sources were registered. The issue was caused by the views used to calculate the Record Count for the table. With this fix, the following updates have been made to correct the issue:

      • Inactive sources are no longer counted.

      • The Max Record Sources For Union View parameter has been added in Common to the Parameters – Collect page, General Settings tab. If the number of sources registered exceeds the threshold set by this parameter, no Record Count is calculated and the Record Count field on the Tables page’s Vertical View is 0. [DSP-9085]

    Common

    • An issue caused an error in Common on the User Management page's Vertical View when updates were saved. The calendar ID parameter was not being supplied. With this fix, the calendar ID parameter is supplied and user information can be saved. [DSP-9176]

      NOTE: The User Management page was removed with 7.1.

    • An issue occurred in Common on the System Types Model Group Tables page that allowed duplicate tables to be assigned to a Model Group. This caused the System Type Model Group import to fail. With this fix, duplicate tables have been removed from the delivered System Type Models and validation prevents users from adding the same table to a group multiple times.[DSP-9094]

    • An issue occurred in Common when importing a System Type from a System Type Model Group. Lookup and description tables associated with the tables in the Model Group were not imported. With this fix, when importing a table from a model group, all tables along with their associated descriptions and lookup tables are imported. Refer to Import a Model for more information. [DSP-7519]

    • An issue occurred in Common > Configuration > System Type Models where the Value field in the MODEL VIEW: TABLE FIELD STATIC VALUE LIST was limited to NVARCHAR(10). With this fix, the Value field is now set to, NVARCHAR(128). Refer to View Fields Required for System Type Tables for more information. [DSP-9219]
    • An issue occurred in Common where the table names were not displayed on the System Types Groups page. A GUID was displayed in place of the table name. With this fix, the System Types Groups page is not populated by the import process until the System Type Tables have been populated and a System Type Table ID exists. [DSP-9231]

    • An issue occurred in Common when importing a System Type model with a NULL language field in the description table. The description table fields were not imported. With this fix, the description table and field with a NULL value for the language column is imported. Refer to Import a Model for more information. [DSP-9257]
    • An issue occurred in Common on the System Type Models page where validation was failing for fields in views when the fields were correct. With this fix the correct view is validated and only fields that are missing or incorrect are marked as invalid. [DSP-9232]

    • An issue occurred when adding a record on the System Types Tables page in Common when a user accessed the page from the Horizontal View of the System Types page. The user could enter data and attempt to save, but the record was not added to the database. With this fix, records added on the System Types Tables page are now saved to the database as expected. [DSP-9220]
    • An issue occurred when importing a System Type from a System Type Model in Common. If the data source for the System Type Model was not DSPCommon, the import failed. With the fix, a System Type imports successfully, using the data source from the System Type Model, whether it is DSPCommon or not. [DSP-9258]

    • An issue occurred when importing a non-SAP System Type Model into a System Type. SAP was hard coded as the source connection type, preventing field data types from importing properly. A field has been added to the System Types Models page to allow the user to select a source connection type for the System Type Model. The available source connection types are configured in Collect and provide a mapping from the data type supplied in the Table Field Model View to a valid SQL Server data type. If a mapping does not exist in the connection type, DSP will directly pass the data type from the Table Field Model View into the System Type on import. [DSP-9230]

    Integrate

    In Integrate, an issue that caused slow performance while loading data with large record sets has been corrected with the addition of SQL indexes. [DSP-7532]

    Online Help

    • In the topic Keyboard Shortcuts, the Date Time picker shortcuts have been updated because they were incorrect. [DSP-8984]
    • In the topic View the Construction Page in Construct, the typo "Contract" was corrected to "Construct." [DSP-9186]
    • When the user clicked the help icon in DSP Add Ons, the product help opened, which did not contain help for DSP Add Ons. With the fix, the DSP Add Ons help displays correctly when the user clicks the help icon on any DSP Add Ons page. [DSP-9055]
    • The topic Synchronize a Template Role’s Excel Column Control Settings with the Template Role’s Assigned Platform Page has been replaced with Import a Column Added to the Role’s Assigned Page to reflect current functionality. The description of the Import Columns button on the Template (Role Excel Column Control) page has also been updated. [DSP-9290]
    • The steps for the All Objectspage have been updated to reflect the correct navigation. In the topic Append Columns to all Target or Source Tables in Target Design,"or edited" was removed from the note below as there is no Edit button on the page.
      NOTE: The zSource column is installed with the platform and cannot be deleted. [DSP-9329]

    dspCompose™

    • Any dspCompose™ Archive Compare tables - rtxxxCompare - that were created prior to 6.6 have ArchiveID defined as an Identity field. In 6.6, the Compare tables do not have the ArchiveID as an Identity field.
      • During the upgrade, these Compare tables should be modified to drop the Identity field for the existing Compare tables.
      • Templates in 6.6 and later will create rtxxxCompare tables with a foreign key from ArchiveID to rt table ArchiveID. [DSP-9331]
    • An Internal Error occurred when a posting failed for a dspCompose™ request under certain conditions. During the posting process, if no record was written into the rt table, the process still attempted to insert a record into the rt Compare table, causing the error. With the fix, the process does not attempt to insert a record into the rt Compare table, and the Internal Error no longer occurs. [DSP-9337]

    6.6.1 Enhancement Request From the User Base

    Fields have been added to dspCompose™ and Integrate pages to provide users with more details about when scheduled posts will run.

    • On the dspCompose™ Request (Roles) page, these fields have been added to the Vertical View:
      • Scheduled Post Start Time — Displays the time the schedule background post runs.
      • Integrate Posting ID — Click the link to open the Post Monitor page in Integrate for details about this posting.
    • On Integrate’s Post Monitor page, these fields have been added to the Vertical View:
      • Posting Placed In Queue — Displays the time when a user clicked the Schedule Post icon on the Request (Post) page
      • Post Scheduled To Start — Displays the post start time as set on the Request (Post) page’s Vertical View.
      • Post Scheduled By — Displays the user ID of the user who clicked the Schedule Post icon on the Request (Post) page.

    What's New in Syniti Solutions 6.6

    This topic contains:

    6.6 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.

    6.6 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 andScenario (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.

    6.6 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]

    What's New in Syniti Solutions 6.5.6

    This topic contains:

    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.

    6.5.6 New Feature

    Import IGC™ Governance Elements into dspConduct™

    NOTE: This feature has been deprecated in a later version.

    Business processes built and published in the Information Governance Cloud™ (IGC™) can be imported into dspConduct™ to create an on premise instance of these elements. On import, the category, business process, scenario, role, and task records are registered in dspConduct™. Refer to Import IGC™ Governance Elements into dspConduct™ for more information.

    After IGC™ tasks have been imported, they display on the IGC Task page, where they can be reviewed and mapped to dspConduct™ tasks. Refer to View Tasks Imported from IGC™ in dspConduct™ for more information.

    Once imported, IGC™ tasks are mapped to dspConduct™ tasks. A Process Designer can map an IGC™ task to:

    • An existing task in dspConduct™, including the delivered tasks Request Post and Request Post Workflow Notification
    • A new task based on a page that already exists in the Content WebApp
    • A new task based on a new page created in the Content WebApp

    Task mappings can be updated if needed as business processes are updated.

    NOTE: When importing a category from IGC™, if there is a category in dspConduct™ that has the same name, the IGC™ category is automatically mapped to the dspConduct™ category. If more than one dspConduct™ category has the same name in the database, the IGC™ category is mapped to the category with the earliest Added On date. All Business Processes, Scenarios and Roles coming from the IGC™ are created as new elements in the matched category. A process Designer can then map dspConduct™ tasks to the IGC™ tasks.

    6.5.6 Enhancements

    dspConduct™

    • The Business Process Visualization page has been enhanced to display more information on multi-scenario business processes in the hover view. . It displays a diagram of the current configuration of the business process including roles and tasks for the associated scenarios and any scenario and role dependencies.

    The following information is included:

    • Business Process: Name, Description, Status
    • Scenario: Type, Status, Name, Description with relevant dependencies with conditions as they relate to the Business Process
    • Roles: Type, Name Description, Dependencies as they are relevant within the scenario and existing Conditions
    • Tasks: Name, Type, ReadOnly flag setting.

       

    • The dashboard accessed by the Metrics option on the Business Process page’s Vertical View contains the following charts:
    • SLA Percent On Time by Business Process – Displays the on time percent for a Business Process.
    • Business Process Request Duration – Displays the average duration of a Business Process.
    • Active Requests for Business Process – Displays the number of active requests for a Business Process.
    • All Requests for Business Process – Displays all requests for a Business Process by status.

     

    • The dashboard accessed by the Metrics option on the Scenario page’s Vertical View contains the following charts:
    • SLA Percent On Time by Scenario – Displays the on time percent for a Scenario.
    • Scenario Request Duration – Displays the average duration of a Scenario.
    • Active Requests for Scenario – Displays the number of active requests for a Scenario.
    • All Requests for Scenario – Displays all requests for a Scenario by status.

     

    • The dashboard accessed by the Metrics option on the Role page’s Vertical View contains the following charts:
    • SLA Percent On Time by Role – Displays the on time percent for a role.
    • Role Request Duration – Displays the average duration of a role.
    • Active Requests for Role – Displays the number of active requests for a role.
    • All Requests for Role – Displays all requests for a role by status.

     

    • The Request Created-Completed Scenario Type Metrics chart displays the Scenario Types (Create, Change, Org Extend, and Business Extend) that are included in the Request Create-Completed Metrics chart.
    • The Request Count by Category, Active Request for Category and Active Request for Category Details charts have been added.
    • The Request Details diagram has been updated to include the Request ID, related requests in the scenario and their status, and whether a role is finished and its dependencies are complete.
    • The following topics have been added to the online help to assist in Content WebApp development.

    6.5.6 Resolved Issues

    dspConduct™

    • An issue that caused the dspConduct™ Schedule Post Monitor service page to fail with timeout issues has been corrected. [DGE-1118]
    • An issue occurred in the Content WebApp for dspConduct™ that did not allow a role to be completed. Validations within a scenario-role included inactive scenario-role-tasks. With the fix, validations within a scenario-role include only active scenario-role-tasks for that scenario, and the role can be completed. [DGE-1120]
    • An issue has been corrected that caused an error to display when a user clicked the link in the Post workflow notification email. [DGE-1125]
    • When auditing was enabled for specific tables and data changes were captured in the audit details table, those changes would not be contained in the Audit Details workflow for the Review Role. With the fix, the Review Role workflow contains all the audited data changes. [DGE-1151]

    dspCompose™

    • An issue occurred in dspCompose™ when archiving a request based on a template, typically a custom template, with a custom archive table. The request data was archived in the standard archive table, but was not added to the custom archive table. With the fix, request data is archived correctly, and added to both the standard and custom archive tables. [DSP-7425]
    • An issue that caused the service page Service (Archive Requests) to fail has been corrected. [DSP-7447]
    • As part of the standard archiving process in dspCompose, old request data is stored in archive tables before being purged from the request table. Although the request was being archived correctly, an issue prevented the request compare tables from being purged along with their associated request tables. With this fix, data is purged from both the request tables and the request compare tables.[DSP-7456]

    Data Stewardship Platform (DSP)®

    Collect

    • An issue occurred when building SAP Data Services packages against an Oracle ODBC Target Source. The package could be built successfully once, but subsequent attempts failed. The Oracle connection information was being deleted in Data Services after the build completed. With the fix, SAP Data Services, Oracle, and ODBC packages build successfully. [DSP-7335]
    • As part of the standard archiving process in dspCompose™, old request data is stored in archive tables before being purged from the request page. Although the request was being archived correctly, an issue prevented the request compare tables from being purged along with their associated request tables. With this fix, data is purged from both the request tables and the request compare tables.[DSP-7456]

    What's New in Syniti Solutions 6.5.3

    Version 6.5.3 contains various fixes to existing features, including:

     

    Fiori

    Display and visualize the key activities in a Data Migration given a single pane of glass view into the status of the migration by deploying the Fiori add-on into your SAP HANA Cloud Platform (HCP) account. Using the Fiori user interface, the key metrics of the migration are extracted from the DSP® and displayed using Fiori. These metrics and details can be viewed on a mobile device as well as a workstation and have complete drill-through capabilities directly into dspMigrate™.

    Map

    A user can profile a source data source on the Vertical View of the Target Sources page or an Update Row source data source on the Vertical View of the Target Sources (Update Row) page. Once the profile has run, the user can view the profile results such as record counts, unique values, or field data types.

    Target Design

    A new Visibility column has been added for both Natural and Utility fields. Setting the visibility determines whether a field is available to be mapped on the source or target pages. Refer to Set Visibility for Mapping of Target and Source Fields and Set Visibility for Appended Utility Columns for more information.

    Transform

    Transform provides measurable advantages in the Data Preparation phase of a data migration project. The tool cleans, manipulates and reports on data, and exports the data so that it can be loaded into a target ERP system using a load tool.

    Use Transform to register target rules, target remediation rules, and target reports. Transform also creates Target Source rules and Target Source reports. A user can audit updates to target data as a result of rule processing, debug rules and reports, and view dashboards that display a count of active source rules, source reports, target rules and target reports by Wave and Process Area; the number of processes running for reports broken out by report type; and the count of changes to all object types in the Wave and Process Area.

    Access to report data can be controlled at the report level by restricting access to reports, or through user filters assigned to a report.

    Refer to Transform for more information.

    dspCompose™

    A user can access the black dspCompose Requests tab on the Quick Panel to navigate among active requests for which the logged in user has access. Refer toView Your Active Requests Details for more information.

    Data Stewardship Platform (DSP)®

    Common

    Profiling

    Profiling is a quick and easy method to perform an assessment of data contained within a database. The goal of data profiling is to save hours of research effort by listing all database information in one location. It is important to note that data profiling does not replace viewing and analyzing data, but is considered a value-added activity for reporting to the client and can provide useful information at the beginning of a Data Migration project.

    The following elements are available for all profiled databases:

    • A list of all tables in the database
    • A list of all columns within each table with defined Data Type, Length and Table Order
    • A frequency distribution of values for each column
    • A minimum and maximum value for each column
    • A number of blank, null or empty values for each column
    • Indication of unused tables and fields

    Duplicate Detection

    The duplicate detection feature provides an easy method to identify and resolve duplicate data. After the user creates and register the objects (tables and views) that contain the data to be analyzed for duplication, the process finds potential duplicate data and displays it on a results page. The user can configure this results page as needed. The user reviews the results and identifies duplicate records to decide if the record is a true duplicate, if the record must be reset, or if the record is not a duplicate.

    Integrate

    • A user can configure After Post rules that run after the process template executes successfully and before the next process template begins processing (if posting with a multi-template process)After a process template that has an After Post rule registered posts successfully, the data is passed to the next dependent process template as an input parameter. Refer to Register After Post Rules to a Process Template for more information.
    • The SAP Data Services Job  template type has been added to Integrate. It uses a Data Services Job (consisting of a Data Services Repository and a job name) when posting request data to a target system. Refer to Post Data Using an SAP Data Services Job for more information.
    • A user can add a Custom template in Integrate for posting to any application. Refer to Post Data Using a Custom Template for more information.

    6.5.3 Resolved Issues

    Target Design and Map

    An issue occurred when syncing a target between Target Design and Map. After an initial sync, if the sync process was run again, the process took longer than expected to complete. Updates were made to correct the issue, and the second time a sync process runs, it now completes in an acceptable amount of time. [DSP-7309]

    Data Stewardship Platform (DSP)®

    • An issue occurred when the Validation icon was clicked and the pop-up window contained no errors. With this fix, the pop-up window displays with any and all validation errors. [DCR-579]

    What's New in Syniti Solutions 6.5.2

    NOTE: DSP® version 6.5 implements a new licensing scheme that ties the license key to a hardware ID specific to the application server on which DSP® is installed. This license key will therefore not work on other machines. In addition, hardware changes to the server, including virtual machine reconfiguration, may cause the license to be invalidated. In the event of a hardware change, server move, or other action that may require a new license to be issued, please open a Support message via SAP Solution Manager using component XX-PART-BOA to request a new license. The request for a new license should be made a minimum of 2 business days before the license is needed to allow time for review and approval.

    This topic contains:

    The following issues have been resolved in version 6.5.2.

    6.5.2 New Features

    dspMigrate™

    SQL AutoGen

    SQL AutoGen creates basic objects used by the migration process (tables, rules and reports) so that users can focus on addressing complex requirements. 

    All objects created using SQL AutoGen are written to the data source defined for the object in Console (Process Area > Objects > Vertical View > Data Source ID).

    Access SQL AutoGen by clicking the gold Automation tab in the Quick Panel.

    Refer to SQL AutoGen for more information.

    With SQL AutoGen these tasks can be performed automatically:

     

    Fiori

    Display and visualize the key activities in a Data Migration given a single pane of glass view into the status of the migration by deploying the Fiori add-on into your SAP HANA Cloud Platform (HCP) account. Using the Fiori user interface, the key metrics of the migration are extracted from the DSP® and displayed using Fiori. These metrics and details can be viewed on a mobile device as well as a workstation and have complete drill-through capabilities directly into dspMigrate™.

    Map

    A user can profile a source data source on the Vertical View of the Target Sources page or an Update Row source data source on the Vertical View of the Target Sources (Update Row) page. Once the profile has run, the user can view the profile results such as record counts, unique values, or field data types.

    Target Design

    A new Visibility column has been added for both Natural and Utility fields. Setting the visibility determines whether a field is available to be mapped on the source or target pages. Refer to Set Visibility for Mapping of Target and Source Fields and Set Visibility for Appended Utility Columns for more information.

    Transform

    Transform provides measurable advantages in the Data Preparation phase of a data migration project. The tool cleans, manipulates and reports on data, and exports the data so that it can be loaded into a target ERP system using a load tool.

    Use Transform to register target rules, target remediation rules, and target reports. Transform also creates Target Source rules and Target Source reports. A user can audit updates to target data as a result of rule processing, debug rules and reports, and view dashboards that display a count of active source rules, source reports, target rules and target reports by Wave and Process Area; the number of processes running for reports broken out by report type; and the count of changes to all object types in the Wave and Process Area.

    Access to report data can be controlled at the report level by restricting access to reports, or through user filters assigned to a report.

    Refer to Transform for more information.

    dspCompose™

    A user can access the black dspCompose Requests tab on the Quick Panel to navigate among active requests for which the logged in user has access. Refer to View Your Active Requests Details for more information.

    Data Stewardship Platform (DSP)®

    Common

    • Target system connections and the user credentials for these connections are now set in Common. Refer to Establish a Connection to a Target System for more information.
      NOTE: This feature replaces Back End Authentication that was previously established in Integrate and dspCompose™.
    • An Administrator can import a System Type from any system. The user can add a System Type using that system’s data dictionary to create a System Type Model with the correct SQL. The process imports table descriptions and field descriptions and registers check tables to fields. Refer to Import a Data Source for more information.
      NOTE: The SAP and DE System Types are included with the DSP®.
    • Profiling and duplicate detection have been added.

    Profiling

    Profiling is a quick and easy method to perform an assessment of data contained within a database. The goal of data profiling is to save hours of research effort by listing all database information in one location. It is important to note that data profiling does not replace viewing and analyzing data, but is considered a value-added activity for reporting to the client and can provide useful information at the beginning of a Data Migration project.

    The following elements are available for all profiled databases:

    • A list of all tables in the database
    • A list of all columns within each table with defined Data Type, Length and Table Order
    • A frequency distribution of values for each column
    • A minimum and maximum value for each column
    • A number of blank, null or empty values for each column
    • Indication of unused tables and fields

    Duplicate Detection

    The duplicate detection feature provides an easy method to identify and resolve duplicate data. After the user creates and register the objects (tables and views) that contain the data to be analyzed for duplication, the process finds potential duplicate data and displays it on a results page. The user can configure this results page as needed. The user reviews the results and identifies duplicate records to decide if the record is a true duplicate, if the record must be reset, or if the record is not a duplicate.

    Integrate

    • A user can configure After Post rules that run after the process template executes successfully and before the next process template begins processing (if posting with a multi-template process). After a process template that has an After Post rule registered posts successfully, the data is passed to the next dependent process template as an input parameter. Refer to Register After Post Rules to a Process Template for more information.
    • The SAP Data Services Job  template type has been added to Integrate. It uses a Data Services Job (consisting of a Data Services Repository and a job name) when posting request data to a target system. Refer to Post Data Using an SAP Data Services Job for more information.
    • A user can add a Custom template in Integrate for posting to any application. Refer to Post Data Using a Custom Template for more information.

    6.5.2 Enhancements

    dspMigrate™

    Console

    Map

    • In Value Mapping, when refreshing the target values, a warning displays if the language or client fields are entered for the lookup table but the language or client value fields are not populated for the Wave. These fields are maintained on the Waves page's Vertical View in Console.
    • A Migration Developer can designate a system other than the target system for check tables. Refer to Use Check Tables from Different Systems While Value Mapping for more information.
    • The process for establishing relationships has been updated. External sources, Add Row sources (formerly primary sources), and Update Row sources (formerly secondary sources) can now be used when creating relationships. Refer to Work with Sources for more information.
    • The Submit All icon on the Field Mappings page can be used to submit any mappings with a Mapping Status of In Progress and any mappings with a Mapping Status of Complete (if that Mapping Status was set manually by the user but had not yet been submitted).
    • On the Mapping Approval page, a user can click the Complete icon to approve the selected mapping(s) and set the Rule Status to Complete.
    • An Update Row source that is a table can now be added. Rules can be created for this Update Row source table which convert the data before it is processed by the main source rule. The table can also be used as a snapshot of data for results validation. Refer to Add Update Row Sources that are Tables for more information.
    • Mapping Status and Rule Status values and the Mapping Approval process have been updated. During the Mapping Approval process, the Mapper submits a mapping for review. When submitted, the mapping status is set to Complete. The Developer can approve the mapping, which sets the Rule Status to In Progress. The Developer can also select an option to set the Rule Status to Complete when approving a mapping.
      Mapping Status values are:
    • Pending Review – The default value indicates that a mapping has been either:
      • Synced with Target Design but work on the mapping has not begun.
      • Synced with Target Design, has been worked on, but the saved changes did not pass validations.
      • Reset by a Mapper or a Developer. Mappings can be reset on the Field Mappings page or on the Mapping Approval page.
    • Design Required – The mapping has been reviewed by a Developer and rejected on the Mapping Approval page. The Mapper must update the mapping and submit it again.
    • Complete – The mapping has been submitted when the Mapper has finished creating the mapping and clicks the Submit or Submit All icons on the Field Mappings page.

    Rule Status values are:

    • Pending Review – The default value indicates that a mapping for the rule:
      • Has not yet been submitted.
      • Has been submitted and is waiting for Developer review.
      • Has been reset by a Mapper or a Developer. Mappings can be reset in AutoGen on the Automation SQL Field Mappings page, in Map on the Field Mappings page, or on the Mapping Approval page accessible from the Quick Panel.
    • Revision Requested – The mapping for this rule has been reviewed by a Developer and rejected on the Mapping Approval page. The Mapper must update the mapping and submit it again.
    • In Progress – The mapping has been approved on the Mapping Approval page.
    • Complete – The mapping development has been completed. A user clicked the Create and Complete icon on the  Automation SQL Field Mappings page or the Create All Rules icon on the Automation page. A Developer clicked Complete on the Mapping Approval page.

    Target Design

    • The Derived from Source field has been added to the Target Fields page. It allows the user to include or exclude a field from an insert rule when building the rule in SQL AutoGen.
    • When a lookup table is registered in Target Design, it is registered as a source table with a status of Documentation and a rule priority offset of 50000 so that it is sorted last. Documentation sources are not processed but are a reference item to see all the sources of data.

    dspCompose™

    • On the Template (Role Excel Column Control) page, the Include, Exclude, and Exclude If Null options have been moved to the toolbar to allow updates to multiple records.
    • If columns have been previously imported and a new column is added to a template, when the columns are imported again, the new column is added but there are no updates to existing columns.  
    • On the Template (Post Message Tables) page, a user can identify the Integrate template ID specific to the post message tables if a dspCompose™ template is associated with a multi-template process in Integrate.

    Data Stewardship Platform (DSP)®

    Collect

    • For a Target Source, the data store created in Data Services now has the Target Source name as part of the name when using an SAP Data Services using RFC package type (for example, <DS_SAP_SOURCE1_RFC>) to allow multiple sources to download to a single DS repository.
    • A validation message has been added in Collect, on the Tables page, for Data Services or Data Service using RFC package types to let the user know if a data services repository is not assigned on the Targets page’s Vertical View.
    • The Data Services using RFC package type can only be used by a Target Source with a connection type of SAPAPPSERVER. The Manual Data Services package type is now available for Data Services connections.
    • On the Tables page’s Vertical View Advanced Settings tab, a user can now edit the package name for a Manual Data Services package or accept the default name for the package.
    • When a table is added to a Target Source with SAPAPPSERVER as a source type, the package type now defaults to SAP Data Services using RFC regardless of the package type set in Common on the Parameters – Collect page > Package Info tab.
    • A Do Not Delete check box has been added in Collect on the Target Sources page's Vertical View so that a user can choose whether or not data is automatically deleted from the target table when the target data is built and refreshed. This option has been added to support change data capture with Data Services.
    • In Collect, <source> has been added to the name of SAP RFC connections to allow multiple connections to SAP in a single Data Services Repository.

    Excel Integration

    • A user can now update data in the DSP® from an Excel spreadsheet created by the user (based on the current DSP® page) or from a spreadsheet previously downloaded from the DSP®. Refer to Import Data for more information.
    • The default values from the page are now applied for records inserted via Excel Integration. Refer to Import Data for more information.

    Integrate

    In Integrate, the Delay Between Records field has been added to the Process page's Vertical View. It allows the user to set the amount of time, in milliseconds, that passes after processing of one record is complete and processing of the next record can begin.

    Online Help

    A glossary has been added.

    6.5.2 Resolved Issues

    dspConduct™

    • An issue occurred when a user created a request role validation that used the SPRAS field in SAP to filter the validation report by language. The SPRAS field was aliased as the boaSAPLanguage field, which is a reserved field that should not display to the user. boaSAPLanguage did display on the validation report. With the fix, this reserved column no longer displays. [DGE-989]
    • An issue occurred with the Active in Scenario Role setting for a task. When the setting was disabled for a Review or Post type task, requests based on the scenario still included the task. With the fix, only tasks marked as Active in Scenario Role are included in requests. [DGE-992]
    • An issue occurred when a page created in a Content WebApp used multiple tasks within the same role. When a user navigated to the Content WebApp page from the Request Role Task page, the control views underlying the Content WebApp page did not filter as expected and data did not display correctly. The Task ID had not been used as a filter when accessing the Content WebApp page from the Request Role Task page. The Task ID has been added as a filter, and when the user clicks the TASK ID button to access the Content WebApp page, the page data now displays correctly. [DGE-1007)
    • An issue occurred when:
      1. A scenario with dependent roles was configured such that when an Application role (e.g., Role A) was finished, the dependent Application role (e.g., Role B) was also finished.
      2. A request based on that scenario was processed by the Application role (Role A) and the user clicked Finish.
      3. A validation error displayed for the Application role (Role A) and the user corrected the error.
      3. The user clicked Finish again for the Application role (Role A).
      The workflow did not process correctly and the dependent role (Role B) was not finished. With the fix, in this scenario, the dependent role is finished when the user clicks Finish for the Application role after correcting an error. [DGE-1003]
    • An issue occurred regarding the content of workflow emails sent to the Review role. If a user updated multiple records in a table, the changes to only one record displayed in the workflow email. With the fix, all changes associated with the request display in the email sent to the Review role after the Application role is finished. [DGE-991]
    • An issue occurred during audit data collection for a specific page layout. If a task was performed on a Header/Detail page (e.g., pages A and B), and the detail page (e.g., page B) is also a Header/Detail page, changes to requests entered on page B were not tracked. The Review role could not see the list of changes while reviewing the request, as no audit data was collected. With the fix, audit data is collected for child pages that have a Header/Detail layout. [DGE-1004]
    • An issue occurred when viewing the Review Role Audit Details page. Columns that were marked to display on this page (i.e., the INCLUDE IN RECORD KEY check box was enabled for the columns on the Audit Table Column Registration page) did not display data on the Review Role Audit Details page. With the fix, the data for these columns displays and the Review role can now view the changes to the request. [DGE-1006]

    Data Stewardship Platform (DSP)®

    • The LinkTag feature allows the page Designer to link to another page and pass an identifying string (stored in the Link Tag field) in order for that page to conditionally choose a Page Control View (PCV) by name. For example, webMyTable#LinkTag#Pcv can become webMyTable#LinkTag1#Pcv or webMyTable#LinkTag2#Pcv. An issue occurred when the wrong PCV was used and the identifying string (the value of the Link Tag) was not maintained throughout the usage of the page. With this fix, the value of the LinkTag is always maintained and the correct PCV view is used. [DCR-595]
    • An issue occurred when the Validation icon was clicked and the pop-up window contained no errors. With this fix, the pop-up window displays with any and all validation errors. [DCR-579]

    Collect

    Fixed an issue in Collect which affected Oracle replications in DBMoto®. [DSP-6741]

    Common

    An issue occurred where the import event on the System Type Import page did not check for whether or not a check table entry already existed for a field. It continued to add them resulting in duplicate entries. With this fix, there are no duplicate check table entries. [DSP-7056]

    System Administration

    The issue of an exception being thrown during an Excel file upload when the drill down criteria contained a column which did not exist on the underlying table for the page has been fixed. [DCR-576]

    Transform

    • When Generate Documentation was enabled, an error occurred when the object, target, or Target Source table name was more than 50 characters long. With this fix, the object, target and Target Source table names are allowed to be up to 128 characters. [DSP-7128]
    • An issue occurred where the segmented reports displayed the total record count for the report as if it was not segmented. With this fix, each of the segmented reports displays the record count for the individual report. [DSP-6035]
    • An error occurred when special characters were used in segmented reports. The report would not save, validate or run successfully. With this fix, the report runs successfully. [DSP-6505]
    • An error occurred when attempting to execute the Source Rule in Transform due to the EscapeObjectName function used by the framework. With this fix, the Source Rule executes without error. [DSP-6523]

    6.5.2 Enhancement Requests from theUser Base

    Data Stewardship Platform (DSP®)

    What's New in Syniti Solutions 6.5.1

    This topic contains:

    6.5.1 Enhancements

    dspMigrate™

    Target Design

    When a lookup table is registered in Target Design, it is registered as a source table with a status of Documentation and a rule priority offset of 50000 so that it is sorted last. Documentation sources are not processed but are a reference item to see all the sources of data.

    Map

    An Update Row source that is a table can now be added. Rules can be created for this Update Row source table which convert the data before it is processed by the main source rule. The table can also be used as a snapshot of data for results validation. Refer to Add Update Row Sources that are Tables for more information.

    6.5.1 Resolved Issues

    dspMigrate™

    Transform

    • An issue occurred where the segmented reports displayed the total record count for the report as if it was not segmented. With this fix, each of the segmented reports displays the record count for the individual report. [DSP-6035]

    • An error occurred when special characters were used in segmented reports. The report would not save, validate or run successfully. With this fix, the report runs successfully. [DSP-6505]

    • An error occurred when attempting to execute the Source Rule in Transform due to the EscapeObjectName function used by the framework. With this fix, the Source Rule executes without error. [DSP-6523]

    Data Stewardship Platform (DSP)®

    Collect

    Fixed an issue in Collect which affected Oracle replications in DBMoto®. [DSP-6741]

    System Administration

    The issue of an exception being thrown during an Excel file upload when the drill down criteria contained a column which did not exist on the underlying table for the page has been fixed. [DCR-576]

    What's New in Syniti Solutions 6.5

    This topic contains:

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

    6.5 New Features

    dspConduct™

    dspConduct™ provides a full end-to-end solution for on premise Master Data Management and data stewardship within the DSP®.

    dspConduct™ provides the ability to design, execute, and monitor business processes within an organization as they relate to the creation and maintenance of data within the enterprise architecture of an organization.  A Designer creates the governance elements hierarchy, where tasks, roles, scenarios, business processes and their dependencies are defined.

    dspConduct™ enables users to manage the creation of master data. Master data is collected, validated, reviewed, approved and posted through a request process that dspConduct™ provides.  A request is comprised of tasks, roles, and scenarios within a business processes. The processes are grouped by category (e.g., Material, Customer, Vendor). Users of dspConduct™ can create their own custom applications and request pages for any object necessary. The Content WebApp is registered at the category level within dspConduct™.

    • A task is a Content WebApp page designed to collect and validate information required to support the business process. Not all pages are tasks as some pages can be navigated to as child pages from the main task page header. Tasks and pages can be enabled to use Microsoft Excel Interoperability so that they can create or update data for the tasks within Excel. Refer to Excel Integration for more information.
    • A role is a collection of tasks and a unit of security where an individual or groups of individuals perform their duties during a step or role within the workflow of the business process.
    • A scenario is a collection of roles that outlines a single sub-process that can either be an entire business process on its own or just a step within that business process, containing its own dependencies.  For example, a user can create a Basic Data for a Finished Good scenario, while other scenarios within the business process can be created to extend that same material to plants or sales organizations. 
    • A business process is a compilation of scenarios that allows a series of linked scenarios to be created.
    • A category is a collection of the tasks, roles, scenarios and business process governance elements and is created to organize the elements by the category (for example, line of business, business unit or division, or data domain).

    Security setup in dspConduct™ uses positions, which are security templates defined by a Security Administrator, to which multiple users can be assigned. With positions, a Security Administrator can create a template for security once and assign multiple users to the template as needed. The position security set up is used to establish security for users in the Content WebApp.

    Content WebApps use the governance elements and security setup from dspConduct™ to manage the process of coordinating data collection, validating the data and posting information. dspConduct™ also provides the ability to ensure that only resources that have been explicitly given access can create, read, update and delete data.

    dspConduct™ supports mass change data to be posted via Integrate, a Syniticomponent used as the posting mechanism and script repository. Refer to Integrate for detailed information.

    Documents can be attached to governance elements to provide instructions and supporting documentation that communicates information to users of the governance process about how to work with certain elements. Refer to Upload and Download Element Documentation for more information.

    A dashboard is available in dspConduct™ with charts that show metrics for velocity and efficiency in roles processing. Refer to View Charts in dspConduct™  for more information.

    Use dspConduct™ to:

    AutoGen

    dspCompose™

    A user can access the black dspCompose Requests tab on the Quick Panel to navigate among active requests for which the logged in user has access. Refer to View Your Active Requests Details for more information.

    Integrate

    • A user can configure After Post rules that run after the process template executes successfully and before the next process template begins processing (if posting with a multi-template process). After a process template that has an After Post rule registered posts successfully, the data is passed to the next dependent process template as an input parameter. Refer to Register After Post Rules to a Process Template for more information.
    • The SAP Data Services Job  template type has been added to Integrate. It uses a Data Services Job (consisting of a Data Services Repository and a job name) when posting request data to a target system. Refer to Post Data Using an SAP Data Services Job for more information.
    • A user can add a Custom template in Integrate for posting to any application. Refer to Post Data Using a Custom Template for more information.

    Map

    A user can profile a source data source on the Vertical View of the Target Sources page or an Update Row source data source on the Vertical View of the Target Sources (Update Row) page. Once the profile has run, the user can view the profile results such as record counts, unique values, or field data types.

    Common

    • Target system connections and the user credentials for these connections are now set in Common. Refer to Establish a Connection to a Target System for more information.
      NOTE: This feature replaces Back End Authentication that was previously established in Integrate and dspCompose™.
    • An Administrator can import a System Type from any system. The user can add a System Type using that system’s data dictionary to create a System Type Model with the correct SQL. The process imports table descriptions, field descriptions and registers check tables to fields. Refer to Import a Data Source for more information.
      NOTE: The SAP and DE System Types are included with the DSP®.

    Target Design

    A new Visibility column has been added for both Natural and Utility fields. Setting the visibility determines whether a field is available to be mapped on the source or target pages. Refer to Set Visibility for Mapping of Target and Source Fields and Set Visibility for Appended Utility Columns for more information.

    6.5 Enhancements

    AutoGen

    Collect

    • For a Target Source, the data store created in Data Services now has the Target Source name as part of the name when using an SAP Data Services using RFC package type (for example, <DS_SAP_SOURCE1_RFC>) to allow multiple sources to download to a single DS repository.
    • A validation message has been added in Collect, on the Tables page, for Data Services or Data Service using RFC package types to let the user know if a data services repository is not assigned on the Targets page’s vertical view.
    • In Collect, the Data Services using RFC package type can only be used by a Target Source with a connection type of SAPAPPSERVER. The Manual Data Services package type is now available for Data Services connections.
    • In Collect, on the Tables page’s Vertical View Advanced Settings tab, a user can now edit the package name for a Manual Data Services package or accept the default name for the package.
    • In Collect, when a table is added to a Target Source with SAPAPPSERVER as a source type, the package type now defaults to SAP Data Services using RFC regardless of the package type set in Common on the Parameters – Collect page > Package Info tab.
    • A Do Not Delete check box has been added in Collect on the Target Sources page's Vertical View so that a user can choose whether or not data is automatically deleted from the target table when the target data is built and refreshed. This option has been added to support change data capture with Data Services.
    • In Collect, <source> has been added to the name of for SAP RFC connections, to allow multiple connections to SAP in a single Data Services Repository.

    Common

    Profiling and duplicate detection are available again after being removed in a previous version.

    Console

    dspCompose™

    • On the Template (Role Excel Column Control) page, the Include, Exclude, and Exclude If Null options have been moved to the toolbar to allow updates to multiple records.
    • If columns have been previously imported and a new column is added to a template, when the columns are imported again, the new column is added but there are no updates to existing columns.  
    • On the Template (Post Message Tables) page, a user can identify the Integrate template ID specific to the post message tables if a dspCompose™ template is associated with a multi-template process in Integrate.

    Excel Integration

    • A user can now update data in the DSP® from an Excel spreadsheet created by the user (based on the current DSP® page) or from a spreadsheet previously downloaded from the DSP®. Refer to Import Data for more information.
    • The default values from the page are now applied for records inserted via Excel Integration. Refer to Import Data for more information.

    Integrate

    In Integrate, the Delay Between Records field has been added to the Process page's Vertical View. It allows the user to set the amount of time, in milliseconds, that passes after processing of one record is complete and processing of the next record can begin.

    Target Design

    The Derived from Source field has been added to the Target Fieldspage. It allows the user to include or exclude a field from an insert rule when building the rule in SQL AutoGen.

    6.5 Resolved Issues

    AutoGen

    • An issue occurred after reports were created in AutoGen. If any values were changed on the Target Lookup Table page in Target Design and the reports were rebuilt, the lookup table changes weren’t reflected in the reports. A target table join was not being updated. With the fix, the join is updated when reports are rebuilt, and changes to lookup tables display on reports.

    • In AutoGen, the Include Action In Rule Name option was available in the Parameters Automation page. The underlying functions for this option had been removed previously. With the fix, the field is no longer on the page.  
    • In Data Services AutoGen, the data types FLOAT and BIGINT were causing validation errors. With the fix, the data types FLOAT and BIGINT are supported.
    • In Data Services AutoGen, the Data Services rules in Transform were not properly identifying a field mapped to default to <blank> in Map. With the fix, fields mapped to default to <blank> in Map are correctly set to blank by the Data Services rules in Transform. Refer to Default for more information about the Default action used in field mapping.

    Collect

    • Errors occurred during the Build Package process on AIX for DB2 ODBC. The ODBCDB2AIX connection type is available for Source Connection Types for the build/refresh process. With this fix, the Build Package process executes with no errors.
    • Post action rules would fail because of missing brackets around columns names. With the fix, in Common, on the Collect configuration Post Action Rule Table Column page, when a column name is added the rule is created with the column name in brackets.

    dspMonitor™

    An error occurred when workflow emails were sent for reports. By default, dspMonitor™ does not send workflows to users if a report has zero records. If a report was generated that had zero records, but had previously generated with records, workflow emails were sent to users incorrectly. With the fix, workflows are not sent to users once the report has zero records.

    Integrate

    An issue occurred when posting data using the post method BOAFileCreation. If the process post was based on a template view that contained thousands of records, the file creation process could take over an hour. The method for writing files using this post method has been updated. With the fix, these same files are created in under 10 minutes.

    Map

    • An issue occurred when generating a snapshot for Wave Gate metrics. If the snapshot contained a large number of records, the daily service page that calculates metrics failed. With the fix, the service page runs with no errors and the metrics are calculated.
    • An error occurred when building reports with remediation that did not allow the reports to generate. The field length of the Specifications Section field on Transform's Target Reports page has been updated to unlimited, which corrected the issue. With the fix, remediation reports generate.

    Online Help

    • TheTarget Fields page field descriptions was updated with this note: "NOTE: If the field is Natural, the Verify Post Load check box is enabled by default when a user clicks the Activate icon on the Page toolbar."
    • References to DTS packages were removed. Supported SQL versions have been updated to 2012 and 2014.

    System Administration

    • Setting up a custom Security Role that only provides access to a single Wave-Process Area and limited objects did not prevent assigned users from seeing additional Process Areas and objects. Security checks were added to the Wave: Process Areas and  Process Area: Object to prevent users from seeing Process Areas and objects they were not assigned to.
    • An error occurred when navigating to the Security Definitions page after a record was deleted from the Security Definition Keys page because the values for the key record were orphaned in the key value table. With the fix, the key definition and value records are deleted and the Security Definitions page loads correctly.
    • In System Administration, the tasks were not visible on the Failed Jobs page's Vertical View for the General job type. The Tasks option was added to the Failed Jobs page's Vertical View. With this fix, the tasks are now visible.
    • Failures occurred at a client's site for reports due to incorrect syntax in the code when object names contain spaces or special characters. With this fix, the reports are generated with no failures.
    • Members of the Migration Developers group could not see the data source in Analyze after adding a data source in System Administration (on the Data Sources page). The DataSourceID was added to the Migration Developer Security Role which allows migration developers to see the data source when viewing the page.
    • The email address for license requests has been updated to licenserequests@boaweb.com.
    • When a validation failed for a soft required field, a warning message displayed. With the fix, validation failures for soft required fields return an error.
    • When a validation for a soft required field was created, it was saved with a nonstandard name and description that made identifying the validation difficult. With the fix, the name follows this naming convention:
      [TableName] + [ColumnName] + NN + “Val”
      The description that displays for a validation failure is clear: the target field names are translated, and instructions to remediate the issue are included.
    • When a validation for a list source was created, it was saved with a nonstandard name and description that made identifying the validation difficult. With the fix, the name follows this naming convention:
      web[PageTableName]_[ColumnName]_NotInListVal
      The description that displays for a validation failure is clear: the target field names are translated, and instructions to remediate the issue are included.
    • When a validation failed for a list source, a warning message displayed. With the fix, validation failures for list sources return an error

    Target Design

    An issue occurred that prevented a user from adding a source when the number of roles and role key values is in the thousands. After a user clicked Add, the processing icon displayed followed by a network connection error. With the fix, an Insert statement in a stored procedure was optimized and a user can add sources without receiving the error.

    Transform

    • Members of the ReportsOnly WebApp group in Transform could not access the All Business Reports – All Wave/Process Areas page. An update to the pages accessible to the WebApp group now allows members of that group to view the page.
    • A procedure in Transform had a poorly formed concatenated IN clause which caused performance issues on the Targets and Target Sources pages. The procedure has been rewritten and views optimized to alleviate the performance issues.
    • When a new report header/footer created in Console was chosen in Transform, the header/footer did not display on the report. With this fix, the new header/footer appears on the report.
    • An error occurred when a user entered a value in the Export Order By field on the Target Exports page’s Vertical View. After processing the export, when a user clicked the View Export icon on the Target Exports page, an error displayed. With the fix, an invalid ORDER BY clause was removed from the query used to view the target export from DSP®. The ORDER BY clause is placed in the Assemble package. The records in the export file sort by the ORDER BY and the error no longer displays when the user clicks the View Export icon. Note that when viewing the export from DSP®, the sort occurs by the left most column.
    • An error displayed if a user attempted to generate reports in Transform when the Report Generate Empty check box was disabled in Console on the Transform tab of the Parameters page. The Report Generate Empty setting determines whether Transform generates reports when there are no records on the report. With the fix, if the setting is disabled, only those reports that have records are generated from Transform.
    • When registering a Target Remediation rule on the Target Remediation page, rules for all targets were available for selection in the Target Report Remediation Rule View list box. With the fix, only rules for the selected target display.
    • Line feed characters from the field mapping fields in Map caused incorrect formatting in the Rulebook reports. With the fix, the line feed characters have been removed and reports are formatted correctly.
    • If a target report had sampling configured, the sample report was not generated when the target was processed. With the fix, a report with sampling configured generates the sampling report when the target is processed.
    • An error occurred when creating and executing a report that had an Order By clause. With the fix, reports can be created and executed in Transform with an Order By clause.
    • An issue occurred when a business user was assigned to a report segment, but not to the full report. When the report was executed, the business user was removed from all of the report’s segments, so could not access any report data. With the fix, the business user remains assigned to the report segment and unassigned to the full report. The user can view report data for assigned segments only.

    6.5 Enhancement Requests from the Field

    • In online help, page navigation has been added to all field description topics.
    • In online help, information has been included about how to Use Field Groups with Target Sources Other than the Default (*) Field Group.
    • In online help, a note was added to clarify using the RuleXref and Xref actions: "When mapping fields on a multiple key lookup table, concatenate the fields with a ":" separator, for example, field1:field 2. "
    • In online help, the naming convention for packages (#Database#%#Source#%) has been added. Refer to Create Packages for more information.
    • When in edit mode, if the user clicked an element on the page which resulted in a navigation, the record changes could have been lost. With the fix, the system displays a warning that the record changes can be lost and the user is required to confirm the action.
    • In System Administration, added a parameter to adjust the number of days prior to expiration the license expiration warning message is displayed.
    • In Transform, the UI has been updated so that the Target Source Rules and the Target Rules page are consistent. The Source Rule field has been removed from the Target Source Rules page's Horizontal View and the Target Rule field has been removed from the Target Rules page's Horizontal View.
    • In Transform, when registering a flat file export, the Assemble process is generated automatically and is defaulted to a tab delimited text file. The user has the option to specify alternate delimiters when registering a flat file export.
    • In Transform, when adding a target export, if a Migration Developer selected a load type of LSMW, BDC views displayed as an option in the Target Export list box on the Target Exports page. BDC views should not be used with exports of LSMW load type. A filter on the list box was updated, and BDC views no longer display in the list box when load type of LSMW is selected.

     

    What's New in Syniti Solutions 6.3.1

    This topic contains

    Bugs Fixed

    6.3.1 Bugs Fixed

    • Intermittently, an error message displayed in the platform when the system was left idle due to an unhandled exception. With the fix, the exception is handled and logged in the Windows Event View with a status of Warning. The error message no longer displays.
    • In Collect, when setting a filter on Collect’s Tables page, a user could not filter on the date and time when a refresh completed. The Completed field accepted a filter value using the time but not the date. With the fix, the Completed field allows a user to enter a date to create the filter.
    • In Collect, corrected an issue where the Duration field was sorting as text. With this fix the Duration field sorts numerically.
    • In Collect, corrected an issue where a table refresh repeated indefinitely when the table name in Collect did not match the target table name in Assemble. With this fix, an error message displays if the table name in Collect does not match the target table name in Assemble.
    • In Collect, when building a Data Services RFC SAPAPPSERVER package, the record count was not updated correctly even though the package was successfully built. With the fix, the record count is being updated.
    • In Common, when a user clicked the Trace button for a data source, the Trace page did not display. The issue was caused by a large number of records that were retained in the debug log. A service page that runs once daily was created in Common to clear out the debug logs if the logs exceed 100K records. With the fix, the Trace page displays.
    • In Common, a problem occurred during a System Type import. An import can add or delete records but must not update them. In this case, the key field indicator check box that had been unchecked was checked on import. Specifically if the key field on the System Type table was manually added and the key field did not exist in the source database, the system unchecked the key field indicator. With the fix, the key field is maintained as checked and is not updated during the import.
    • In dspMonitor, an issue occurred if a job was scheduled to run once daily. If the job ran over multiple minutes, a new job was created once a minute.  The Next Run Date calculation was updated.  With the fix, multiple jobs are no longer created for jobs scheduled to run once daily.
    • In dspMonitor, if a user created a report that uses an Order By clause, an error displayed when the user clicked the View icon on the Your Reports page to view the report. SQL views were updated and a function was added. With the fix, the report displays without the error.
    • The customer requested to run A Group in dspMonitor from Automate. A change was made to the event to allow this to happen.
    • In Map, when refreshing Lookup tables that had been added or updated in Target Design, the setting in the description fields on the Value Mapping Source Values did not always update the source value descriptions correctly. The source value description fields were blank. A Where clause was updated. With the fix, after a refresh, source value description fields display data correctly.
    • In Map, an issue occurred that allowed inactive mappings to display when a user clicked the Field Mappings icon for a lookup table on the Value Mapping page. If a lookup table was assigned to a target and synced with Map, and then the target’s design status was updated to Inactive in Target Design, the mappings for that table still displayed on the Field Mappings page. With the fix, only active target fields display.
    • In Map, The AutoMap icon on the Target Sources page in Map was disabled and Auto Mapping could not be performed under certain conditions. When a source (e.g., a set of Excel files or a table with a custom table name such as KNA1_flatfile instead of ttKNA1) was added to an SAP target in Target Design, the icon was disabled if the user selected the source on the Target Sources page. With the fix, Auto Mapping uses field names only and Auto Mapping is available for all sources.
    • In Map, a validation error displayed when a user attempted to update a field mapping that had already been mapped with a Copy action. After resetting the mapping, if a user attempted to update the mapping to a NotUsed action, and any of the fields in the WHERE clause were empty, the error displayed. A validation view was written incorrectly. With the fix, a user can reset a mapping with a Copy action and update it to an action of NotUsed and the error does not display.
    • In Map, corrected an issue where Export Mapping caused a WebApp error. With this fix, Export Mapping is a background event and does not cause an error.
    • In Map, when refreshing Lookup tables that had been added or updated in Target Design, the setting in the description fields on the Value Mapping Source Values did not always update the source value descriptions correctly. The source value description fields were blank. A Where clause was updated. With the fix, after a refresh, source value description fields display data correctly.
    • An issue occurred when SQL AutoGen generated source rules with a Copy action. The view and rule autogenerated for the source rules had an incorrect name that did not include a leading “z” for the field name. A SQL function was updated. With the fix, source rule and view names include zFieldName as expected.
    • An issue occurred when a field name (e.g., NAME2) in the Target Design table matched a field name in the source and the target field was made inactive. The source field (e.g., NAME2) was set to inactive as well. The inactive status prevented the source field from being loaded into the Transform source table for data conversion. A source field may be used in other rules so the data is required. For example, a business user may require that the values in the NAME2 source field be visible to use in a conversion rule, even though the target field with the same name is inactive. The fix allows source fields with the same name as inactive target field to load into the source table.
    • In Target Design, duplicate mapping records were created while importing the design of a target from a System Type. If the configuration in System Types did not match the Target Design configuration, then a duplicate entry was created. A new view was created that prevents the record duplication.
    • In Target Design, an issue occurred after reports were created in AutoGen. If any values were changed on the Target Lookup Table page in Target Design and the reports were rebuilt, the Lookup Table changes weren’t reflected in the reports. A target table join was not being updated. With the fix, the join is updated when reports are rebuilt, and changes to Lookup tables display on reports.
    • In AutoGen, there was a problem generating a target table based on a Target Design that had many key fields, and the target was not created. With this correction, target tables based on Target Design with many key fields are generated as expected.
    • In Transform, an issue occurred when a secondary source with the same source ID as the primary source was added to a target. Duplicate job IDs displayed on the Monitor page. The source ID column did not use the correct column in the view. With the fix, the source ID column uses the primary key column in the view, and no duplicate records display on the Monitor page.
    • In Transform, when adding a target export, if a Migration Developer selected a load type of LSMW, BDC views displayed as an option in the Target Export list box on the Target Exports page. BDC views must not be used with exports of LSMW load type. A filter on the list box was updated, and BDC views no longer display in the list box when load type of LSMW is selected.
    • In Transform, a “MaxBufferSize Exceeded” error was returned when a report was executed. The DSPCommon ReportEngine's dll were patched by a 6.2.1.patch to resolve this error and applied to this version.
    • In Transform, reports that included a comma in a data field were not displaying in Excel correctly. This only occurred when the report was downloaded from My Reports in Transform. With this fix there is now a data field delimiter other than a comma (a value that is not likely to be in the data to be output). This will allow the Excel to display the data correctly.
    • In Transform, an issue occurred when a target export used a Database export type. The export could not be properly configured, as a user could not select a database name for the export. The Export Instance field on the Vertical View of the Target Exports page was hidden. With the fix, the field is visible and can be used to set up a Database export correctly.
    • In Transform, if a user saved a target export with an export type of Local File, an Assemble package was created and registered to the export.  When the export package was changed in Assemble to use a different delimiter and in Transform the target export was modified/validated, the incorrect delimiter (tabs) was written into in the package. With the fix, the Assemble delimiter is not overwritten by Transform and  the export file is created with the desired delimiter.
    • In Transform, When processing an Export with "NONE" for Target "Export Type", the action on was not updated.
      When "Export Type" is "NONE", use "Export Name" view to determine record count and update action on date.
      With this fix , the record count and action on date are now correctly shown.
    • In Transform, an error occurred when a user entered a value in the Export Order By field on the Target Exports page’s Vertical View. After processing the export, when a user clicked the View Export icon on the Target Exports page, an error displayed. With the fix, an invalid ORDER BY clause was removed from the View Export query and the error no longer displays when a user clicks the View Export icon. The is Order By still applied to Target Export package if it is an Assemble package.
    • In Transform, when registering a Target Remediation rule on the Target Remediation page, rules for all targets were available for selection in the Target Report Remediation Rule View list box. A filter on the field was updated. With the fix, only rules for the selected target display.
    • In Transform, views were causing performance issues. With this fix, several Transform views have been optimized to improve performance.
    • In System Administration, the Role Key Values page's performance has been drastically improved.

    What's New in Syniti Solutions 6.3

    This topic contains

    6.3 New Features

    Target Design

    In Target Design, users can set dependency relationships (parent and child) for targets across all Waves and Process Areas. Users can view all relationships for a selected target as well. Refer to Set Target Dependencies for more information.

    dspCompose

    The data sources available for View Import at the Template-Role level are now limited and configured on the new View Import DataSources page. Refer to Add a Data Source that Stores Views for Import for more information.

    Added naming conventions to the Parameters page for views used to import data into a request.

    Construct

    New custom pages and existing custom pages created with Full Construction and Enrichment Construction can use Excel Integration and Bulk Execution. For Full Construction pages, these features are available after the user syncs a target, using Target Design with a source of {Full Construction} with Map. For Enrichment Construction, these features are available when a field mapping with an action of Construction is submitted on the Field Mappings page in Map.

    Transform

    Added ReportsOnly WebApp group.

    dspTrack

    In dspTrack, added the Resource Synonym page allowing users to map the resource names from an MS Project plan to the DSP® users.

    Excel Integration

    End-users of DSP® application pages that need to import data from Excel into custom DSP® pages can use Excel Integration. This feature is primarily for users of Data Construction pages and custom applications pages deployed at customer sites by technical power users.

    Bulk Execution

    Bulk Execution is the ability to run an event on a DSP® page for all records or a subset of those records via a simple, guided user experience.  

    For the initial release (6.3), it is limited to the bulk execution of the Validation event (the event that checks to see if a record is valid).

    End-users of DSP® application pages can perform Bulk Execution on custom DSP® pages created by the page Designer. The following DSP® pages are delivered with Bulk Execution enabled:

    • Tables (Collect)
    • Data Source Registry (Common)
    • Plan Task (dspTrack™)
    • Field Mappings (Map)
    • Users (System Administration)
    • Rules: Basic Rules (Target Design)
    • Target Fields (Target Design)
    • Target Data Services Rules (Transform)
    • Target Data Services Reports (Transform)
    • Target Reports (Transform)
    • Target Source Reports (Transform)
    • Target Sources (Transform)

    6.3 Enhancements

    • In Target Design, a user can add a description of a lookup table on the Target Lookup Table page's Vertical View.
    • In the online help, explained registering a data source in Common as the preferred method and described the sync process for data sources for Common and System Administration. Refer to Data Sources in Common for more information.
    • Three charts were added at the Wave level: Field Construction by Wave, Value Mapping by Wave, and Field Mapping by Wave.
    • To improve accessibility to chart data, charts across the DSP® allow users to access the data in a tabular format. When a user clicks the View Data icon to the right of a chart name, a pane opens that displays alternate text descriptions of chart data in a table.

    6.3 Bugs Fixed

    • When the SQL AutoGen process generated tables for Construction pages, if the table name contained special characters, the table name was not included in brackets and the table was not created. In addition, reports and remediation reports did not generate. With the fix, the target table, source table, and reports allow for custom tables with special characters in the table name.
    • An issue occurred when creating a source using SQL AutoGen. When a user added a source to a target in Target Design but did not initially set a System Type for the source, an error displayed when the user attempted to create the source table on the Automation SQL Target Source page. With the fix, the source table can be created in SQL AutoGen when a System Type is added to a source after the source was initially added.
    • When a mapping was imported, exported or copied, if relationships existed, they were not included with the mapping. With the fix, existing relationships are included with mappings when copied, imported, or exported.
    • In Map, an issue with changing the Action on a mapping has been fixed. If a field mapping was saved with the Copy Action, an error displayed if a user attempted to change the Action to Internal. With the fix, a user can edit a mapping and change the Action from Copy to Internal and no error displays.
    • An error displayed if a user attempted to auto-generate a table under certain conditions. In Target Design, a user updated a Key Target Field (e,g,, KUNNR)’s Date Type from NVARCHAR to DECIMAL. The user then deleted the corresponding zLegacy* record (for example,zLegacyKUNNR). After synching Map and Target Design, the user attempted to auto-generate a table and received the error. When Target Design attempted to create the zLegacy field, it did not create the data type (DECIMAL) of the zLegacy field correctly. With the fix, the data type of the zLegacy field is created correctly, and a user can auto-generate a table without receiving this error.
    • When a System Type was imported into Target Design, all targets in all Waves displayed the message "Pending Design Changes"  in the Status of Sync column on the Targets page. With the fix, when a System Type is imported for a target, only that target displays the Pending Design Changes message on the Targets page.
    • When registering a source to a target in Target Design, occasionally the request timed out and the source was not added. An insert statement in a stored procedure has been optimized and sources can now be registered to targets.
    • In dspCompose™, corrected an issue that caused external request scenario processes that existed on upgrade from dspCompose™ 6.0.3 to fail. With the fix, external request scenarios that existed before the upgrade process.
    • The download time for SSIS package types was slow, taking longer to download than other package types such as DTS and Assemble. With the fix, SSIS package types download more quickly at a rate comparable to other package types.
    • In System Administration, corrected an issue where the default page sort was on the toolbar field.  With this fix, the page is ordered by the first visible column. A down arrow beside the column header denotes the sort order.
    • In System Administration, corrected an issue where the import and export buttons on the Catalog page's Vertical View were not working.
    • An issue was fixed related to custom security roles and security access in Console. If a custom security role allowed access to a single Wave and Process Area and limited objects within that Wave and Process Area, users assigned to the custom security role did not have proper security set. These users could access additional Process Areas and objects and add targets in Target Design, though the targets did not display on the Targets page for the user. With the fix, security checks have been added to Process Areas and objects so that the configured security is enforced.
    • When exporting a target report in Transform whose rows exceed the limit for Excel exports, a delimited file is generated instead of an Excel Workbook. A hard-coded semicolon delimiter was used, so if the report data contained a semicolon, the report generated a new column for each occurrence of the semicolon in the data. With the fix, the user can change the delimiter applied to a character that is not present in the report data so that reports are formatted as expected on non-Excel exports.
    • In Transform, Generated Reconciliation/Audit/Technical Specs report creation was removing white space between words from text fields, making them difficult to read. With the fix, white space is retained to maintain readability.

    6.3 Enhancement Requests from Users

    • Across all components in the product, a record can be added to a filtered record set.
    • Added support for sorting on the boaStatus column on Collect's Targets, Target Sources, and Tables pages. The header for this column is S.
    • In Console, an Administrator user can assign a default Context for users. Refer to Set the Default Context For a User for more information.
    • In Console, a user can assign multiple Developer or Business User contacts to an object(s) at the same time. These object assignments cascade down to Target Design, and the contacts are assigned to every target and source in the object. Developers can review and approve mappings. Business Users are used for reporting purposes and allows users to receive published reports and Data Services reports from Transform. Refer to Add Multiple Target Contacts to an Object for more information.
    • In Target Design, the user can view all pending changes for a target on the Target Design Pending Changes page (Design > Targets > Pending Design Changes).
    • In Map, a user can view a list of all archived mappings across all Waves and Process Areas for a field (based on System Types) and import a mapping for use in the selected target or source. Refer to Copy a Mapping for more information.
    • Updated the online help for the Value Mapping (Config) page in Map. The Refresh button's description includes the note "The language to be refreshed is controlled at the Wave level (Console > Wave > Vertical View > Language field)."
    • In the online help, added a troubleshooting topic in Integrate documentation: Resolve Problem Connecting to the SAP GUI During Template Recording. The topic describes how to configure security settings in Internet Explorer to resolve the issue.  
    • In Transform, when a user processes Rules Only, the record count for the target is now updated.
    • An enhancement request from BOAUnited Customer addresses an issue with filtering on a single client when generating views from an SAP source using SQL AutoGen. When using SAP, a filter on the Client column is now included in the Where clause when generating views based on check tables that contain the Client column.
    • If a target exists in the database, a user cannot build a table using SQL AutoGen until the target is synced with Map. Refer to Build Target Tables Using SQL AutoGen for more information.
    • In Transform, when a process fails and the user clicks the Continue button on the Monitor page, the status column on the Monitor page updates to reflect the correct status ("Processing").
    • In dspMonitor™, a user can add a subset of frequently used reports to the Your Favorite Reports page. Refer to View Your Favorite Reports for more information.

    What's New in Syniti Solutions 6.2

    This topic contains

    6.2 New Features

    dspCompose™

  • dspCompose™ is a generic governance engine used with SAP Master Data Governance (MDG). It provides industry-specific content and workflows to initiate process governance scenarios for data domains not already handled by SAP MDG, such as Human Capital Management (HCM), Bill of Materials (BOMs), and routings. This strategy results in reduced development cycle time and faster achievement of master data objectives while fully leveraging SAP MDG.

  • dspCompose™ is a workflow-enabled application to govern the entry, review and approval of a proposed mass change. Users are assigned to roles, which are associated with templates. A template aligns with a single BDC or GUI script, an Integrate template, or a custom template, and can be reused for multiple requests. A request drives the workflow process to mass change a single object in SAP.

  • Refer to Requests vs. Templates for more information.

  • Highly customizable, dspCompose™ can be configured to control user access to request data and how a request is processed from request data entry through review and posting to a target system.

  • A change can be based on a database view utilizing a Where clause, an Excel spreadsheet, or manual input by the user. BDC and GUI scripts can be used to update data in a target ERP system such as SAP. Messages are returned from the target system to show which objects were successfully updated.

  • dspCompose™ supports mass change data to be posted to SAP via Integrate, a Syniti component used as the posting mechanism and script repository. Integrate contains all the commands for every BDC and GUI script used to load data into SAP. Each script represents a mass update process. Refer to Integrate for more information.

    Integrate

    Custom fields can be added to BDC Script templates. Use custom fields when conditional screen execution is required and the data for existing template fields is not adequate. Refer to Add Custom Fields to a BDC Script Template  for more information.

    Transform

    ReportsOnly WebApp group.

    6.2 Enhancements

    Integrate

    The Create BAPI Template icon has been added to the Templates page's Vertical View for use with BAPI/RFC template types. When a user clicks this button, Integrate retrieves the metadata for the template prior to validating the template to save processing time.

    6.2 Enhancement Requests from Users

    The message type setting can be configured for a Developer assigned to the target or source. When a mapping is reset or submitted for approval on the Field Mappings page in Map, a Developer can choose to receive a notification via email,