Merative ™ Social Program Management 7.0.6.0 iFix2

 

 

 

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

 

 

 

Release Notes

 

 

Abstract

 

Merative Social Program Management 7.0.6.0 iFix2 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.6.0 iFix2 release.

 

This is a cumulative release which incorporates the Improvements, Resolved Issues and Third Party Updates contained in all previous 7.0.6.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 https://www.merative.com/support/spm.

 

 

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.

 

You can download the appropriate version of the Merative Social Program Management Upgrade Helper from https://www.merative.com/support/spm.

 

 

Improvements, Resolved Issues and Third Party Updates

 

Cúram Enterprise Framework
Cúram Modules
Solutions

 

Cúram Enterprise Framework

 

Application Development Environment

 

Application Development Environment

 

Client Development Environment

 

CLIENT DEVELOPMENT ENVIRONMENT

 

Look & Feel

 

PO08577, WorkItem:261852 - Date selector displays a duplicate date in the month where the clock goes back one hour for daylight saving

 

Issue Description:

 

The Date Selector displays a duplicate date in the month where the clock goes back one hour as part of daylight savings time adjustments. The date that is duplicated varies depending on the time zone of the client machine.

 

User Interface Impact: No

 

Steps to Reproduce:

 

  1. Ensure the time zone on the client machine is set to EST (New York).
  2. Login as a caseworker.
  3. Navigate to the Person Search page.
  4. Select the Date Selector icon beside the Date of Birth field.
  5. Navigate to November.
  6. Issue: A duplicate date occurs after the first Sunday of the month.
  7. Ensure the time zone on the client machine is set to GMT (Dublin).
  8. Login as a caseworker.
  9. Navigate to the Person Search page.
  10. Select the Date Selector icon beside the Date of Birth field.
  11. Navigate to October.
  12. Issue: A duplicate date occurs after the last Sunday of the month.

 

Resolution:

 

This issue has been resolved by updating the underlying JavaScript around the Date Selector to correctly handle daylight savings time.

 

Technical:

 

The following file was updated to resolve this issue

 

  • ../CuramCDEJ/lib/curam/web/jscript/curam/dateSelectorUtil.js

 

The logic for rendering the Calendar was continually adding 24 hours to calculate each day of the month. When Daylight Savings Time ends, the clock goes backward and creates a 25 hour day. This caused the Calender to insert the same day twice, as adding 24 hours was not enough time to advance to the next day. This has been updated to instead add 1 day to the JavaScript Date object which automatically handles Daylight Savings Time.

 

LOOK & FEEL

 

PO08539, WorkItem:261850 - Printing a context panel results in overlapping text and images, misaligned fields and loss of data on the printed page

 

Issue Description:

 

In Merative Social Program Management (SPM) version 7, printing a context panel results in large amounts of overlapping text and images, misaligned fields and loss of data on the printed page. The issue occurs for multiple case and participant types.

 

User Interface Impact: No

 

Steps to Reproduce:

 

Scenario1:

 

  1. Login as an Income Support caseworker.
  2. Register a Participant.
  3. Create a Food Assistance application for this participant and when asked to add additional household members, answer 'Yes' and add a child.
  4. Complete the application.
  5. Open the application case for the member.
  6. Click the print icon on the page.
  7. Issue: Printing the context panel results in overlapping text and images, misaligned fields and loss of data on the printed page.
  8. Resolve any pending evidence issues and verify any outstanding verifications.
  9. Check participant is eligible for Food Assistance.
  10. Authorize the result from the Review Eligibility Result modal.
  11. Open Food Assistance case.
  12. Click the print icon on the page.
  13. Issue: Printing the context panel results in overlapping text and images, misaligned fields and loss of data on the printed page.

 

Scenario 2:

 

  1. Login as a caseworker.
  2. Register an Employer.
  3. Open the registered employer.
  4. Click the print icon on the page.
  5. Issue: Printing the context panel results in overlapping text and images, misaligned fields and loss of data on the printed page.

 

Scenario 3:

 

  1. Login as an Insurance Affordability caseworker.
  2. Register a Participant.
  3. Create an Insurance Affordability case for this participant.
  4. Open the registered Insurance Affordability case.
  5. Click the print icon on the page.
  6. Issue: Printing the context panel results in overlapping text and images, misaligned fields and loss of data on the printed page.

 

Resolution:

 

The CSS style related to printing context panels has been updated to address the large amounts of overlapping text and images, misaligned fields and loss of data on the resulting printed page.

 

Cúram Modules

 

Universal Access
Evidence Broker

 

Universal Access

 

PO08796, WorkItem:260632 - Intelligent Evidence Gathering Rest APIs in SPM version 7.0.6 IFix1 are not compatible with versions of the Universal Access Web App on v2.6.0

 

Issue Description:

 

The 2.6.0 version of the Universal Access Web App does not work with the 7.0.6 SPM Version.

 

User Interface Impact: No

 

Steps to Reproduce:

 

  1. Install a system with SPM v7.0.6.x and UA 2.6.0.
  2. Try to use the Universal Access Web App.
  3. Issue: Errors are displayed to the user in the Web App.

 

Resolution:

 

Incompatibilities between the Web App and SPM were resolved by iFix2.

 

Evidence Broker

 

PO08711, WorkItem:257517 - When evidence is shared as a correction, the associated proof is not shared to the target case

 

Issue Description:

 

Caseworkers may make updates to incorrect evidence to correct the data. The system recognizes that the update was a correction to the data. When a verified evidence record is shared as a correction, the proof that is associated with the verification is not shared. This results in an outstanding verification against the shared evidence.

 

User Interface Impact: No

 

