Changes in Previous Versions 6.0.1 to 6.7.1

Changes in versions 8.0 and later

Changes in previous versions 7.0 to 7.5.1

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.

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.

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.

    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 ' ' 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 (' ') 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, to receive a popup notification from within the product, or not to receive emails and notifications.

    As a result of requests from the field, the following enhancements were added to the product.  

    • In Console, the following field values have been changed:

    Process Area ID: Each value is a concatenated value that is comprised of the Process Area name and the description (<Process Area name> + ‘-‘ + <description>).

    OBJECT ID: Each value is a concatenated value that is comprised of the object name and the description (<object name> + ‘-‘ + <description>).

    • In Console, an object can be moved between Wave Process Areas and will retain all the history and metrics for the object in the Wave.
    • In Target Design, a System Type without tables cannot be imported. If a System Type without tables is imported, an error displays. A System Type table without fields can be imported. The table is added to Target Design with no fields.
    • In Map, the Cross Reference Load Sequence page was removed.
    • In Map, a Rulebook report is generated automatically for each target. Business Validators use the Rulebook reports during PreLoad validation to compare the mapping rules listed on the Rulebook report to the PreLoad report.
      The Rulebook report:

    Includes all the mapping fields for the source and target

    Includes relevancy criteria for mapping fields

    Does not display GUIDS

    NOTE: GUIDs are available in a view in the database, saved with the naming convention [Target table name] _debugRuleBookSel.

    • In Collect, the BOA RFC using Options package type was removed as an option.
    • In Collect, once a Target is built, a list of tables is published into a group Group that can then be used to publish the same list of Targets / Rules to a new Target. (e.g. dgSAP to dgQR1 to dgSR1 to dgPR1).
    • In Collect, the Fetch process creates groups by schema owner. A group is added for each schema with the naming convention of <source>_<schemaowner>.
    • In Collect, when a table entry uses a CranPort package, it is hyperlinked to the CranPort package in Assemble.
    • In Collect, when deactivating a table, the DTS Package is not removed and the Built check box on the Tables page remains checked.
    • In Collect, when viewing data in the table TEXT_SAP in the dsSAP target, the IDENT field is translated to Identifier and the TDNAME field is translated to Text Name.
    • When a package type is changed to a manual package type (DTS, SSIS, and DataServices) the package name is not changed. The package type must be from the AutoGenerate Package of the same type.
    • In Construct, the Address Server and Duplicates page were removed.
    • In dspMonitor™, when a user adds a report to a group, the METRICS check box on the Group Reports page is enabled by default. dspMonitor™ tracks metrics for the group report on the reports accessed by clicking Dashboard > Metrics in the Navigation pane.
    • In SQL Automation, to view information about the source in Map, including field mappings and the source schema, click Map Source on the Page toolbar on the Automation SQL Target Source page.
    • In Transform, when a target is made inactive, it does not display in Transform.
    • In Transform, on the Horizontal View of the Target Rules and Target Source Rules pages, the DESCRIPTION field length has been increased to 100 characters.
    • In Transform, only rules or views that follow the standard naming convention display in list boxes on the Target Rules and Target Source Rules pages. Refer to Naming Conventions for more information.
    • In Transform, the default record count for a newly registered report is NULL.
    • In Transform, on the Monitor page’s Horizontal View, GUIDs no longer display for sources or targets.
    • In Transform, if a user saves a target export with an export type of Local File, an Assemble tab-delimited package is created and registered to the export.
    • In dspTrack™, when a user clicks the Next Action button on the Work List for a task whose status is Waiting on Dependency, a message displays indicating the task(s) and dependencies that prevent the selected task from moving to the next status.
    • An object’s priority set in Console cascades down to Target Design. Once the target that belongs to the object is synced with Map, the priority is also available in Map, and displays on the Objects page (Process Area Launch > Objects). The priority is also used in Transform, but can be updated in Transform to change the order the object is processed.

    What's New in Syniti Solutions 6.1

    This topic contains

    6.1 New Features

    Collect

    SAP Data Services using RFC package type uses Remote Function Calls via Data Services to extract data from an SAP Application instance.

    Document Migration targets with Target Design

    Use Target Design to document tables, fields and sources used in the migration project. Targets can be imported from a database, System Type, or Excel file. Configure rules for target fields and lookup tables for value mapping and create field groups and metric groups to categorize and prioritize data as it is mapped.

    Refer to Target Design Overview for more information.

    System Administration

    New SQL Server Health dashboards available (Admin > Resources > SQL Server Health) that display the status of:

      • Current database connections
      • Database file sizes
      • Database memory overview

    Hover text available for columns. Current supported column types are: list box, combo box, image and button.

    The Font Size Panel allows the font size of the DSP® to be scaled between 75% and 200%. The value selected is remembered within the browser and is retained across all DSP® instances that use this feature. Access the Font Size Panel via the "A" icon on the login page or under Site Gear icon > Preferences > Font Config.

    DSP Add-Ons

    An Administrator user can use DSP Add-Ons to create custom security for delivered WebApps or custom WebApps. By creating Custom WebApp groups, users can easily customize access for pages depending on any organizational need. Refer to DSP Add-Ons for more information.

    dspTrack™

    dspTrack™ is a project tracking tool used to ensure project tasks are completed according to a project schedule and to alert managers when tasks and projects are in danger or being late or are late. The parameters for schedule status calculation can be fine tuned so that managers and resources can most effectively meet project deadlines. Dependency types for tasks ensure that tasks occur in the right order to complete the project efficiently.

    Refer to dspTrack™ Overview for more information.

    Mapping Approvals

    Ensure that a Developer can review every field mapping between source and target. No mapping is complete until it has been approved.

    Refer to Approve or Reject Mappings for more information.

    Full Construct Automation

    In cases where no legacy data is available, a user can create a source of Full Construction, which can be used as a single source or as one of multiple sources for a target.

    Refer to Full Construction for more information.

    SQL Automation

    SQL automation creates basic objects used by the migration process (tables, rules and reports)so that users can focus on addressing complex requirements.  

    Refer to SQL Automation for more information.

    View Summaries and Trends using Dashboards

    Dashboards have been added across the DSP to give users insight into summary data for field mapping, data construction, value mapping, task tracking and other factors.

    View the following topics for more information:

    Enhancements

    General

    Various changes were implemented to improve Accessibility, including:

    • Two high contrast styles have been created for visually impaired users.
    • Fields available when adding custom styles to view the contrast ratios between the style color choices based on which colors display on top of each other from within the Platform.
    • Keyboard controls added to ensure proper flow through the UI using keyboard only.

    Exception stack traces are now limited to members of the Debugger WebApp group.

    Added ability to explicitly define the language used to translate a message based on a language ID or a user's language (via a plugin).

    Collect

    Re-factor effort to improve performance and code stability.

    Record Count and Duration fields separated into two fields on the Tables page.

    Common

    Content Scope, profiles and duplicates have been removed.

    Map

    Value Mapping has been updated to streamline the workflow

    New Action of Manual Construction

    Online Help

    The product help has been updated to describe the new features and functionality and contains an Implementation Guide to help users get started with each component.

    6.1 Resolved Issues

    • In Common, Collect and System Administration, the Test Connection icon was not consistent across pages. With the fix, the Test Connection icon is the same throughout the product.
    • Fixed various issues with IE 8, 9 and 11
    • Fixed various issues with the user interface
    • The Monitor page in Common has been updated to include a CREATED ON field to be used as a filter to track when records were added.
    • In Collect, the Fetch Table process inserted multiple table entries in the System Type table, one for each schema owner in the source system. With the fix, one table entry is added to the System Type Table, no matter how many schema owners exist for the table.
    • Issues were fixed related to importing group tables in Collect.
      • If one table in the group had a rule, the rule was being applied to all tables in the group. Now, rules are applied to the table to which they are assigned.
      • Users require more flexibility over when rules should be applied when group tables are imported. For example, a rule to strip leading zeros from a field may not need to be run while importing. The Publish Rules check box has been added to the Group Import page (Targets > Sources > Import Group Tables). If enabled, rules that are assigned to the tables in the group import will run and will update data in the tables. If disabled, rules assigned to the tables will not run.
    • A user could not preview the SQL for the rule so could not know what rules are being applied to a table. The Vertical View of the Table Rule page (Targets > Sources > Tables > Rules > Vertical View) allows a user to preview the SQL. The user clicks Generate Rule Preview. The SQL display in the Rule Preview field.
    • An issue occurred that caused pool and cluster tables to be empty when tables are refreshed. If the Test Connection was successful but the SAP Test Connection failed, the download process continued and the pool and cluster tables were not populated. With the fix, If the SAP Test Connection fails, the process stops. The SAP Test Connection must be successful before the process can complete.

    6.1 Enhancement Requests fron Users

    A message has been added that displays when a user attempts to save a mapping for a field with an action of Xref or RuleXref rule or attempts to build the rule and a check table has not been assigned to the field. A user must assign a check table (also called a lookup table) to the field in Target Design.

    What's New in Syniti Solutions 6.0.3

    This topic contains

    6.0.3 New Features

    Common

    • System type table copy functionality. Refer to Copy a System Type Table.

    • ReadOnly WebApp group.

    • Rule Field field on the System Types – Table Fields page. This field marks a field as Rule Only. Refer to the Common field descriptions.

     Console

    • Auto Set Not Used for Multiple Sources parameter. This field controls whether Map updates the ACTION column to “Not Used” for primary and secondary source mappings where the action has not been set (i.e., the ACTION column is blank). Refer to Set Parameters for Map, Transform and Construct.

    • Move targets from one object to another functionality. Refer to Move a Target to Another Object.

    • ReadOnly WebApp group.

    dspCompose™

    • CTS for Org Units, Roles, Teams, and Templates.

    • ReadOnly WebApp group.

    Map

    • Auto Update Not Used icon is on the Target Sources page. This field is used to set all blank Actions to “NotUsed” for the Target Source mappings. Refer to the Target Sources field descriptions.

    • Target Field Value Field field on the Cross Reference Check Table page. This field gives the ability to select which Multi-Part key to use for Value Mapping rules. Refer to Cross Reference Check Table field descriptions.

    • New fields used in the Copy Source process:

    o   Activate Inactive Fields In Copy To Target

    o   Initialize All Mappings In Copy To Target

    o Create And Insert Mapping Groups In Copy To Target

    • Synchronize Target icon on the Targets page. This field provides the ability to immediately refresh the target and target field configuration using the new Synchronize Target. Refer to the Targets field descriptions.

    • FieldMapper, ValueMapper, ObjectRuleBuilder and ReadOnly WebApp groups.

    • Lock Field field on the TargetSchema and Target Source Schema pages. This field controls if the field will be reset when the target or Target Source is reset. Refer to the Target Schema and the Target Source Schema field descriptions.

    • Rule Field field on the Target and Target Schema pages. This field marks a field as Rule Only.  Refer to the Targets and the Target Schema field descriptions.

    Transform

    • ReadOnly WebApp group.

    • Fields added to the My Worklist process to provide additional information when reviewing new or changed field mappings:

      • Object
      • Target
      • Source

    Refer to the My Worklist field descriptions.

    6.0.3 Enhancements

    • Various validation rules added and improvements to user experience

    Collect

    • Download time reduced for BOA RFC downloads

    • Count on Fields icon on Targets page refactored to include completed mappings for each primary source

    Console

    • Records delivered on the List Value Configuration page (i.e., records where DSP Supplied is enabled) cannot be deleted. Refer to Configure List Box Values.

    • Hid the Instance field on the Parameters page because it wasn’t being utilized.

    • Expanded the length of the Language field from 1 to 25 characters to support any ERP Target system requirements. This change impacts the Waves and the Target: Source pages.

    Common

    • Updated the Profile feature to be more user friendly by disabling

      • Profile TT Tables Only when there are no tt tables in the data source
      • Activate All Tables when all tables are active
      • Inactivate All Tables when all tables are inactive

    Refer to Profile Data Sources.

    • Added ‘TEXT_SAP’ table to the ‘DG Reports SAP Tables’ scope

    • Removed DBMoto Function Setup page and all field references to “DBMoto Function”

    dspCompose™

    • GUI Script posting is restricted to background only

    • Updated template and org unit security. Refer to Add the Org Unit Security View to Template Role Validation Rules.

    dspMonitor™

    • Information Steward integration files were incorporated into the installation package for dspMonitor™. Refer to SAP Information Steward Integration.

    Integrate

    • GUI Script posting is restricted to background only

    • GUI script posting supports SAP GUI 7.30

    • SAP Transport RD2K900SN was replaced with RD2K900T0

    • SAP Transport RD2K900T0 was replaced with RD2K900U1

    Map

    st tables creation via Map automation improved to adhere to methodology change of key creation on st tables.

    Transform

    • Source Table limit has been increased from 50 characters to 128 characters

    • Default value added to the Source Database Object field on the Target Sources page. Refer to Assign Additional Target Sources.

    • SAP Readiness Report Type are now Target Readiness Report Type

    • The performance of the Targets page has been improved so that the page loads faster compared to previous versions.

    Online Help

    • Feedback link in the footer

    • Note in footer about limited access based on security

    • Screen shots to instructional steps

    • Various edits and clarification notes

    • New task descriptions :

    o   Common

    §  Copy a System Type Table

    §  Set up Security for Common

    o   Console

    §  Move a Target to Another Object

    o   dspCompose™

    §  Add the Org Unit Security View to Template Role Validation Rules

    o   dspMigrate™

    §  Grant Users Access to dspMigrate™

    o   dspMonitor™

    §  Getting Started with Running Reports

    §  Set up Data Sources for dspMonitor™

    o   Integrate

    §  Import Legacy Scripts into Integrate

    §  Set up Security for Integrate

    o   Map

    §  Copy Sources

    §  Create Custom Workflow Messages

    §  Track Changes for Field Mappings, Value Mappings, and Target and Rule Creation

    §  Update Unmapped Target Fields to NotUsed

    §  Update Unmapped Target Source Fields to NotUsed

            o   System Administration

    § Getting Started with DSP® Security for Delivered Components

    § Getting Started with DSP® Security for Custom Components

    § WebApp Groups

    §Assign Users to WebApp Groups

    o   Transform

    §  Set up Data Sources for Transform

    §  View Transform Reports

    §  View Summary Dashboard

    ·         New field descriptions:

    o   Collect

    §  Workflow Summary User Settings

    o   dspCompose™

    §  Create Custom Template

    o   System Administration

    §  Bulk Duplicate Detection

    §  Dictionaries

    §  Dictionary Words

    § Groups

    § Group Pages

    §  Stop Lists

    §  Stop List Words

    o   Transform

    §  All Reports

    §  Cutover Plan

    §  Source (Errors)

    §  Source (Info)

    §  Target (Errors)

    §  Target (Info)

    §  Target Metrics Content

    §  Target Metrics Object Development

    §  Target Metrics Report

    §  Target Rule (Audit)

    • Re-organized layout of System Administration documentation

    • Standardized Overview and Getting Started sections for every component

    • Re-wrote Construct documentation to better capture end user’s goal and purpose

    Security

    • Modified security for dspMonitor™ so only users with security can be assigned as a Group Owner.

    • Added new WebApp groups to various components. Refer to WebApp Groups.

    • Re-organized the Security documentation to be clearer and more process-driven

    User Interface Enhancements

    • Standardized Date, Application and Version fields on the Parameters page for each component

    • Fixed typos and capitalization errors in various field names

    • Added missing and updated various icons

    • Added entries to catalogs

    6.0.3 Resolved Issues

    Various bugs were fixed.

    6.0.3 Known Issues

    Common

    1.  An error occurs when adding object for duplicate detection more than once

     

    An object can be added for duplicate detection one time (Common > Analyze > Duplicates). If a user attempts to add an object for duplicate detection that was previously added, the following error displays:

     

    1.Violation of PRIMARY KEY constraint 'PK_ttDupObject'. Cannot insert duplicate key in object 'dbo.ttDupObject'. The duplicate key value is (JM497_3). The statement has been terminated

     

    Workaround: When the error message displays, close the error message, cancel the record and click OK. The unsaved changes will be lost.

     

    2. An error occurs when disabling the Key check box on the Object Columns page

    When configuring column display for the duplicate detection process on the Object Columns page, disabling the Key check box results in an error. When the user disables the Key check box, this message displays: “One column must be defined as the KEY. Check Key for another record”. When the user clicks OK to confirm the message, the following error message displays.

     

    Internal CranSoft Error

    The CranSoft website could not finish processing the current request due to an unexpected system error.

     

    Summary

    The website reports the following:

    1.Object reference not set to an instance of an object.

    Workaround: Follow these steps.

    1. Click x to close the error message.

    2. Click the Back button in the browser.

    3. Click the Columns icon on the Objects page to return to the Object Columns page.

     4. Click the Failed Status icon for the row with the error to validate the record on the Object Columns page.

     5. Click the Back button in the browser to return to the Objects page.

    6. Click the Failed Status icon for the row with the error to validate the record on the Object page. .

     Continue with the object build process.

    System Administration

    Refresh issue on CTS Items page

    This known issue occurs when adding CTS items on the CTS Items page during the CTS process. After all items have been added, the user clicks Cancel on the CTS Items page. The page remains in Add mode and duplicate rows display.

    Workaround: Refresh the CTS Items page. The page no longer displays in Add mode, and the data displays correctly.

    What's New in Syniti Solutions 6.0.2

    Quick Start Guide for dspMigrate™

    This topic provides a checklist of tasks to perform to get up and running quickly using dspMigrate™.

    dspCompose™

    dspCompose™ is a generic governance engine and is the Syniti Accelerator Pak for 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 HCM, BOMs, and routings. This results in reduced development cycle time and faster achievement of master data objectives while fully leveraging SAP MDG.

    Refer to dspCompose™ for more information.

    What's new in Syniti Solutions 6.0.1

    This section contains:

    New Features

    Collect

    • OLEHITDB2 connection type available

    • Fetch table process has new setting to activate/inactivate tables, described on the Target Sources page.

    Common  

    Options added to Activate All and Deactivate All System Type group tables on the System Types Groups Tables page. .

    CTS

    CTS between environments for all components of the DSP®, dspMigrate™ and dspMonitor™, including:

    • Transform:  Objects, Targets (Rules, Reports, Exports), Sources (Rules, Reports)

    • Map: Targets, Sources, Field Mappings, Mapping Groups

    • Console: Waves, Process Areas, Objects, Targets, Sources

    • Integrate: Templates, Processes

    • Collect: Targets, Sources, Tables, Rules, Indexes

    • Common: Automation Engine (Instruction Task Groups, Instruction Tasks, Tasks, Engine Actions), System Types, Schedules 

    • dspMonitor™: Groups, Reports, DataSources, Objects

    • Assemble: Assemble Packages

    Map

    Reset feature allows users to reset field lengths in Target or Source tables if these tables were based on System Type tables with invalid field lengths.

    Refer to Reset Target Schema and Target Source Schema Field Lengths for more information.

    Platform

    Custom links allows toolbar buttons to be added to a DSP® page via a registration within the DSP® UI exclusively without the need for database changes.

    Enhancements

    Online help

    • Changes to documentation branding

    • Updated Naming Conventions topic to reflect current Syniti methodology

    • Updates to online help to support changes in this patch release.

    Transform

    • HTML reports have been re-configured and re-implemented.  

    • Allows users to generate and download reports, including Audit documentation for objects, targets and target sources, and Reconciliation reports and Technical Specs for targets

    Refer to Generate Documentation for Objects, Targets, and Target Sources for more information.

    Integrate

    Execute icon on Copy page is disabled when Copy To fields are not populated.

    Refer to Copy a Template, Copy a Process, and Use BDC Screens in Another BDC Script Template for more information.

    Collect

    • Key fields on tables in Common System Types are marked as key fields when imported into Collect

    • DSW Param Table field on the Advanced View Builder page renamed to Transform Param Table.

    Console

    Removed the following check boxes from the Map tab on the Parameters page because they were no longer used:

    • Target Create Active Only

    • Source Create Active Only

    Resolved Issues

    Various bugs were fixed.