Merative ™  Social Program Management 8.0.1.0 iFix3

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

Release Notes

Abstract

Merative Social Program Management 8.0.1.0 iFix3 Release Notes

Content

Introduction
System Requirements
Download
Installation
Improvements, Resolved Issues, Third Party Updates
Known Issues
Notices

Introduction

Welcome to the Merative Social Program Management 8.0.1.0 iFix3 release.

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

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 https://www.merative.com/support/spm.

Improvements, Resolved Issues, Third Party Updates

Look and Feel
Curam Enterprise Framework
Curam Modules
Third Party Updates

Look and Feel

PO09779, WorkItem:277262 - Form control labels are not displayed when a nested LABEL child element is used

Issue Description:

A form control's label is not displayed on a page or modal if the associated FIELD element in UIM has a nested LABEL child element.

For example, the 'Show Nicknames' label is not displayed for a checkbox form control on the Person Search page if the label is nested.

User Interface Impact: Yes

Prerequisite(s):

• Install Merative Social Program Management from a development installer.
• Locate the file: ../webclient/components/core/Person/Search/Person_searchCriteriaView.vim.
• Find the 'Nickname' field:

<FIELD LABEL="Field.Label.Nickname">
<CONNECT>
  <SOURCE NAME="DISPLAY" PROPERTY="result$dtls$searchWithNicknamesInd" />
</CONNECT>
<CONNECT>
  <TARGET NAME="ACTION" PROPERTY="personSearchKey$nicknameInd" />
</CONNECT>
</FIELD>

• Modify the field so that the LABEL is a child element instead of a FIELD attribute:

<FIELD>
<LABEL>
  <CONNECT>
   <SOURCE NAME="TEXT" PROPERTY="Field.Label.Nickname" />
  </CONNECT>
</LABEL>
<CONNECT>
   <SOURCE NAME="DISPLAY" PROPERTY="result$dtls$searchWithNicknamesInd" />
</CONNECT>
<CONNECT>
   <TARGET NAME="ACTION" PROPERTY="personSearchKey$nicknameInd" />
</CONNECT>
</FIELD>

• Run the client build (build clean client).

Steps to Reproduce:

1. Log in as a caseworker.
2. Navigate to 'Cases and Outcomes', expand the 'Shortcuts' panel and select 'Searches'.
3. Click 'Person' to open the 'Person Search'.
4. Issue: The 'Show Nicknames' label for the checkbox on the Person Search page is not displayed.

Resolution:

The JSP generator has been updated so that a label that is associated with a form control on an application page or modal is correctly displayed when a FIELD element has a nested LABEL element in UIM.
 

PO09812, WorkItem:277300 - Date picker content is partially hidden making it difficult to select a date value

Issue Description:

When you open a date picker that is positioned at the end of a modal window, the calendar expands but the dates at the end of the modal are not displayed.

Scrolling is required to select the hidden dates but the calendar in the date picker closes when you click the scroll bar. To select a date, you must scroll down by using the track pad or the wheel on the mouse, or tab into the widget and use the arrow keys.

User Interface Impact: Yes

Steps to Reproduce:
 

1. Log in as a caseworker.
2. Register a Person.
3. Create a Social Assistance case.
4. Navigate to the Evidence tab and add new Dividends evidence.
5. Select the date widget on the 'New Dividends Evidence' modal.
6. Issue: The date picker expands but the content is partially hidden. Scrolling is required to select some of the dates but the date picker closes when the scroll bar is clicked.

Resolution:

Now, when the calendar in the date picker opens, all the days from that month are visible and available to be selected without the need to scroll.

Curam Enterprise Framework

Administration Suite

PO09703, WorkItem:277263 - Third-party address lookup services cannot access information from dropdowns in address fields

Issue Description:

Incorrect address evidence can be created where custom screens that use a third-party address lookup service cannot access data from dropdowns in address fields.

User Interface Impact: No

Prerequisites:

A third-party address lookup service and an Merative Social Program Management custom person registration screen that calls the lookup service and populates the results.

Steps to Reproduce:

1. Log in as a caseworker.
2. Navigate to 'Cases and Outcomes', expand the 'Shortcuts' panel and select 'Registration'.
3. Click 'Person' to open the 'Register Person' modal.
4. Use the address lookup service to collect the address to be populated.
5. Issue: The address fields are not populated on the person registration screen when the address is selected.

Resolution:

Two functions are now available in the 'curam.util.Dropdown' JavaScript module to support an update to the selected value of an address dropdown by a third-party address lookup service.

WorkItem:277265 - Hook point to support drag-able modals

Issue Description:

Currently in Merative Social Program Management Version 8, the Carbon Design System does not allow the modal windows to be moveable.

User Interface Impact: No

Steps to Reproduce: N/A

Resolution:

A new JavaScript file called webclient/components/core/WebContent/CDEJ/jscript/curam/application/modal/ModalHooks.js is available to allow the implementation of custom functionality to make modal windows moveable. The function enableDraggableModals(modalRoot) can be implemented within the custom component copy of this file. The modalRoot node of the modal is available within this function and can be updated to implement the required behaviour. One of the most common ways to do this is to use event listeners that listen for users dragging the modals and update the position of node using the style attribute.

Administration Suite

Case Audits

CASE AUDITS

PO09795, WorkItem:277273 - When an audit coordinator tries to assign a case audit, action buttons disappear from the modal dialog

Issue Description:

When an audit coordinator tries to assign a case audit by selecting the ‘New Auditor’ or ‘New Audit Team’ button, all the available buttons disappear from the 'Assign Case Audits' modal dialog.

User Interface Impact: Yes

Prerequisite(s):

1. Log in as an Administrator.
2. Create new Case Audit Configuration from Case Audits menu item on the Shortcuts panel.
3. Select following values on the modal dialog -

• Case audit type as Integrated Case
• Default Algorithm
• Check "Allow Audit Coordinator to specify cases for audit"
• Integrated Case Dynamic Query
• Any available Focus Area

Steps to Reproduce:

1. Log in as an Audit Coordinator.
2. Create an Audit Plan from the New Audit Plan Shortcuts menu item.
3. Select any of the available mandatory values.
4. Navigate to 'My Audit Plans' list page and select the audit plan created above.
5. Add a Schedule to Audit Plan by using Add Schedule tab level action menu.
6. On the modal dialog select any End Date in the future.
7. Open the Page Actions menu from Home tab of the Case Audit Plan and Generate Random Case Sample.
8. On the Criteria screen of the 'Generate Random Case Sample' modal, select a 'Start Date From' value which is a year in the past.
9. Enter 100 as the value for Percentage field on next screen, use default for the rest of the wizard and click Finish.
10. Navigate to the Case Audits Tab and click on Assign Case Audits Link to open Assign Case Audits dialog.
11. Click the 'New Auditor' or 'New Audit Team' button.
12. Issue: All the buttons disappear from the modal dialog.

Resolution:

The ‘New Auditor’ and ‘New Audit Team’ buttons do not disappear from the screen and the audit coordinator can now successfully assign a case audit to a new auditor or audit team.

Curam Modules

Universal Access

Universal Access

WorkItem:273073 - corrupted PDF Generated for Insurance Affordability Application submitted by hcrcaseworker when PDF Summary Template enabled

Issue Description:

Previously, the summary PDF template configuration enabled summary PDF generation for all scripts without any exclusions. As a result, invalid PDFs were generated for nonsupported IEG scripts that contained nonsupported conditions as listed at https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation. For example, a corrupt PDF document was generated for the Insurance Affordability application IEG script because the script does not support summary PDF generation.
By default, the Insurance Affordability application IEG script is now excluded from summary PDF generation through a new curam.intake.pdftemplate.iegsummarypagelayout.scriptexcludelist environment variable. The environment variable defines a list of scripts to be excluded from summary PDF template generation, if a summary PDF template is configured.
For more information about summary PDF template configuration, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

User Interface Impact: Yes

Steps to Reproduce:

1. Enable the new PDF Summary template as documented in https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation
2. Submit an application for Insurance Affordability with minimum data.
3. Click Administration > Attachments and download the PDF that is generated as part of the application case creation.
4. Issue: Observe that a corrupted PDF document is generated.

Resolution:

This issue is now resolved and the old data store PDF template is used to generate PDF documents for Insurance Affordability applications when a summary PDF template is configured.

Third Party Updates

WorkItem:276506 - [Security] Update the Google gson JAR file to the latest version

Google Gson is a Java library that can be used to convert Java Objects into their JSON representation. It can also be used to convert a JSON string to an equivalent Java object. A number of areas in the Social Program Management (SPM) product utilize this library. These include Advanced Evidence Sharing (AES) administration screens, the Timeline Calendar and the Smart Navigator feature.

The version of the Google Gson library has now been updated from 2.2.2 to 2.8.9. The new version contains some defect fixes and minor enhancements. As a result of this upgrade, the following changes have been made in the SPM deliverable.

• EJBServer/components/core/lib/gson-2.2.2.jar - old JAR removed.
• EJBServer/components/core/lib/gson-2.8.9.jar - new JAR added.

It should be noted that any references in custom scripts and other artifacts to the updated JAR files listed above should be updated.