Prerequisite(s):

 

  1. Login as an administrator.
  2. Navigate to Evidence Sharing under Rules and Evidence in the shortcuts panel.
  3. Add a new evidence sharing configuration with the following details:
    • Select Income Support as the source and Income Support as the target; and Integrated Case as both the source type and the target type.
    • Select the evidence type Unearned Income.
    • Share Verifications = Always, Trusted Source = Yes.

 

Steps to Reproduce:

 

  1. Login as an Income Support caseworker.
  2. Register a person and create an Income Support integrated case.
  3. On the integrated case create Unearned Income with an amount of 100. Verify the outstanding verification and apply changes.
  4. Submit an Income Support application with Unearned Income with an amount of 200. Verify the outstanding verification and apply changes.
  5. Navigate to the Income Support application incoming evidence page and expand Unearned Income.
  6. From the Existing Evidence actions menu select 'Update with Incoming' and choose to do a Correction. Apply changes.
  7. Navigate to the Income Support application active evidence page and update the Unearned Income to have an amount of 300.
  8. Verify the outstanding verification and apply changes.
  9. Navigate back to the original integrated case.
  10. Issue: The Unearned Income has been corrected and has the new value of 300, but the proof has not been shared and the verification has a status of Not Verified.

 

Resolution:

 

This issue has been resolved. Any proof associated with evidence that is shared as a correction will now correctly share to the target case and the evidence will remain verified.

 

Technical:

 

When sharing verifications with corrections or successions, the system references the sharedInstanceId on the evidence descriptors to determine if proof should be shared to the target case. The logic responsible for handling these actions was not correctly setting the sharedInstanceId on the target case. As a result, when proof was being shared, the sharedInstanceId's did not match and the verification was left as unverified. This has been updated and the correct sharedInstanceId is now being used and associated proof will correctly share.

 

PO08655, WorkItem:261885 - Verifications do not share when sharing evidence which is logically equivalent

 

Issue Description:

 

Logically Equivalent sharing is configured between two evidence types, with verifications configured to share with the evidence. After a caseworker verifies evidence of this type, the evidence shares to the target case as expected but the verifications do not share with the evidence.

 

User Interface Impact: No

 

Prerequisite(s):

 

  1. A logically equivalent sharing configuration exists from Disability on an Income Support integrated case to Disability on an Insurance Affordability integrated case with the sharing rules uploaded in an appropriate XML file. Also, Trusted Source is set to Yes and Share Verifications is set to Always.
  2. Verifications are configured against both types of Disability evidence.
  3. Both verifications are satisfied with the same Verification Items.

 

Steps to Reproduce:

 

  1. Login as an Income Support caseworker.
  2. Register a person and create an Income Support integrated case.
  3. Create Disability evidence and add proof to satisfy the outstanding verification.
  4. Apply Changes.
  5. Login as an Insurance Affordability caseworker.
  6. Submit an application for the previously created person.
  7. Authorize the application.
  8. Navigate to the Verifications tab on the newly created Insurance Affordability integrated case.
  9. Issue: The Disability evidence has been shared to the case, but it has an outstanding verification against it.

 

Resolution:

 

This issue has been resolved by updating logic to correctly identify when different evidence types use the same Verification Items to satisfy outstanding verifications on them.

 

Technical:

 

The logic responsible for sharing verifications checked to see if the same Verifiable Data Item was configured against the source and target evidence. If they matched the verification would be shared. As verifications are configured separately against each evidence type, for logically equivalent sharing, the source verifiable data item and target verifiable data item would never match and the proof would never be shared.

 

The logic has been extended to now check if the Verification Item provided on the source evidence is configured against the target. If it is, then the proof will be shared to the target case to satisfy the outstanding verification.

 

PO08698, WorkItem:262019 - Verifications are not being shared when evidence is added to a target case from the Incoming Evidence page

 

Issue Description:

 

As part of configuring evidence to share, an administrator has the option of determining if verifications associated with the evidence should be shared. Evidence which has been configured to share its verifications and verifications exist on the source case for that evidence. When the evidence is shared and appears on the Incoming Evidence page of a target case, adding the evidence on the target case does not result in the verification also being added to the target case for that evidence.

 

User Interface Impact: No

 

Prerequisite(s):

 

Configure evidence sharing for any evidence type that requires a verification from Integrated Case A to Integrated Case A with Trusted Source set to No and Share Verifications set to Always.

 

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Register a Person and create two integrated cases.
  3. Navigate to the first integrated case and add the evidence that was configured for sharing.
  4. Add proof to satisfy the outstanding verification and apply changes.
  5. Navigate to the Incoming Evidence page on the second integrated case.
  6. Expand the incoming evidence and select Add to Case from the actions menu.
  7. Navigate to the In-edit evidence page.
  8. Issue: The evidence added from the Incoming Evidence page does not have a verification associated with it.

 

Resolution:

 

This issue has been resolved. When evidence is added to a case from the Incoming Evidence page, the system will now correctly copy across the associated verification items and add them to the target case as expected.

 

Solutions

 

Income Support

 

Income Support

 

WorkItem:262021 - New hook point to support cascading eligibility between non-MAGI and MAGI programs.

 

Issue Description:

 

A new hook point has been introduced to allow for custom persistence of eligibility data on new and changed Income Support decisions to support cascading eligibility between Income Support and HCR; ISMedicaidEligibility evidence is no longer created by the system.

 

See attached guide - Guide_Cascade_NonMagiToMagi_v1.2.pdf for details of the new hook point and guidance on implementing cascading eligibility.

 

 

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".

 

 

Guide_Cascade_NonMagiToMagi_v1.2.pdf

 

This PDF file summarizes the details of the new hook point and provides guidance on implementing cascading eligibility

Document Information

 

More support for:

Merative Social Program Management

 

 

Software version:

7.0.6

 

 

Operating system(s):

Linux, Windows

 

 

Modified date:

09 July 2020