Merative ™ Social Program Management 7.0.4.4 iFix3

Release Notes

Abstract

Merative Social Program Management 7.0.4.4 iFix3 Release Notes

Content

Introduction
System Requirements
Download
Installation
Improvements, Resolved Issues and Third Party Updates
Known Issues
Notices

Introduction

Welcome to the Merative Social Program Management 7.0.4.4 iFix3 release.

This is a cumulative release which incorporates the Improvements, Resolved Issues and Third Party Updates contained in all previous 7.0.4.4 iFix releases. Details of these Improvements, Resolved Issues and Third Party Updates are included separately in the release notes for each of the previous iFix releases.

For the latest version of the release notes, see https://curam-spm-devops.github.io/wh-support-docs/spm/release-notes.

Full product documentation can be found in the documentation.

System Requirements

For information about the supported software and hardware for this release, see the Merative Social Program Management Prerequisites.

Download

See the download instructions for this release at /support/spm.

Installation

Prior to running the installer please ensure all files in your Merative Social Program Management installation are writable.

The installation steps are as follows:

Additional installation instructions can be found in the Development Environment Installation Guide.

Upgrading

If you are upgrading from a previous version, the Merative Social Program Management Upgrade Helper contains documentation and tooling to help you to upgrade your Merative Social Program Management application codebase and database to work with your new version of Merative Social Program Management. The Merative Social Program Management Upgrade Guide describes a recommended process for performing application and database upgrades. The Upgrade Helper contains tools to assist you with implementing the upgrade, including tooling to produce a schedule of required migrations for your upgrade, tooling to provide information about database schema changes and tooling to generate initial SQL scripts for applying changes to your database.

To download the appropriate version of the Merative Social Program Management Upgrade Helper, see the download instructions at /support/spm.

Improvements, Resolved Issues and Third Party Updates

Cúram Enterprise FrameworkCúram Modules

Cúram Enterprise Framework

Dynamic Evidence
Technical Services
Integrated Case Management

Dynamic Evidence

PO05235, PO06727, WorkItem:265928 - Problem loading dynamic evidence pages during a restart of a Social Program Management cluster

Issue Description:

Changes to the dynamic evidence definitions require a restart of a Social Program Management environment. In a cluster environment with many nodes, if a user launches a dynamic evidence page during restart and hits a node that hasn't initialised correctly, they will get an error saying "DynEvdDomain.xml not found" and they will then continue to get this error on all dynamic evidence pages until the node affected is restarted. Other users utilizing other nodes in the cluster that initialised correctly will be not be impacted.

**User Interface Impact: **No

Prerequisite(s):

Change one dynamic evidence definition XML.
Restart the Social Program Management cluster.

Steps to Reproduce:

  1. While the system is trying to restart a user attempts to load a dynamic evidence page.
  2. Issue: If the user hits the Node that hasn't correctly initialised the dynamic evidence page will fail to load and an error is thrown - DynEvdDomain.xml not found.

Once hit this issue would affect the dynamic evidence pages as a whole for that user's session and would not recover until the affected node was restarted.

Resolution:

Now only the changed dynamic evidence domain definition needs to be reloaded to the database table which speeds up the restart process resolving the dynamic evidence page availability.

Technical:

The code responsible for loading the DynEvdDomain.xml resource into the APPRESOURCE table has been modified to first attempt to read the resource from the database. If the resource already exists, it is then compared to the generated domains. If there is no difference to the stored domains, it will not be reloaded. Only if there is a difference will the resource be reloaded onto the table. This will prevent the error caused by the resource being inaccessible during the startup of a clustered node.

Technical Services

WorkItem:266232 - An unhandled server exception is thrown when a business method (facade) is invoked before a database connection has been established

Issue Description:

An unhandled server exception is thrown when a business method (facade) is invoked before a database connection has been established in the server infrastructure. This results in no data being returned to the calling client page and may cause the application to become unusable.

User Interface Impact: No

Note:

This issue only surfaced intermittently in the SPM application. There are no consistent series of steps that can be documented to reproduce it. The following is a general pattern that can cause the issue.

Prerequisite(s):

  1. A class member variable for a code-table entry exists on a facade object.

Steps to Reproduce:

  1. Call the facade containing the code-table entry via a client page.
  2. Issue: An attempt will be made to validate the code-table value when the facade object is being created, but before it is invoked. Since no database connection has yet been established, an unhandled server exception is thrown and no data is returned to the client page.

Resolution:

The server infrastructure has been updated to ensure a database connection is established before any other server logic is executed. The server data will now be returned to the client page requesting it.

Technical:

The java class that was updated to resolve this issue is:

Integrated Case Management

PO08332, WorkItem:266165 - Merative SPM v6 notes that contain supplementary characters do not display in Merative SPM v7

Issue Description:

Notes created in Merative SPM v6 that include supplementary characters, such as an emoji character, are not visible in Merative SPM v7.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a caseworker in Merative SPM v6.
  2. Register a new Person.
  3. Click on the Client Contact tab and select Notes.
  4. Use the New page action to add a new Note that contains at least one emoji character.
  5. Click on the toggle of the newly created record to view its details. Everything should appear fine.
  6. Now perform an upgrade to Merative SPM v7.
  7. Issue: The note created above is not displayed.

Resolution:

The serializer library has been updated to fix the specific issue with the supplementary characters.

Cúram Modules

Intelligent Evidence Gathering
Evidence Broker

Intelligent Evidence Gathering

WorkItem:264275 - Universal Access Responsive Web Application: Child code-table name in a code-table hierarchy is not translated

Issue Description:

The child code-table name in a code-table hierarchy is not translated when a locale other than the default English locale is selected for an IEG page that contains a question with a code-table hierarchy.

User Interface Impact: No

Steps to Reproduce:

  1. Translate a code-table hierarchy.
  2. Update an IEG script to contain a question with that code-table hierarchy.
  3. Navigate to the IEG page that contains the question with the code-table hierarchy.
  4. Change the page locale.
  5. Issue: Observe that the child code-table name in the code-table hierarchy is not translated.

Resolution:

The child code-table name in a code-table hierarchy is now translated when a locale other than the default English locale is selected for an IEG page that contains a question with a code-table hierarchy.

Evidence Broker

PO09032, WorkItem:266241 - Activate Share Set activity of the Advanced Evidence Sharing workflow is not correctly handling timeout exceptions

Issue Description:

When a transaction timeout occurs during the Activate Share Set activity of the Advanced Evidence Sharing workflow, the exception that is thrown is not correctly propagated to the infrastructure. This can cause the workflow activity to remain stuck at the 'In Progress' state.

Steps to Reproduce:

This issue occurs when the transaction for the Advanced Evidence Sharing workflow times out during the Activate Share Set activity. A number of underlying issues could cause a timeout to occur, including but not limited to:

If a timeout happens for any reason during this particular workflow activity, then it will remain stuck in the 'In Progress' state.

Resolution:

The exception handling has been updated in the Activate Share Set logic to correctly handle transaction timeouts. These exceptions will now correctly propagate to the infrastructure and the workflow activity will be retried a number of times. If the activity continues to fail, it will be placed on the process instance error (PIE) queue.

Technical:

The Activate Share Set logic was attempting to catch any exceptions that occurred during the activation of shared evidence on a case. If evidence failed to activate, the system was updating the associated delivery plan status to 'Complete with fallback to in-edit' indicating that the evidence was shared successfully but was unable to be activated. The logic handling this was too generic, which led to it incorrectly catching timeout exceptions. The update to the logic now means that timeout transactions are properly handled and exceptions of this nature are correctly propagated to the infrastructure.

Known Issues

See the Known Issues section in the 7.0.2.0 release notes.

Notices

Before using this information and the product it supports, read the information in "Notices".

Document Information

More support for:

Merative Social Program Management

Software version:

7.0.4

Operating system(s):

Linux, Windows

Modified date:

01 December 2020