Skip to content
Product Support Cúram

Merative ™ Social Program Management 7.0.9.0 iFix11

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

Release Notes

Abstract

Merative Social Program Management 7.0.9.0 iFix11 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 iFix11 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. 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/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/curam

Improvements, Resolved Issues and Third Party Updates

Third Party Updates

WorkItem:277728 - Update the Google gson JAR file to the latest version

Google Gson is a Java library that can be used to convert Java Objects into their JSON representation. It can also be used to convert a JSON string to an equivalent Java object. A number of areas in the Social Program Management (SPM) product utilize this library. These include Advanced Evidence Sharing (AES) administration screens, the Timeline Calendar and the Smart Navigator feature.

The version of the Google Gson library has now been updated from 2.2.2 to 2.8.9. The new version contains some defect fixes and minor enhancements. As a result of this upgrade, the following changes have been made in the SPM deliverable.

  • EJBServer/components/core/lib/gson-2.2.2.jar - old JAR removed.
  • EJBServer/components/core/lib/gson-2.8.9.jar - new JAR added.

It should be noted that any references in custom scripts and other artifacts to the updated JAR files listed above should be updated.

WorkItem:277786 - Update the versions of the Jackson JARs to the latest version - 2.13.2

The Jackson API contains multiple functions to read and build JSON using Java. It has 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 use these utilities.

The versions of these JARs have now been updated to a later version. 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.13.2.jar - new JAR added.
  • CuramSDEJ\lib\jackson-core-2.13.2.jar - new JAR added.
  • CuramSDEJ\lib\jackson-databind-2.13.2.2.jar- new JAR added.
  • CuramSDEJ\lib\jackson-annotations-2.12.1.jar - old JAR removed.
  • CuramSDEJ\lib\jackson-core-2.12.1.jar - old JAR removed.
  • CuramSDEJ\lib\jackson-databind-2.12.1.jar- old JAR removed.
  • CuramCDEJ\lib\ext\jar\jackson-annotations-2.13.2.jar - new JAR added.
  • CuramCDEJ\lib\ext\jar\jackson-core-2.13.2.jar - new JAR added.
  • CuramCDEJ\lib\ext\jar\jackson-databind-2.13.2.2.jar - new JAR added.
  • CuramCDEJ\lib\ext\jar\jackson-annotations-2.12.1.jar - old JAR removed.
  • CuramCDEJ\lib\ext\jar\jackson-core-2.12.1.jar - old JAR removed.
  • CuramCDEJ\lib\ext\jar\jackson-databind-2.12.1.jar - old JAR removed.
  • EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-annotations-2.13.2.jar - new JAR added.
  • EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-core-2.13.2.jar - new JAR added.
  • EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-databind-2.13.2.2.jar - new JAR added.
  • EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-annotations-2.12.1.jar - old JAR removed.
  • EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-core-2.12.1.jar - old JAR removed.
  • EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-databind-2.12.1.jar - old JAR removed.

Note that any references in custom scripts and other artifacts to the updated JAR files listed above must be updated.

WorkItem:277841 - Updates to some of the libraries present in Axis 2 and Rampart

Merative Social Program Management web services are based on Apache Axis2. With the Rampart security module of Axis2, Social Program Management web services can be secured for authentication, integrity (signature), confidentiality (encryption/decryption), and non-repudiation (timestamp).

The versions of some of the JARs in both Axis 2 and Rampart have been updated. As a result of these updates, the following changes have been made in the JDE Axis 2 deliverable.

  • CuramSDEJ\lib\third_party_version.properties - the versions of the specified Axis 2 and Rampart JARs have been updated.
  • CuramSDEJ\lib\axis2\axis2-ant-plugin-1.8.0.jar - version updated from 1.6.2 to 1.8.0.
  • CuramSDEJ\lib\axis2\xmlbeans-3.1.0.jar - version updated from 2.3.0 to 3.1.0.
  • CuramSDEJ\lib\axis2\esapi-2.2.3.1.jar - version updated from 2.0GA to 2.2.3.1.
  • CuramSDEJ\lib\axis2\velocity-engine-core-2.3.jar version updated from velocity-1.5.jar to velocity-engine-core-2.3.jar.
  • CuramSDEJ\lib\axis2\xmltooling-1.4.4.jar- version updated from 1.3.2-1 to 1.4.4.

