Merative ™ Social Program Management 7.0.9.0 iFix8

Merative ™ Social Program Management is now Cúram ™ by Merative™

Release Notes

Abstract

Merative Social Program Management 7.0.9.0 iFix8 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.9.0 iFix8 release.

This is a cumulative release which incorporates the Improvements, Resolved Issues and Third Party Updates contained in all previous 7.0.9.0 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. The release notes for previous releases and the most up to date version of these release notes are available online at the 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:271635 - Update the version of Apache Commons IO library used in the Merative Social Program Management application

The Apache Commons IO library contains utility classes, stream implementations, file filters, file comparators, endian transformation classes, and much more. Its usage in Merative Social Program Management (SPM) is related to the client generators, the XML Server, Word Integration and also Axis 2 web services.

The version of the commons-io library used by SPM has now been updated from 1.4 and 2.4 to 2.8.0 which 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 version of the commons-io JAR file has been updated.
• CuramSDEJ\xmlserver\third_party_version.properties - the version of the commons-io JAR file has been updated.

The changes to the commons-io JAR file include:

• CuramCDEJ\lib\ext\jar\signed\sha-2\commons-io-2.8.0.jar - version updated from 2.4 to 2.8.0.
• CuramCDEJ\lib\ext\jar\commons-io-2.8.0.jar - version updated from 2.4 to 2.8.0.
• CuramSDEJ\xmlserver\commons-io-2.8.0.jar - version updated from 2.4 to 2.8.0.
• CuramSDEJ\lib\commons-io-2.8.0.jar - version updated from 2.4 to 2.8.0.
• CuramSDEJ\lib\axis2\commons-io-2.8.0.jar - version updated from 1.4 to 2.8.0.

It should be noted that any references in custom build scripts and other artifacts to the versioned JAR file should be updated to point to the new version of the JAR file as specified above.

WorkItem:271636 - Dojo update to ensure compatibility with the Websphere Application Server

The Dojo Toolkit is an open-source modular JavaScript library (or more specifically JavaScript toolkit) designed to ease the rapid development of cross-platform,
JavaScript/Ajax-based applications and web sites. It is used as the JavaScript framework of choice in the CDEJ (Curam Development Environment for Java) delivered as part of SPM.

An incompatibility issue with the version of Dojo used in SPM (dojo-ibm-V1.10.5) and traditional WebSphere Application Server has been addressed. This has resulted in an update to the following file within the delivered toolkit:

• dojo/request/util.js

This change is not impactful as it does not modify any of the externally available Dojo APIs delivered.

Cúram Enterprise Framework

Integrated Case Management

ELIGIBILITY & ENTITLEMENT

WorkItem:272225 - Improve reassessment performance when using CER rules - enable evidence descriptor cache only during reassessment transactions

Issue Description:

SQL searches from the Evidence Descriptor table which include caseID or successionID
result in all the Evidence Descriptor records for the case being cached in the current transaction.

User Interface Impact:

No

Steps to Reproduce:

1. Start up the application server
2. Modify a piece of static evidence on an integrated case, but do not apply the evidence changes. No case reassessment will occur.
3. Download the JMX statistics for the server
4. Issue: The JMX statistics will show that cache 'curam.cache.transaction-group.evidencedescriptorcache.bycase' was populated.

Populating this cache when editing a single piece of evidence is inefficient because only reassessment transactions benefit from this cache.

Resolution:

The Evidence Descriptor cache is now activated only for transactions which are performing a reassessment.

Business Services

WORD INTEGRATION

PO09352, WorkItem:271904 - Microsoft Word integration feature in Google Chrome fails to launch intermittently with NullPointerExceptions in Word Integration Assistant debug logs

Issue Description:

When a system administrator attempts to create or edit a Microsoft Word Communication in Merative Social Program Management using the Google Chrome browser, Microsoft Word fails to launch intermittently. When this happens, an error displays in the File Edit Control Panel modal dialog. If debug logging is enabled for the Word Integration Assistant, its logs show a NullPointerException when calling the method 'curam.util.tools.fileedit.common.WordManagement.
openWordApplication'.

User Interface Impact: No

Prerequisite(s):

1. Install Microsoft Word.
2. Install a Java Runtime Environment (JRE) version 8.
3. Install Google Chrome.
4. Install and enable the SPM File Edit Native Messaging Bridge Extension for Google Chrome. This is available on the Chrome Web Store.
5. Install the SPM Word Integration Assistant. This is distributed with the Merative SPM Client Development Environment.
6. Login as a system administrator.
7. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
8. Select the New page action to create a new Microsoft Word template.
9. Enter a name and template document ID for the template and upload a file to be used as the template.
10. Select a suitable category and sub-category and click Save.

Steps to Reproduce:

Note: Though this issue can occur intermittently, the error can be forced using the following steps.

1. Login as a system administrator.
2. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
3. Click on the edit link for the template configured above.
4. The Word File Edit Screen is loaded in the Tab Content page, and the File Edit Control Panel modal is shown.
5. Microsoft Word is launched. Close Microsoft Word.
6. A pop-up appears in the browser window. Click OK.
7. Open a new browser tab and go to chrome://settings/clearBrowserData
8. Clear the data for the last hour.
9. Return to the first tab and repeat steps 1 to 4.
10. Issue: Microsoft Word does not launch the second time, and an error icon is shown in the File Edit Control Panel. If debug logging is enabled for the Word Integration Assistant, the log shows a NullPointerException stack trace.

Resolution:

The Word Integration Assistant Java code has been updated so that the circumstances leading to the NullPointerException cannot occur.

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"