Merative ™ Social Program Management 7.0.4.0 Refresh Pack

Release Notes

Abstract

Merative Social Program Management 7.0.4.0 Refresh Pack Release Notes

Content

Important Note

Introduction

System Requirements
Download
Pre-Installation Steps
Installation
Post-Installation Steps
Improvements, Resolved Issues and Third Party Updates
Known Issues
Notices

Important Note

Merative Social Program Management 7.0.4.0 is a Refresh Pack.

Introduction

Welcome to the Merative Social Program Management 7.0.4.0 Refresh Pack release. Read this document to find important installation information, and to learn about product improvements and resolved issues in this release.

This 7.0.4.0 Refresh Pack release also includes new Enhanced Universal Access functionality

For detailed information about these optional new features, see the What's new in Version 7.0.4.0 Refresh Pack topic in the product documentation.

For more information about version 7.0.4.0 Refresh Pack, see the full product documentation in Product documentation and PDFs.

For the latest version of the release notes, see https://curam-spm-devops.github.io/wh-support-docs/spm/release-notes.

A CSV file is attached at the end of this document, which summarizes these release notes.

This 7.0.4.0 Refresh Pack release incorporates content from previous 7.0.X releases, which is documented separately in the following online release notes:

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

Pre-Installation Steps

WorkItem:230244 - Pre-Installation Step for Smart Navigator Component

You must add the SmartNavigator component to the Components List.

Before running the installer, add the following to the InstalledComponents.xml, in the /IBM/Curam/Development/Installer folder:

<component version="IntelligentSearch" name="SmartNavigator" packName="Smart Navigator" />

Installation

This 7.0.4.0 Refresh Pack release can be installed on top of the following Merative Social Program Management releases:

Prior to running the 7.0.4.0 Refresh Pack 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.

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.

Post-Installation Steps

WorkItem:230246 - Post-Installation Step for Smart Navigator Component

You must add the SmartNavigator Component to the Components Order.

For the SetEnvironment.sh or SetEnvironment.bat, add SmartNavigator as the last component to Server/Client component Order.

For the deployment_packaging.xml, add SmartNavigator, as the second last component (core component should be last), for the Merative Social Program Management ear.

Improvements, Resolved Issues and Third Party Updates

Third Party UpdatesCúram Enterprise Framework
Cúram Modules
Solutions

Third Party Updates

Workitem:227965 - Introduce support for the Extended Data Types feature of the Oracle Database

Beginning with Oracle Database 12c, you can specify a maximum size of 32767 bytes for the VARCHAR2 data type. You can control whether your Oracle database supports this new maximum size by setting the initialization parameter MAX_STRING_SIZE to enable the Extended Data Types feature. Please refer to the relevant Oracle documentation for information on how to set this feature, utilize it and also some caveats which you must be aware of when using this feature.

Merative SPM now supports the usage of the Oracle Extended Data Types feature.

Note that care should be taken by customers when using this Oracle feature. The process of switching to use the Oracle Extended Data Types feature is a one-way operation. Once you switch to extended data types you cannot switch back without some form of database recovery. Therefore, extensive regression testing should be performed before this feature is utilized in production environments.

WorkItem:230016 - Upgrade Adobe Flash Player to the latest version

The version of the Adobe Flash Player that has been certified to be used by the Social Program Management (SPM) application has been updated to 30.

WorkItem:230022 - Update Browser Plugins JRE levels used in Microsoft Word Integration.

The following JRE levels for Word Integration are supported for this release:

WorkItem:230030 - Browser Support Update

The following browser versions have been updated and certified for this release:

Case Worker Application Browser Support

Universal Access Application Browser Support

WorkItem:230033 - Update the version of Apple VoiceOver and Chrome for 7.0.4.0 for Apple iPad tablet accessibility

The certified version of Apple VoiceOver has been updated to iOS 11.4. This has been certified against Chrome 68.

Cúram Enterprise Framework

Dynamic Evidence
Integrated Case Management
Application Development Environment

Dynamic Evidence

WorkItem:210535 - The context panel is incorrectly updated when a historic Names evidence is captured and there is a more recent Name for the person

Issue Description

Previously, the context panel was incorrectly updated when a case worker was capturing a historic name change for a person. This occurred where there were multiple changes over time, in the same succession set, for the Names evidence and a more recent name existed for the person than the historic name being captured for them.

This resulted in two problems in the application. Searching for the person, they could only be found by searching on this newly created, historic name, searching by their latest name would not return the person in the search results. Secondly, this issue caused confusion for caseworkers, because the name displayed in the context panel was a name the person was previously known by, not the current name.

The issue resulted from the Alternate Name and Concern Role tables being updated every time a Name was changed. Instead the Alternate Name and Concern Role tables should only be updated when the Name evidence is the latest name for the person.