Note that any references in custom scripts and other artifacts to the updated JAR files listed above must be updated.

WorkItem:277912 - JDom library update

The JDOM library is a Java-based solution for accessing, manipulating, and outputting XML data from Java code. Its usage in Merative Social Program Management is widespread across all areas of the application.

The jar file jdom-1.0.jar has been updated to jdom-1.0-1.jar.

As a result of this upgrade, the following changes have been made to the JDE deliverables.

  • CuramSDEJ\lib\third_party_version.properties - the version of the specified JDom JAR has been updated.
  • CuramSDEJ/lib/jdom-1.0.jar has been removed.
  • CuramSDEJ/lib/jdom-1.0-1.jar has been added.

Note that any references in custom scripts and other artifacts to the updated JAR file listed above must be updated.

WorkItem:277972 - The version of the logging framework used by the SPM product has been updated to Log4j-ibm-1.2.17.2

Apache Log4j is a Java-based logging utility that is used as the logging provider for the Social Program Management (SPM) product.

The jar file log4j-ibm-1.2.17.1.jar is an IBM version of Log4j which was derived from Apache Log4j-1.2.17.
A class in this jar file was found to be incompatible with some logging configurations and could not be shipped. Therefore the jar has been updated to remove the affected class. The classes which have been removed from the jar file are:

  • org.apache.log4j.net.JMSAppender
  • org/apache/log4j/net/JMSSink.class
  • org/apache/log4j/jdbc/JDBCAppender.class
  • org/apache/log4j/chainsaw/
  • (8 classes)

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

  • CuramSDEJ/lib/log4j-ibm-1.2.17.1.jar - This JAR file has been removed.
  • CuramSDEJ/xmlserver/log4j-ibm-1.2.17.1.jar - This JAR file has been removed.
  • CuramCDEJ/lib/ext/jar/log4j-ibm-1.2.17.1.jar - This JAR file has been removed.
  • CuramSDEJ/lib/log4j-ibm-1.2.17.2.jar - This JAR file has been added.
  • CuramSDEJ/xmlserver/log4j-ibm-1.2.17.2.jar - This JAR file has been added.
  • CuramCDEJ/lib/ext/jar/log4j-ibm-1.2.17.2.jar - This JAR file has been added.

It should be noted that any references in custom scripts and other artifacts to the old 'log4j' JAR file should be updated to point to the new version of that JAR file as specified above. References to the JAR file which is no longer part of the JDE deliverable should be removed.

Curam Enterprise Framework

CLIENT DEVELOPMENT ENVIRONMENT

WorkItem:276056 - Incorrect Log4j and commons-io references in CuramCDEJ .classpath

Issue Description:

When the CuramCDEJ project is loaded in Eclipse as part of the Curam Development Environment, two jar files are reported as being missing.
This prevents the project from being built within Eclipse - though it does not prevent the project from being built and deployed onto an application server.

User Interface Impact: No

Steps to Reproduce:

  1. Install the Curam Development Environment.
  2. Import the CuramCDEJ project
  3. Issue: The following two errors will present in the Problems view:

Project 'CuramCDEJ' is missing required library: '/CuramSDEJ/lib/commons-io-2.4.jar'

Project 'CuramCDEJ' is missing required library: '/CuramSDEJ/lib/log4j-1.2.17.jar'

Resolution:

The correct versions of the jar files are now loaded by the project in Eclipse.

WORD INTEGRATION

PO09746, WorkItem:276843 - Editing a Word document on Google Chrome browser displays 'X' error randomly

