Merative ™ Social Program Management 7.0.7.0 iFix5

Release Notes

Abstract

Merative Social Program Management 7.0.7.0 iFix5 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.7.0 iFix5 release.

This is a cumulative release which incorporates the Improvements, Resolved Issues and Third Party Updates contained in all previous 7.0.7 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 Product documentation and PDFs.

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/curam.

Installation

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

The installation steps are as follows:

• Extract the contents of the .zip file to a local drive location.
• Run the Merative Social Program Management installer, which can be found in the INSTALLER folder at that location.
• After installing, the appropriate build targets must be run as necessary for your installation.

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/curam.

Improvements, Resolved Issues and Third Party Updates

Third Party Updates

WorkItem:256904 - Update the versions of the Jackson JARs

The Jackson API contains multiple functions to read and build JSON using Java. It has very powerful data binding capabilities and provides a framework to serialize custom Java objects to JSON strings and deserialize JSON strings back into Java objects. The Java Development Environment (JDE) and the REST infrastructure utilize these utilities.

The versions of these JARs have now been updated from 2.9.9 and 2.9.9.3 to 2.10.2. As a result of this upgrade, the following changes have been made in the JDE and REST deliverables.

• ../CuramSDEJ/lib/third_party_version.properties - the versions of the specified Jackson JARs have been updated.
• ../CuramSDEJ/lib/jackson-annotations-2.10.2.jar - new JAR added.
• ../CuramSDEJ/lib/jackson-core-2.10.2.jar - new JAR added.
• ../CuramSDEJ/lib/jackson-databind-2.10.2.jar - new JAR added.
• ../CuramSDEJ/lib/jackson-annotations-2.9.9.jar - old JAR removed.
• ../CuramSDEJ/lib/jackson-core-2.9.9.jar - old JAR removed.
• ../CuramSDEJ/lib/jackson-databind-2.9.9.3.jar - old JAR removed.
• ../CuramCDEJ/lib/ext/jar/jackson-annotations-2.10.2.jar - new JAR added.
• ../CuramCDEJ/lib/ext/jar/jackson-core-2.10.2.jar - new JAR added.
• ../CuramCDEJ/lib/ext/jar/jackson-databind-2.10.2.jar - new JAR added.
• ../CuramCDEJ/lib/ext/jar/jackson-annotations-2.9.9.jar - old JAR removed.
• ../CuramCDEJ/lib/ext/jar/jackson-core-2.9.9.jar - old JAR removed.
• ../CuramCDEJ/lib/ext/jar/jackson-databind-2.9.9.3.jar- old JAR removed.
• ../EJBServer/components/Rest/restlib/dependencyLibsExt/jackson-annotations-2.10.2.jar - new JAR added.
• ../EJBServer/components/Rest/restlib/dependencyLibsExt/jackson-core-2.10.2.jar - new JAR added.
• ../EJBServer/components/Rest/restlib/dependencyLibsExt/jackson-databind-2.10.2.jar - new JAR added.
• ../EJBServer/components/Rest/restlib/dependencyLibsExt/jackson-annotations-2.9.9.jar - old JAR removed.
• ../EJBServer/components/Rest/restlib/dependencyLibsExt/jackson-core-2.9.9.jar - old JAR removed.
• ../EJBServer/components/Rest/restlib/dependencyLibsExt/jackson-databind-2.9.9.3.jar - old JAR removed.

Cúram Enterprise Framework

Dynamic Evidence

EVIDENCE VALIDATIONS

PO08703, WorkItem:256886 - A comparison validation with multiple clauses in a Dynamic Evidence definition gets cached repeatedly in memory at run time resulting in the heap space being exhausted

Issue Description:

If a Dynamic Evidence type definition includes a validation which has a comparison validation containing multiple clauses, duplicate copies of this configuration information will be repeatedly added to a list in memory each time the validation executes.

Each time one of the affected validations succeeds, the configuration information gets added to the list in memory once more and persists there. However, each time one of them fails, this list in memory multiplies in size. All users who encounter the affected validation will contribute to this memory issue. This leads to a rapid increase in heap usage and eventually exhausts all the heap space available resulting in the server crashing or becoming unresponsive.

User Interface Impact: No

Prerequisite(s):

This issue only affects Dynamic Evidence with comparison validations which have multiple clauses. The following example describes how to configure such a validator.

1. Login as an administrator.
2. Navigate to Dynamic Evidence under Rules and Evidence in the shortcuts panel.
3. Locate an evidence type that contains an integer attribute.
4. Select one of the Evidence Type Versions and choose New In Edit Copy specifying an effective from date.
5. For this new version, select the Edit Metadata row-level action.
6. On the Evidence Properties panel of the evidence editor, click on the Validations tab.
7. Click Add to add a new Comparison validation. Specify the required fields for the validation details. Ensure Use Literal and Multiple Clauses are checked.
8. Add two Clauses to the validation.
9. Choose the Conjunction (Any or All) and click Save.
10. Save the evidence type version in the editor.
11. Activate the new Evidence Type Version from the row-level menu on the Dynamic Evidence list page.

Steps to Reproduce:

1. Login as a caseworker.
2. Navigate to a case for which the evidence type is configured.
3. Add an instance of the evidence type to the case.
4. Specify an invalid value for the attribute that has the comparison validation. Try to save the evidence.
5. The previously configured validation message is displayed correctly.
6. Try to save the evidence again.
7. Issue: Multiple copies of the same validation message will be displayed on the screen, due to the multiple copies of the configuration data stored in memory on the server. The number of validation messages will increase significantly with each attempt to save the evidence. In a worst-case scenario, the heap space on the server will be exhausted, resulting in the server crashing or becoming unresponsive.

Resolution:

The configuration data for comparison validators in Dynamic Evidence is now only processed once and duplicates are no longer loaded into memory.

Application Development Environment

PO08611, WorkItem:256400 - Field focus delay on the Microsoft Internet Explorer and Edge browsers

Issue Description:

On the Microsoft Internet Explorer (IE) and Edge browsers, there is a delay before focus is set to the first editable field on a form when a page loads. This delay is not seen when using Google Chrome. If the user does not notice this change, they will type in an incorrect field.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Click on the Cases and Outcomes workspace tab.
3. Select Person under Searches in the shortcuts panel.
4. On the Person search page, quickly begin typing in any field other than the Reference field.
5. Issue: After a small delay the cursor will be moved back to the first row, the Reference field.

Resolution:

The issue has been resolved to prevent switching the focused field if the user has already started typing in the form.

Cúram Modules

Intelligent Evidence Gathering

PO08491, WorkItem:256334 - A blank modal is displayed instead of the Application home page after selecting the Next button from the Save Application page

Issue Description:

When using Internet Explorer 11 to process an application, an issue occurs when the modal is closed. When the user is presented with the Save Application modal, chooses to Save and then clicks Next, a blank modal is displayed.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker using the Internet Explorer 11 browser.
2. Register a Person and create a new Application.
3. Complete half of the application and click Close.
4. Select the first option 'Save the application and come back to work on it later.' and click Next.
5. Issue: A blank modal is displayed.

Resolution:

This issue has been resolved by updating the JavaScript for closing modals, the Save Application modal is now correctly closed after selecting Next.

Known Issues

See the Known Issues section in the 7.0.5.0 release notes.

Notices

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