The scenario below, describes how a participant would potentially have multiple records for Names evidence. A person is registered on the system, and over time there are multiple effective dated changes to the Names evidence. The caseworker will then make an update to an older instance of the Names evidence.

**User Interface Impact: **No

Steps to Reproduce

  1. Register a person named Joan Doe.
  2. Select the Evidence tab, a list of evidence pertaining to Joan is displayed to the user.
  3. Move the system date forward 1 year, for example a date in 2019.
  4. Change Joan’s name, to Joan Bloggs by selecting the “Edit” link in the list action menu.
  5. Effective date the change to the system date. This change will result in a new succession.
  6. To view the list of successions, expand the toggle beside the Names evidence, and click on the ‘Corrections’ tab.
  7. Move the system date forward 1 year, for example a date in 2020.
  8. Change Joan’s name to back to Joan Moon by selecting the “Edit” link in the list action menu.
  9. Effective date the change to the system date. This change will result in a new succession.
  10. There are now three successions for Joan’s Name evidence.
  11. Introduce a fourth succession, however, this new name will be a historic name change.
  12. Select the first succession that ended in 2019.
  13. Change Joan’s name, to Joan Blue by selecting the “Edit” link in the list action menu.
  14. Effective date the change to 10/10/2018. This change will result in a new succession which has been correctly inserted in the first succession.
  15. As a result of the change, the context panel is incorrectly updated with Joan Blue, the name from 2018.

Resolution

This issue has been resolved. When case worker captures a historic name where a more recent name changes exists for that person, the context panel is no longer updated. A new check has been added to the system to ensure that the Concern Role and Alternate Name tables are updated only when the evidence that is being processed is the latest evidence record.

Integrated Case Management

PO07799, WorkItem:231327 - Case Search Performance Issue post v7.0.2 Upgrade

Issue Description:

Release V7.0.2.0 introduced an option to display all clients of type 'primary' or 'member' on the case lists search pages controlled by the property 'Display Case Clients On Case List Pages'. As a result, the case lists search pages were not performing.

User Interface Impact: Yes, when the property Display Case Clients On Case List Pages is true some case lists pages will not have a list of clients populated.

**Steps to Reproduce: **N/A

Resolution:

Now, the changes have been reverted and the pages behave as before. It is recommended to set the primaryclient.display.caselistpages.caseclients to false.

Application Development Environment

Client Development Environment

CLIENT DEVELOPMENT ENVIRONMENT

Widgets

WIDGETS

PO07771, WorkItem:226702 - Microsoft Word documents do not open when using Chrome browser version 65 or later.

Issue Description:

Previously, when a user was using the Chrome browser version 65 or later to create a new Microsoft Word communication, the Word document did not open. However, the File Edit Control Panel dialog remained open.

**User Interface Impact: **No

Steps to Reproduce:

  1. On Chrome 65 browser add in the Chrome Extension.
  2. Install Word Integration assistant from the Merative Social Program Management build you are testing.
  3. Ensure that you have a JRE_HOME system variable and that it points to a valid installed JRE.
  4. Login as superuser and register a person.
  5. Create a Social Assistance and then Employment Benefit Case.
  6. Click on Contact and then on communications.
  7. Create a New Microsoft Word communication.
  8. The word document does not open.

Resolution:

This issue has been resolved. The Word Integration functionality has been updated to be compatible with Chrome browser version 65 and later.

Cúram Modules

Universal Access

Universal Access

PO06859, WorkItem:230678 - In the existing Universal Access application the page theme changed when a user clicked "Submit", and a validation error was thrown

Issue Description:

In the existing Universal Access application, the theme changed from the 'One UI theme' to the 'Internal theme' when a user clicked "Submit", and a validation error was thrown due to incorrect information having been submitted.

**User Interface Impact: **Yes
Steps to Reproduce:

  1. Go to Universal Access application.
  2. Register a user and click on Apply for Benefits.
  3. Select an application (Medical assessment or UA Test application).
  4. Complete the application form and submit.
  5. Click on the Person Home icon.
  6. Click on the withdraw link.
  7. Fill in the information, without selecting the checkbox, and click on the Submit button.

Resolution:

This issue has been resolved. When the user opts to withdraw the application and does not select the checkbox, the application maintains the same external application theme.

PO06511, WorkItem:230679 - In the existing Universal Access application, the 'Withdraw Application' page was missing the checkbox when printed or when an error is thrown

Issue Description:

In the existing Universal Access application, the checkboxes and radio buttons were missing on the printed page, or when the application was submitted and the user withdrew the application.
User Interface Impact: Yes
Steps to Reproduce:

  1. Go to Universal Access application.
  2. Register a user and click on Apply for Benefits.
  3. Select an application.
  4. Complete the application form and submit.
  5. Click on IBM Curam Universal Access Icon to return to the Universal Access home page.
  6. Click on Apply for Benefits.
  7. Current Applications page will be displayed.
  8. Select the Withdraw link on the application.
  9. Fill in the information and select the check box.
  10. Select Print on the browser.