Issue Description:

Caseworkers are able to edit the contents of Word documents using the Word Integration Assistant. An intermittent issue occurs after a caseworker edits a document and then shuts down the Word Integration Assistant when the Google Chrome browser is used. When the caseworker then tries to edit another document, a red X icon is displayed in the File Edit Control Panel in the browser window.

User Interface Impact:** **No

Prerequisite(s):

  1. Install Microsoft Word.
  2. Install a supported (supported for Social Program Management Word Integration) Java Runtime Environment.
  3. Install Google Chrome.
  4. Install and enable the Cúram File Edit Native Messaging Bridge Extension for Google Chrome. This is available on the Chrome Web Store.
  5. Install the Social Program Management Word Integration Assistant. This is distributed with the Cúram Client Development Environment.
  6. Log in 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. To allow the template to be used for any communication, set the category to All Communication and the subcategory to All Communications. Click Save.

Steps to Reproduce:

Note that this is an intermittent issue, there is no known method to force this.

  1. Log in as a caseworker.
  2. Navigate to a Person home page.
  3. Go to the Client Contact tab and choose Communications.
  4. Click the page-level menu to create a new Microsoft Word communication.
  5. On the New Microsoft Word Communication modal, specify a Correspondent and click Next.
  6. Enter the Subject and Address. Choose the Template Name that was configured previously. Click Save.
  7. The Word File Edit Screen is loaded in the Tab Content page and the File Edit Control Panel modal is shown.
  8. Microsoft Word opens.
  9. Make an edit to the Word document.
  10. Close the Word editor.
  11. The document will be saved and the File Edit Control Panel will close.
  12. In the same browser window, try editing another Word document.
  13. Issue: A red X icon appears in the File Edit Control Panel.

Resolution:

A caseworker is now able to edit multiple Word documents without seeing the red X icon.

Technical:

This issue was caused by the improper handling of an initial exception that occurs when the user attempts to shut down the Word Integration Assistant Java process. The Java process is prevented from exiting correctly after the Word editor is closed. The red X icon is the result of starting a second Word Editing session in an inconsistent state. The fix also contains changes to ensure the problem state data that was previously long-lived is now short-lived.

PO09782, WorkItem:276845 - Microsoft Word closes unexpectedly in Google Chrome if an unrelated Chrome browser is also open and is closed

Issue Description:

When using the Microsoft Word Integration feature through the Google Chrome browser, if a separate Chrome browser window is also open and a user closes this browser, Microsoft Word closes unexpectedly in the other browser.

User Interface Impact: No

Prerequisite(s):

  1. Install Microsoft Word.
  2. Install a supported (supported for Social Program Management Word Integration) Java Runtime Environment.
  3. Install Google Chrome.
  4. Install and enable the Cúram File Edit Native Messaging Bridge Extension for Google Chrome. This is available on the Chrome Web Store.
  5. Install the Social Program Management Word Integration Assistant. This is distributed with the Cúram Client Development Environment.
  6. Log in 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. To allow the template to be used for any communication, set the category to All Communication and the subcategory to All Communications. Click Save.

Steps to Reproduce:

  1. In Google Chrome, go to 'chrome: settings/system' and enable 'Continue running background apps when Google Chrome is closed.'
  2. Open a second browser tab and move it out to be its own window.
  3. In the first window, log in as a caseworker.
  4. Navigate to a Person homepage.
  5. Go to the Client Contact tab and choose Communications.
  6. Click the page-level menu to create a new Microsoft Word communication.
  7. On the New Microsoft Word Communication modal, specify a Correspondent and click Next.
  8. Enter the Subject and Address. Choose the Template Name that was configured previously. Click Save.
  9. The Word File Edit screen is loaded in the Tab Content page and the File Edit Control Panel modal is shown.
  10. Microsoft Word opens.
  11. Close the second browser window (the one that did not open the Word editing session).
  12. Issue: Microsoft Word closes after the browser window is closed.

