Merative ^TM Social Program Management 7.0.8.0 iFix4

Release Notes

Abstract

Merative Social Program Management 7.0.8.0 iFix4 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.8.0 iFix4 release.

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

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

Cúram Modules

Intelligent Evidence Gathering

PLAYER

PO08420, WorkItem:258725 - Read only values within a conditional cluster are cleared when navigating from their question page.

Issue Description:

For an assessment question page containing a conditional cluster, any questions within the conditional cluster that are read only will lose their values once the user navigates to the next page.

**User Interface Impact: **No

Steps to Reproduce:

1. Configure a custom IEG script that has a previously answered read only question within a conditional cluster.
2. Launch your custom IEG script.
3. Answer the question which will later be displayed as read only within the conditional cluster.
4. Navigate to the question page where the answered question is displayed as read only within the conditional cluster.
5. Click Next.
6. Issue: The previously answered read only question within the conditional cluster has lost its value.

Resolution:

This issue has been resolved by ensuring that each read only question within a conditional cluster maintains its value upon navigating away from its question page.

Financial Management

PO08721, WorkItem:257903 - Incorrect processing of manual payments for open-ended cases

Issue Description:

CREOLE based products can be configured to be open-ended. A product delivery will be open-ended if the underlying product is configured to be open-ended and certification is not required. Open-ended means that the decisions and related financial component(s) have a blank end date. Such cases will pay indefinitely until such time as the caseworker specifies an expected end date on the case. Once that happens, the old financial components are expired and new ones are generated. The new financial components will not be open-ended and will reflect the expected end date of the case.
It was found that capturing a manual payment for a period where the due financial component(s) are open-ended results in those financial components not being picked up. This means that the entire manual payment is captured as a manual payment overpayment.

**User Interface Impact: **No

Prerequisite(s):

1. A CREOLE product exists on the system that is configured to be open-ended.
   • Whether a product is open-ended or not is governed by a setting on the CREOLEProduct entity, allowOpenEndCases.
2. The product rules do not require certification to be specified for eligibility.

Steps to Reproduce (Generic):

Setting up the case

1. Login as a caseworker.
2. Register a new Person.
3. Create an instance of the product configured above, paying 'Weekly By Cash In Advance On A Monday'.
4. Add the necessary evidence to make the product delivery eligible.
5. Submit, approve and activate the case.
6. Click on the Financials tab and select Transactions.
7. Generate the first payment on the case using the Issue Payment page action.
8. Now select the Simulate Payment page action.
9. Specify the Payment Due Date for the next payment and click Simulate. Make sure to keep a note of the amount due.

Capturing the manual payment

1. Login as a financial user.
2. Click on the Transaction and Accounts workspace tab.
3. Expand the shortcuts panel and select Record a Manually Issued Payment.
4. Search for the person and select them in the Search Results.
5. On the second page of the wizard select the product delivery case.
6. On the third page select the case nominee.
7. On the last page of the wizard specify the manual payment details, including:
   • The cover period of the next payment due.
   • The amount of the payment - this should be the same as the amount from the Simulate Payment step above.
8. Click Save.

Checking the manual payment

1. Login as a caseworker.
2. Use the Person Search to find the person registered above.
3. From the person home page, click on the Care and Protection tab.
4. Click on the product delivery case.
5. Click on the Financials tab and select Transactions.
6. Issue: The manual payment line item that was captured shows up as a Manual Payment Overpayment instead of the component that was due, as per the Simulate Payment step above.

Resolution:

This issue is now resolved and the manual payment processing works as expected. In the scenario above, the line item for the manual payment will reflect what was displayed as part of the Simulate Payment process.

Technical:

The underlying problem was that the manual payment processing did not handle open-ended financial components, that is, financial components with null end dates. The processing has been updated to handle financial components with null end dates.

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"