Merative ™ Social Program Management 7.0.10.0 iFix5

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

Release Notes

Abstract

Merative Social Program Management 7.0.10.0 iFix5 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.10.0 iFix5 release.

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

Installation

Before running the installer please ensure all files in your Merative Social Program Management installation are writable.

The installation steps are as follows:

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

Cúram Enterprise Framework

Cúram Modules

Cúram Enterprise Framework

Integrated Case Management

Integrated Case Management

Eligibility & Entitlement

ELIGIBILITY & ENTITLEMENT

WorkItem:267796 - Performance optimization for method CaseNomineeObjective.searchObjectiveHistoryForCase

Issue Description:

Bulk reassessment after rate and threshold changes as well as online reassessments resulting from evidence changes sometimes run slowly.
This is due to the performance of the SQL query for method CaseNomineeObjective.searchObjectiveHistoryForCase that can show up as having a very high CPU consumption in the Oracle Automatic Workload Repository Report.

User Interface Impact:
No

Steps to Reproduce:

This change relates to a performance optimization of the CaseNomineeObjective.searchObjectiveHistoryForCase API.
It is highly dependent on user data and as such is not directly reproducible.

Resolution:

The SQL query has been refactored into two separate queries and the version of the query which is used now depends on whether the toDate parameter is specified. This enables the database to apply the most optimal access plan for the query.

Cúram Modules

Provider Management
Universal Access
Intelligent Evidence Gathering
Provider Management

PO09081, WorkItem:266612 - Page becomes unresponsive when adding a third compartment to a provider facility

Issue Description:

The Manage Provider Facility page becomes unresponsive after adding a third child compartment to the top-level compartment.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a Provider Management Resource Manager.
  2. Navigate to a provider and from the provider home page, select the Manage Facility action menu item.
  3. From the Compartment Details page, select the New Compartment menu item.
  4. Insert a name and save the compartment.
  5. Add a second compartment with a unique name.
  6. Add a third compartment with a unique name.
  7. Issue: The page becomes unresponsive.

Resolution:

The Manage Provider Facility page behaves as expected after adding three or more child compartments to the top-level compartment.

Technical:

The data from the CompartmentLoader and FacilityLoader classes was not ordered when it was returned to the client. The page uses the curam.widget.FramesetWidget Dojo widget. The widget became unresponsive because when a new child compartment node is added to the root node, a dijit.tree.ForestStoreModel._requeryTop() function is called which triggers the curam.util.orgTreeStore.fetch() function to retrieve the child compartment data from the server. As the data was returned in a different order for each call, this lead to the ForestStoreModel._requeryTop() function being re-triggered and this flow repeated. This caused the page to become unresponsive after three or more child compartments were added to the root compartment. The data is now sorted before it is returned to the client.
The following files were updated as part of addressing this issue:

Universal Access

PO08998, WorkItem:267952 - Universal Access Responsive Web Application: IEG page answers REST API does not validate answers to questions from current form page

Issue Description:

The IEG REST API for submitting answers on an IEG script can be used outside of the context of the current question page. This can allow datastore values to be changed that were not available for change by the questions listed on the current question page.

**User Interface Impact:**No

Prerequisite(s): None

Steps to Reproduce: None

Resolution:

Now, when the IEG REST API for submitting answers is called, it will compare any submitted question-answer pair against the questions that were defined on the current question page. Answers from questions that were not on the current question page will not be processed. This is enabled by default but can be disabled using the new system property curam.ieg.answers.mustmatch.currentpagequestions.disabled. A new server logging message will appear when curam.trace is set to trace_on and will log when an answer is submitted by a user to a question not available from the current question page.

PO08998, WorkItem:267956 - Universal Access Responsive Web Application: Possible to navigate to incorrect IEG pages

Issue Description:

****It is possible to navigate to incorrect IEG pages by using the browser buttons or via REST APIs.

User Interface Impact: No

Prerequisite(s):

An IEG script with the following scenario:

  1. (Section 1)(Page 0) - Page to submit data
  2. (Section 2)(Page 1) - Page to submit data
  3. (Section 2)(Page 2a) - Conditional Page that is displayed if data submitted on Page 1 is TRUE
  4. (Section 2)(Page 2b) - Conditional Page that is displayed if data submitted on Page 1 is FALSE, disable the next button, so the user can not navigate forward.
  5. (Section 3)(Page 3) - Summary Page that is displayed only if the button next on Page 2a is clicked.

Steps to Reproduce:

  1. Go to page 0, Provide any data, click continue.
  2. Go to page 1 and submit data in order to make the condition TRUE so Page 2a and Page 3a are displayed.
  3. Go to page 2a - Provide any data, click continue.
  4. In the summary (Page 3), click on edit on the data of Page 1.
  5. Page 1, edit the data in order to make the condition FALSE , Click continue.
  6. Page 2b is loaded, then click on the browser back button.
  7. Page 1 is displayed, then click on the browser back button.
  8. Summary page (Page 3), is displayed, this is an error as this page should not be available as the section is not enabled.

Resolution:

Now a sync token is sent back and forward to the IEG REST API to avoid the front-end and back-end to be out of sync, therefore preventing any incorrect navigation through IEG Pages.

Intelligent Evidence Gathering

Player

PLAYER

PO09115, WorkItem:267608 - Custom functions called from an Intelligent Evidence Gathering (IEG) script may receive null value instead of the entity attributes specified in the script definition

Issue Description:

When a custom function is invoked during the completion of an IEG (Intelligence Evidence Gathering) script, the value passed to the custom function may be null. This occurs when the data entity containing the value being passed is not the most recent entity being operated on.

User Interface Impact: No

Note:

You need to use IEG scripts for an application intake to reproduce this issue. You can reproduce this scenario by performing the following prerequisite steps to configure an assessment.

Prerequisite(s):

  1. A question page to input information about a Person entity that relates to the primary applicant.
  2. A second question page to input income amount information for the primary applicant Person entity through its child Income entity.
  3. A third question page to input employment information for the primary applicant Person entity through its child Employment entity.
  4. A callout surrounding a fourth question page that executes a custom function to ensure the amount attribute on the Income entity is not null before opening the fourth page in the IEG script.

Steps to Reproduce:

  1. Launch the custom assessment IEG script.
  2. Navigate to the third question page by entering information for the primary applicant and their income amount.
  3. Click Next.
  4. Issue: The fourth question page is skipped since the amount attribute on the person's Income entity was evaluated as null by the custom function.

Resolution:

The previously skipped question page is now displayed correctly as the value of the Income entity's amount attribute is successfully passed to the custom function.

Technical:

A callout is an Intelligent Evidence Gathering (IEG) script element that is used to invoke code that is not part of IEG. It can be used to execute a custom function which, for example, modifies the attributes of an entity on the Datastore.

This issue was resolved by ensuring entities are populated correctly in a way in which their attributes can be read and passed to a custom function successfully at all times, preventing unexpected behavior when navigating through an IEG script.

The java class that was updated is:

Known Issues

See the Known Issues section in the 7.0.10.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.10

**Operating system(s):**Linux, Windows

**Modified date:**11 February 2021