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.

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.

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.

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]

 

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 Syniti Solutions were not released. The immediately prior release to 6.5.6 was version 6.5.3.

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