What's New in SAP Accelerators by Syniti 6.5.6

This topic contains:

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

Enhancements

Information Steward Accelerator (ISA)

  • ISA can now handle multiple parameter rules correctly. Previously, a multiple parameter rule could result in incorrect scoring when a rule was initially bound to multiple columns and the columns were different or in a different order in a subsequent binding.
    With this change, rule bindings are identified as unique based on a combination of Project, Rule, Table and Column(s) bound. The Rule Binding ID field on the Rule Binding List, Rule Binding Detail, and Project Distribution Rule Bindings pages now display a comma-delimited list of the table and columns to which the rule is bound. Refer to View Rule Bindings for more information.
  • In order to be displayed in the User ID list box on the Project Distribution Users page, a user's account must be set up with an email address, and, once the user’s account is set up, the list must be refreshed by navigating to the ISA > Configuration > Users page. Refer to Create User Accounts in System Administration help and Configure Workflow Options for more information. This change was made to avoid having users with no email address added to a Project Distribution. Refer to Add Users to a Project Distribution for more information.
  • To make adding many users on the Project Distribution Users page easier, the page now remains in add mode after a record is added and saved until a user clicks Cancel.
  • To improve performance when the page is loaded, the Project Distribution Users page is no longer populated with all users assigned to ISA security roles. Users must be added on the Project Distribution Users page as needed. When added to a Project Distribution, a user is active in the Distribution by default. A user can now be deleted from the Distribution or deactivated. Refer to Add Users to a Project Distribution for more information.
  • The Report Data Viewer page has been updated to include the Rule Description, and a Vertical View has been added to the page.
  • On the Project Distribution Reports page, a user can now select two options that set the type of reports that can be selected for display on the Report Data Viewer. The Actionable Reports option displays a list of reports that excludes any report with zero records. The All Reports option displays all reports regardless of record count.

NOTE: The enhancements above were made available in 6.5.3, but were not documented in the help for that version.

Resolved Issues

Information Steward Accelerator (ISA)

  • An issue occurred that caused the Selected Dimension by Distribution chart to display data for only one Distribution under certain conditions. If a Project had two Distributions, and rules in both of these Distributions were assigned to the same Quality Dimension, the chart only displayed a bar for one of the Distributions. With the fix, the chart displays a bar for each Distribution.. [DSP-7368]

NOTE: The fix above was included in 6.5.3, but was not documented in the help for that version.

  • An issue occurred that caused summary workflow emails to be sent to users who were deactivated on the Project Distribution Userspage. With the fix, summary workflow emails are not sent to deactivated users.[DSP-7114]
  • Previous versions of ISA did not support Public Rules. New functionality now supports the Public Rules concept in IS and correctly identifies the bindings of the rule in each project. The CTS process can also transfer this content successfully. [DSP-7424]
  • An issue occurred in ISA when processing rules. In this case, a single rule was bound in IS to two tables (or views) that have identical names (e.g., objects from multiple connections) in one IS project. If IS tasks generated failed data for both of the tables, rules in ISA failed to process. With the fix, a single rule can be bound to duplicate tables or views across separate connections. Rules process correctly, and the connection information displays on the Report Data Viewer and on the Rule Summary worksheet in the Excel file generated with failed rule data. [DSP-7441]
  • An issue occurred in ISA because Project Distribution names were not unique across projects. Report processing failed if:
    1. A user was assigned to multiple Distributions with the same name and
    2. Failed data existed for multiple Distributions and
    3. One ISA job processed the Distributions
    Additionally, each Excel file generated as a result of this scenario would be overwritten with the last Excel file processed because Excel file names were not unique.
    Processing is handled differently in 6.5.5, and rules now process in this scenario. Excel files are not overwritten. The naming convention for spreadsheets is now "<User>_<Distribution>_<Date>_<Time>.xlsx ". [DSP-6325]
  • Issues occurred in previous versions of ISA that caused timeout and memory consumption failures due to the volume of users, distributions, rules and bindings. With 6.5.5, the number of failures has decreased significantly. Additionally, for those errors that still occur, the user can easily view information about the error. When processing fails, the Service icon in the Site toolbar now displays yellow, and the details associated with the failure display in the error message. [DSP-7323]
  • In previous versions, ISA only processed rules successfully in which all the rule and rule binding parameters were scored. A rule and rule binding which had scoring disabled for a subset of parameters would fail to find the failed data and metrics associated to the bindings when querying the failed data database. ISA can now handle scoring changes in rule parameters, and a query based on the rule and rule binding parameters returns the correct failed data. [DSP-7437]
  • Data on the Records by Rule chart did not display correctly in certain scenarios. If multiple tasks were run in IS for the same rule but for different tables/views, the x-axis of the chart did not display all rule bindings. The x-axis labels were not unique. With the fix, x-axis labels are unique and display correctly on the Records by Rule chart. [DSP-5377]
  • In previous versions of ISA, the CTS process did not transfer all of the content between development tiers. With the fix, CTS now fully supports the content migration of ISA when adding and updating data. Refer to CTS for ISA for more information. Before performing CTS for ISA:
  • IS content must be promoted first between the IS tiers
  • The project names must be identical when promoting IS code
  • The connection names must be identical when promoting IS code
  • The versions of ISA in the source and target instances must match

[DSP-7381]

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]

Known Issue

A known issue in SAP's Information Platform Service (IPS) 4.2 SP8 (see SAP Note 2270642 for DS and SAP Note 2270630 for IS) prevents Data Services from registering a connection to a SQL Server repository.

As a workaround, add a JVM parameter “-Dcom.sun.net.ssl.enableECC=false” for the EIMAdaptiveProcessingServer to disable ECC using the Central Management Console (CMC).

To add the parameter in the CMC:

1. Click Services, or select Services in the CMC Home list box.

2. Click Service Categories > Enterprise Information Management Service in the left pane.

3. Right-click EIMAdaptiveProcessingServer in the right pane and select Stop Server from the menu.

4. Right-click EIMAdaptiveProcessingServer again and select Properties.

5. In he Command Line Parameters text box, add the parameter below after -Djava.awt.headless=true

 

-Dcom.sun.net.ssl.enableECC=false

 

NOTE: Ensure there is space before and after the parameter, so that the line reads

 

-Djava.awt.headless=true -Dcom.sun.net.ssl.enableECC=false "

 

6. Click Save and Close.

7. Start EIMAdaptiveProcessingServer.

8. Register the Microsoft SQL Server repository.

 

WARNING: Customizations made to any component of thedelivered Syniti Solutions will be overwritten in the next upgrade. To preserve customizations, make a copy of the customizations prior to applying any upgrade.

A customization is a change to the underlying source code, which differs from configuration – normal setup of the software, such as setting up workflows and defining parameters via the configuration pages.

Previous Versions

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

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