Resolution:

This issue has been resolved. In the existing Universal Access application, the check boxes and radio buttons are visible on a printed page, or when an application was submitted and the application withdrawn.

Solutions

Income Support
Child Welfare

PO07787, WorkItem:230171 - Documentation update: Automatic addition of program to application case if only one program is configured

Issue Description:

The program documentation does not clarify what occurs when only one program is configured on an application case.

User Interface Impact: No

Steps to Reproduce:

N/A

Resolution:

A statement has been added to the program documentation to clarify that if only one program is configured, this program is automatically added to the application case. For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

Income Support

PO07765, WorkItem:228864 - Issue with RuleSetSnapshotCache memory usage while superseding a CREOLEProgramGroupDetermination

Issue Description:

Previously a large amount of memory was consumed when modifying active evidence.

User Interface Impact: No

Steps to Reproduce:

  1. Create and submit an Insurance affordability application.
  2. Ensure the applicants are eligible for one of the Insurance Assistance programs.
  3. Authorize the application and create a new Integrated Case.
  4. Verify that the Integrated Case has one or more product delivery cases active under the new Integrated Case.
  5. Make a change to any active evidence record and apply changes.
  6. An incorrect call was causing a performance issue to occur resulting in a large amount of memory to be consumed.

Resolution:

The problematic call causing this memory issue has now been removed.

PO07820, WorkItem:232198 - When clicking the "Evidence in Edit" link in the far right of the Context Panel for an Insurance Affordability Integrated Case, the left navigation panel and page tab are not displayed correctly

Issue Description:

Previously, when clicking the Evidence in Edit link of the context panel of an Insurance Affordability Integrated Case, the left navigation panel and its page tab were not displayed correctly.

User Interface Impact: Yes

Steps to Reproduce:

  1. Navigate to an existing Insurance Affordability Integrated Case or create a new one.
  2. Click the Contact tab.
  3. Observe the left-navigation panel.
  4. Click the "Evidence in Edit" link on the far right of the Context Panel.
  5. The left navigation panel and its page tab are not displaying correctly.

Resolution:

Now, the Evidence in Edit link of the context panel on the left navigation panel and its associated tab displays correctly.

Child Welfare

PO06624, WorkItem:174812 - Error message displayed when viewing Inter-Jurisdictional Agreement

Issue Description:

Previously an error occurred when displaying the Inter-Jurisdictional agreement when a person record had a parent relationship with a representative or a prospect person.

**User Interface Impact: **No

Steps to Reproduce:

  1. Log in as sysadmin and enable the "Background" tab.
  2. Log in as caseworker and register a person.
  3. Select the Background Tab => Relationships => New.
  4. Enter the From date, Relationship Type Parent and enter the name/address in the Related Person Details cluster. Save the changes.
  5. Select the Care and Protection Tab => Cases => New. Create an Ongoing Case. Save the changes.
  6. Select the Legal Tab => Select New Inbound Agreement from Inter-Jurisdiction sub tab. Complete all required fields and Save.
  7. Expand the Inter-jurisdictional agreement details. An Unhandled Server Exception is thrown.

Resolution:

Now the Inter-jurisdictional agreement displays successfully with participant details.

PO07596, WorkItem:219800 - Intake Narrative text is displaying twice in the intake PDF report

Issue Description:

Previously, when generating an Intake report from an approved Intake case which contained narrative text, the narrative text was displayed twice on the report file.

User Interface Impact: No

Steps to Reproduce:

  1. Login as caseworker => Go to quick links => New intake > Enter a category and type => Click save.
  2. Navigate to participants tab => Add participant => Add an alleged victim.
  3. Go to Actions menu => Open intake.
  4. Actions menu => Update narrative => Enter long text.
  5. Navigate to recommendation tab => Capture recommendation => Submit.
  6. Logout and login as supervisor => On Available tasks widget => Open intake.
  7. Click make decision => Approve => Logout and login as caseworker.
  8. Go to My child welfare intakes widget => Open approved intake from previous step.
  9. Go to Action menu => Intake report => Intake report pdf file is generated. The narrative is included twice in the intake report.

Resolution:

****Now the narrative text is no longer duplicated in the Intake report.

Known Issues

See the Known Issues section in the 7.0.2.0 release notes.

Notices

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

CSV Release Notes

ReleaseNotes_7.0.4.0.csv

This CSV file summarizes the individual release notes documented above in the "Improvements, Resolved Issues and Third Party Updates" section. The individual release notes documented above will be maintained and will reflect the latest version of the release notes from eGA onwards. However, the content of this CSV file is valid on eGA date, but is not maintained after that.

Document Information

More support for:
Merative Social Program Management

Software version:
7.0.4

Operating system(s):
Linux, Windows

Modified date:
18 January 2019