Merative Social Program Management 7.0.10.0 iFix9

Release Notes

Abstract

Merative Social Program Management 7.0.10.0 iFix9 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 iFix9 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/curam.

Installation

Before 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/spm.

Improvements, Resolved Issues and Third Party Updates

Cúram Enterprise Framework

Dynamic Evidence

EVIDENCE VALIDATIONS

PO09471, WorkItem:273199 - 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.'

Resolution:

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.

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"