Merative ™ Social Program Management 7.0.1.3

Release Notes

Abstract

Merative Social Program Management 7.0.1.3 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.1.3 release.

This is a cumulative release which incorporates the Improvements, Resolved Issues and Third Party Updates contained in all previous 7.0.1 Fix Pack releases. Details of these Improvements, Resolved Issues and Third Party Updates are included separately in the release notes for each of the previous Fix Pack 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

Prior to 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/spm.

Improvements, Resolved Issues and Third Party Updates

Third Party Updates

WorkItem:233467 - Introduce the jsoup library into the Social Program Management application

Jsoup provides helper classes to cleanse HTML documents and strings of malicious code.
Version 1.11.3 has been introduced into the product to improve security. The library is located in the CDEJ/lib/ext/jar directory.

WorkItem:237753 - Update the version of Apache FOP used in the Social Program Management application

Apache™ FOP is a print formatter driven by XSL formatting objects and an output independent formatter. It is used by the Merative SPM XML Server in the generation of PDF documents.

The version of FOP used by the Merative SPM XML Server has now been updated from 2.2 to 2.3. FOP 2.3 contains some bug fixes and a number of improvements.

As a result of this upgrade, the following changes have been made in the Java Development Environment deliverable.

• CuramSDEJ\lib\third_party_version.properties - the versions of the specified FOP related JARs have been updated.
• CuramSDEJ\xmlserver\third_party_version.properties - the version of the specified FOP related JARs have been updated.

The existing avalon-framework.jar file present in previous versions of the FOP deliverable has now been split into two separate JAR files. As a result of this, the following changes have been made.

• CuramSDEJ\xmlserver\avalon-framework-4.2.0.jar - this JAR file has been removed.
• CuramSDEJ\xmlserver\avalon-framework-api-4.3.1.jar - this JAR file has been added.
• CuramSDEJ\xmlserver\avalon-framework-impl-4.3.1.jar - this JAR file has been added.

The changes to the other FOP related JAR files include:

• CuramSDEJ\xmlserver\batik-all-1.10.jar - new version of the batik-all JAR.
• CuramSDEJ\xmlserver\fop-2.3.jar - new version of the FOP JAR.
• CuramSDEJ\xmlserver\xmlgraphics-commons-2.3.jar - new version of the xmlgraphics-commons JAR.
• CuramSDEJ\xmlserver\xml-apis-ext-1.3.04.jar - this JAR file has been added.

It should be noted that any references in custom scripts and other artifacts to the now removed "CuramSDEJ\xmlserver\avalon-framework-4.2.0.jar" should be updated to point to the two newly added avalon JARs as described above.

WorkItem:238960 - Browser Support Update

The following browser versions have been updated and certified for this release:

Case Worker Application Browser Support

• Google Chrome updated to 70

Universal Access Application Browser Support

• Google Chrome updated to 70
• Mozilla Firefox updated to 63
• Microsoft Edge updated to 44

WorkItem:239439 - Adobe Flash Player version update.

The version of the Adobe Flash Player that has been certified to be used by the Social Program Management (SPM) application has been updated to 31.

WorkItem:239455 - Update the Browser Plugins JRE levels used in Microsoft Word Integration

The following JRE level for Microsoft Word Integration is supported for this release:

• JRE 1.8 u191

Cúram Enterprise Framework

Dynamic Evidence

EVIDENCE MAINTENANCE

PO07819, WorkItem:237071 - Discarding an In-edit Evidence causes an unhandled server exception to be thrown

Issue Description:

An un-handled server exception is thrown when a user attempts to discard in-edit evidence where the underlying evidence descriptor does not have a participantID set. This cannot ordinarily arise through the standard evidence maintenance functionality, but could arise if data is migrated to Merative Social Program Management from a legacy system without a participantID specified.

User Interface Impact: No

Steps to Reproduce:

1. Register a Person.
2. Create an Integrated Case.
3. Add evidence so the Integrated Case, but do not activate it.
4. In order to reproduce the issue, the participantID on the underlying evidence descriptor needs to be set to null.
5. Now attempt to discard the evidence from the evidence workspace.
6. Issue: an un-handled server exception is thrown.

Resolution:

The Evidence API has been made more robust and is now able to handle a blank participantID when evidence is being discarded.

Application Development Environment

CLIENT DEVELOPMENT ENVIRONMENT

PO07333, WorkItem:237076 - Page level PRINT icon does not print the Details section of expanded evidences in evidence list

Issue Description:

Previously, when using the page level Print icon to print a list of Evidence details, certain information was missing. When the evidence was expanded to display the full details associated with the evidence, only the Change Summary information was printed. No information from the Evidence Details page was printed.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Register a Person.
3. Create a Case.
4. From the Evidence dashboard, create a new Evidence.
5. Activate the Evidence.
6. View the newly created Evidence from the Active Evidence list.
7. Click the toggle to view the Change Summary for the evidence.
8. Click the toggle to view the Evidence Details associated with the evidence.
9. Print the page using the print button in the options menu of the page.
10. The only information present in the print preview is the Change Summary information.

Resolution:

This issue has been resolved by adding specific styling for Evidence pages when they are printed. This ensures all the visible Evidence information is printed correctly.

PO07507, WorkItem:237079 - Page level PRINT icon does not print Notes History or Search Results correctly

Issue Description:

Previously, when a user selected the page level print to print Notes or Search Results, not all of the information that was displayed to the user was printed. When the Search Results or Notes were expanded to show the inline page containing the all the information available, the information in the inline page was not printed correctly.

User Interface Impact: No

Steps to Reproduce using Search:

1. Login as a caseworker.
2. From the Shortcuts area of the Cases and Outcomes section, select "Person".
3. Enter criteria and search for a person on the system.
4. When the search is completed, expand the toggle associated with one of the search results, so that more participant information is visible.
5. Print the page using the print button in the options menu of the page.
6. Not all of the information is present on the print preview.

Steps to Reproduce using Notes:

1. Login as a caseworker.
2. Register a Person.
3. Click on the Contact tab.
4. Create multiple notes.
5. Expand the toggle associated with one of the Notes, so that the note is visible.
6. Print the page using the print button in the options menu of the page.
7. Not all of the information is present on the print preview.

Resolution:

This issue has been resolved by adding specific styling to pages as they are printed. This ensures all information on the Person Search page and Notes is printed clearly.

Solutions

Income Support

PO07765, WorkItem:240248 - Issue with RuleSetSnapshotCache memory usage while superseding a CREOLEProgramGroupDetermination

Issue Description:

Previously a large amount of memory was used in HCR when modifying active evidence.

User Interface Impact: No

Steps to Reproduce:

1. Create and submit an Insurance affordability application.
2. Ensure the applicants are eligible for one of the Insurance Assistance programs.
3. Authorise the application and create a new Integrated Case.
4. Verify that the Integrated Case has one or more product delivery cases active under the new Integrated Case.
5. Make a change to any active evidence record and apply changes.
6. An incorrect call was being made to cause a performance issue to occur resulting in a large amount of memory to be consumed.

Resolution:

The problematic call causing this memory issue has now been removed to resolve this issue.

Known Issues

See the Known Issues section in the 7.0.1.1 release notes.

Notices

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