Document Information
More support for:
Merative Social Program Management
Software version:
8.0.1
Operating system(s):
Linux, Windows
Modified date:
18 July 2022
Merative ™ Social Program Management 8.0.1.0 iFix6
Merative ™ Social Program Management is now Cúram ™ by Merative™
Release Notes
Abstract
Merative Social Program Management 8.0.1.0 iFix6 Release Notes
Content
IMPORTANT NOTE - THIS RELEASE HAS NEW DOWNLOAD INSTRUCTIONS, AS DESCRIBED BELOW.
Introduction
System Requirements
**Updated Download Information**
Installation
Improvements, Resolved Issues, Third Party Updates
Known Issues
Notices
Introduction
Welcome to the Merative Social Program Management 8.0.1.0 iFix6 release.
This is a cumulative release which incorporates the Improvements, Resolved Issues and Third Party Updates contained in all previous 8.0.1.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 Product documentation and PDFs.
For information about the supported software and hardware for this release, see the Merative Social Program Management Prerequisites.
**Updated Download Information**
See the download instructions for this release at https://www.merative.com/support/spm.
Before you run the installer, ensure that 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 https://www.merative.com/support/spm.
Improvements, Resolved Issues, Third Party Updates
Curam Enterprise Framework
Solutions
Application Development Environment
Common Intake
Application Development Environment
Server Development Environment
SERVER DEVELOPMENT ENVIRONMENT
DT036276, WorkItem:278145 - Batch launcher error when DB-to-JMS is enabled with WebSphere Liberty server
Issue Description:
The batch launcher fails when DB-to-JMS is enabled in conjunction with WebSphere Liberty server.
In addition the server logs will include one or both of the following messages:
- User ‘UNAUTHENTICATED’ does not have role on CuramServer'
- java.lang.ClassCastException: curam.util.invoke.EJSLocal0SLEJBMethod_2b4572e3 incompatible with curam.util.invoke.Method
User Interface Impact: No
Steps to Reproduce:
- Set application property 'Database-to-jms - enable flag' to 'True'.
- Set application property 'Database-to-jms - Notification batch launcher mode' to '1'.
- Set application property 'Database-to-jms - Notification host name' and 'Database-to-jms - Notification port number' to reference an SPM application on WebSphere Liberty.
- Run the batch launcher.
Issue:
[batchlauncher] A runtime exception occurred: An error occurred triggering the database-to-JMS server
at '<host name>':'<port number>' (SSL mode: false):(). Note that properties `curam.batchlauncher.dbtojms.notification.host` and `curam.batchlauncher.dbtojms.notification.port` respectively must be set to the host and port number on which the Curam client application is deployed, because the database to JMS server is part of the Curam client application.
Resolution:
When DB-to-JMS is enabled, the batch launcher can authenticate with the server to obtain an LTPA token required by WebSphere Liberty to trigger a database-to-JMS transfer.
LTPA token usage is enabled by setting the application property 'Database-to-jms - Enable LTPA token usage for DB-to-JMS triggering'
(Technical ID: curam.batchlauncher.dbtojms.notification.ltpa) to 'True'.
To help with troubleshooting another property 'Database-to-jms - Enable tracing for DB-to-JMS triggering'
(Technical ID: curam.batchlauncher.dbtojms.notification.trace) is now available. Setting this property to 'True' enables diagnostic logging for DB-to-JMS operations. Previously it was necessary to set the application-wide property 'Tracing level' (Technical ID: curam.trace) to 'trace_verbose' in order to activate this logging, which was less convenient.
DT036281, WorkItem:278274 - Opening a modal to add static evidence throws an Application Error with a ClassCastException in the logs if the property 'curam.trace.methods' is set to true
Issue Description:
Adding static evidence results in the message 'An Application Error Has Occurred' being presented to the user as well as a ClassCastException in the server logs if the property 'curam.trace.methods' is set to true.
User Interface Impact: No
Prerequisite(s):
- Log in as a system administrator.
- Navigate to Property Administration under Application Data in the shortcuts panel.
- Search for the property 'curam.trace.methods'.
- Use the row-level action to edit the value and set it to true. Click Save.
- Publish the changes.
Steps to Reproduce:
- Log in as an Income Support caseworker.
- Register a person and complete a new Income Support Application.
- Open the Income Support Application case and navigate to the Evidence dashboard.
- Add static evidence, such as Work Registration.
- Issue: When clicking to add Work Registration evidence, the following error is presented to the user 'An Application Error Has Occurred' together with a ClassCastException in the server logs.
Resolution:
This issue has been resolved and a ClassCastException is no longer thrown in the server logs when opening a modal to add static evidence.
WorkItem:278282 - Authorizing a Income Support Application throws an Application Error with a ClassCastException in the logs if the property 'curam.trace.methods' is set to true
Issue Description:
Authorizing an Income Support Application results in the message 'An Application Error Has Occurred' being presented to the user as well as a ClassCastException in the server logs if the property 'curam.trace.methods' is set to true.
User Interface Impact: No
Steps to Reproduce:
- Log in as an Income Support caseworker.
- Register a new Person.
- Create an Income Support application for Food Assistance for this person.
- Submit the application.
- Add Work Registration and Head of Household evidence for Food Assistance.
- Apply evidence changes.
- Log out.
- Log in as a system administrator.
- Select Property Administration under Application Data in the shortcuts panel.
- Search for the 'curam.trace.methods' application property.
- Set the value to 'true'. Click Save.
- Publish the changes.
- Log out.
- Log in as an Income Support caseworker.
- Search for the application created in the steps above.
- Set the application to Ready for Determination.
- Check eligibility and authorize the application.
- Issue: An Application Error Has Occurred is presented to the user and a ClassCastException can be found in the server logs.
Resolution:
This issue has been resolve and the exception is no longer thrown in the server logs when authorizing an Income Support Application with method tracing enabled.