Merative ™ Social Program Management 7.0.11.0 iFix5

Release Notes

Abstract

Merative Social Program Management 7.0.11.0 iFix5 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.11.0 iFix5 release.

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

See the download instructions for this release at /support/curam.

Improvements, Resolved Issues and Third Party Updates

Cúram Enterprise Framework

PO09395, PO07952, WorkItem:271144 - Evidence Source column is not correctly set for shared evidence records

Issue Description:

The source column for an evidence record does not correctly show where a piece of evidence was shared from.

User Interface Impact: No

Prerequisite(s):

Evidence sharing should be configured from an integrated case to a person case with trusted source Yes for the Addresses evidence.

Steps to Reproduce:

1. Login as a caseworker.
2. Register a person and create a new integrated case.
3. Navigate to the evidence dashboard on the integrated case.
4. Create new address evidence with an address type that does not yet exist on the person case.
5. Apply changes.
6. Navigate to the active evidence on the person case.
7. Issue: The new address is displayed but the source column incorrectly shows that the evidence originated from the person record.

Resolution:

The code for creating the shared evidence descriptors has been updated to properly set the SharedInd field. The source column will now correctly display the case that the evidence was last shared from.

Integrated Case Management

WorkItem:272588 - Merative SPM v6 notes that contain supplementary characters do not work in Merative SPM v7

Issue Description:

Notes created in Merative SPM v6 that include supplementary characters, such as an emoji character, are not visible in Merative SPM v7.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker in Merative SPM SPM v6.
2. Register a new Person.
3. Click on the Client Contact tab and select Notes.
4. Use the New page action to add a new Note that contains at least one emoji character.
5. Click on the toggle of the newly created record to view its details. Everything should appear fine.
6. Now perform an upgrade to Merative SPM SPM v7.
7. Issue: The note created above is not visible.

Resolution:

The serializer library has been updated to fix the specific issue with the supplementary characters.

Business Services

WORD INTEGRATION

WorkItem:272039 - Add system level install capability to Word Integration Assistant installer

Issue Description:

IBM Word Integration Assistant is installed at the user level and not at the system level. When installed, the Assistant is available at C:\Users\<user>\IBM\WordBridge and a registry key is created at the user level. For machines that support multiple user accounts, the installer has to be run by each user in order to use the Word Integration functionality with Google Chrome. To facilitate customers who have shared machines with multiple user accounts, we are introducing a means of installing the Word Integration Assistant at the system level, so that the Word Integration Assistant installer needs only to be run once on such a machine.

User Interface Impact: No

Steps to Reproduce:

1. Copy the IBMCuramWordIntegrationAssistant from the Merative SPM Client Development Environment (CuramCDEJ\lib\curam\installers\IBMCuramWordIntegration
   Assistant.msi) to the client machine.
2. Run the MSI installer.
3. The installer installs the install artefacts to:
   • C:\Users\<user>\IBM\WordBridge
4. The Installer creates a registry key here:
   • Computer\HKEY_CURRENT_USER\Software\Google\Chrome\
     NativeMessagingHosts\curam.fileedit.chrome.nativebridge
5. Issue: For every user on a shared machine that needs to use the Word Integration Assistant, the above steps must be repeated.

Resolution:

We now support an install property that can be passed when running the installer using msiexec that will install the Word Integration Assistant at the system level.

These steps must be run as an Administrator of the target machine:

• msiexec /i IBMCuramWordIntegrationAssistant.msi ALLUSERS=
  1 /l*v UIPerMachineInstall.log

The install location will be:

• C:\Program Files (x86)\IBM\WordBridge

The installer will create the registry key here:

• Computer\HKEY_LOCAL_MACHINE\Software\Google\Chrome\
  NativeMessagingHosts\curam.fileedit.chrome.nativebridge

If the user does not specify the ALLUSERS=1 install property, the installation process will be as described in the 'Steps to Reproduce'.

PO09352, WorkItem:272662 - Microsoft Word integration feature in Google Chrome fails to launch intermittently with NullPointerExceptions in Word Integration Assistant debug logs

Issue Description:

Microsoft Word fails to launch intermittently when a system administrator attempts to create or edit a Microsoft Word Communication in Merative SPM using the Google Chrome browser. When this happens, an error displays in the File Edit Control Panel modal dialog. If debug logging is enabled for the Word Integration Assistant, its logs show a NullPointerException when calling the method 'curam.util.tools.fileedit.common.WordManagement.
openWordApplication'.

