Merative ™ Social Program Management 8.0.2.0 iFix2

Release Notes

Abstract

Merative Social Program Management 8.0.2.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 8.0.2.0 iFix2 release.

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

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 you run the installer, ensure that 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/curam.

Improvements, Resolved Issues, Third Party Updates

Look and Feel

PO09810, WorkItem:278380 - Passive modal dialogs can display buttons when opened from a modal dialog

Issue Description:

If a passive modal dialog (a modal dialog with no action controls), is opened from another modal dialog in the application, it incorrectly shows buttons from the previous modal dialog. Users can get confused and think that the buttons can be used in the new context.

**User Interface Impact: **No

Steps to Reproduce: N/A

Resolution:

The buttons are now hidden as expected in passive modal dialogs that open from a modal dialog in the application.

Curam Enterprise Framework

CLIENT DEVELOPMENT ENVIRONMENT

Widgets

PO09838, WorkItem:278376 - Custom search page with multiple searches display all of the search result counts on the first search list

Issue Description:

Custom search pages with multiple searches display all of the search result counts on the first results list instead of displaying separate counts for each result list on the page. The search result count needs to be displayed on each results list to give the user context.
**User Interface Impact: **No

Prerequisite(s):

1. Set LIST_ROW_COUNT to be true in the curam-config.xml configuration file.
2. Customize Person_search1.uim and Person_search1.properties to have more than one LIST element.
3. Rebuild and deploy the application.

Steps to Reproduce:

1. Log in as a caseworker.
2. Navigate to Person under Searches in the Shortcuts panel.
3. Search for an existing person (using search criteria such as Last Name).
4. Issue: The first set of search results shows '(Number of Items: X)' twice, where X is the number of items in the list.

Resolution:

The search result count is displayed separately on each list which helps provide appropriate context to the user.

Technical:

When LIST_ROW_COUNT is configured in the application and when multiple lists are present on a page, the page correctly displays the search result count on each list separately.

DT036247, WorkItem:278382 - Spinner disappears after 15 seconds even if the associated activity has not completed

Issue Description:

The process spinner disappears after 15 seconds even if the associated activity has not completed indicating to the user that the process had finished when it is actually still running.
**User Interface Impact: **No

Prerequisite(s):

1. Identify a process (for example a particular person search ) that requires more than 15 seconds for the server to complete.

Steps to Reproduce:

1. Log in as a Caseworker.
2. Navigate to Cases and Outcome, open the person search by expanding the short cut panel and selecting Person under Searches.
3. Enter the search criteria that will start the process identified in the Prerequisite, e.g. Last Name 'Smith'.
4. Issue: The progress spinner disappears after 15 second giving no indication to the user that the process is still running.

Resolution:

The progress spinner no longer terminates after 15 seconds.

Technical:

The maximum spinner timeout period can be increased by setting the curam.progress.widget.timeout.max property to an appropriate value in the ApplicationConfiguration.properties file. The default spinner maximum timeout period is 90000 (90 seconds).

DT036254, WorkItem:278385 - Claim Representatives page not loading due to JSP Scriptlet page tag

Issue Description:

The Create Claim Representatives page does not finish loading correctly, preventing user input.

No.

Steps to Reproduce:

1. Log on as Claim worker.
2. Navigate to Cases and select New Case.
3. Search for and select a registered person (for example John Smith).
4. Enter the values to create the claim.
5. On the claim home page select Case Summary and then Case Representatives and click New.
6. Select Case Participant (John Smith) and click Next.
7. Issue: The page does not finish loading correctly preventing user input.

Resolution:

The Create Claim Representatives page now loads correctly.
Technical:

In the Workers Compensation component, WCO_createClaimRepresentatives.uim uses a JSP_SCRIPTLET tag, which has been updated to correctly render on pages where it is configured in UIM. The page now loads correctly.

WIDGETS

PO09836, WorkItem:278377 - The progress spinner is not displayed when fetching search results

Issue Description:

When you click a Search button on a modal or wizard to search for data in the system, the progress spinner is not displayed to indicate that the search is in progress.

**User Interface Impact: **No

Steps to Reproduce:

1. Log in as a caseworker.
2. Navigate to Person under Searches in the Shortcuts panel.
3. Enter some search criteria into the fields provided in the form.
4. Click the Search button.
5. Issue: A progress spinner does not display as expected while the system fetches the data to populate the search results.

Resolution:

When a Search button on a modal or wizard is clicked to search for data in the system, the progress spinner is displayed to indicate that the search is in progress.

PO09817, WorkItem:278378 - A button is displayed as a link where an ACTION_CONTROL has a nested CONDITION element

Issue Description:

A button in the application is incorrectly displayed as a link if the corresponding ACTION_CONTROL element has a nested CONDITION element.

For example, when a conditional Cancel button on a modal dialog is configured in UIM/VIM with a nested CONDITION element on an ACTION_CONTROL element that does not have TYPE="SUBMIT", it is not displayed correctly to the user.
**User Interface Impact: **No

Prerequisite(s):

1. RegisterPerson_duplicateCheckForPDCWizard.uim is customized to have a Cancel button ACTION_CONTROL element that is a nested CONDITION element.

Steps to Reproduce:

1. Log in as a caseworker.
2. Navigate to and open the person registration wizard.
3. Issue: The Cancel action button is displayed as a link.

Resolution:

The button is correctly displayed on the customized page.

Technical:

The infrastructure that generates JavaServer Pages from UIM has been updated. A button on a modal dialog is now correctly rendered when the associated ACTION_CONTROL element has a nested CONDITION child element.

PO09827, WorkItem:278379 - Incorrectly entered dates are converted to random dates in the application

Issue Description:

When a user manually enters an incorrect date value into a date field on a form in the application, a seemingly random date is displayed.

User Interface Impact: No

Steps to Reproduce:

1. Log in as a caseworker.
2. Navigate to Person under Registration in the shortcuts panel.
3. Manually enter an incorrect date into the Date of Birth field on the first step of the Register Person wizard.
4. Click the Search button.
5. Issue: An incorrect random date is generated and displayed in the field when the search is being done in the system.

Resolution:

When a user manually enters an incorrect date into a form within the application, an error message now notifies them that an incorrect date was entered. Users can enter a new date by clearing the incorrect date and manually entering the correct date.

PO09775, WorkItem:278381 - The date picker is unnecessarily opened when certain modal dialogs open

Issue Description:

The date picker is activated by default when you open a modal dialog where the first field accepts a date value. The open date picker can block some of the modal dialog content that the user needs to see.
User Interface Impact: No

Steps to Reproduce:

1. Log in as a caseworker.
2. Register a new Person.
3. On the Evidence tab for the person, select New to add email address evidence.
4. Issue: When the New Email Address modal dialog opens, the date picker for the Received Date field opens and blocks some content on the modal dialog.

Resolution:

When a user opens a modal dialog that has the date picker form control as the first field, the focus now goes to the modal dialog body instead of the first input field.

DT036263, WorkItem:278384 - Time Widget clears manually entered time values on pressing Tab

Issue Description:

When a user manually enters a time into the time widget in the new Activity Modal and presses Tab, the value entered is cleared and a place holder text displayed.

**User Interface Impact: **No.

Steps to Reproduce:

1. Login as a Caseworker.
2. Navigate to the Calendar.
3. Select New activity from the page level action menu.
4. In the New Activity modal, navigate to the time widget by pressing the Tab keyboard navigation key.
5. Manually enter a value from the time drop down list (For example 00:00, 00:30, 01:00, 01.30 ...)
6. Press the Tab key to move to the next input field.
7. Result: the entered time value is erased and the placeholder HH:mm is displayed

Resolution:

The time is now set correctly when a user enters a value manually and presses the Tab keyboard navigation key.

Curam Modules

Universal Access

WorkItem:278264 - Corrupted PDF generated for Insurance Affordability applications submitted online in the caseworker application when PDF Summary Template enabled

Issue Description:

A PDF summary template can be configured for use in creating PDF documents that are generated when an application is submitted. When the PDF summary template configuration is enabled, it is used for the generation of a PDF document for all scripts, without any exclusions. As a result, invalid PDFs are generated for unsupported IEG scripts that contain unsupported conditions as listed at https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation. For example, a corrupt PDF document is generated for the Insurance Affordability application IEG script because the script does not support summary PDF generation.

**User Interface Impact: **No

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. Log in as an Insurance Affordability caseworker.
3. Register a new person.
4. Submit an application for Insurance Affordability with minimum data.
5. Click on the Administration tab and select Attachments. Download the PDF that is generated as part of the application case creation.
6. Issue: Observe that a corrupted PDF document is generated.

Resolution:

This issue is now resolved and the original data store PDF template is used to generate PDF documents for Insurance Affordability applications that are submitted in the online application when a summary PDF template is configured.

By default, the Insurance Affordability application IEG script is excluded from summary PDF generation through a new environment variable, 'curam.intake.pdftemplate.iegsummarypagelayout.scriptexcludelist'. The environment variable defines a list of scripts to be excluded from summary PDF template generation if a PDF summary template is configured.

Solutions

Child Welfare

WorkItem:278383 - Save and Cancel buttons disappear from the New Petition modal

Issue Description:

When a Child Welfare caseworker creates a new legal action but incorrectly populates the Participant and Respondent fields as the same person, the Save and Cancel buttons disappear from the New Petition modal.

**User Interface Impact: **No

Prerequisite(s):

1. Legal Actions are configured.

Steps to Reproduce:

1. Log in as a Child Welfare caseworker.
2. Register a person and create an Ongoing Case.
3. Open the ongoing case and navigate to the Legal tab.
4. Select Legal actions and then click New.
5. The New Legal Action modal is displayed.
6. Select 'Petition' for the Legal Category and 'Petition to Transfer' for the Legal Action and click the Next button.
7. Complete the mandatory fields and select the same person as participant and respondent and click on save. For example, select James Smith for both Participant and Respondent fields.
8. Issue: The buttons on the modal will disappear from view and the only resolution is to start the task of creating a New Legal Action again.

Resolution:

The Save and Cancel buttons do not disappear from the New Petition modal when a new legal action is being created.

Third Party Updates

WorkItem:278409 - Update to the latest version of the Rampart Axis 2 security library - esapi

Merative Social Program Management web services are based on Apache Axis2. With the Rampart security module of Axis2, Social Program Management web services can be secured for authentication, integrity (signature), confidentiality (encryption/decryption), and non-repudiation (timestamp).

The version of one of the JAR files in Rampart has been updated. As a result of this update, the following changes have been made in the JDE Axis 2 deliverable.

• CuramSDEJ\lib\axis2\esapi-2.4.0.0.jar - version updated from 2.2.3.1 to 2.4.0.0.

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

Known Issues

See the Known Issues section in the 8.0.2.0 release notes.

Notices

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