Merative ™ Social Program Management iFix9

Release Notes


Merative Social Program Management iFix9 Release Notes


IntroductionSystem Requirements
Improvements, Resolved Issues and Third Party Updates
Known Issues


Welcome to the Merative Social Program Management iFix9 release.

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

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.


See the download instructions for this release at /support/spm.


Prior to 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.


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

Application Development Environment

PO09471, WorkItem:278126 - Unhandled server exception when modifying an in-edit dynamic evidence into new version

Issue Description:

In Merative Social Program Management, when a user tries to modify a historical in-edit dynamic evidence record on a case to update the evidence record from Version1 (old) to Version2 (new), an unhandled server exception is thrown if the previous version included validations on the removed attributes.

User Interface Impact: No

Steps to Reproduce:

  1. Login as an administrator.
  2. Click on the Administration Workspace tab.
  3. Select Dynamic Evidence under Rules and Evidence in the shortcut panel.
  4. Click on the New page action button.
  5. Create a new dynamic evidence type using the following details:
    • Evidence Type: MyTestEvidence
    • Logical Name: MyTestEvidence
    • Effective From: 1/1/1900
    • Security Group: SAMPLE_INCOME_GROUP
  6. Click the toggle to expand the newly created MyTestEvidence evidence type.
  7. From the inline row-level action menu, choose Edit Metadata to launch the external Dynamic Evidence Editor.
  8. In the editor, add 4 data attributes as follows: attribute1, attribute2, attribute3, attribute4.
  9. Click the General tab, and set the option Correction Only to True.
  10. Click the Validations tab, and add a new validation with the following details:
    • Validation Type: Dependency
    • First Attribute: attribute3
    • Second Attribute: attribute4
    • Dependency: Must enter second attribute
    • Narrative: If ‘attribute3’ is entered, ‘attribute4’ must also be entered
  11. In the Dynamic Evidence Editor, select User Interface. Add attribute1 and attribute2 to a new cluster and click Save.
  12. Return to the dynamic evidence list and select the Activate row-level action to activate the new dynamic evidence type.
  13. From the row-level action, choose New In Edit Copy and set the Effective From date to 2/1/1900.
  14. Choose Edit Metadata to launch the Dynamic Evidence Editor.
  15. In the editor, remove attribute3 and attribute4. Also remove the dependency validation on attribute3 and attribute4.
  16. Navigate to the dynamic evidence page, and choose Activate from the row-level action menu.
  17. Navigate to Integrated Cases under Case in the shortcuts panel.
  18. Use the New page action to configure a new integrated case.
  19. Click on the hyperlink of the newly created integrated case and select the Evidence tab.
  20. Choose Add Evidence action and link the MyTestEvidence dynamic evidence to the integrated case.
  21. Login as a caseworker.
  22. Register a new Person.
  23. Click the New Case link from the tab actions menu and create an instance of the newly configured integrated case.
  24. Navigate to the Evidence tab.
  25. Add evidence of type MyTestEvidence with a Received Date of 1/1/1900.
  26. Choose Save.
  27. Click In-Edit evidence from the Page Group Navigation Bar.
  28. Modify the evidence and change the received date to 2/1/1900 and save.
  29. Issue: The following error is presented to the user, 'An un-handled server exception occurred. Please contact your administrator.'


The un-handled server exception has been resolved. Now the issue that was causing the retrieval of incorrect validations when the version of dynamic evidence being used was changed has been fixed.

WorkItem:278129 - 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:


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.


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.

Application Development Environment

Client Development Environment


PO08832, WorkItem:278128 - The Close all tabs button does not always close all the application tabs that are opened

Issue Description:

In the Internet Explorer 11 browser, the Close all tabs button, which is supposed to close all application tabs that are open in the caseworker application, does not always work as intended. If there is more than one application tab open or if the Close all tabs button is selected from a tab whose content is not currently displayed, some of the tabs may remain open.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a caseworker using the Internet Explorer 11 browser.
  2. Open three application tabs.
  3. Right click on a tab whose content is not currently displayed.
  4. Select Close all tabs.
  5. Issue: Only the application tab that was clicked is closed.


This issue was resolved by updating the JavaScript executed when Close all tabs is selected.


The following file has been changed:


Cúram Modules

Provider Management

Provider Management

PO09081, WorkItem:278127 - 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.


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


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:

Known Issues

See the Known Issues section in the release notes.


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:


Operating system(s):

Linux, Windows

Modified date:

29 June 2022