User Interface Impact: No

Prerequisite(s):

1. Install Microsoft Word.
2. Install a Java Runtime Environment (JRE) version 8.
3. Install Google Chrome.
4. Install and enable the Cúram File Edit Native Messaging Bridge Extension for Google Chrome. This is available on the Chrome Web Store.
5. Install the SPM Word Integration Assistant. This is distributed with the Merative SPM Client Development Environment.
6. Login as a system administrator.
7. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
8. Select the New page action to create a new Microsoft Word template.
9. Enter a name and template document ID for the template and upload a file to be used as the template.
10. Select a suitable category and sub-category and click Save.

Steps to Reproduce:

Note: Though this issue can occur intermittently, the error can be forced using the following steps.

1. Login as a system administrator.
2. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
3. Click on the edit link for the template configured above.
4. The Word File Edit Screen is loaded in the Tab Content page, and the File Edit Control Panel modal is shown.
5. Microsoft Word is launched. Close Microsoft Word.
6. A pop-up appears in the browser window. Click OK.
7. Open a new browser tab and go to chrome://settings/clearBrowserData
8. Clear the data for the last hour.
9. Return to the first tab and repeat steps 1 to 4.
10. Issue: Microsoft Word does not launch the second time, and an error icon is shown in the File Edit Control Panel. If debug logging is enabled for the Word Integration Assistant, the log shows a NullPointerException stack trace.

Resolution:

The Word Integration Assistant Java code has been updated so that the circumstances leading to the NullPointerException cannot occur.

WorkItem:272716 - The original Cúram File Edit Native Messaging Bridge browser extension for Social Program Management v7.0.x has been delisted from the Chrome Web Store

Issue Description:

Google has removed the original Cúram File Edit Native Messaging Bridge Extension https://chrome.google.com/webstore/detail/file-edit-native-messagin/legdjfnmdmcapoeifgelafpoeljdlbmc from the Chrome Web Store. This browser extension and a desktop application called the Word Integration Assistant are required to enable Word Integration functionality in Social Program Management v7.0.x, for the Google Chrome browser. The extension and application communicate with each other using the native messaging API functionality of Google Chrome.

The Word Integration functionality in Social Program Management v7.0.x will not work in Google Chrome, without installing the original extension to a Google Chrome browser profile. Clients who have already installed the original extension with ID legdjfnmdmcapoeifgelafpoeljdlbmc to their Google Chrome browser profile are not affected.

Additionally, the new extension https://chrome.google.com/webstore/detail/c%C3%BAram-file-edit-native-me/jmhkbmmljlemjenoklondlldimojdgll is designed to work with v8.0 only and currently does not work against older v7.0.x lines. The extension page currently has a disclaimer "This extension is not designed to be used with v6.x or v7.x of Merative SPM".

User Interface Impact: No

Steps to Reproduce:

Scenario 1

1. Open a Google Chrome browser and go to https://chrome.google.com/webstore/detail/file-edit-native-messagin/legdjfnmdmcapoeifgelafpoeljdlbmc the address for the original extension.
2. Issue: A Page Not Found Error is returned.

Scenario 2

1. Install Microsoft Word.
2. Install a Java Runtime Environment (JRE) version 7 or 8.
3. Install Google Chrome.
4. Install and enable the v8.0 Cúram File Edit Native Messaging Bridge Extension for Google Chrome. This is available on the Chrome Web Store at this address https://chrome.google.com/webstore/detail/c%C3%BAram-file-edit-native-me/jmhkbmmljlemjenoklondlldimojdg
5. Install the SPM Word Integration Assistant. This is distributed with the Merative SPM Client Development Environment.
6. Login as a system administrator.
7. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
8. Select the New page action to create a new Microsoft Word template.
9. Enter a name and template document ID for the template and upload a file to be used as the template.
10. Select a suitable category and sub-category and click Save.
11. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
12. Click on the edit link for the template configured above.
13. The Word File Edit Screen is loaded in the Tab Content page, and the File Edit Control Panel modal is shown.
14. Issue: Microsoft Word does not launch.

Resolution:

IBM is extending the support of the new version of the extension https://chrome.google.com/webstore/detail/c%C3%BAram-file-edit-native-me/jmhkbmmljlemjenoklondlldimojdg, designed for use with Social Program Management v8.0, to be also supported with Social Program Management v7.0.x. Additionally, the new extension's page on the Chrome Web Store will be updated to reflect that it is also supported on v7.0.x lines. Note: Though Word Integration supports Microsoft Edge on Chromium in the v8.0.x release, It is not supported on the v7.0.x release, even with this new extension installed.

The added support for the new extension requires additionally delivering changes to the Word Integration Assistant installer for v7.0.x. The nature of the change is an update to the hostmanifest.json file in the Word Integration Assistant, to allow the v8.0 extension with the extension identifier, jmhkbmmljlemjenoklondlldimojdgll to communicate with it.

The updated installer IBMCuramWordIntegrationAssistant.msi will be available in 7.0.11.0 iFix 5 and subsequent iFixes.

The installer is distributed in this location CuramCDEJ\lib\curam\installers of the Cúram Client Development environment.

For customers on older v7.0.x lines, the updated installer will be available for download as a consolidated patch on Fix Central. Note: For clients who have the old extension installed (legdjfnmdmcapoeifgelafpoeljdlbmc) already, the clients should not install the new extension unless

1. They remove the old extension from their Google Chrome browser profile
2. Uninstall the old Word Integration Assistant for v 7.0.x.
3. Install the new Word Integration Assistant for v7.0.x.

Alternatively, these clients can keep the original extension with ID, legdjfnmdmcapoeifgelafpoeljdlbmc, installed. If they install the new Word Integration Assistant for v7.0, it will also work with the original extension.

Cúram Modules

Intelligent Evidence Gathering

APIS

WorkItem:272303 - IEG Application Form throws Null Pointer Exception when navigating from one section to another via Left Panel Navigation, given that there are disabled sections in between

Issue Description:

IEG Application Form throws Null Pointer Exception error when navigating from one section to another via the left panel section navigation if there are disabled sections in between.

User Interface Impact: No

Prerequisite(s):

An IEG script with the following structure:

1. Section navigation panel enabled (show-sections="true").
2. The script contains 4 sections: Section A, Section B, Section C, Section D.
3. Section A contains a question page that is always enabled, with a Question A1 that will be used as criteria to display Section B and Section C, question pages.
4. Section B contains a question page wrapped by a condition that evaluates Question A1 as criteria to display the question page.
5. Section C contains a question page wrapped by a condition that evaluates Question A1 as criteria to display the question page.
6. Section D contains a question page that is always enabled with at least one question.

Steps to Reproduce:

1. Start the IEG script.
2. In Section A, question A1 provides an answer that will ensure the question pages of Section B and Section C are not displayed, therefore not enabling the sections.
3. Click Next.
4. Section B and Section C are not displayed, and the navigator jumps to Section D.
5. In Section D, question page, click on the left panel navigation to go to Section A.
6. In Section A, question page 1, click on the left panel navigation to go to Section D.
7. Issue: A Null Pointer Exception is thrown and the user can not navigate to the desired section.

Resolution:

Previously in IEG, when a user navigated from one section to another using the section navigation panel, an NPE was thrown if there were disabled sections in between. Now IEG disabled sections are handled properly to avoid an NPE and the user can navigate to previous sections as expected.

Evidence Broker

PO09358, WorkItem:270545 - Unable to share evidence from multiple source Participant Data Cases in a single transaction

Issue Description:

Advanced evidence sharing enhancements made to the Evidence Broker introduced additional filtering for determining what evidence should be shared. Prior to these enhancements it was possible under some scenarios to share evidence from multiple source Participant Data Cases (PDCs) in a single transaction to one target case such as an integrated case. Now when advanced evidence sharing is enabled this type of sharing can no longer occur. This can cause issues for custom processing that was implemented prior to the release of the enhancements to the Evidence Broker.

**User Interface Impact: **No

Steps to Reproduce:

There are no steps to reproduce this issue out of the box. This can be reproduced with custom code that creates or modifies evidence records on multiple person cases within the same transaction.

Resolution:

The Evidence Broker functionality has been updated to support the ability to share evidence from multiple source PDCs in a single transaction to one target case. A new application property curam.aes.advancedEvidenceSharingPDCException has been added. Any evidence types specified in this property, which also exist on PDCs, will be eligible for sharing from multiple source cases in the same transaction. Note that this feature does not support reciprocal evidence such as Relationships as they are handled in a different way.