WorkItem:276615 - [Security] 8.0.1.0_iFix3 Update the versions of the Jackson JARs to the latest version - 2.13.1

The Jackson API contains multiple functions to read and build JSON using Java.
It has very powerful data binding capabilities and provides a framework to serialize custom Java objects to JSON strings and deserialize JSON strings back into Java objects.
The Java Development Environment (JDE) and the REST infrastructure utilizes these utilities.

The versions of these JARs have now been updated from version 2.12.1 to version 2.13.1. As a result of this upgrade, the following changes have been made in the JDE and REST deliverables.

  CuramSDEJ\lib\third_party_version.properties - the versions of the specified Jackson JARs have been updated.

  CuramSDEJ\lib\jackson-annotations-2.13.1.jar - new JAR added.
  CuramSDEJ\lib\jackson-core-2.13.1.jar - new JAR added.
  CuramSDEJ\lib\jackson-databind-2.13.1.jar- new JAR added.
  CuramSDEJ\lib\version-jackson-datatype-jdk8-2.13.1 - new JAR added.
  CuramSDEJ\lib\version-jackson-dataformat-yaml-2.13.1 - new JAR added.

  CuramSDEJ\lib\jackson-annotations-2.12.1.jar - old JAR removed.
  CuramSDEJ\lib\jackson-core-2.12.1.jar - old JAR removed.
  CuramSDEJ\lib\jackson-databind-2.12.1.jar- old JAR removed.
  CuramSDEJ\lib\version-jackson-datatype-jdk8-2.12.1 - old JAR removed
  CuramSDEJ\lib\version-jackson-dataformat-yaml-2.12.1 - old JAR removed.

  CuramCDEJ\lib\ext\jar\jackson-annotations-2.13.1.jar - new JAR added.
  CuramCDEJ\lib\ext\jar\jackson-core-2.13.1.jar - new JAR added.
  CuramCDEJ\lib\ext\jar\jackson-databind-2.13.1.jar - new JAR added.
  CuramSDEJ\lib\version-jackson-datatype-jdk8-2.13.1 - new JAR added.
  CuramSDEJ\lib\version-jackson-dataformat-yaml-2.13.1 - new JAR added.

  CuramCDEJ\lib\ext\jar\jackson-annotations-2.12.1.jar - old JAR removed.
  CuramCDEJ\lib\ext\jar\jackson-core-2.12.1.jar - old JAR removed.
  CuramCDEJ\lib\ext\jar\jackson-databind-2.12.1.jar - old JAR removed.
  CuramSDEJ\lib\version-jackson-datatype-jdk8-2.12.1 - old JAR removed
  CuramSDEJ\lib\version-jackson-dataformat-yaml-2.12.1 - old JAR removed.

  EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-annotations-2.13.1.jar - new JAR added.
  EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-core-2.13.1.jar - new JAR added.
  EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-databind-2.13.1.jar - new JAR added.

  EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-annotations-2.12.1.jar - old JAR removed.
  EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-core-2.12.1.jar - old JAR removed.
  EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-databind-2.12.1.jar - old JAR removed.

  EJBServer\components\Rest\restlib\dependencyLibsCore\jackson-jaxrs-base-2.13.1.jar - new JAR added.
  EJBServer\components\Rest\restlib\dependencyLibsCore\jackson-jaxrs-json-provider-2.13.1.jar - new JAR added.
  EJBServer\components\Rest\restlib\dependencyLibsCore\jackson-module-jaxb-annotations-2.13.1.jar - new JAR added.

  EJBServer\components\Rest\restlib\dependencyLibsCore\jackson-jaxrs-base-2.12.1.jar - old JAR removed.
  EJBServer\components\Rest\restlib\dependencyLibsCore\jackson-jaxrs-json-provider-2.12.1.jar - old JAR removed.
  EJBServer\components\Rest\restlib\dependencyLibsCore\jackson-module-jaxb-annotations-2.12.1.jar - old JAR removed.

GraphQL jars:

  CuramSDEJ\lib\version-jackson-datatype-jdk8-2.13.1 - new JAR added.
  CuramSDEJ\lib\version-jackson-dataformat-yaml-2.13.1 - new JAR added.

  CuramSDEJ\lib\version-jackson-datatype-jdk8-2.12.1 - old JAR removed
  CuramSDEJ\lib\version-jackson-dataformat-yaml-2.12.1 - old JAR removed.

Note that any references in custom scripts and other artifacts to the updated JAR files listed above must be updated.

Known Issues

See the Known Issues section in the 8.0.1.0 release notes.

Notices

Before using this information and the product it supports, read the information in "Notices"