Resolution:

When an unrelated Chrome browser window is closed, the browser window in which the Word editing session opened is no longer closed.

Technical:

The code executing in the browser mistakes the event of closing an unrelated Chrome browser window as the closing of the browser window that started the Word editing session. Therefore, a message is sent in error by the browser to the Word Integration Assistant instructing it to close Word and then itself. The Word Integration Assistant now ignores these events from other Chrome browser windows. Changes were also made to bring the actual behavior in line with the preferred behavior described here [[https://www.ibm.com/docs/en/spm/8.0.2?topic=reference-file-edit-widget]]. If the user chooses to leave the page, the editing session is terminated and the document or Microsoft Word (if it was the only document open) closes along with the browser.

PO09747, WorkItem:276846 - File Edit Control Panel is closed on Google Chrome without informing the user that an error has occurred

Issue Description:

Caseworkers are able to edit the contents of Word documents using the Word Integration Assistant. When the Word Integration Assistant is used through a Google Chrome browser and a user chooses to save changes by closing the Word Editing session, if an error is encountered the File Control Panel closes. In this instance, the caseworker is unable to see that an error has occurred. This is in contrast to when a user uses the commit changes button on the File Control Panel to save periodically to the Cúram server, where the same error is visible in the File Edit Control Panel.

User Interface Impact: No

Prerequisite(s):

  1. Install Microsoft Word.
  2. Install a supported (supported for Social Program Management Word Integration) Java Runtime Environment.
  3. Install Google Chrome.
  4. Install and enable the Cúram File Edit Native Messaging Bridge Extension for Google Chrome. This is available on the Chrome Web Store.
  5. Install the Social Program Management Word Integration Assistant. This is distributed with the Cúram Client Development Environment.
  6. Log in 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. To allow the template to be used for any communication, set the category to All Communication and the subcategory to All Communications. Click Save.

Steps to Reproduce:

  1. Log in as a caseworker.
  2. Navigate to a Person homepage.
  3. Go to the Client Contact tab and choose Communications.
  4. Click on the page-level menu to create a new Microsoft Word communication.
  5. On the New Microsoft Word Communication modal, specify a Correspondent and click Next.
  6. Enter the Subject and Address. Choose the Template Name that was configured previously. Click Save.
  7. The Word File Edit Screen is loaded in the Tab Content page and the File Edit Control Panel modal is shown.
  8. Microsoft Word is launched.
  9. Copy and paste the content of a 1MB text file into the Word document. The resulting Word document will be too large to be saved by the Cúram server and will cause an error.
  10. Close the Word editor.
  11. The File Edit servlet responds with a 500 HTTP response code indicating an error and the document is not saved.
  12. Issue: The File Edit Control Panel closes. It should remain open and display an error message to the user. Having reviewed the error message, the user should be able to close the File Edit Control Panel.

Resolution:

The FIle Edit Control Panel modal now stays open so the error is visible to the user. The user can then close the modal after they have been shown the error message.

Technical:

The issue has been resolved by updating the functionality so that the browser does not close the File Edit Control Panel modal if there are any errors during the saving of the document. The user will be able to close the modal manually.

PO09745, WorkItem:276847 - Edits to Word document on Google Chrome browser are not saved when the Word editing session is closed and user delays in confirming the edits

Issue Description:

Using the Microsoft Word Integration feature in the Google Chrome browser, when a user makes an update to a Word document they can choose to save their changes. Saving can be done either by closing the Word Editing session and confirming in a pop-up modal that is displayed or by selecting the commit changes button on the File Edit Control Panel. When users select to save changes by closing the Word editing session, if they wait more than 5 seconds before confirming in the pop-up dialog that appears in the browser (asking if they want to save their edits to the Cúram server), the edits are not saved.

User Interface Impact: No

Prerequisite(s):

  1. Install Microsoft Word.
  2. Install a supported (supported for Social Program Management Word Integration) Java Runtime Environment.
  3. Install Google Chrome.
  4. Install and enable the Cúram File Edit Native Messaging Bridge Extension for Google Chrome. This is available on the Chrome Web Store.
  5. Install the Social Program Management Word Integration Assistant. This is distributed with the Cúram Client Development Environment.
  6. Log in 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. To allow the template to be used for any communication, set the category to All Communication and the subcategory to All Communications. Click Save.

Steps to Reproduce:

  1. Log in as a caseworker.
  2. Navigate to a Person homepage.
  3. Go to the Client Contact tab and choose Communications.
  4. Click the page-level menu to create a new Microsoft Word communication.
  5. On the New Microsoft Word Communication modal, specify a Correspondent and click Next.
  6. Enter the Subject and Address. Choose the Template Name that was configured previously. Click Save.
  7. The Word File Edit Screen is loaded in the Tab Content page and the File Edit Control Panel modal is shown.
  8. Microsoft Word opens.
  9. Make an edit to the Word document.
  10. Close the Word editor.
  11. The pop-up dialog appears in the browser window asking if you want to save your edit to the Cúram server. Wait 5 seconds, then press OK.
  12. Issue: The file changes are not saved to the Cúram server.

Resolution:

When a user closes the Word Editing session, the changes are now saved. The Word Integration Assistant no longer deletes the Word file from the local file system before the browser code can attempt to save the changes to the Cúram server. The delete of the local file now only happens after the operation to save the document to the Cúram server has finished.

PO09822, WorkItem:277382 - Microsoft Word integration feature in Google Chrome fails to save changes when the application is in the background

Issue Description:

When using the Microsoft Word Integration feature in a Google Chrome browser tab, if users close the Word editing session on a tab that is not the active tab or if the browser window is covered by another application window, no pop-up modal is displayed asking if they want to save their edits. The File Edit Control Panel closes and any edits made to the document are not saved.

User Interface Impact: No

Prerequisite(s):

  1. Install Microsoft Word.
  2. Install a supported (supported for Social Program Management Word Integration) Java Runtime Environment.
  3. Install Google Chrome.
  4. Install and enable the Cúram File Edit Native Messaging Bridge Extension for Google Chrome. This is available on the Chrome Web Store.
  5. Install the Social Program Management Word Integration Assistant. This is distributed with the Cúram Client Development Environment.
  6. Log in 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. To allow the template to be used for any communication, set the category to All Communication and the sub-category to All Communications. Click Save.

Steps to Reproduce:

  1. Log in as a caseworker.
  2. Navigate to a Person homepage.
  3. Go to the Client Contact tab and choose Communications.
  4. Click the page-level menu to create a new Microsoft Word communication.
  5. On the New Microsoft Word Communication modal, specify a Correspondent and click Next.
  6. Enter the Subject and Address. Choose the Template Name that was configured previously. Click Save.
  7. The Word File Edit Screen is loaded in the Tab Content page and the File Edit Control Panel modal is shown.
  8. Microsoft Word opens.
  9. Either switch to another tab in the same browser window or maximize Word so that it completely obscures Google Chrome.
  10. Make changes in Word and then exit by closing the Word editor.
  11. Issue: The changes are not saved and the File Edit Control Panel closes automatically without prompting the user to save their changes.

Resolution:

When a tab in Google Chrome is not in focus, or if the whole browser application is not in focus, Chrome does not allow the pop-up dialog to launch which should prompt users to save their changes to the Word document. When the Word editing session is closed, to prevent the loss of updates made by the user in instances such as these, the application now automatically saves any changes made to the document. The File Edit Control Panel is closed without displaying a confirmation modal to the user, logging the save operation in the developer console and the native messaging log.

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"

Document Information

More support for:

Merative Social Program Management

Software version:

7.0.9

Operating system(s):

Linux, Windows

Modified date:

31 May 2022