PO09032, WorkItem:272426 - Activate Share Set activity of the Advanced Evidence Sharing workflow is not correctly handling timeout exceptions

Issue Description:

When a transaction timeout occurs during the Activate Share Set activity of the Advanced Evidence Sharing workflow, the exception that is thrown is not correctly propagated to the infrastructure. This can cause the workflow activity to remain stuck at the 'In Progress' state.

Steps to Reproduce:

This issue occurs when the transaction for the Advanced Evidence Sharing workflow times out during the Activate Share Set activity. A number of underlying issues could cause a timeout to occur, including but not limited to:

• Network latency
• Database performance
• Volume of data

If a timeout happens for any reason during this particular workflow activity, then it will remain stuck in the 'In Progress' state.

Resolution:

The exception handling has been updated in the Activate Share Set logic to correctly handle transaction timeouts. These exceptions will now correctly propagate to the infrastructure and the workflow activity will be retried a number of times. If the activity continues to fail, it will be placed on the process instance error (PIE) queue.

Technical:

The Activate Share Set logic was attempting to catch any exceptions that occurred during the activation of shared evidence on a case. If evidence failed to activate, the system was updating the associated delivery plan status to 'Complete with fallback to in-edit' indicating that the evidence was shared successfully but was unable to be activated. The logic handling this was too generic, which led to it incorrectly catching timeout exceptions. The update to the logic now means that timeout transactions are properly handled and exceptions of this nature are correctly propagated to the infrastructure.

PO09064, WorkItem:272427 - Rework the Advanced Evidence Sharing Workflow to activate evidence on each target case in a share set in separate transactions

Issue Description:

When evidence from a source case is shared to multiple target cases, the Activate Share Set activity of the Advanced Evidence Sharing Workflow process is responsible for activating the evidence on each target case. If a transaction timeout occurs during the Activate Share Set activity before the evidence on each target case is activated, the workflow activity can remain stuck at the 'In Progress' state.

Steps to Reproduce:

This issue occurs when the transaction for the Advanced Evidence Sharing Workflow times out during the Activate Share Set activity. A number of underlying issues could cause a timeout to occur, including but not limited to:

• Network latency
• Database performance
• Volume of data

If a timeout happens for any reason during this particular workflow activity, then it will remain stuck in the 'In Progress' state.

Resolution:

This issue has been resolved by releasing an updated version of the Advanced Evidence Sharing Workflow. The updated workflow process will activate evidence on each target case in a separate transaction.

Technical:

The original workflow was designed to iterate through each target case that evidence was shared to and activate each case in a nested transaction. All of the nested transactions were contained inside a single workflow activity transaction and if this outer transaction timed out the remaining nested transactions that were not complete would fail and remain stuck in the 'In Progress' state. The updated workflow process changes this and instead of running many nested transactions within one workflow transaction, the new Activate Target Case Evidence activity now only operates on a single target case at a time. The updated workflow process now iterates through all target cases to execute each Activate Target Case Evidence activity in its own transaction.

Solutions

Income Support HCR

PO09380, WorkItem:270733 - Advanced Evidence Sharing is not logging the underlying stack trace if an unexpected failure occurs during a reflection call to the HCR apply changes logic

Issue Description:

HCR specific logic is used to apply changes to evidence within Insurance Affordability cases. As a result, it is necessary to use a reflection API to initiate the apply changes functionality. When an unexpected exception occurs during the activity in the Advanced Evidence Sharing workflow that attempts to automatically activate shared evidence on an Insurance Affordability target case, the underlying stack trace is not being logged by the reflection API call which is required to call the HCR specific apply changes logic.

User Interface Impact: No

Prerequisite(s):

An unexpected exception during the auto-activation of evidence on an Insurance Affordability integrated case is required to reproduce this issue.

Steps to Reproduce:

1. Login as an Insurance Affordability caseworker.
2. Register a person and submit a new application.
3. Authorise the application.
4. Navigate to the newly created integrated case.
5. Issue: The evidence has been shared but is left in edit on the target case as the auto-activate failed with an unexpected exception and the underlying stack trace has not been logged.

Resolution:

The logic for handling unexpected exceptions during the reflection call has been updated to correctly log the underlying stack trace that caused the activation of evidence to fail.

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"