Merative ™ Social Program Management 8.0.1.0

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

Release Notes

Abstract

Merative Social Program Management 8.0.1.0 Release Notes

Merative Social Program Management 8.0.1.0 is now the Long Term Support Release.

Install Merative Social Program Management 8.0.0.0 full installers and then the Merative Social Program Management 8.0.1.0 installer.

Updated on 21 December 2021 to state that 8.0.1.0 is the Long Term Support Release.

Content

Important Note
Introduction
System Requirements
Download
Installation
Improvements, Resolved Issues, Third Party Updates
Notes on Deprecation
Known Issues
Notices

Important Note

Merative Social Program Management 8.0.1.0 is now the Long Term Support release. For further details about the new support policy see Introducing a new support policy for Merative Social Program Management.

Introduction

Welcome to the Merative Social Program Management 8.0.1.0 release.

This 8.0.1.0 release includes new functionality, for detailed information about these new features, see the What's new in Version 8.0.1.0 topic in the product documentation.

For more information about 8.0.1.0, 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.

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

This 8.0.1.0 release can be installed on top of the following Merative Social Program /support/curam. Management release:

• 8.0.0.0

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 tools 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 tools to produce a schedule of required migrations for your upgrade, tools to provide information about database schema changes and tools 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

Accessibility

PO08151, WorkItem:244196 - The documented keyboard shortcuts don't work for the Date Picker widget in the Universal Access classic application

Issue Description:

When a supported screen reader is used in the Universal Access classic application, the date fields are not announced correctly. Also, the Date Picker widget is not accessible when pressing the keyboard commands (Ctrl+Page Up and Ctrl+Page Down) that are defined in the product documentation.

User Interface Impact: No

Steps to Reproduce:

1. Start a screen reader.
2. Login as an external user to the Universal Access classic application by using a supported browser.
3. Create an account.
4. On the home page, select the 'Apply for assistance with your Health Care application' link.
5. Navigate to the Information About You page.
6. Navigate to the Date of Birth field by pressing the Tab keyboard navigation key.
7. Issue 1: The date field is not announced correctly by the screen reader.
8. Press the Down Arrow key to open the Date Picker.
9. Go to the current date and press Ctrl+Page Down to navigate to the same day in the following year.
10. Issue 2: The Date Picker does not respond to the keyboard commands (Ctrl+Page Up and Ctrl+Page Down).

Resolution:

The product documentation now includes the keyboard commands (Alt+Page Down and Alt+Page Up) to navigate to the previous and next year in the Universal Access classic application Date Picker widget. Also, the date field input was updated so that the screen reader now announces the field correctly.

The updated documentation is available at: https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

PO08578, WorkItem:254172 - Screen reader does not read out context for the phone number fields on the Edit Office Phone Number modal

Issue Description:

When a supported screen reader is used, the screen reader does not correctly announce the contents of the phone number fields on the Edit Office Phone Number modal.

**User Interface Impact: **No

Steps to Reproduce:

1. Start a screen reader.
2. Login as a caseworker.
3. Register an external party of type Community Based Organisation.
4. Click the Offices tab and use the New page action to create an office with a phone number.
5. Expand the new office created and select the Phone Numbers tab.
6. Select the Edit row-level action to launch the Edit Office Phone Number modal.
7. Issue: The screen reader does not correctly announce the three phone input fields, the Phone Country Code, Phone Area Code, and Phone Number.

Resolution:

When a user now opens the Edit Office Phone Number modal, and the user navigates to the three phone input fields on the page, the text Phone Country Code, Phone Area Code and Phone Number are correctly announced by the screen reader.

PO08605, WorkItem:254792 - Screen reader does not read out context for the phone number on the Add Incident Participant modal

Issue Description:

When a supported screen reader is used, the screen reader does not correctly announce the contents of the two phone fields on the Add Incident Participant modal, and when a user hovers over these fields they both display the text 'Phone'.

User Interface Impact: No

Steps to Reproduce:

1. Start a screen reader.
2. Login as a caseworker.
3. Register a new Person.
4. Click the Issues and Proceedings tab and select Incidents.
5. Click the New page action to create a new incident.
6. Select an Accident type reported by the person and populate other mandatory fields.
7. Click Save.
8. On the Incident page, click the Participants tab.
9. Use the Add Participant page action to add a new participant.
10. Navigate to the Phone cluster on the Add Incident Participant modal.
11. Issue 1: The screen reader does not correctly announce the contents for the two phone fields on the modal.
12. Issue 2: When the user hovers over the phone fields, both display the text 'Phone'.

Resolution:

When a user navigates to the phone field on the Add Incident Participant modal, the screen reader correctly announces the two phone fields as Phone Area Code and Phone Number and when the user hovers over the two phone input fields on the page, the text 'Phone Area Code' and 'Phone Number' is now displayed.

PO08641, WorkItem:255412 - Screen reader does not read out context within address clusters as no titles are present

Issue Description:

When a supported screen reader is used, and no title or description is displayed, the contents of an address cluster are not announced by the screen reader.

**User Interface Impact: **No

Steps to Reproduce (Generic):

1. Start a screen reader.
2. Login as a caseworker.
3. Register a new Person and create a new integrated case for this person.
4. Create an associated product delivery case for this person.
5. Click the Financials tab and select Nominees.
6. Click the New page action to add a new case nominee.
7. Issue: The screen reader does not announce any contents for the address cluster on the New Case Nominee modal.

Resolution:

When any page that contains an address cluster now loads, the screen reader announces the contents of the page.

Technical:

A new JavaScript function executes on any page containing an address cluster and adds content for screen reader users.

WorkItem:272564 - When a user cancels a modal dialog, the tab title displays the title of the modal

Issue Description:

When a user closes a modal dialog by clicking Cancel, the tab title does display the correct title. It displays the page title from the modal dialog that the user canceled.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Click Person under Search in the shortcuts panel.
   • The tab title will read 'Person Search - Merative Social Program Management'.
3. Click Prospect Person under Registration in the shortcuts panel.
4. Click Cancel on the Register Prospect page.
5. Issue: The tab title reads 'Register Prospect - Merative Social Program Management' even though the Person Search page is open.

Resolution:

Now when a user closes a modal dialog by clicking Cancel, the tab displays the correct title.

WorkItem:272565 - The keyboard tab focus remains on the page behind the warning dialog when the maximum number of tabs are open

Issue Description:

When the maximum number of open tabs is reached and the warning dialog is displayed, the keyboard tab focus remains on the page behind the warning dialog and the user is unable to select the Ok button to close the dialog.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Navigate to Cases and Outcomes.
3. Open all the pages under Search in the shortcuts panel (need to open 15 to reach the limit).
4. Issue: The keyboard tab focus remains on the page behind the warning dialog and does not move to the Ok button.

Resolution:

The keyboard focus is now set to the Ok button when the maximum number of open tabs dialog is open and the user can close the dialog.

WorkItem:272728 - The New Evidence dialog is not closed when the ESC key is selected and the tab focus is set on a button

Issue Description:

The New Evidence dialog remains open when the tab focus is set on a button and the ESC key is selected.

**User Interface Impact: **No

Steps to Reproduce (Generic):

1. Login as a caseworker.
2. Register a new Person and create a new integrated case for them.
3. From the newly created integrated case, click the Evidence tab.
4. Select New Evidence from the page actions menu.
5. Move the tab focus to a button and then select the ESC key.
6. Issue: The New Evidence dialog remains open and does not close.

Resolution:

Now when the tab focus is set on a button in the New Evidence dialog and the user selects the ESC key, the modal dialog closes.

WorkItem:272941 - Label color has insufficient contrast with background on hover in Outcome Plan item action menu

Issue Description:

When a user hovers over an item of an action menu in an Outcome Plan by using the mouse, the label color has insufficient contrast with the background.

User Interface Impact: No

Prerequisite(s):

1. Login as an administrator.
2. Click Outcome Plans under Outcome Management in the shortcuts panel.
3. Add a new Objective for the Child Welfare Objective Plan.

Steps to Reproduce:

1. Login as a Child Welfare adoption worker.
2. Create an Ongoing Case.
3. Navigate to the Outcome Plan workspace.
4. Hover over either of the items in the action menu with the mouse.
5. Issue: Label color has insufficient contrast with the background color in the Outcome Plan action menu.

Resolution:

The text of the action menu item in an Outcome Plan has been updated to ensure that if a user hovers over an item of the action menu, the color contrast with the background meets the requirements for color contrast.

WorkItem:272944 - Styling of hover state on disabled action menu is the same color as the enabled action item

Issue Description:

Styling of hover state on disabled action menu is the same color as the enabled action item. As a result, when a caseworker hovers over a disabled action item, it gives the appearance that it is an enabled action. This might confusion and prompt a caseworker to inadvertently click the disabled action item.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Locate an action menu that contains disabled actions.
3. Click the action menu that contains disabled actions.
4. Move the mouse down the action menu.
5. Issue: As the mouse moves down the action menu, and hovers over disabled items in the action menu, the text color of the disabled items changes to the same color as the enabled action item.

Resolution:

The style of disabled actions is updated so that now when a caseworker hovers over a disabled item the color does not change.

WorkItem:272963 - The subject input field in the Smart Panel has an incorrect background color of white

Issue Description:

The background color of the subject input field in the Smart Panel is white, instead of the expected gray.

**User Interface Impact: **No

Steps to Reproduce:

1. Log in as a caseworker and register a new person.
2. On the home page, expand the Smart Panel.
3. Issue: The subject input field background color is white.

Resolution:

In line with accessibility guidelines, the subject input field background color was updated to the color gray in the Smart Panel.

WorkItem:272997 - The placeholder text displayed in the Smart Navigator before focus fails minimum color contrast

Issue Description:

The placeholder text displayed in the Smart Navigator before focus fails minimum color contrast.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Do not focus on the Smart Navigator search.
3. Using an accessibility contrast checker, check the contrast ratio between the text and the background color in the Smart Navigator.
4. Issue: The placeholder text displayed in the Smart Navigator before focus fails minimum color contrast.

Resolution:

The background color in the Smart Navigator has been updated so that now the placeholder text that is displayed in the Smart Navigator passes the minimum color contrast.

WorkItem:273994 - When launching a search pop-up, which opens a new second modal, the focus is lost between the modals when the second modal is closed

Issue Description:

When launching a search pop-up from a modal, which opens up a new modal, the focus is lost between the modals when the search pop-up modal is closed. In this instance, the focus incorrectly returns to the main page instead of to the previous modal.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Register a new Person.
3. Click the Evidence tab and use the New page action to launch the New Evidence dialog.
4. For Relationships evidence, select Add from the row-level actions.
5. On the New Relationships dialog, click the Search icon next to the Participant text field in the Related Participant cluster to open the Relative Search dialog.
6. Enter Smith in the Last Name field and click the Search button to show persons having the last name as Smith.
7. Navigate to the Select link next to James Smith and press the Enter key.
8. Issue: The focus is behind the modal on the main page instead of on the modal.

Resolution:

This issue is resolved. Now the focus takes into account the intermediate modal between the search pop-up and the main page.

WorkItem:274183 - The focus is not set to the first input field on a page or modal when a drop-down or date is the first element

Issue Description:

When a caseworker accesses any page or modal, the keyboard focus does not go to the first field if the first element is a drop-down or date field. The focus is set to the next input field that is not a drop-down or date.

**User Interface Impact: **No

Steps to Reproduce:

Scenario 1:

1. Login as a caseworker.
2. Click Incident under Searches in the shortcuts panel to open the Incident Search page.
3. Issue: Focus is set to the Location text field.

Scenario 2:

1. Login as a caseworker.
2. Register a new Person.
3. Create an integrated case for the person.
4. From the integrated case home page, click the Evidence tab.
5. From the dashboard, click to add any evidence type.
6. Issue: If the Received Date is the first field, the focus is set to the first input field that is not a date, or a drop-down.

Resolution:

The keyboard focus is now set to the first field of the page or modal, even if the field is a date, a drop-down, or an input field.

WorkItem:274383 - Unable to select an option in a combo box by using the keyboard Tab key

Issue Description:

After navigating to a combo box by using the keyboard Tab key, if the caseworker then highlights an option and presses Tab again the option is not selected as expected.

**User Interface Impact: **No

Steps to Reproduce:

1. Login as a caseworker.
2. Click Person under Registration in the shortcuts panel.
3. Navigate to the Gender combo box on the first page of the wizard by using the keyboard Tab key.
4. Type 'f' to highlight the Female option from the list and press the Tab key.
5. Issue: The focus moves but the option Female is not selected in the combo box.

Resolution:

Caseworkers can now use the keyboard Tab key to select a highlighted combo box option. The changes made to resolve this issue improve the usability of the combo box component.

WorkItem:274396 - The value is not selected when a user selects an item in a Carbon drop-down by pressing the Enter key

Issue Description:

The drop-down value is not being set when you type an option using the keyboard and then press the Enter key. Instead, the typed text is retained as the value. There is no issue when using a mouse, the selected value in the drop-down is correctly retained.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Click Person under Registration in the shortcuts panel.
3. Click Next on the Register Person wizard.
4. Navigate to the Title drop-down, type m (the Miss option is selected), and select the value highlighted by pressing the Enter key.
5. Enter all mandatory fields and click Save.
6. Issue: An error is displayed with the message: 'The field 'Title' contains a code value 'm' that is not a recognized code in the 'PersonTitle' code-table for the 'en_US' locale'.

Resolution:

When a user now types text into a drop-down, pressing the Enter key will correctly select the value highlighted.

Look and Feel

PO08295, WorkItem:251907 - Multiple vertical scrollbars are displayed in content area of expanded list row items

Issue Description:

Unnecessary vertical scrollbars are displayed in the page content area for expanded list row items.

**User Interface Impact: **No

Steps to Reproduce:

Scenario 1:

1. Login as a Child Welfare Structured Decision-Making caseworker.
2. Click Person under Search in the shortcuts menu.
3. Search for and open a registered person.
4. Click the Background tab and select Education.
5. Using the New page action, create an education record.
6. Expand the record and observe that an unnecessary scrollbar is introduced in addition to the rightmost vertical scrollbar.
7. Select the New Performance row-level action for this education to create a new performance record.
8. Expand the details panel on the education to view the performance record.
9. Select the New Attachment row-level action for this performance entry to create an attachment record.
10. Expand the details panel on the performance record and click the Attachments inline tab.
11. Issue: Observe that an unnecessary vertical scrollbar is present on the Attachments list page.

Scenario 2:

1. Login as a caseworker.
2. Click the Inbox section and select My Tasks in the shortcuts panel.
3. Select New Task from the tab actions menu.
4. Add a Subject, check the Add to My Tasks checkbox, and click Save.
5. From the Open Tasks list, expand the newly created task.
6. Issue: Observe that an unnecessary vertical scrollbar is present on the Actions page.

Scenario 3:

1. Login as a Child Welfare Intake worker.
2. Click the Inbox section and select My Tasks in the shortcuts panel.
3. From the Open Tasks list, expand an existing task.
4. Issue: Observe that an unnecessary vertical scrollbar is present on the Actions page.

Scenario 4:

1. Login as a Provider Manager.
2. Click the Providers and Services section and select My Providers in the shortcuts panel.
3. Select an existing provider.
4. Click the Credentials tab, then select Categories.
5. Expand the existing Category.
6. Issue: Observe that an unnecessary vertical scrollbar is present on the Provider Type.

Resolution:

Unnecessary vertical scrollbars are no longer displayed in the page content area for expanded list row items.

WorkItem:272250 - Some modals are not sized based on the contents they are displaying

Issue Description:

In version 8.0.0, with the introduction of the new look and feel and standardization of modal sizing, the following issues were observed:

1. Some modals were too large, and the contents too spread out causing an increase in eye movement and cognitive load.
2. Some modals were too small and hard to read.

For more information about the standardization of modal sizing, see WorkItem:271924 in the version 8.0.0 release notes: /support/spm/release-notes/8-0-0.

User Interface Impact: Yes

Prerequisite(s):

1. Upgrade from 7.0.11 to version 8.0.0.
2. As part of the Upgrade process, run the UI Upgrade Helper Tool.

Steps to Reproduce:

Scenario 1: Edit a person (modal too wide example)

1. Log in as a caseworker.
2. Register a Person.
3. Click the Edit action in the page actions menu.
4. Issue: The Edit Person modal is very large, spanning the width of the page.

Scenario 2: View a list of waivers (modal too small example)

Configure a Milestone

1. Log in as an administrator.
2. Click Milestones under Case in the shortcuts panel.
3. Add a Milestone with the following details:
   • Name: Test Milestone
   • Type: Milestone
   • Earliest Start Day (days): 0
   • Duration (days): 10
   • Start Date: 10 days prior
   • Expected Date Extension Allowed: True
4. Click Investigations under Case in the shortcuts panel.
5. Navigate to an existing Investigations Case.
6. Click the Add Existing page action.
7. Select your newly created Milestone and click Save.

Add a Milestone to a case

1. Log in as a caseworker.
2. Register a Person.
3. Navigate to the Issues and Proceedings tab and select Investigations.
4. Create an Investigation, selecting the Type with the waiver configured.
5. From within the Investigation case, click the Milestone tab.
6. Use the New page action to create a Milestone.
7. To view the Milestone, navigate to the Events tab.
8. Click any Milestone Added entry in the calendar to open the Milestone.
9. Click the Waivers tab.
10. Issue: The small modal presents a list and the list header is poorly spaced.

Resolution:

The UI Upgrade Helper has been improved to resize modals based on the content that is contained within the modal and the modal's width. The Modal Sizing Tool has been run on the core caseworker product and as a result, generic case management and person management modals, such as notes, have been updated.

To obtain the benefits of optimum modal sizing, customers can run the tool on their own codebase. For more information about the tool, see https://merative.github.io/spm-ui-upgrade-helper/. The tool is available from https://github.com/merative/spm-ui-upgrade-helper.

**Note: **See Work Item 272250 in the Known Issue section for information on the modules that have not been updated and the impact on files that have been overridden.

WorkItem:272254 - Allegations list in the Dispose Allegations modal is incorrectly displayed beneath the comments

Issue Description:

When a Child Welfare investigator views the Dispose Allegations modal, the modal layout is not correct. The Allegations list that allows the Child Welfare investigator to select the maltreater for an allegation is displayed beneath the comments.

User Interface Impact: No

Steps to Reproduce:

1. Login as a Child Welfare Investigator and click the Investigator workspace.
2. Click New Investigation under Investigations in the shortcuts panel for an already approved intake.
3. Navigate to the Allegations tab.
4. Click the Dispose Allegations link to open the Dispose Allegation modal.
5. Issue: The Allegations list in the Dispose Allegations modal is incorrectly displayed beneath the comments instead of over the disposition details.

Resolution:

The Allegations list is now displayed over the Disposition details.

WorkItem:272255 - Time entered manually into a date/time field is cleared when moving focus from the field

Issue Description:

When entering an arbitrary time value into a date/time input field, the entry is cleared when the user moves from the field. The time entered will be saved if the Enter key is pressed.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Click the Calendar workspace.
3. Select New Meeting from the tab actions menu.
4. Enter a time into the time input that is not in the drop-down list and then click outside of the field.
5. Issue: The entry is cleared when the user moves from the field.

Resolution:

When moving the focus away from a date/time input field by using the Tab key, or by using a mouse click, or by using the Enter key, the selected value or the value entered manually in a time field is kept selected in the field.

PO09629, WorkItem:272266 - Duplicate buttons are displayed on the Pro Forma Communication modal as well as some of the wizards in the application

Issue Description:

Duplicate buttons are displayed on the Pro Forma Communication modal. They are also displayed on some wizards, for example, New Contact wizard, New Service wizard, and New Outcome Plan wizard.

User Interface Impact: No

Steps to Reproduce:

Scenario 1: Duplicate Cancel buttons are displayed on the end of the wizard

1. Login as an administrator.
2. Click Outcome Plan under Outcome Management in the shortcuts panel.
3. Click the New page action to launch the New Outcome Plan wizard.
4. Issue: The wizard displays a second Cancel button.

Scenario 2: Duplicate Cancel buttons are displayed on a modal

1. Login as a caseworker.
2. Register a new Person.
3. Click the Client Contact tab and select Communications.
4. Select the New Pro Forma page action.
5. Select any correspondent and click Next.
6. Select Letter in the Type drop-down and click Search.
7. Select any of the Pro Forma Types to open the New Pro Forma Communication modal.
8. Issue: The communication modal displays two Cancel buttons.

Resolution:

Now when a caseworker launches the Pro Forma Communication modal, and the wizards mentioned, only one of each action button is displayed.

WorkItem:272267 - Users cannot scroll down to the end of the sections within the Client Merge wizard

Issue Description:

When a caseworker was using the Client Merge wizard, they were unable to scroll to the end of the wizard to view the page content. To view the full page content, the caseworker had to use the Tab key to go to the end of the wizard.

User Interface Impact: No

Prerequisite(s):

1. Login as a system administrator.
2. Click Property Administration under Application Data in the shortcuts panel.
3. Enter 'Client Merge' in the Name field and click Search.
4. Use the Edit Value row-level action to set all 18 Client Merge properties to YES.
5. Publish the changes using the Publish page action.

Steps to Reproduce:

1. Login as a caseworker.
2. Register a new person and add the following evidence:
   • Mailing Address
   • Phone Number
   • Email
   • Social Security Number
   • Bank Account
   • Relationship
3. Register a second person with a similar name and gender as the person in step 5.
4. Also, add the following evidence for each person:
   • Notes
   • Special Caution
   • Employment
   • Web Address
   • Communication Exceptions
5. Click the Administration tab from the home page of the second registered person.
6. Select Duplicates and click the Mark New Duplicate page action.
7. Search for and select the duplicate person.
8. Click the Save & Start Merge button to open the Client Merge wizard.
9. Issue 2: The caseworker cannot scroll to the end of the wizard to view content. To view content and progress through the wizard, the caseworker had to use the Tab key.

Resolution:

Caseworkers are now able to scroll down to view the full page content within Client Merge wizard.

WorkItem:272268 - Save and Cancel buttons missing on Placement modal in Adoption Case

Issue Description:

In an Adoption Case, the Save and Cancel buttons are not always displayed during the creation of a new placement from the page action menu. The Save button is not displayed when Adoption or Foster Care are selected from the Type drop-down menu. The Cancel button is not displayed when Runaway or Trial Home Visit are selected from the Type drop-down menu.

User Interface Impact: No

Prerequisitie(s):

An Adoption Case must be created and available.

Steps to Reproduce:

1. Log in as a Child Welfare caseworker.
2. Navigate to an existing Adoption Case.
3. Select New Placement from the page action menu.
4. Select Adoption or Foster Care from the Type drop-down.
5. Issue 1: The Save button is not displayed on the New Placement modal.
6. Select Runaway or Trial Home Visit from the Type drop-down.
7. Issue 2: The Cancel button is not displayed on the New Placement modal.

Resolution:

These issues were resolved by fixing the logic of the onChange() event function of the Type drop-down in the New Placement modal. Save and Cancel buttons now display as expected in the New Placement modal when options from the Type drop-down are selected.

WorkItem:272563 - The context panel of the person home and the Smart Navigator search results displayed the incorrect icon to represent a person

Issue Description:

The context panel of the person home and the Smart Navigator search results displayed the incorrect icon to represent a person. A new icon was introduced to represent a person in version 8.0.0.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Search for James Smith on the Smart Navigator Search.
3. Issue 1: Search results in the Smart Navigator display a version 7.0.0 icon for the person entity.
4. Click James Smith to open the person home page.
5. Issue 2: The context panel displays the version 7.0.0 icon for the person.

Resolution:

This issue is resolved for demo persons (James Smith, Linda Smith, and so on) by removing the references to these images from the CONCERNROLEIMAGE.dmx files and from the ../components/core/data/demo/blob files.

WorkItem:272669 - The Summary is incorrectly styled for the Long Term Care product delivery summary display rules tab

Issue Description:

When a caseworker views the Eligibility Decision split information in the Determinations tab in the LTC Spend Down program, the page is not correctly styled. The Eligibility information is incorrectly positioned beneath the Assistance Unit information instead of beside the Assistance Unit information.

**User Interface Impact: **No

Steps to Reproduce:

1. Login as an Income Support caseworker.
2. Register a new Person (older than age 65 years).
3. For the person, add a new application for both Retroactive Medical Assistance and Medical Assistance on the same application.
4. Submit the application with the application date set to today's date and both Member of Household and Living Arrangement start dates set to 3 months ago. For example, if the application date is 13 October, then the correct start dates are 13 July.
5. On the application add evidence details:
6. Add Level of Care:
   • Level of Care Type: Hospital Level of Care
   • Certification Start Date: the same date as Living Arrangement above
   • Certifier Type: Physician
   • Add Certifier details
7. Add Medical Institution:
   • Institution Type: Hospital
   • Entered Date: the same date as Living Arrangement above
   • Expected Length of Stay: > 6 months
   • Application Filed By Type: Other
   • Add Medical Institution details, Placed By details & Application Filed By details
8. Add Medical Expense evidence with details
   • Amount: $10
   • Frequency: Monthly
   • Medical Expense Type: Cost of Care Expenses
   • Start Date: the first of the previous month (for example 1 September if using the example dates above)
   • Add Medical Service Provider details
9. Check eligibility for Medical Assistance.
10. For the eligibility check, confirm that the client is eligible for Long Term Care (LTC).
11. Add verifications proof, apply evidence changes, and mark as Ready for Determination.
12. Authorize the eligible Long Term Care coverage and activate the product delivery online.
13. Navigate to the Determinations tab on the Long Term Care product delivery.
14. Select Eligibility Decision split.
15. Issue: Eligibility is displayed beneath the Assistance Unit information making it harder for the caseworker to view the information summary.

Resolution:

The Eligibility information is now positioned beside the Assistance Unit information, making it easier for the caseworker to view the information summary.

WorkItem:272707 - The space between the text fields is too small and there is no space between the rich text area and the buttons on the Smart Panel

Issue Description:

The layout of the Smart Panel is not correct. The space between the subject line and the rich text area is too small, and no space is visible between the rich text area and the buttons.

**User Interface Impact: **No

Steps to Reproduce:

1. Login as a caseworker.
2. Register a new Person.
3. Expand the Smart Panel.
4. Issue: The space between the input field and the rich text area is too small, and no space is visible between the rich text area and the buttons.

Resolution:

The layout of the Smart Panel is now adjusted. Enough space is now visible between the subject line input and rich text area, and between the rich text area and the buttons.

WorkItem:272711 - Too much padding around the Smart Panel

Issue Description:

Too much padding is displayed around the Smart Panel. The extra padding reduces the space that is available to users to capture notes.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Register a new Person.
3. Expand the Smart Panel.
4. Issue: The padding in the Smart Panel is larger than expected.

Resolution:

The padding around the Smart Panel has been reduced so that users can capture notes more easily.

WorkItem:272800 - The buttons disappear when a user clicks Save on the Register Provider wizard

Issue Description:

When a user clicks on the Save button on the Register Provider wizard, the buttons on the wizard disappear.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Register a new Provider.
3. Issue: The buttons disappear on the Register Provider wizard.

Resolution:

When a user is now using the Register Provider wizard and clicks on the Save button, the buttons continue to be displayed on the modal. The modal closes and the provider is registered.

WorkItem:272939 - The progress bar within the Client Merge wizard is not visible on clicking the Next button

Issue Description:

The progress bar within the Client Merge wizard is not visible on clicking the Next button. However, once a user clicks on the Back button in any of the wizard screens, the progress bar is displayed.
User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Register a new person and add the following evidence:
   • Mailing Address
   • Phone Number
   • Email
   • Social Security Number
   • Bank Account
   • Relationship
3. Register a second person with a similar name and gender as the person in step 5.
4. Also, add the following evidence for each person:
   • Notes
   • Special Caution
   • Employment
   • Web Address
   • Communication Exceptions
5. Click the Administration tab from the home page of the second registered person.
6. Select Duplicates and click the Mark New Duplicate page action.
7. Search for and select the duplicate person.
8. Click the Save & Start Merge button to open the Client Merge wizard.
9. Issue: The progress bar on the upper right of the wizard is not visible after selecting the Next button.

Resolution:

The progress bar within the Client Merge wizard is visible when a caseworker clicks the Next button.

WorkItem:272987 - The buttons 'Stay logged in' and 'Log out' were not displayed in the session timeout warning modal in the Citizen Portal

Issue Description:

When a user session times out in the Citizen Portal, the session timeout warning modal is displayed but the 'Stay logged in' and 'Log out' buttons are not displayed in the modal. The user is unable to indicate if they want to remain logged in or if they want to log out.
**User Interface Impact: **No

Steps to Reproduce (Generic):

1. Set the session timeout in the application server to something low, for example, 2 minutes, and restart the application server.
2. Using the Citizen Portal, apply for an application.
3. As part of the application, create an account. Creating your own account will let you save your work and return to it later.
4. Navigate through some of the steps in the application script.
5. Stop midway through the application and wait until the session times out and the session timeout warning dialog is displayed.
6. Issue: The 'Stay logged in' and 'Log out' buttons are not displayed in the session timeout warning dialog.

Resolution:

When using the Citizen Portal to submit an application, if the session expires and the timeout warning modal appears, the 'Stay logged in' and 'Log out' buttons are displayed on the modal. The user is now able to indicate if they want to stay logged in, or log out of the Citizen Portal when a user session expires.
More information on configuring a user session timeout can be found on: https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

WorkItem:273176 - Some UI Carbon components are not using the 'data-testid' attribute

Issue Description:

In version 8.0.0, a new attribute, called 'data-testid', was introduced to enable easier targeting of user interface elements in user interface automation tools. Two components, 'Date' and 'Date-Time', were not using the correct attribute name. Also, the attribute was missing from the 'Multiple select list' component.

User Interface Impact: No

Steps to Reproduce:
N/A

Resolution:

All components that were converted to Carbon now contain the 'data-testid' attribute. The attribute can be used in UI automation tools to target Carbon components that are used within a page.

For more information on the 'data-testid', refer to the What's New, and the 'UI test automation' section in the Merative SPM web client reference guide.

WorkItem:273196 - The New Social Enterprise Folder (SEF) modal displays Reset and Search buttons that originate from the page that is displayed before the SEF modal

Issue Description:

When a caseworker creates a new Social Enterprise Folder (SEF) folder, the modal incorrectly displays two additional buttons, Reset and Search. The buttons originate from the previous Person Search page that was displayed before the launch of the SEF modal.

**User Interface Impact: **No

Steps to Reproduce:

1. Login as a caseworker.
2. Select Social Enterprise Folders from the shortcuts panel to open the Person Search dialog.
3. Search for a person and select that person to create a new Social Enterprise Folder for.
4. Issue: When the Social Enterprise Folder is displayed, the modal contains two additional buttons, Reset and Search.

Resolution:

When a caseworker now views the Social Enterprise Folder, the only buttons that are visible are Cancel and Create.

PO09603, WorkItem:274148 - The List Pagination element is not visible at the end of a list

Issue Description:

In version 8.0.0, the List Pagination element that is normally visible at the end of a list was not visible to the user. To see the List Pagination element, the user had to navigate through the entire list by using the keyboard and selecting the Tab key.

**User Interface Impact: **No

Steps to Reproduce:

1. Log in as an administrator.
2. Click New User under Users in the Shortcuts panel.
3. On the New User modal, locate the Role Name field and click the search icon.
4. Issue: Scroll to the end of the list. The List Pagination element, which users can use to traverse through the list, is not visible.

Resolution:

The List Pagination element is now visible at the end of the list so users can traverse the list.

WorkItem:274163 - The caseworker has to scroll to the end of the Client Merge wizard to access the wizard buttons

Issue Description:

When a caseworker is performing a Client Merge, they need to scroll to the end of the wizard to access the buttons. Before the new Look and Feel, the buttons in the Client Merge wizard were always visible to the caseworker for quickly merging a client. The new Look and Feel changes introduced unnecessary scrolling for the caseworker.

User Interface Impact: No

Prerequisite(s):

1. Login as a system administrator.
2. Click Property Administration under Application Data in the shortcuts panel.
3. Enter 'Client Merge' in the Name field and click Search.
4. Use the Edit Value row-level action to set all 18 Client Merge properties to YES.
5. Publish the changes using the Publish page action.

Steps to Reproduce:

1. Login as a caseworker.
2. Register a new Person.
3. Add the following information for the newly registered person:
   • Notes
   • Special Caution
   • Employment
   • Web Address
   • Communication Exceptions
4. Register a second person with a similar name and gender as the person in the previous step.
5. Also, add the following information for the newly registered person:
   • Notes
   • Special Caution
   • Employment
   • Web Address
   • Communication Exceptions
6. Click the Administration tab from the home page of the second registered person.
7. Select Duplicates and click the Mark New Duplicate page action.
8. Search for and select the duplicate person.
9. Click the Save & Start Merge button to open the Client Merge wizard.
10. Issue: As the caseworker progresses through the Client Merge wizard, they have to scroll to the end of the page to select the button to proceed to the next step.

Resolution:

When the caseworker uses the Client Merge wizard, the buttons are always presented so that the caseworker does not need to scroll to the end of the page to move to the next page in the wizard.

WorkItem:274273 - Some drop-downs display a blank entry if no default value is specified

Issue Description:

Since version 8.0.0, some drop-downs display a blank value as the default option. Before version 8.0.0, the drop-downs displayed the first value in the code table as the default item. In UIM, when configuring a field to display the contents of a code table that displayed a default value, two settings are considered.

• Update the UIM field and set the value USE_DEFAULT. When set to true, a default value is displayed in the code table, otherwise, the first item in the drop-down is displayed,
• Set the default attribute to an item in the corresponding code table.

In version 8.0.0, if USE_DEFAULT was false or no default value was specified in the code table, the drop-down field had no default selection and a blank value was displayed.

**User Interface Impact: **No

Steps to Reproduce (Generic):
Scenario 1:

1. Login as a caseworker.
2. Register a new Person and create an integrated case for them.
3. Click the Evidence tab and select Dashboard.
4. Add an evidence type.
5. Click the link to edit the newly created evidence.
6. Expand the toggle and select the row-level action Continue Editing.
7. The evidence modal opens.
8. Issue: The Change Reason field is blank.

Scenario 2:

1. Login as an administrator.
2. Select Process Instance Errors under Process Monitoring in the shortcuts panel.
3. Issue: The Process Name drop-down is blank.

Resolution:

Now when the property USE_DEFAULT is set to false, or no default code table item is specified, the first item in the code table is used as the default selection.

WorkItem:274388 - Modal dialog buttons transition improvements

Issue Description:

In version 8.0.0, modal dialogs and modal-based wizards have the following transition issues.

While modal-based wizards are in transition, for example, loading the next page, the modal footer buttons style remains the same as the general button styling concerning color and layout. This implies that the user can interact with the modal footer buttons while the rest of the content in the modal is blurred by the progress spinner background or the loading mask. If a user clicks on any of the footer buttons during this transition time, they no longer display.

The button transition issue can also be seen in a single modal scenario. The buttons disappear after a click but the screen itself is still displayed; the buttons become opaque and stay until the dialog closes.

There is no difference in principle between the single modal and the wizard, the same is happening in both transitions. The only difference is that in the case of wizards, the modal stays with the new content, and in the case of the single modal, the action usually returns to the content pane which is optionally reloaded.

User Interface Impact: No

Steps to Reproduce:

Scenario 1:

1. Login as a caseworker.
2. Click Person under Registration in the shortcuts panel.
3. Click the Next button in the Register Person wizard.
4. Issue: When the wizard is transitioning, all the modal buttons disappear and the new buttons are just drawn after the next screen with the full details loads.

Scenario 2:

1. Login as a caseworker.
2. Create a new Task to open the New Task modal.
3. Click the Save and New button.
4. Issue: When the modal is transitioning, all the modal buttons disappear and the new buttons are just drawn after the next screen with the full details loads.

Resolution:

The modal dialog buttons transition has been improved by delaying their removal from the modal footer until the new button set is to be drawn. The modal footer style has been updated to display a different style when the transition is ongoing. The opacity (transparency) has been increased while the dialog is in transition, for example, when new content is loading. When the dialog is closed or has new content loaded, this styling is removed. The buttons are now not disappearing as previously and are displayed on the modal until either the dialog closes or the new content loads into the same dialog.

The buttons are now put in the transitional state which is marked by making them partly opaque and not active. The transition state lasts until the dialog is discarded (single modal scenario), or the new content with different buttons is loaded (modal-based wizard scenario).

WorkItem:274393 - When a caseworker clicks to download the contract on the Preview Contract confirmation modal, the buttons are no longer visible on the modal

Issue Description:

When a caseworker views the Preview Contract confirmation modal and clicks the button to download a provider contract, the buttons on the confirmation modal disappear.
User Interface Impact: No
Steps to Reproduce:

1. Login as a Provider Management manager.
2. Click My Providers under Provider in the shortcuts panel.
3. Click the Provider Reference Number hyperlink to open an existing provider in a new tab.
4. Click the Financial tab and select Contracts.
5. Create and generate a Utilization Contract for the contract to go to an Issued state.
6. Select the Preview row-level action for the Utilization Contract.
7. Click the leftmost button on the Preview Contract confirmation dialog.
8. Issue: The Provider contract downloads but the buttons disappear from the Preview Contract dialog.

Resolution:

When a caseworker clicks on the leftmost button to preview the provider contract, the contract is downloaded and the buttons on the confirmation modal continue to be displayed.

Note: The Preview Contract confirmation modal contains a button with a missing label. The button incorrectly displays the value 'Null' instead of the value 'Yes'. This is a Known Issue in Work Item 274492.

WorkItem:274525 - The modal layout is not maintained for medium modals when the width of the browser is significantly reduced

Issue Description:

Caseworkers might need to resize their browser if they are interacting with multiple systems. The modal layout is not consistent for medium modals when the width of the browser window reduces significantly. As the modal size reduces, the fields reposition as expected. However, as the modal size continues to reduce, the fields revert to their original positions, resulting in a poor user experience.
**User Interface Impact: **No

Steps to Reproduce:

1. Login as a caseworker.
2. Register a new Person.
3. Open the Client Contact tab of the person case and select Communications Exceptions.
4. Click the New page action to open the New Communication Exception modal.
5. Reduce the width of the browser window significantly.
6. Issue: As the caseworker resizes the browser window the modal shrinks and the fields are repositioned. As the user continues to reduce the window size, the fields revert to their original position.

Resolution:

As the size of a medium modal reduces, the modal fields reposition as expected and no longer revert as the size decreases further, giving a consistent user experience.

Curam Enterprise Framework

Dynamic Evidence
Technical Services
Integrated Case Management
Administration Suite
Intake
Application Development Environment
Business Services
Common Intake

PO09210, WorkItem:268286 - Modifying meeting minutes values causes other unmodified values to be deleted

Issue Description:

In Merative Social Program Management (SPM), modifying meeting minutes can cause other values that were not modified to be deleted.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Register a new Person and create an integrated case for them.
3. On the integrated case, click the Contact tab and select Meeting Minutes.
4. Click the Record Meeting Minutes page action and click Next.
5. Provide values for the following: Subject, Location, Sensitivity, Meeting Type, Agenda, and Organized by me.
6. Click Save & Exit.
7. Expand the toggle for the meeting minutes and confirm all the values entered.
8. From the meeting minutes record's action menu, select Edit Agenda.
9. Modify the Agenda and click Save.
10. Expand the toggle for the meeting minutes.
11. Issue 1: The expected behavior is that the previously provided Meeting Type and Location details remain unchanged. The actual behavior is that the previously provided values for Meeting Type and Location are deleted.
12. From the meeting minutes record's action menu, select Edit.
13. Update the Location and Meeting Type values and click Save.
14. Expand the toggle for the meeting minutes record.
15. Issue 2: The expected behavior is that the previously provided Agenda details remain unchanged. The actual behavior is that the previously provided Agenda details are deleted.
16. From the meeting minutes record's action menu, select Edit Decisions.
17. Provide some text for the decision and click Save.
18. Expand the toggle for the meeting minutes and confirm that the Decision text is present.
19. From the meeting minutes record's action menu, select Edit.
20. Provide new Location and Meeting Type values and click Save.
21. Expand the toggle for the meeting minutes record.
22. Issue 3: The expected behavior is that the previously provided decision details remain unchanged. The actual behavior is that the previously provided Decision details are deleted.

Resolution:

Missing Source or Target tags are now connected to the relevant meeting minutes UIM pages so that the data for Location, Meeting Type, Meeting Agenda, and Decisions is not lost during modification.

PO09532, WorkItem:273065 - Unable to compliantly extend Smart Navigator search by reference authorization check

Issue Description:

In version 7.0.7, an authorization check was included for the Smart Navigator search by reference and case keyword so that only those results that the caseworker has permission to view are returned in the results list. The default implementation performs authorization checks only for the following case types: Integrated Case (CT5), Product Delivery (CT2), Investigation (CT2000), Liability (CT4), Service Plan (CT1), and Application Case (CT10201).
The result for the rest of the case types was not displayed to the caseworker as the authorization check was considered to have failed. It was not possible for customers to compliantly modify the authorization check to add more case types.
User Interface Impact: No

Steps to Reproduce:
N/A

Resolution:

A new interface is now provided to allow compliant customization. For more information about how to use the new interface, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

PO09395, PO07952, WorkItem:273118 - 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):

1. Configure evidence sharing from an integrated case to a person case with Trusted Source set to Yes for the Addresses evidence.

Steps to Reproduce (Generic):

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 now properly sets the SharedInd field. The source column now correctly displays the case that the evidence was last shared from.

WorkItem:273436 - Verification Engine performance improvement addressing redundant calls to determine verification status during product authorization

Issue Description:

Verifications that are configured at the product delivery level are inserted as required during product authorization. On insertion of each new product level verification, the status of the new verification needs to be determined. However, the status of all verifications on the product delivery case and the parent-integrated case that are linked to the same evidence type is evaluated during each new insertion. While this does not cause a functional issue, it does cause a large amount of redundant processing that results in the product delivery authorization process taking longer than necessary to complete.

**User Interface Impact: **No

Steps to Reproduce:

1. Login as an Income Support caseworker.
2. Register a new Person.
3. Submit an application for Food Assistance and Medical Assistance.
4. Add evidence to be eligible for Food Assistance (Head of Household and Work Registration evidence) and Medical Assistance programs ABD (Disability evidence with type Blind and 1619b indicator checked) and QMB (Benefit evidence with Medicare Part A).
5. Add monthly Earned Income evidence records of $1 (start and end dates matching calendar month dates) for the previous 6 years.
6. Clear verifications and apply all evidence changes.
7. Authorize the individual product deliveries.
8. Issue: The time taken to authorize is considerable, and the time taken increases as each subsequent product delivery is authorized.

Resolution:

Now as each new verification is inserted, the status of only that verification is determined, which improves the overall performance of product authorization.

WorkItem:273624 - Hook point required to facilitate setting the Case Header effective date as part of case approval

Issue Description:

Currently, it is not possible to compliantly customize the function that sets the Case Header effective date when approving a product delivery. Customers might want to set this to a specific value depending on their payment schedules.

For example, a customer might pay out every 4 weeks on particular days of the month. Setting the effective date in line with those days ensures the desired payment behavior in accordance with those schedules.

User Interface Impact: No

Steps to Reproduce: N/A

Resolution:

To support compliant customization, a new external, implementable interface curam.core.hook.impl.ProductDeliveryApprovalStrategyHook has been added. The method setEffectiveDate(final Long caseID, final Date approvalDate) can be implemented to customize the logic that sets the effective date on product deliveries during the case approval process. The custom implementation can be injected through the standard Guice dependency injection mechanism.

WorkItem:274329 - Undo deprecation of meeting minutes responses feature

Issue Description:

The meeting invite response feature was deprecated in error in version 8.0.0. The feature forms part of meeting minutes PIM integration, which processes responses that are returned to a configured email account and updates meeting attendee response data. Some of the artifacts are used in batch jobs and were deprecated in error.

For more information, see WorkItem: 263097- Deprecate an unused facade method that processed email meeting responses as part of Meeting Minutes PIM integration in the version 8.0.0 Release Notes.

**User Interface Impact: **No

Steps to Reproduce:

N/A

Resolution:

The feature is no longer deprecated. All deprecation labels have been removed from the related artifacts.

Dynamic Evidence

Evidence Validations

PO09463, WorkItem:272386 - Incorrect user and timestamp information is displayed when evidence is edited and the edit is then discarded

Issue Description:

Incorrect user and timestamp information is displayed in the Updated By field of a Corrections record when viewing the change history for an evidence record where a user selects to edit active evidence and then discard the in-edit evidence changes.
User Interface Impact: No

Steps to Reproduce:

1. Login as an Income Support intake worker.
2. Register a Person and create a new Income Support integrated case.
3. Click the Evidence tab and select Dashboard.
4. Create any new evidence from the dashboard.
5. Apply changes.
6. Login as a second user such as an Income Support eligibility worker.
7. Search for the case and edit the evidence to change any of the information.
8. After saving, notice the 'In-Edit' status in the Change Summary section and that Updated By is the name of the second user.
9. Discard the changes.
10. Issue: The name of the user that is displayed in the Updated By field for the initial Corrections record is incorrectly updated to the name of the second user that edited and then discarded the edit.

Resolution:

The Updated By field that is displayed for each Corrections record now shows the user who applied the changes for the initial creation of the evidence and each subsequent correction, including when evidence is edited and then those edits are discarded.

WorkItem:273340 - Improvements to evidence change history

Issue Description:

Previously when viewing a change history of evidence the following two items made it more difficult for caseworkers to understand the changes that occurred to the evidence:

1) The labels that are used for tab names were not consistent across person, dynamic evidence, and static evidence leading to potential confusion about whether the information displayed across case types was the same. For static evidence, such as that captured in an Income Support case, the label that was used for the tab that is used to view corrections information was labeled ‘History’, however, for dynamic evidence, such as that displayed within an Insurance Affordability case, the tab name was displayed as ‘Corrections’. Additionally, when evidence was viewed at the person level, the label for the tab that is used to view the overall change history was labeled ‘Corrections’.

2) When evidence is expanded, a change history of the evidence, including the user who modified the evidence, is displayed. Previously, when the evidence was created by one user and then corrected by other users, the last user to correct the evidence was being displayed for all correction records making it difficult to view a history of all users who are involved in updating the evidence.
User Interface Impact: No

Steps to Reproduce (Issue 1: Tab names):

(Issue 1a: Person evidence tab names):

1. Login as a caseworker.
2. Register a new Person.
3. Click the Evidence tab and expand any of the evidence types.
4. Issue: The set of tab names display as: Details, Corrections, Issues, Verifications. When the Corrections tab is then expanded another tab name Corrections is then also displayed.

(Issue 1b: Static evidence tab names):

1. For the person created above, create an integrated case that uses static evidence.
2. Create any evidence record and apply changes.
3. Expand the evidence to view the change history. Expand the evidence again at the next level.
4. Issue: The set of tab names display as: Details, History. This is inconsistent with dynamic evidence that displays Details and Corrections.

Steps to Reproduce (Issue 2: Change History)

1. Record the case number of the integrated case created above.
2. Logout and login as a different user who has access to the same integrated case type.
3. Open the same integrated case and the same evidence.
4. Select to edit the evidence and make a correction to the evidence.
5. Expand the evidence to view the change history that now includes two corrections records - one for the initial version of the evidence and one for the correction.
6. Issue: Both corrections records display the name of the user that made the correction.

Resolution:

For static evidence, the tab name previously labeled 'History' has been updated to now display ‘Corrections'.

For person evidence, the top-level tab name previously labeled 'Corrections' has been updated to now display 'Change History'.

When a user different from the user that initially created evidence modifies the evidence by making a correction, the name of the user that initially created the evidence is no longer overwritten.

Note: Taking on the change to the naming of the tab for person-level evidence is optional but if taken on requires the insertion of updated lob data into the database. The associated upgrade steps are outlined in the Merative Social Program Management Upgrade Guide in the chapter entitled PDC Dynamic Evidence Navigation Label Update.

EVIDENCE VALIDATIONS

PO09471, WorkItem:272306 - Unhandled server exception when modifying an in-edit dynamic evidence into new version

Issue Description:

An unhandled server exception occurs when a user creates and then attempts to modify in-edit dynamic evidence on a case. This exception occurs when a second version of a dynamic evidence type is configured by an administrator that involves the removal of attributes that were used by validations in the previous version. This unhandled server exception occurs when a user creates and then attempts to modify the in-edit dynamic evidence on a case.

User Interface Impact: No

Prerequisite(s):

1. Login as an administrator.
2. Click the Administration Workspace tab.
3. Select Dynamic Evidence under Rules and Evidence in the shortcuts panel.
4. Click the New page action button.
5. Create a new dynamic evidence type using the following details:
   • Evidence Type: MyTestEvidence
   • Logical Name: MyTestEvidence
   • Effective From: 1/1/1900
   • Security Group: SAMPLE_INCOME_GROUP
6. Click the toggle to expand the newly created MyTestEvidence evidence type.
7. From the inline row-level actions menu, select Edit Metadata to launch the external Dynamic Evidence Editor.
8. In the editor, add 4 data attributes as follows: attribute1, attribute2, attribute3, attribute4.
9. Click the General tab and set the option Correction Only to True.
10. Click the Validations tab, and add a new validation with the following details:
    • Validation Type: Dependency
    • First Attribute: attribute3
    • Second Attribute: attribute4
    • Dependency: Must enter the second attribute
    • Narrative: If ‘attribute3’ is entered, ‘attribute4’ must also be entered
11. In the Dynamic Evidence Editor, select User Interface. Add attribute1 and attribute2 to a new cluster and click Save.
12. Return to the dynamic evidence list and select the Activate row-level action to activate the new dynamic evidence type.
13. From the row-level actions, select New In Edit Copy and set the Effective From date to 2/1/1900.
14. Select Edit Metadata to launch the Dynamic Evidence Editor.
15. In the editor, remove attribute3 and attribute4. Also, remove the dependency validation on attribute3 and attribute4.
16. Navigate to the dynamic evidence page and select Activate from the row-level actions menu.
17. Navigate to Integrated Cases under Case in the shortcuts panel.
18. Use the New page action to configure a new integrated case.
19. Click the hyperlink of the newly created integrated case and select the Evidence tab.
20. Use the Add Evidence page action to link MyTestEvidence dynamic evidence to the integrated case.

Steps to Reproduce:

1. Login as a caseworker.
2. Register a new Person.
3. Click the New Case link from the tab actions menu and create an instance of the newly configured integrated case.
4. Navigate to the Evidence tab.
5. Add evidence of type MyTestEvidence with a Received Date of 1/1/1900.
6. Click Save.
7. Click In-Edit evidence from the Page Group Navigation Bar.
8. Modify the evidence and change the received date to 2/1/1900 and save.
9. Issue: The following error is presented to the user, 'An un-handled server exception occurred. Please contact your administrator.'

Resolution:

The dynamic evidence can now be created and edited successfully within a case. An issue that was causing the retrieval of incorrect validations when the version of dynamic evidence being used was changed has been fixed.

Technical Services

Workflow

PO08759, WorkItem:259492 - Inconsistent username size limit in SPM is 64 characters causing errors when attempting to load pages

Issue Description:

When using Oracle or H2 databases, usernames can be up to 64 characters long. However, some database fields in Social Program Management are too small to contain a username longer than 40 characters and cause errors when attempting to load pages.

Note DB2 databases are typically not impacted by this issue because DB2 databases allocate four bytes of storage per character on the database and are not usually affected by this issue unless the username consists of mostly multi-byte characters.

User Interface Impact: No

Steps to Reproduce:

1. Login as an administrator to an SPM deployed server using an Oracle database.
2. Click New User under Users in the shortcuts panel.
3. Create a user with a name length of 51 characters and a Role Name of SUPERROLE. Enter the mandatory fields and enable the account.
4. Assign the user a position.
5. Login as the user you created.
6. Register a new Person.
7. Issue: An unhandled exception is displayed.

Resolution:

The sizes of the username fields have been increased to 64 characters. The affected fields have been increased to 64 characters as follows:

• CREOLERuleSetSnapshot.username
• CREOLERuleSetEditAction.username
• PrecedentChangeItem.changedByUsername
• UserPageConfig.username

Note one of the affected tables, PrecedentChangeItem, typically contains a large number of records and resizing a field on this table can take a long time to process. Archiving the dependency manager data first can reduce the processing time.

WORKFLOW

PO08167, WorkItem:244487 - The existing overflow indicator flag is not taken into account when modifying existing Process Instance WDO Data Overflow

Issue Description:

When a workflow is processed, the first entry that is written to the Process Instance WDO Data Overflow entity works correctly. The issue occurs when subsequent updates occur. When the threshold limit of 3900 characters is reached, an overflow indicator flag is set on the Process Instance WDO Data entity. The flag is not taken into account when modifying an existing Process Instance WDO Data Overflow, which results in Duplicate Record Exceptions occurring in the server logs.
**User Interface Impact: **No
Steps to Reproduce:

1. Create a workflow that writes to the Process Instance WDO Data Overflow entity and that increases in size between insertions.
2. The first insertion must be shorter than 3900 characters and then later insertions must cause the overflow to have more than 3900 characters.
3. Issue: A DuplicateRecordException occurs in the server logs.

Resolution:

When a workflow now causes the Process Instance WDO Data Overflow to exceed the 3900 character threshold, the Process Instance WDO Data Overflow processes the overflow indicator flag correctly.

Technical:

The overflow indicator is now calculated based on the record to update instead of the existing record. A Duplicate Record Exception no longer occurs in the server logs.

Integrated Case Management

ELIGIBILITY & ENTITLEMENT

PO08910, WorkItem:263819 - The format of dates that are displayed in the Eligibility Viewer's evidence based key event data is not configurable

Issue Description:

The Eligibility Viewer gives caseworkers a holistic view of eligibility for a person or for an integrated case and includes the display of key events that are changes to an integrated case that might affect eligibility. The format of dates that are displayed in the eligibility viewer's evidence-based key event data is not configurable and defaults to US format, MM/dd/yyyy.
User Interface Impact: No

Prerequisite(s):

1. The Eligibility Viewer must be configured for an integrated case.
2. The date format must be set to a format other than MM/dd/yyyy in both the server's Bootstrap.properties and the client's ApplicationConfiguration.properties.

Steps to Reproduce:

1. Login as a caseworker.
2. Register a new Person.
3. Create an instance of the integrated case configured in the prerequisites for the person.
4. Add the necessary evidence to make the person eligible and apply changes.
5. Add an associated product delivery to the integrated case.
6. Add certification to the product delivery if required.
7. Submit, approve, and activate the product delivery.
8. Click the Eligibility tab on the integrated case to see the Eligibility Viewer.
9. On the viewer, select a product delivery.
10. Issue: Key event dates continue to display in US format.

Resolution:

In the Eligibility Viewer, key event dates are now formatted by using the date format properties that are specified in the Bootstrap properties file. The new formatting is for both the integrated case and person views.
Technical:

For consistent date formatting by the Eligibility Viewer, both client and server date formats must be set to the same value. For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation. In particular, see the related links in** Customizing the display of evidence-based key events//.

WorkItem:274157 - Case Overview does not present entitlement information for cases that use classic rules

Issue Description:

For the Case Overview, the entitlement data and the determination navigation link are not displayed for product delivery cases that use classic rules.

User Interface Impact: No

Prerequisite(s):

1. The agency delivers a product delivery that uses classic rules and has the Case Overview tab enabled for the associated integrated case type.

Steps to Reproduce (Generic):

1. Login as a caseworker.
2. Register a new Person.
3. Create an integrated case for the person.
4. Click the Evidence tab and from the dashboard, add evidence that will make the client eligible.
5. Apply changes.
6. Create an associated product delivery case that uses classic rules.
7. Add certification if required.
8. Submit, approve, and activate the product delivery.
9. Click the Financials tab and use the Issue Financials page action to generate the initial payment.
10. Navigate to the Case Overview tab on the integrated case.
11. Expand the product delivery row on the entitlement card.
12. Issue: The Case Overview entitlement card does not display the product delivery case entitlement details and the case 'Decisions' navigation link.

Resolution:

The Case Overview entitlement card has been updated to support product deliveries that use either classic rules or Merative Social Program Management Express Rules (CER). The Case Overview Entitlement card now displays entitlement details for either case type and navigation links to the case 'Decisions' for cases that use classic rules or 'Determination History' for cases that use Merative SPM Express Rules (CER).

CASE AUDITS

PO09048, WorkItem:266034 - Unhandled server exception occurs when generating random case sample in an audit plan

Issue Description:

When generating a random sample of cases within an audit plan, auditors can specify search criteria to be used to generate the sample. When using a DB2 database, if an Organization Unit, Position, or Work Queue is selected for the Owner search criterion in the first step of the Generate Random Case Sample wizard, an unhandled server exception occurs when moving to the next step of the wizard.

User Interface Impact: No

Prerequisite(s):

1. Login as an administrator on a server using a DB2 database.
2. Click New Case Audit Configuration under Case Audits in the shortcuts panel.
3. On the Case Audit Type drop-down, select Integrated Case and click the search icon.
4. Select an integrated case type and click Next.
5. Populate the required fields for the Case Audit configuration and click Save.

Steps to Reproduce:

1. Login as an audit coordinator.
2. Click New Audit Plan under Audits in the shortcuts panel.
3. Populate the required fields, choosing the integrated case type configured above as the Audit Item.
4. Click Save.
5. Click My Audit Plans in the shortcuts panel and select the new audit plan from the My Audit Plans list page.
6. Select Generate Random Case Sample from the page action menu.
7. On the first page of the wizard set the Owner as Organization Unit, Position, or Work Queue and click the search icon.
8. Select one of the items in the list and then click Next on the wizard.
9. Issue: An unhandled server exception occurs.

Resolution:

It is now possible to generate a random sample of cases where the owner is an Organization Unit, Position, or Work Queue. The SQL string and parameters generated for performing the case search have been fixed to properly set the correct data type for the case owner.

COMMON

PO09585, WorkItem:273565 - The build client target fails due to missing property Field.Label.Comments in ICProductSample_close.properties

Issue Description:

The build client target fails due to the missing property Field.Label.Comments in the file ICProductSample_close.properties in the core component.
User Interface Impact: No

Steps to Reproduce:

1. On a Merative Social Program Management development installation, edit the SetEnvironment.sh file and remove the 'sample' component from the component orders.
2. Perform a 'build clean server'.
3. Perform a 'build clean client'.
4. Issue: The client build fails due to the missing property value.

Resolution:

The issue has been resolved by adding the property Field.Label.Comments to ICProductSample_close.properties in the core component.

INCIDENTS

PO09293, WorkItem:269243 - Outcome Plan incidents tooltip displaying incorrect roles

Issue Description:

Registered and prospect persons can be included as participants in an Incident, such as an accident where the participants are given specific incident roles. These same participants can also be included in an Outcome Plan where information about the incident displays in the context panel when selecting the tooltip. When this situation occurs, the outcome plan incidents tooltip displays incorrect roles.

**User Interface Impact: **No

Steps to Reproduce:

1. Login as a Child Welfare caseworker.
2. Register 3 persons.
3. Navigate to the home page of the first person.
4. Select the Issues and Proceedings tab and click Incidents.
5. Use the New page action to create an Incident with the following details:
   • Type: Accident
   • Role: Affected Client
   • Description: ‘Test’
   • Date: Today’s Date
   • Reporter Details: Click Anonymous Report
6. Click Save.
7. On the incident home page, navigate to the Participants tab and click Add Participant.
8. For Participant, select Person on the search type, and search for the Second Person registered.
9. Select the person and add the role as Affected Party.
10. Repeat steps 7- 9 for the Third Person registered, specifying the role as Witness.
11. Navigate to the home page of the First Person.
12. From the tab actions menu, create a case with the type Ongoing Case.
13. On the ongoing case, navigate to the Case Members section under the Participants tab.
14. Click New, add the Second Person and click Save.
15. Click New, add the Third Person and click Save.
16. Navigate to the Outcome Plans tab and click New.
17. Select Type as Child Welfare Outcome Plan Basic Version and Name as Test Outcome Plan.
18. Select all the three clients and click Save.
19. On the outcome plan home page, click the incident tooltip for any case member on the context panel.
20. Issue: Incorrect roles are displayed for the participants.

Resolution:

When a person is a participant in both an incident and an outcome plan, the outcome plan context panel now displays the correct participant tooltip for the incident. The code changes to the method that lists the incident roles for the participants in an incident resolves the issue.

INVESTIGATIONS

PO09556, WorkItem:249545 - Page Not Found error occurs when previewing contacts within a contact log

Issue Description:

A Page Not Found error occurs when a user attempts to preview selected contacts on the Contact Logs page.
User Interface Impact: No

Steps to Reproduce:

1. Login as a Child Welfare intake worker.
2. Create a new Child Protection Services intake.
3. Screen-in, submit, and approve the intake.
4. Login as a Child Welfare investigator.
5. Click the task in the Available Tasks pod.
6. Click the Create Investigation link in the Primary action cluster to open the Create Investigation modal.
7. Select the Participants and click Start to create an Investigation case.
8. Click the Contacts tab and create multiple contacts.
9. Select one or more contacts and select the Preview Selected Contacts page action.
10. Issue: The page for previewing the contact logs cannot be found.

Resolution:

This issue is resolved and contacts now display correctly when they are selected for preview.

PARTICIPANT MANAGEMENT

PO09534, WorkItem:272942 - Adding a previously deleted External Party Office Member is resulting in a validation being thrown

Issue Description:

A validation message is thrown when adding a previously deleted External Party Office Member to an External Party Office.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Click External Party under Registration in the shortcuts panel.
3. On the External Party home page click the Offices tab.
4. Use the New page action to add a new Office.
5. Click the row-level actions menu for the newly added Office and select New Office Member.
6. Add a Name, select the Profile as Administrator, and click Save.
7. Navigate to the Office Members tab within the Office.
8. Remove the newly added Office Member using the Delete row-level action.
9. Click the row-level actions menu for the previously added Office and click New Office Member.
10. Add the same Name and Profile details as the previously deleted Office Member and click Save.
11. Issue: A validation message ‘An office member with the same user name and profile already exists for this external party office.’ is thrown.

Resolution:

The validation logic has been updated to consider the record status of the office member. The office member that was previously deleted with the status of ‘Canceled’ can now be re-added to an office.

PO09521, WorkItem:272947 - Deleting an External Party Office Member's email address results in an error being thrown

Issue Description:

When deleting an email address of an External Party Office Member for the first time, the following validation message is displayed: 'This record has already been deleted'.

**User Interface Impact: **No

Steps to Reproduce:

1. Login as a caseworker.
2. Click External Party under Registration in the shortcuts panel.
3. Register an External Party.
4. On the External Party home page, click the Offices tab.
5. Use the New page action to add a new Office.
6. Click the row-level actions menu for the newly added Office and select New Office Member.
7. Add a Name, select a Profile, and click Save.
8. Navigate to the Office Members tab within the Office.
9. Add an email address for the newly added Office Member using the row-level action.
10. Delete the email address using the row-level action from the email addresses list for the Office Member.
11. Issue: A validation message 'This record has already been deleted' is displayed.

Resolution:

The email address of an External Party Office Member can now be deleted successfully.

Administration Suite

Organization

PO08920, WorkItem:264071 - Descriptions are missing for some of the security groups listed in the Security Group table

Issue Description:

Descriptions are missing for the following entries in the Security Group table:

• EVIDENCEGROUP
• EXTERNALUSERNONSECUREGROUP
• EXTERNALUSERSECUREGROUP
• NAVIGATOREXTERNALUSERNONSECUREGROUP
• NAVIGATOREXTERNALUSERSECUREGROUP
• SUPERGROUP
• SUPERVISORGROUP

User Interface Impact: No

Steps to Reproduce:

1. Login as a system administrator.
2. Click Groups under Security in the shortcuts panel.
3. Issue: The entries above are missing descriptions.

Resolution:

Descriptions have been added for the above security groups in the Security Group table.

ORGANIZATION

PO09256, WorkItem:268833 - Error message not displaying when attempting to delete a user with tasks

Issue Description:

When an administrator tries to delete an internal user when tasks or cases are assigned to that user, the system prevents the delete from occurring and initiates a workflow process to inform the user’s supervisor that they need to action the assigned tasks and cases. However, no validation message is displayed to inform the administrator that the delete cannot occur and to confirm the initiation of the workflow process.

User Interface Impact: No

Prerequisite(s):

1. Login as an administrator.
2. Click the Inbox workspace.
3. Select New Task under Tasks in the shortcuts menu.
4. Create a new task and assign it to an existing user.
5. Click Save.

Steps to Reproduce:

1. Login as an administrator.
2. Click User Search under Users in the shortcuts panel.
3. Search for the user above for which there is an assigned task.
4. Select the user to open the user's homepage.
5. Select Delete from the page action menu.
6. Confirm the deletion in the Delete User modal.
7. Issue: The user delete does not occur as expected; however the user sees no message as to why the delete failed.

Resolution:

Now when an administrator tries to delete an internal user that has tasks or cases assigned, the user sees a validation message that describes why the user cannot be deleted. For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

Technical:

The Delete User modal has been changed so that it invokes the following new facade operation when it is launched:

• Organization.cancelUserPreCheck()

This method validates that the deletion of the user can proceed.

• If there are any validation errors, such as if the user has any tasks or cases assigned, it will display any validation errors in the Delete User modal and ask whether to send a task to the supervisor informing them of the need to reassign tasks or cases. Clicking Yes initiates the Remove User workflow to send the task to the supervisor.
• If there are no validation errors, clicking Yes in the modal initiates the Remove User workflow to proceed with the user deletion.

Intake

PO06416, WorkItem:207558 - Find Client pod gets minimized and the home page reloads

Issue Description:

Using the Find Client pod to enter a person's Reference, First Name, Middle Initials, or Last Name and then pressing the Enter key minimizes the pod and reloads the home page.

User Interface Impact: No

Steps to Reproduce:

1. Login as an intake worker.
2. On the home page in the Find Client pod, enter text into the Last Name field.
3. Press the Enter key on the keyboard.
4. Issue: The Find Client pod minimizes and the home page reloads rather than displaying a search result.

Resolution:

The search criteria now entered in the Find Client pod runs a search of the system to return any results for the person details that are entered.

Technical:

This issue is now resolved by adding onKeyPress listeners to the Reference, First Name, Middle Initial, Last Name, and Date of Birth fields on the Find Client pod. When the Enter key is pressed, JavaScript clicks Search on the Find Client pod.

Application Development Environment

WorkItem:273496 - The GraphQL build script did not include the data fetcher classes from all server components

Issue Description:

The 'rest' and 'restEAR' Ant build targets that build the GraphQL data fetcher Java classes in the REST application did not use the correct list of server components and were not including GraphQL data fetcher Java classes from custom components.
User Interface Impact: No

Resolution:

The relevant Ant build script has been updated to compile GraphqQL data fetcher Java classes from all components that are included in the SERVER_COMPONENT_ORDER environment variable.

WorkItem:273513 - The default-secure-sanitize-allowlist.properties Application Resource is not being loaded from the Application Resource Cache whenever possible

Issue Description:

In version 8.0.0 of the product, the sanitization library was updated. This updated library sanitizes data and property values throughout the application to remove HTML which is potentially malicious. This sanitization library is customizable through an allowlist by adding HTML elements and attributes which are deemed to be safe and removing HTML elements and attributes which are deemed to be potentially malicious. The allowlist of HTML elements and attributes is defined in the 'default-secure-sanitize-allowlist.properties' application resource file. It has been found that the default-secure-sanitize-allowlist.properties Application Resource is not being loaded from the Application Resource Cache whenever possible. This results in an unnecessary number of database calls to retrieve this information.

User Interface Impact: No

Steps to Reproduce:
N/A
Resolution:

The default-secure-sanitize-allowlist.properties Application Resource is now loaded from the Application Resource Cache whenever possible which reduces the number of database calls.

CLIENT DEVELOPMENT ENVIRONMENT

Widgets

PO08982, WorkItem:265493 - Column headers on Apply Changes modal are not displayed after adding SCROLL_HEIGHT to LIST element

Issue Description:

Column headers on a list within the Apply Changes modal are not displayed when the SCROLL_HEIGHT attribute is added to its LIST VIM element.

User Interface Impact: No

Prerequisite(s):

1. Open the Evidence_listEvidenceView1.vim file
   (../webclient/components/core/Evidence Infrastructure).
2. Add SCROLL_HEIGHT="280" to the LIST element on line 42
   • <LIST SCROLL_HEIGHT="280" PAGINATED="false">.
3. Run 'build client'.
4. Build the Merative Social Program Management EAR and deploy the application.

Steps to Reproduce (Generic):

1. Login as a caseworker.
2. Register a person and create an integrated case.
3. Click the Evidence tab and select the Apply Changes page action.
4. Issue: Column headers on the list within the Apply Changes modal are missing.

Resolution:

The column headers in the Apply Changes modal are now displayed.

Technical:

A change was made to gen-jsp-external.xsl to correctly generate the JSP for the Apply Changes page so that column headers are now rendered.

PO09234, WorkItem:268445 - The copy to clipboard functionality is not supported in recommended browsers

Issue Description:

The clipboard functionality in the Merative Social Program Management application is not supported when using a recommended browser.

**User Interface Impact: **No

Steps to Reproduce:

1. Login as an administrator.
2. Click the Administration Workspace tab.
3. Click Merative Social Program Management Rule Sets under Rules and Evidence in the shortcuts panel.
4. Click the Sample Liability Product hyperlink in the list.
5. In the Items cluster, expand the Prerequisites rule group.
6. Select the Edit row-level action on the Eligibility Indicator Test rule.
7. Click the 'Click here to open the formula helper' button.
8. Click Search.
9. Click the [Copy] hyperlink to copy any of the items listed in the Search Results into the browser clipboard.
10. Paste the content of the clipboard into any text processing application to check the content.
11. Issue: The clipboard content does not hold the data that is copied from the application.

Resolution:

The clipboard functionality is now supported on modern browsers on any pages where this functionality is set.

WIDGETS

WorkItem:273101 - Session Timeout modal dialog is incorrectly sized and the buttons for external application are not displayed

Issue Description:

The Session Timeout modal dialog that warns the user that their session is about to expire is incorrectly sized. The Continue and Quit buttons to take any user action are not displayed. The issue occurs in the external application, for example, the Universal Access classic application.
User Interface Impact: No

Steps to Reproduce:

1. Configure the application server to reduce the session timeout to a short interval or take note of the preset timeout interval (usually 30 minutes).
2. Navigate to the first screen of the Universal Access classic application (no login is required) and click a button to start the application.
3. Leave the second screen idle for the timeout interval set or noted in Step 1.
4. After the timeout period, the modal dialog that warns the user that their session is about to expire is displayed.
5. Issue: The dialog is oversized and does not have any control to either log out or extend the current session. The only course of action for the user is to wait for the auto-logout when the count-down that is displayed reaches 0.

Resolution:

The modal dialog size has been restored to the appropriate size and the Continue and Quit buttons are displayed again to allow the user to take the appropriate action.

CORE DEVELOPMENT INFRASTRUCTURE

PO09389, WorkItem:271026 - H2 database driver should not be part of release

Issue Description:

The H2 database driver was included in the directory created by the release target. This driver is only used for development and should not be included in the directory created by the release target.
User Interface Impact: No

Steps to Reproduce:

1. Run the SPM installers.
2. Run the 'build server' target.
3. Run the 'build client' target.
4. Run the 'build {websphere|weblogic} EAR' target.
5. Run the 'build release' target.
6. Issue: The H2 database driver was included in the release target directory.

Resolution:

The issue is resolved by excluding the H2 database driver when populating the release directory.

Technical:

As part of this change, the following file has been updated:

• CuramSDEJ/bin/app_release.xml

WorkItem:273762 - Update the third_party_tools_version.properties file with the supported prerequisite versions

Issue Description:

The configtest target does not reflect the supported third-party prerequisite versions for Merative Social Program Management (SPM) version 8.0.0 and allows false positives to be returned on some dropped third-party software.

**User Interface Impact: **No

Steps to Reproduce:

1. On a freshly installed version of Merative SPM, with all third-party software installed and Bootstrap.properties in place, run 'build configtest'.
2. Issue: No issues are reported even though the installed version of WebSphere does not match what's in the third_party_tools_version.properties file. The same issue occurs if running with WebLogic.

Resolution:

This issue is resolved by making the following changes to the third_party_tools_version.properties file:

version-weblogic {12.1.3.0.0,12.2.1.3.0 => 12.2.1.0.0,14.1.1.0.0}
version-websphere {8.5.5.0,9.0 => 9.0.5}
version-ORA-12 {12 => Removed}
version-ZOS-11 {11.1 => Removed}

The properties version-ORA-12 and version-ZOS-11 have been removed as they are now defunct.

SERVER DEVELOPMENT ENVIRONMENT

XML Server

PO09458, WorkItem:272103 - Code table view does not work if the code table is used in a FIELD with USE_BLANK="true"

Issue Description:

An error occurs if a blank value is chosen from the drop-down field where a code table view is configured for a code table.
User Interface Impact: No

Prerequisite(s):

1. Activate the code table view for code table Gender and the application context APC01 by updating the following files:
a) ../EJBServer/components/core/codetable/CT_Gender.ctx
After line 54 inside CT_Gender.ctx, add the following:

<views>
<view context="APC01">
<code value="SX2"/>
</view>
</views>

**Note: **Any code table can be used here. Gender is used for convenience.
b) .. /EJBServer/components/PFMAppViews/tab/
DefaultAppView/DefaultApp.app
Replace the following line inside DefaultApp.app:

user-message="DefaultApp.UserMessage">

with

user-message="DefaultApp.UserMessage"
context="APC01">

Note: Any .app can be updated. DefaultApp.app is used here.
2. From the EJBServer directory, run the command:

• build ctgen (Note: build server can also be used)

3. From the EJBServer directory, run the command:

• build database

Steps to Reproduce:

1. Login as a caseworker.
2. Select Person under Search in the shortcuts panel.
3. Leave the Gender drop-down blank.
4. Enter First Name and Last Name and click the Search button.
5. Issue: The following error message is displayed - ERROR: The format of an error message is invalid or the placeholder substitution failed: ERROR: The code '%1s' was not found in the code-table '%2s' view '%3'.

Resolution:

The issue is resolved by including conditional logic in the infrastructure for the case where a blank value is chosen for the code table view. Now when a blank value is submitted for a optional drop-down field where a code table view is configured, no error message is displayed.

XML SERVER

WorkItem:271979 - XML Server ThreadPoolWorker data not immediately available for monitoring

Issue Description:

A new XML server startup argument (-forcestatswrite) has been added for the

stats/ThreadPoolWorker-*

records to be flushed from the buffer with each write. This argument is intended for Kubernetes environments where the expectation for performance data (for example, Prometheus) is to be available as it occurs. There is no change to the default behavior.
**User Interface Impact: **No

Steps to Reproduce:

1. Run the Merative SPM application and XML server.
2. Observe that as the application runs and starts the XML server (for example, by creating a referral) that no data is produced in the following files:

• stats/ThreadPoolWorker-*

1. Stop the XML server.
2. Issue: Observe that when stopped, if there was XML server activity, there is data in the following files:

• stats/ThreadPoolWorker-*

Resolution:

Starting the XML server with -Dadditional.args="-forcestatswrite" now flushes the statistics buffer with each write and there is data in the following file:

stats/ThreadPoolWorker-*

Business Services

Word Integration

PO09019, WorkItem:265565 - File Not Found errors in server logs for the quicknote_settings.js file

Issue Description:

When a caseworker adds a Quick Note for a person by using the Smart Panel, the following error appears in the server logs:

'SRVE0190E: File not found: /cefwidgets/ckeditor_settings/
cefwidgets/ckeditor_settings/quicknote_settings.js'

**User Interface Impact: **No

Steps to Reproduce:

1. Login as a caseworker.
2. Search for and open a person.
3. Expand the Smart Panel on the right side.
4. Enter a quick note and click Save.
5. Issue: 'SRVE0190E: File not found: /cefwidgets/ckeditor_settings/
   cefwidgets/ckeditor_settings/quicknote_settings.js' appears in the server log.

Resolution:

This issue is resolved by correcting a malformed reference to the file's location in a renderer file.

WORD INTEGRATION

WorkItem:272357 - Silent install of Word Integration Assistant ignores INSTALLDIR install property for Per Machine (system level) install

Issue Description:

When using the silent install option of Word Integration Assistant Installer in version 8.0.0 and performing a system-level install, the INSTALLDIR property that is specified at the outset is ignored and it will always install to 'C:\Program Files (x86)\IBM\WordBridge'. This is not an issue for the UI Wizard install and does not affect Per User install (silent or UI install).
**User Interface Impact: **No

Steps to Reproduce:

1. Install Microsoft Word at the system level.
2. Install a Java Runtime Environment version 8 at the system level. Note the path to the JRE folder for a later step.
3. Install Google Chrome and Microsoft Edge on Chromium at the system level.
4. Open a command window running as administrator and specify this command:

• msiexec /i IBMCuramWordIntegrationAssistant.msi
  ALLUSERS=1 INSTALLDIR="C:\v80WordInteg"
  WORD_BRIDGE_JAVA_HOME="C:\IBM_JAVA\jre" /qn /l*v
  SilentInstallPerSystem.log
• Substitute C:\IBM_JAVA\jre with the path to the JRE folder noted in step 2.

1. Issue: The Word Integration Assistant should be installed to C:\v80WordInteg, but it is installed to C:\Program Files (x86)\IBM\WordBridge.

Resolution:

The installer has been updated so that for both user-level and system-level silent installations, the INSTALLDIR install property is honored.

Common Intake

PO09233, WorkItem:268282 - Find Match issue when multiple application cases exist for a prospect person

Issue Description:

When a prospect person has two open application cases and a caseworker uses the Find Match functionality on one of the application cases to match the prospect person to a registered person, an error message is displayed.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Register a Prospect Person.
3. Select New Application Case from the tab actions menu.
4. Select an application type in the drop-down and click Save.
5. Again, select New Application Case from the tab actions menu.
6. Select a different application type from the one above and click Save.
7. Register a person with the same name as the prospect.
8. Navigate to one of the application cases.
9. Click the Clients tab.
10. Select the Find Match row-level action from the prospect person listed.
11. Enter the name of the person and click Search.
12. Select the person registered at step 7 and click Save.
13. Issue: An error message is displayed, 'The client <client name>, already exists in application case <other application number>'.

Resolution:

This issue is resolved and the error message is no longer displayed in the above scenario.

WorkItem:274887 - New Visibility field added for user grouping of system messages

Issue Description:

System Messages now include a new attribute called Visibility. The attribute determines the user group to which a system message is visible, for example, Logged-in users, Public users, or Public and logged-in users.
User Interface Impact: Yes

**Steps to Reproduce: **N/A

Resolution:

1. Log in to the Administration application.
2. Click the Administration Workspace tab.
3. Click the System Messages menu option in the Universal Access shortcut.
4. You can view the new Visibility field in either the system message list page, or when you edit or create a system message.

Curam Modules

Outcome Management

PO08585, WorkItem:254353 - Recommended activities not automatically added to an outcome plan when configured to do so

Issue Description:

Outcome Plan Recommendations can be configured for services, referrals, and actions to indicate that a caseworker is advised to add the recommended activities to the outcome plan. An application property is also available to indicate that any recommended activities are automatically added to an Outcome Plan when it is created. Currently, when the application property is enabled, the recommended activities are not being automatically added to the Outcome Plan.

**User Interface Impact: **No

Prerequisite(s):

1. Login as an administrator.
2. Click Outcome Plans under Outcome Management in the shortcuts panel.
3. Select an existing outcome plan and navigate to the Recommendations tab.
4. Click the actions menu and select to configure two recommendations for the outcome plan.
5. Navigate to the Cases tab and note which case types are assigned to the outcome plan.
6. Login as a system administrator.
7. Click Property Administration under Application Data in the shortcuts panel.
8. Change the property 'curam.outcomeplanning.outcomePlanAutoPopulateEnabled' to 'true' and publish the change.

Steps to Reproduce:

1. Login as a caseworker.
2. Register a person.
3. Add a new case of the type that is assigned to the outcome plan.
4. Create a new Outcome plan for this case.
5. Issue: The recommended activities are not added automatically to the outcome plan.

Resolution:

When an outcome plan is now created, the recommended activities are automatically added and displayed under the Activities tab.

Technical:

This was resolved by adding the appropriate logic to the OutcomePlan.createFromRelatedCase facade to check the system property and add the activities accordingly. This issue was happening because the facade method, OutcomePlan.createFromRelatedCase, used in creating the outcome plan for an existing case was missing the logic to add the activities if the system property was enabled.

PO08883, WorkItem:268295 - It is not possible to unset the expected end date on an Outcome Plan once it has been set

Issue Description:

On an Outcome Plan when an Expected End Date is entered, the Expected End Date displays in the context panel. When a user attempts to remove the Expected End Date, the date does not get removed and still displays in the context panel.
User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Register a new Person.
3. Create a new integrated case for the person.
4. Click the Outcome Plans tab and select the New page action.
5. Populate the mandatory fields and leave the Expected End Date blank.
6. Select the client and click Save.
7. Edit the outcome plan and enter an Expected End date.
8. Click Save.
9. Note that the Expected End Date is displayed correctly.
10. Edit the outcome plan again and remove the Expected End Date.
11. Click Save.
12. Issue: The Expected End Date is still displayed.

Resolution:

The logic for updating the Expected End Date on an outcome plan has been modified to allow the Expected End Date to be cleared.

WorkItem:272368 - Deprecate property no longer used in the outcome planning workspace

Issue Description:

The property ‘curam.outcomeplanning.defaultTimelineView’ is only applicable to the older Flex-based outcome planning workspace which was removed from the product in version 8.0.0. The newer Dojo JavaScript outcome planning workspace displays an updated layout and this property is not referenced by that workspace.

**User Interface Impact: **No

Resolution:

The property 'curam.outcomeplanning.defaultTimelineView' has been deprecated.

Artefacts were deprecated as a result of this change. For more information, please see this ticket in the "Notes on Deprecation" section.

Verification

PO09154, WorkItem:267601 - Verification Item with 'To Date' in the past causes existing Verified Verifications to change to Not Verified

Issue Description:

When a user selects to view verifications within a case, the status of each verification is redetermined using expiry date information in order to display the current verification status to the user. The status incorrectly changes from Verified to Not Verified when the 'To Date' of the item used to verify is now in the past. The 'To Date' of the verification item utilization is only intended to control the items displayed to a caseworker when adding proof and should not be used in the calculation that determines if the item used to verify has expired.
**User Interface Impact: **No

Prerequisite(s):

1. A verification must be configured against the evidence being added to the case.
2. For the item used to verify, set the verification item utilization 'To Date' to the current date and leave the Expiry Days and Warning Days fields blank.

Steps to Reproduce (Generic):

1. Login as a caseworker.
2. Register a new Person.
3. Click the Care and Protection tab and select Cases.
4. Using the New page action, create an integrated case.
5. Click the Evidence tab on the integrated case.
6. From the Evidence Dashboard, add an evidence record that requires verification (as configured in the prerequisite(s) section above).
7. Navigate to the Verifications list page and satisfy the verification by adding proof (as configured in the prerequisite(s) section above).
8. Apply changes.
9. Roll the server date forward by one day.
10. From the Verifications tab select All. Notice that the verification correctly displays as Verified. Then select the toggle and expand and then collapse the verification.
11. From the Verifications tab, select the refresh icon and refresh the tab.
12. Issue: The status of the verification incorrectly changes from Verified to Not Verified.

Resolution:

The verification status remains the same when the 'To Date' of the item used to verify is in the past.
For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

Technical:

Only those fields within the Expiry Details section of the verification item utilization administration screen are now considered when determining if an item used to verify a piece of evidence has expired, that is 'Expiry Days' and 'Expiry Date From'. The 'To Date' of the verification item utilization is no longer considered in this calculation.

Universal Access

PO07839, WorkItem:232929 - Universal Access classic application help text is cut off on the final summary page

Issue Description:

In the Universal Access classic application, if a citizen mouses over or clicks the help text that is defined for certain UI elements on the final summary page, the system displays both the help text and tooltip together in an overlapping manner making readability difficult.

User Interface Impact: No

Steps to Reproduce:

1. In the Universal Access classic application, submit an application and reach the final results page.
2. On the final summary page, mouse over and click any of the help text question marks.
3. Issue: The help text and tooltip overlap, which makes readability difficult.

Resolution:

This issue is resolved and now the help text and tooltip no longer overlap when the help text question mark is clicked.

WorkItem:272477 - Universal Access Summary PDFs incorrectly generated from screenings instead of intake applications

Issue Description:

Previously when users of Merative Citizen Engagement or classic Universal Access completed a screening before later completing an intake application, the PDF summary was incorrectly generated. The PDF was generated by using the information pre-populated from the screening instead of the information that they later provided in the intake application.

**User Interface Impact: **No.

Steps to Reproduce:

1. Configure the new Summary PDF Template by:
   • Login as a system administrator, go to Communications > XSL Templates.
   • Search for the Intake Application template with the following details:
   • Description: Intake Application
   • Relates To: Intake Application
   • Category: Intake Application
   • Subcategory: Intake Application
   • Template Type: Letter
   • Template ID: Intake Application
   • Select the template and check it out.
   • Locate the template that you want to upload.
   • This can be your own custom template or, for Universal Access Responsive Web Application, the improved template. For example, to use the improved IntakeApplicationPDFTemplate.xsl template, download it from /EJBServer/components/WorkspaceServices/data/initial/blob/
     IntakeApplicationPDFTemplate.xsl so you can upload it here.
   • Click Check-in template and upload the new or updated template.
2. Create an Account on Universal Access
3. Select a Screening configured to pre-populate an intake application.
4. Start the Intake Application (Social Assistance Application) after the screening is completed
5. Complete the Application and submit it
6. The PDF generated is a one-liner and it shows the Summary screen of the Screening, not the Application
7. Issue: The PDF is generated only with the information of the Screening instead of the Intake Application.

Resolution:

Now when users of Merative Citizen Engagement or classic Universal Access complete a screening before completing an intake application, the PDF summary is correctly generated with the information provided in the intake application.

RESPONSIVE WEB APPLICATION

WorkItem:273477 - Public citizen authentication failure during concurrent load

Issue Description:

During concurrent load testing of the Citizen Engagement (CE) web application, public citizen authentication failures are observed in the server logs. The errors take the following form:
CWL0008 - An encryption error was encountered while SecurityStrategy invocation was being performed in Citizen Workspace. This record has been changed by another user. Please start again.. [err] javax.security.auth.login.FailedLoginException: This record has been changed by another user. Please start again.
This error occurs during the invocation of the modify operation on the External User entity.
User Interface Impact: No

Steps to Reproduce:

1. Use the Citizen Engagement web application during concurrent load.
2. Issue: Observe that authentication errors for the public citizen user are logged in the server log file.

Resolution:

A new environment variable 'curam.citizenworkspace.publicuser.lastloginupdate.disabled' has been introduced that has a default value of 'true'. When the variable is set to 'true', the authentication and authorization mechanisms that record the last public user successful login are disabled so that authentication errors do not occur.

Intelligent Evidence Gathering

PLAYER

WorkItem:272077 - Intelligent Evidence Gathering (IEG) date field values are not being cleared when they are dynamically disabled during IEG script execution

Issue Description:

When executing an Intelligent Evidence Gathering (IEG) script definition containing a date field nested in a conditional cluster, if that date field is hidden/disabled by its conditional control, the value in the date field is not reset.

User Interface Impact: No

Prerequisite(s):

Configure an IEG script definition question page containing:

1. A control question to enable or disable a conditional cluster.
2. A conditional cluster that changes visibility according to the value of the control question.
3. A date field that is contained in the conditional cluster.

Steps to Reproduce:

1. Provide the value to the control question that displays the conditional cluster.
2. Enter a valid date in the date field.
3. Change the value in the control question to hide the conditional cluster.
4. Change the value in the control question again to show the conditional cluster.
5. Issue: The value in the field is not reset, however, the date field is displayed.

Resolution:

This issue is resolved and now the value that was entered in the date field is reset.

Evidence Broker

PO09358, WorkItem:273116 - 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 extra filtering for determining what evidence to share. Before 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 before the release of the enhancements to the Evidence Broker.
User Interface Impact: No

Steps to Reproduce:

There are no steps to reproduce this issue. This can be reproduced only 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 this feature does not support reciprocal evidence such as Relationships as they are handled in a different way.

Financial Management

PO08949, WorkItem:264777 - Application Error occurs when selecting 'Reissue with Applied Deduction' at the person level

Issue Description:

At the person level, if a user attempts to use the options 'Reissue with Applied Deduction' or 'Reissue with Un-applied Deduction' for a payment that has been canceled, an application error occurs and they cannot complete the action.
**User Interface Impact: **No

Steps to Reproduce (Generic):

1. Login as a caseworker.
2. Register a new Person.
3. Create an integrated case for the person.
4. Add the necessary evidence to make the person eligible and apply changes.
5. Add an associated product delivery to the integrated case.
6. Add certification to the product delivery if required.
7. Submit, approve, and activate the product delivery.
8. Click the Financials tab and use the Issue Payment page action to issue a payment.
9. Make an evidence change that will result in a Payment Correction - Overpayment.
10. For the payment that was issued, use the row-level action to Cancel the payment.
11. Navigate to the person home page and click the Financials Transactions tab.
12. For the payment listed, select the 'Reissue with Applied Deduction' row-level action.
13. Issue 1: An 'An Application Error Has Occurred' modal is presented to the user.
14. Issue 2: Although inconsistent, an unhandled server exception can occur when selecting 'Reissue with Un-applied Deduction'.

Resolution:

It is now possible for a caseworker to complete both the 'Reissue with Applied Deduction' and 'Reissue with Un-applied Deduction' options for a canceled payment from the person level.

PO09385, WorkItem:270992 - Creating a deduction on a payment correction (underpayment) case closes the related (RBU) financial component

Issue Description:

When a deduction is saved and activated on an active payment correction underpayment case, the existing underpayment financial component is closed. This results in not being able to process the payment or the deduction.

**User Interface Impact: **No

Prerequisite(s):

1. Login as an administrator.
2. Click Corrections under Case in the shortcuts panel.
3. Click the Payment Correction name hyperlink to navigate to the payment correction configuration.
4. Click the Deductions tab.
5. Use the Add Existing page action to add the Liability Repayment deduction to the payment correction.

Steps to Reproduce (Generic):

1. Login as a caseworker.
2. Register a new Person.
3. Add a new integrated case for the person.
4. Add the necessary evidence to make the person eligible and activate it.
5. Add an associated product delivery to the integrated case, payable 'Weekly By Cash In Advance'.
6. Add certification to the product delivery.
7. Submit, approve, and activate the product delivery.
8. Click the Financials tab and select Transactions.
9. Use the Issue Payment page action to generate a payment.
10. Modify the certification on the product delivery and move the certification from date forward by 4 days.
    • Note that an associated overpayment (payment correction) is created.
11. Now modify the certification from date back to its original value.
    • Note that an associated underpayment (payment correction) is created.
12. Navigate to the payment correction underpayment case.
13. Submit, approve, and activate the case.
    • Doing this will result in a new underpayment (RBU) financial component being created.
14. Click the Financial tab on the payment correction underpayment and select Deductions.
15. Select New Applied Deduction (Variable) from the page action menu.
16. Select the Case Member from the drop-down and click Search.
17. From the search results, select the payment correction overpayment case.
18. Select Benefit Underpayment in the Deduct from Component drop-down.
19. Select Liability Repayment in the Type drop-down.
20. Set the start date as today.
21. Set the percentage to 20.
22. Check the Assign Next Priority checkbox.
23. Click Save & Activate.
24. Issue: A new live deduction is created on the database, however, the existing live underpayment (RBU) financial component is closed.

Resolution:

The live payment correction underpayment (RBU) financial component is no longer closed when a deduction is added to the payment correction (underpayment) case.

PO09390, WorkItem:271066 - Deductions page history list values are not rendered in the correct locale

Issue Description:

****On the Deductions page, the history list values are not rendered in the correct locale.

User Interface Impact: No

Prerequisite(s):

1. Use an instance of SPM with a French language pack installed.
2. Ensure that a product delivery case has a Deduction configured, Liability Repayment, for example.

Steps to Reproduce (Generic):

1. Login as a caseworker whose locale is French.
2. Register a person and create an integrated case.
3. Add evidence to the integrated case and apply changes.
4. Create an instance of the product delivery case.
5. Submit the case for approval and activate it.
6. Click the Financials tab and select Issue Payment.
7. Navigate back to the associated integrated case. Edit the evidence in such a way that an overpayment will be created when the evidence is applied.
8. Apply changes.
9. Navigate back to the Financials tab of the product delivery. Select Over And Under Payments. You see an overpayment.
10. Click the Deductions tab. Click the New Applied Deduction (Fixed) page action.
11. Populate the required fields and select the deduction type that is configured for the product delivery, Liability Repayment, for example.
12. Save and activate the deduction.
13. Expand the deduction line item.
14. Issue: The Deductions page history list values of Deduction Activated and Deduction Created are displayed in English instead of French.

Resolution:

The Deductions page history list now displays in the correct locale.

Solutions

Child Welfare

PO09556, WorkItem:249561 - Page Not Found error occurs when a user previews selected contacts on an Ongoing Case

Issue Description:

A Page Not Found error occurs when a user attempts to preview selected contacts on the Contact Logs page on an Ongoing Case.

User Interface Impact: No

Steps to Reproduce:

1. Login as a Child Welfare caseworker.
2. Select Register Person and Create Case from the shortcuts panel.
3. Enter details to register a person and select Ongoing Case in the Type drop-down.
4. Click Save.
5. Click the Contacts tab and create multiple contacts.
6. Select one or more contacts and select the Preview Selected Contacts page action.
7. Issue: The page for previewing the contact logs cannot be found.

Resolution:

This issue is resolved and it is now possible to preview the selected contacts on an Ongoing Case.

WorkItem:272198 - New intake modal Types selection box is too small when the modal first loads

Issue Description:

When an intake worker is creating an intake, the Types selection box is too small on the New Intake modal.

**User Interface Impact: **No

Steps to Reproduce:

1. Login as a Child Welfare intake worker.
2. Navigate to the shortcuts panel.
3. Select New Intake under Intakes in the shortcuts panel.
4. Issue: The Types selection box is too small on the New Intake modal.

Resolution:

When the New Intake modal is launched, the Types selection box is sized correctly and the contents within it are clearly visible to the intake worker.

Income Support CGISS

Medical Assistance

PO08886, WorkItem:263335 - Validation to enforce alignment of household member and living arrangement evidence only gets called when household member evidence changes are applied

Issue Description:

For each case member in an Income Support case, Living Arrangement evidence must cover the full period of time that the case member is a household member as defined by their Household Member evidence on the case.
A validation intended to prevent activation of evidence resulting in living arrangement periods not covering the entire household member period was only being called when applying changes to Household Member evidence. This incorrectly allowed for Living Arrangement evidence to be modified on its own so that the dates no longer covered the entire household member period.

User Interface Impact: No

Steps to Reproduce:

1. Login as an Income Support caseworker.
2. Register a new Person.
3. Create, submit, and authorize an Income Support application for the person.
4. Navigate to the Income Support integrated case evidence dashboard, clear all verifications, and apply all evidence changes.
5. Edit the living arrangement evidence adding an end date.
6. Issue: The evidence is incorrectly allowed to activate even though it no longer covers the entire period of the household member evidence.

Resolution:

The validation check is now called whenever changes to living arrangement evidence, household member evidence, or both are applied. The existing validation logic has also been rewritten to enhance the validation check. Previously, where there were multiple living arrangement evidence records for an individual, the validation only considered the earliest start date and latest end date and did not account for gaps between living arrangement evidence records. The enhancement to the validation logic now fully prevents activation of living arrangement evidence and/or household membership evidence if it will result in any period of household membership not covered by a living arrangement.

PO09051, WorkItem:266091 - Future date of birth can be entered for Absent Parent evidence

Issue Description:

In an Income Support Application, adding Absent Parent evidence with a future date of birth is allowed. This also occurs when adding the Absent Parent evidence on the Income Support case.

User Interface Impact: No

Steps to Reproduce:

1. Login as an Income Support caseworker.
2. Attempt to register a new Person with a date of birth in the future, 1/1/2025, for example.
3. Clicking Save results in the following validation message being thrown: 'Date of Birth must not be later than today'.
4. Create an Income Support Application by registering a new Person with a date of birth in the future,1/1/2025, for example.
5. Update the date of birth with a correct value, 1/1/1990, for example.
6. Complete the person registration.
7. Create a new Income Support Application for the person.
8. Select checkbox 'Are there any other people living in the household' when creating the application.
9. Fill in all required fields for the parent and the child participants.
10. Answer Yes to the question 'Are there any children in the claimant’s home who have a parent not living in the home?'.
11. Fill in the mandatory fields for the Absent Parent and set the date of birth to the future date.
12. Issue 1: The script goes to the next page without any validation for the Absent Parent unlike the new person created in step 2 for the Income Support application.
13. Complete the application.
14. Open the Income Support case and add another Absent Parent evidence.
15. Enter a future date for the date of birth, 5/5/5555, for example.
16. Click Save and then review the Absent Parent evidence.
17. Issue 2: The evidence saves as normal without any date of birth validation for the Absent Parent on the Income Support case.

Resolution:

A future date of birth can no longer be added on the Absent Parent details page in an Income Support application or when creating Absent Parent evidence in an Income Support case. A validation has been introduced on the Absent Parent page in the application that reads: 'The Absent Parent date of birth must not be in the future.'.
Validation for a future date of birth has been added to the insert and the modify logic for Absent Parent evidence. A new validation message, ERR_ABSENTPARENT_XRV_DOB_MUST_NOT_BE_IN_FUTURE, that reads 'The participant date of birth must not be in the future.' has been added for this validation.

MEDICAL ASSISTANCE

PO08916, WorkItem:263937 - Incorrect timer is created when adding a Retroactive Medical Assistance program to an application that has already been submitted

Issue Description:

Milestones are created and displayed to the user on a Timers page when an Income Support application is submitted. These timers are used to impose time limits within which an application for a program must be processed.
When an application for Medical Assistance is submitted, a Milestone Medical Assistance timer is created. When a Retroactive Medical Assistance program is then added to the Income Support application, a Milestone CHIP timer is incorrectly created instead of another Milestone Medical Assistance timer to represent the new program.

User Interface Impact: No

Steps to Reproduce:

1. Login as an Income Support caseworker.
2. Register a new Person.
3. Submit a Medical Assistance application entering the minimum information required.
4. Open the application and click the Timer tab. Note the creation of a Milestone Medical Assistance timer.
5. Click the Programs tab and select the Add Program page action.
6. Select Retroactive Medical Assistance in the drop-down and ensure that the date/time is not before the application date.
7. Click Save.
8. Issue: On the Timer tab, a new Milestone CHIP timer has been created.

Resolution:

Now when adding a Retroactive Medical Assistance program to an existing application, a Milestone Medical Assistance timer is created instead of a Milestone CHIP timer.

Technical:

The following configuration file has been updated to address this: ISIntakeConfiguration/data/initial/clob/ISEligibilityConfiguration.xml. Specifically, the Milestone ID for Program Type PT4001 has been updated from 1125899906842884 (Milestone CHIP timer) to 1125899906842883 (Milestone Medical Assistance timer).

PO08942, WorkItem:264596 - Medical Assistance application submitted with past date showing eligibility results in the incorrect column

Issue Description:

When a caseworker processes an initial Medical Assistance application on the integrated case, rather than on the application, and Check Eligibility results in an eligible determination that ends before the current date, it is not possible to authorize the eligible unit as it displays under Future Eligibility.
**User Interface Impact: **No

Steps to Reproduce:

1. Login as an Income Support caseworker.
2. Register a person with a registration date about a month ago.
3. Submit a basic application for both Food Assistance and Medical Assistance for the person registered, with an application date the same date as person registration.
4. Add evidence so that the Food Assistance application is eligible.
5. Add Disability evidence for the claimant. Disability type: Blind; 1619(b) Recipient checked; Start Date: a date prior to the application date; End Date: a date prior to the current month.
6. Add proof for any outstanding verifications and apply changes.
7. For the Food Assistance application, check eligibility and authorize.
8. From the person home page navigate directly to the integrated case, rather than the application.
9. Check eligibility for Medical Assistance for 12 months with a start date matching the application date.
10. Expand the Eligibility Checks decision for Medical Assistance.
11. Issue: The person is correctly found eligible for Medical Assistance but the eligible period displays under Future Eligibility and cannot be authorized.

Resolution:

The eligible decision is now displayed under the Eligible heading and can be authorized from the row-level action. This has been resolved by treating past periods of eligibility in the same way as current periods of eligibility.

PO09142, WorkItem:267415 - Long Term Care expensive home exception is not being given for an adult child that is blind living in the home

Issue Description:

An individual is incorrectly determined ineligible for Medical Assistance Long Term Care due to the ownership of an expensive home even though they satisfy the exemption criteria based on an adult child who is blind living in the home.

**User Interface Impact: **No

Prerequisite(s):

1. The current Rate Table CER Home Equity Resource Limit is less than 700000.

Steps to Reproduce:

1. Login as an Income Support caseworker.
2. Register an adult.
3. Submit a Medical Assistance application for the adult registered and include an adult child in the application.
4. On the application add the following evidence from the application date:
   • Disability for the claimant. Disability Type: Acquired Brain Injury; Brain Injury Category: Brain Injury which Produces a Motor Deficit; Established Disability Mode: State Approved Disability Determination Body.
   • Level of Care for the claimant. Level of Care Type: Intermediate or Skilled Nursing Care.
   • Medical Institution Evidence. Waiver Type: Brain Injury Waiver; Expected Length of Stay: > 6 months; Application Filed by Type: Self.
   • Property for the claimant. Property Type: Home and Surrounding Property; Fair Market Value: 700000; Category: Real.
   • Ownership record for the claimant for the property. Percentage Owned: 100; Usage: Home; Ownership Type: Owner.
   • Disability for the child. Disability Type: Blind; Disability Duration: Permanent SSA or Permanent Non-SSA.
5. Check eligibility for Medical Assistance.
6. Issue: Medical Assistance Long Term Care is ineligible due to the ownership of an expensive home.

Resolution:

The expensive home exception rule has been modified to correct the relationship logic. Previously the relationship test expected the relationship between the individual being determined for LTC and the reciprocal participant to be 'child of'. This has now been corrected to 'parent of'. The remaining logic for determining whether the exception is satisfied based on the child living in the household was reviewed and considered correct. This same rule is used for Long Term Care, Medically Needy Long Term Care, and Medically Needy Long Term Care with Spend Down.
The following rules have been modified to address this.

• Rule Set: LTCRuleSet
• Rule Class: LTCCPRCalculator
• Attribute: isSatisfyingExpensiveHomeExceptionTimeline

PO09153, WorkItem:267561 - Long Term Care expensive home exception is not being given where the spouse is living in the home

Issue Description:

An individual is incorrectly determined ineligible for Medical Assistance Long Term Care due to the ownership of an expensive home even though the individual is exempt from this rule because their spouse is living in the home.

User Interface Impact: No

Prerequisite(s):

1. The current Rate Table CER Home Equity Resource Limit is less than 700000.

Steps to Reproduce:

1. Login as an Income Support caseworker.
2. Register an adult and submit a Medical Assistance application for them and their spouse where both live at home, are permanent state residents, are US citizens, and each supply their SSN.
3. On the application, add the following evidence from the application date:
   • Disability for the claimant. Disability Type: Acquired Brain Injury; Brain Injury Category: Brain Injury which Produces a Motor Deficit; Established Disability Mode: State Approved Disability Determination Body.
   • Level of Care for the claimant. Level of Care Type: Intermediate or Skilled Nursing Care.
   • Medical Institution Evidence. Waiver Type: Brain Injury Waiver; Expected Length of Stay: > 6 months; Application Filed by Type: Self.
   • Property for the claimant. Property Type: Home and Surrounding Property; Fair Market Value: 700000; Category: Real.
   • Ownership record for the claimant for the property. Percentage Owned: 100; Usage: Home; Ownership Type: Owner.
4. Check eligibility for Medical Assistance.
5. Issue: Medical Assistance Long Term Care is ineligible due to the ownership of an expensive home.

Resolution:

The expensive home exception rule was modified so that it can now be satisfied when the spouse lives in the home. The rule continues to be satisfied by the existing condition related to ownership of the property. This same rule is used for Long Term Care, Medically Needy Long Term Care, and Medically Needy Long Term Care with Spend Down.
The following rules have been modified to address this.

• Rule Set: LTCRuleSet
• Rule Class: LTCCPRCalculator
• Attribute: isSatisfyingExpensiveHomeExceptionTimeline
• Rule Set: ISProductRuleSet
• Rule Class: Ownership
• Attribute: caseParticipantRoleRecord [new]

PO09152, WorkItem:271103 - Long Term Care expensive home exception is not being given for a child under 21 living in the home

Issue Description:

An individual is incorrectly determined ineligible for Medical Assistance Long Term Care due to the ownership of an expensive home even though they satisfy the exemption criteria based on having a child under 21 living in the home.

User Interface Impact: No

Prerequisite(s):

1. The current Rate Table CER Home Equity Resource Limit is less than 700000.

Steps to Reproduce:

1. Login as an Income Support caseworker.
2. Register an adult.
3. Submit a Medical Assistance application for the adult registered and include a child under the age of 21 in the application.
4. On the application add the following evidence from the application date:
   • Disability for the claimant. Disability Type: Acquired Brain Injury; Brain Injury Category: Brain Injury which Produces a Motor Deficit; Established Disability Mode: State Approved Disability Determination Body.
   • Level of Care for the claimant. Level of Care Type: Intermediate or Skilled Nursing Care.
   • Medical Institution Evidence. Waiver Type: Brain Injury Waiver; Expected Length of Stay: > 6 months; Application Filed by Type: Self.
   • Property for the claimant. Property Type: Home and Surrounding Property; Fair Market Value: 700000; Category: Real.
   • Ownership record for the claimant for the property. Percentage Owned: 100; Usage: Home; Ownership Type: Owner.
5. Check eligibility for Medical Assistance.
6. Issue: Medical Assistance Long Term Care is ineligible due to the ownership of an expensive home.

Resolution:

The expensive home exception rule has been modified to correct the relationship logic. Previously the relationship test expected the relationship between the individual being determined for LTC and the reciprocal participant to be 'child of'. This has now been corrected to 'parent of'. The remaining logic for determining whether the exception is satisfied based on the child living in the household was reviewed and considered correct. This same rule is used for Long Term Care, Medically Needy Long Term Care, and Medically Needy Long Term Care with Spend Down.
The following rules have been modified to address this.

• Rule Set: LTCRuleSet
• Rule Class: LTCCPRCalculator
• Attribute: isSatisfyingExpensiveHomeExceptionTimeline

PO09624, WorkItem:274080 - RetroActive Eligibility is listed twice on Long Term Care product delivery summary display rules tab

Issue Description:

Participants can be eligible for Medical Assistance Long Term Care up to three months before the application date through the retroactive rules. When this situation occurs, on the Summary tab of the Long Term Care product delivery case summary display rules, the RetroActive Eligibility section appears twice.

User Interface Impact: No

Steps to Reproduce:

1. Login as an Income Support caseworker.
2. Register a new Person (older than age 65 years).
3. For the person, add a new application for both Retroactive Medical Assistance and Medical Assistance on the same application.
4. Submit the application with the application dates to today's date and both Member of Household and Living Arrangement dates set to 3 months ago. For example, if the application date is 13 October then these dates are 13 July.
5. On the application add evidence details:
6. Add Level of Care:
   • Level of Care Type: Hospital Level of Care
   • Certification Start Date: the same date as Living Arrangement above
   • Certifier Type: Physician
   • Add Certifier details
7. Add Medical Institution:
   • Institution Type: Hospital
   • Entered Date: the same date as Living Arrangement above
   • Expected Length of Stay: > 6 months
   • Application Filed By Type: Other
   • Add Medical Institution details, Placed By details and Application Filed By details
8. Add Medical Expense evidence with details
   • Amount: $10
   • Frequency: Monthly
   • Medical Expense Type: Cost of Care Expenses
   • Start Date: the first of the previous month (for example 1 September if using the example dates above)
   • Add Medical Service Provider details
9. Check eligibility for both Retroactive Medical Assistance and Medical Assistance.
10. For the eligibility check, confirm that the client is eligible for Long Term Care (LTC).
11. Add verifications proof, apply evidence changes, and mark as Ready for Determination.
12. Authorize the eligible LTC coverage and activate the product delivery online.
13. Navigate back to the Income Support application and authorize the Retroactive Eligible LTC case.
14. Open the LTC product delivery then click the Determinations tab and select Current Determinations and select the earliest coverage period.
15. Issue: RetroActive Eligibility is listed twice on the Summary tab.

Resolution:

When a participant is eligible for Medical Assistance for Long Term Care in the three months before the application date, this issue is resolved. Now the RetroActive Eligibility section appears only once within the Long Term Care product delivery case Summary display rules tab.

Income Support HCR

PO08414, WorkItem:250120 - Lump sum amount income is not being counted by rules for the month that it was reported

Issue Description:

For Streamlined Medicaid, Income evidence of type ‘Lump sum Amount’ is intended to be counted by rules only in the month that it was reported. For the initial eligibility result, this is working as expected. However, when subsequent reassessments are made on the case in the following calendar months, the new determinations no longer count the lump sum income amount in the month in which it was reported.
**User Interface Impact: **No

Steps to Reproduce:

1. Login as an Insurance Affordability caseworker.
2. Register a new person.
3. Submit a new application for a one-person household and authorize.
4. Navigate to the Insurance Affordability integrated case and add the following evidence:
   • Income: Wage and Salaries: $500/monthly with a start date set to the first of the current month.
   • Income: Lump Sum Amount: $20000/monthly with a start date set to the first of the current month.
5. Apply changes.
6. Review the determinations on the newly created Streamlined Medicaid product delivery.
   • The person will be ineligible for the current month and eligible thereafter.
   • Within the ineligible coverage period, navigate to the Income tab and then to the Income page within the page group navigation bar.
   • Note that for the current ineligible month, the lump sum has been included under the MAGI Based Income and MAGI Income (Annual Amount) columns in the Income Details list.
   • The lump sum is not counted in subsequent eligible months (as expected).
7. Move the server date forward to a day in the next calendar month.
8. Add Medical Bills evidence with a start date set to the current server date (arbitrary change that does not impact eligibility).
9. Apply changes.
10. Review the determinations on the Streamlined Medicaid product delivery (as above).
11. Issue: The person is now eligible for the previous month. For the previous month, the lump sum is not included under the MAGI Based Income column in the Income Details list. The MAGI Income (Annual Amount) is marked as Not Applicable.

Resolution:

For Streamlined Medicaid, the lump sum income is counted by rules only in the month that it was reported regardless of the reassessment date.

Technical:

The following rules changes have been made to address this issue:

• RuleSet: /EJBServer/components/HCR/CREOLE_Rule_Sets/HealthCareRuleSet.xml
• Rule Class: IncomeCPRCalculator
• Rule Attribute: lumpsumIncomeAmountTimeline, the sum of the lumpsum records where each lump sum amount is timelined from its start date to the end of that month.
• Rule Attribute: amountExcludedForMedicaidTimeline: lumpsumIncomeAmountTimeline is no longer included in this calculation as the lumpsumIncomeAmountTimeline is now constrained to the month in which it should be counted.

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

Issue Description:

Insurance Affordability cases use specific logic to apply changes to evidence. 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 Insurance Affordability-specific apply changes logic.
**User Interface Impact: **No

Prerequisite(s):

1. 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 new Person and submit a new Insurance Affordability application.
3. Authorize the application.
4. Navigate to the newly created Insurance Affordability 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 in Advanced Evidence Sharing for handling unexpected exceptions during the reflection API call has been updated to correctly log the underlying stack trace that caused the activation of evidence to fail.****

Product Documentation

WorkItem:274665 - Introduction of new evidence sharing key terminology documentation

Issue Description:

When using evidence sharing, it can be helpful to have a list of key terms related to the feature. There is currently no such list for easy reference for evidence sharing.

User Interface Impact: N/A

Steps to Reproduce: N/A
Resolution:

The Sharing evidence by using the evidence broker section in the Merative Documentation Evidence information has been updated to now include a new section that covers the key terminology used in evidence sharing.
For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

Third Party Updates

WorkItem:266694 - Update the configuration and usage of XML Parsers

Previously, the common XML parsers used in the SPM application were not cached and instead were instantiated and configured separately each time they were used. These parsers include the following:

• SAXBuilder
• SAXParser
• Oracle DOMParser
• javax.xml.validation.SchemaFactory
• XMLReader
• SAXReader

The XML parsers are now available, configured, and cached in a single class - XMLParserCache. The default configuration for these XML parsers now also disallows external Doctype declarations and External Entities in the XML that they are parsing.

WorkItem:272371 - Remove the Struts 1 JAR file from the Social Program Management (SPM) product

Struts is a helper framework used by the Social Program Management (SPM) application to organize the page flow of the application and for information exchange. It is used as a passive request router (dispatcher).
The version of Struts 1 previously delivered in SPM, 1.2.9-sp3, is now removed. A number of classes found in the 'struts 1.2.9-sp3.jar' were incompatible with some internal SPM configurations and can no longer be included. The Struts 1.2.9-sp3 JAR file was replaced with the 'spm-core-struts.jar' which does not contain those classes.
As a result of this update, the following changes were made in the Java Development Environment deliverable.

• CuramCDEJ\lib\ext\jar\third_party_version.properties - the reference to Struts 1 was removed.
• CuramCDEJ\lib\ext\jar\struts.jar - this JAR file was removed.
• CuramCDEJ\lib\curam\jar\spm-core-struts.jar - this JAR file was added.

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

WorkItem:273277 - Update browser plugin-in Java™ Runtime Environment (JRE) level used in Microsoft Word Integration

The following JRE level for Microsoft Word Integration is supported for this release:

• JRE 1.8 u311

WorkItem:273278 - Browser support update

The following browser versions are now updated and certified for this release.

Caseworker Application Browser Support

• Google Chrome is updated to 95
• Microsoft Edge is updated to 95

Universal Access Application Browser Support

• Google Chrome is updated to 95
• Microsoft Edge is updated to 95
• Mozilla Firefox is updated to 94
• Apple Safari is updated to 15

WorkItem:273279 - Tablet accessibility support

The certified version of Apple VoiceOver is now updated to iOS 15.1. This is certified against Chrome 95.

WorkItem:273311 - Update the version of the Jsoup library to the latest version: 1.14.2

Jsoup is a Java library that is used to work with HTML. It provides an API for fetching URLs and extracting and manipulating data, by using HTML5 DOM methods and CSS selectors.
The version of the Jsoup JAR that is used by SPM has now been updated from 1.13.1 to 1.14.2. This new JAR file contains some minor bug fixes and enhancements.
As a result of this upgrade, the following changes have been made in the Java Development Environment deliverable.

• CuramSDEJ\lib\third_party_version.properties - the version of the specified Jsoup JAR file has been updated.
• CuramSDEJ\lib\jsoup-1.14.2.jar - the jsoup JAR has been added into the SDEJ at this location.
• CuramCDEJ\lib\ext\jar\jsoup-1.14.2.jar - the version of the JAR has been updated.

Note that any references in custom scripts and other artifacts must be updated to point to the new version of the JAR file as specified above.

WorkItem:273343 - Update the version of the Log4j 2 library to the latest version: 2.14.1

Apache Log4j is a Java-based logging utility that is used as the logging provider for the Social Program Management (SPM) product.
The version of the Log4j used by SPM has now been updated from 2.13.0 to 2.14.1. This new JAR file contains some minor bug fixes and enhancements.
As a result of this upgrade, the following changes have been made in the Java Development Environment deliverable.

• CuramSDEJ\lib\third_party_version.properties - the versions of the specified Log4j JAR files have been updated.
• CuramSDEJ\lib\log4j-api-2.14.1.jar - the version of the JAR has been updated.
• CuramSDEJ\lib\log4j-core-2.14.1.jar - the version of the JAR has been updated.
• CuramSDEJ\xmlserver\log4j-api-2.14.1.jar - the version of the JAR has been updated.
• CuramSDEJ\xmlserver\log4j-core-2.14.1.jar - the version of the JAR has been updated.
• CuramCDEJ\lib\ext\jar\log4j-api-2.14.1.jar - the version of the JAR has been updated.
• CuramCDEJ\lib\ext\jar\log4j-core-2.14.1.jar - the version of the JAR has been updated.

Note that any references in custom scripts and other artifacts must be updated to point to the new version of the JAR file as specified above.

WorkItem:273482 - Update to the Dojo Toolkit library used in the SPM Client Development Environment for Java (CDEJ)

The Dojo Toolkit is an open source modular JavaScript library (or more specifically JavaScript toolkit) designed to ease the rapid development of cross-platform, JavaScript/Ajax-based applications and websites. It is used as the JavaScript framework of choice in the CDEJ (Merative SPM Development Environment for Java) delivered as part of SPM.
An issue with the version of Dojo used in SPM (dojo-ibm-V1.10.5) has been addressed. This has resulted in an update to the following module within the delivered toolkit:

• dojox/Grid/DataGrid

This change is not impactful as it does not modify any of the externally available Dojo APIs delivered.

WorkItem:273721 - Update the xmlsec JAR to the latest version: 2.2.3

The Apache XML Security for Java (xmlsec) library includes a mature Digital Signature and Encryption implementation. It is used in the Social Program Management (SPM) product as part of the Axis 2 secure web services solution.
The version of the xmlsec library used by SPM has been updated from 1.5.8 to 2.2.3. This new JAR file contains some minor bug fixes and enhancements.
As a result of this upgrade, the following changes have been made in the Java Development Environment deliverable.

• CuramSDEJ\lib\third_party_version.properties - the version of the specified xmlsec library has been updated.
• CuramSDEJ\lib\xmlsec-2.2.3.jar - the version of the JAR has been updated.

Note that any references in custom scripts and other artifacts must be updated to point to the new version of the JAR file as specified above.

WorkItem:274730 - Update the Carbon version to 10.44

Carbon is the Merative open source design system for products and digital experiences. Carbon consists of working code, design tools, and resources, and human interface guidelines
The version of Carbon that is used by Merative Social Program Management was updated from 10.28 to 10.44.

Notes on Depreciation

This section describes artifacts that are deprecated in this release and the functionality that supersedes them.

Enhancements or defect fixes might require the contract of a development artifact to be changed. In this context, the contract of an artifact is its API or signature, for example, name, parameters, return values, and its documented statement of functionality, for example, Javadoc.

In these cases, deprecation is used to reduce the impact of the change on custom applications. The original artifact is preserved and marked as 'deprecated' to indicate that it has been superseded by other functionality (often a new artifact). Infrastructure is provided to assist you in identifying custom dependencies on these deprecated artifacts. Deprecation can affect customizations in a number of different ways and has some implications for customer support. For more information about deprecation, see the 'Deprecation' chapter in the Merative Social Program Management Server Developer's Guide. This chapter describes what deprecation is, how it can affect custom code, what it means for support and the build infrastructure that helps pinpoint custom artifact dependencies on deprecated artifacts.

You can find out whether your code is affected by any of the following deprecations (and precisely where) by running the deprecationreport build target. If that build produces deprecation warnings, then you are affected by one or more of the deprecated artifacts that are itemized. For more information about using the build target and analyzing its output, see the 'Deprecation' chapter in the Merative SPM Server Developer's Guide.

Curam Modules

Outcome Management

WorkItem:272368 - Deprecate property no longer used in the outcome planning workspace

How to Upgrade:

N/A

Itemised List of Changes:

The following XML file contains the deprecated property 'curam.outcomeplanning.defaultTimelineView':

• ../EJBServer/components/AssessmentPlanning/properties/Environment.xml:

For more context on the change that caused this deprecation, please see this release note in the "Improvements and Resolved Issues" section.

Known Issues

Curam Enterprise Framework

WorkItem:274885 - Session Timeout not working correctly on Register Participant Wizards

The session timeout is not working correctly on register participant wizards such as Register Person. The case worker is not logged out of the application when the session timeout has expired or when logout is selected on the session timeout modal.

Integrated Case Management

WorkItem:272250 - Some modals are not sized based on the contents they are displaying

The Modal Sizing Tool has not been run on the full 8.0.1 internal application codebase. The tool has been run on the core caseworker functionality and as a result, generic case management and person management modals, such as notes will be updated. The modal sizing tool is yet to be run on the following enterprise modules and solutions:

1. Content Management Interoperability Service (CMIS)
2. Merative SPM Provider Management
3. Outcome Management,
4. Merative SPM Provider Management
5. Cúram Social Enterprise Collaboration
6. Cúram Verifications
7. Merative SPM Citizen Portal
8. Merative SPM Citizen Account
9. Cúram Funded Program Management
10. Priority Complexity And Risk
11. Cúram Supervisor Workspace
12. Merative SPM Appeals
13. Cúram Advisor
14. Service Plans
15. Merative SPM Evidence Broker
16. Cúram Identity Intelligence
17. Merative SPM Global Income Support Internal Application
18. Merative SPM Child Welfare

These will be updated in a subsequent release. It is worth noting, that if there is a custom file, or a file that overrides the core product file, the standard override UIM mechanism will apply. This means, that the UIM displayed will be the overridden file, and the sizing changes will not have been applied.

WorkItem:274691 - An error is displayed when a user saves their changes in the Preferences modal dialog box

When a caseworker saves changes in the Preferences modal dialog box, an error is displayed and their changes are not saved.

WorkItem:274692 - The incorrect time is displayed when editing a meeting time after a custom time was input

When a caseworker edits a record that contains a date and time, for example, editing a meeting, an activity, a task, or a deadline, the time component does not display the value entered by the caseworker. Instead, the time component displays the nearest default value, which is different from the time input by the caseworker. If the caseworker saves this record without making any changes to the time, then the new value will be saved and will overwrite the original value entered by the caseworker.

Application Development Environment

WorkItem:274693 - Duplicate data-testids being used on address fields on Register Person modal

A duplicate data-testid element is being used on the fields Apt/Suite and Street 1 in the Private Address section of the Register Person dialog. The data-testid is attached to the labels 'Apt/Suite' and 'Street 1'.
The CSS selector

input[data-testid="textinput_Field.Label.PrimaryAddressData"]

matches two elements in the Address section of the dialog

1. Apt/Suite
2. Street 1

As a result, the selector is no longer unique.
The following UI elements are currently affected by this duplication issue:

1. data-testid="textinput_Field.Label.PrimaryAddressData"
2. data-testid="textinput-1_Field.Label.PrimaryAddressData"

Developers can still use those selectors but they are producing duplicate UI elements, so they need to implement additional workarounds to choose which one of the multiple elements they wish to work with in the automated test.

Common Intake

WorkItem:273964 - iPad - user is forced to logout when trying to add a participant on any intake

On an iPad, a user is unable to navigate to a page that uses the CKEditor. One such instance where this issue manifests is in Child Welfare. When a user creates a Child Welfare intake on an iPad, they are not able to navigate to the Participants tab.

Curam Modules

WorkItem:274649 - System message visibility field code-table blank value does not default to blank on edit of the record.

A new drop-down field called 'Visibility' has been added to the table 'SystemMessage' in 8.0.1. The value determines the user group that the message is visible to, for example, 'Logged-in users', 'Public users' or 'Public and logged-in users'. For existing records on the 'SystemMessage' table, the value of the new field 'Visibility' is set to 'null'. The 'Visibility' field 'null' value has the same meaning as the default value of 'Logged-in user'. When a 'System Message' record with a 'Visibility' field value of 'null' is edited, the 'Visibility' field dropdown incorrectly defaults to 'Logged-in user' instead of a blank value.
To address this issue, an additional property 'USE_DEFAULT="false"' needs to be added to the 'Visibility' 'FIELD element of the page SystemMessage_modifySystemMessage.vim. This will be updated in a subsequent release.

Provider Management

WorkItem:103350 (was previously CPM-2415) - Incorrect underpayment amount created when multiple service invoice line items reassessed due to change in service rate

When there are multiple service invoice line items created and paid for a provider using a fixed amount service rate and payment option of 'pay fixed amount', if the service rate that was used to determine the payment amount is retrospectively modified, to a higher rate, for example, underpayments are not being generated for all of the affected service invoice line items.

WorkItem:274492 - A 'Null' button appears on the Preview Contract confirmation modal

When a caseworker views the Preview Contract confirmation modal, the 'Yes' button is incorrectly labeled as 'Null'. To view the Preview Contract confirmation dialog, perform the following steps:

1. Login as a Provider Management manager.
2. Click My Providers under Provider in the shortcuts panel.
3. Click the Provider Reference Number hyperlink to open an existing provider in a new tab.
4. Click the Financial tab and select Contracts.
5. Create and generate a Utilization Contract for the contract to go to an Issued state.
6. Select the Preview row-level action for the Utilization Contract.
7. Issue: The 'Yes' button is incorrectly labeled as 'Null'.

Notices

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

CSV Release Notes

ReleaseNotes_8.0.1.0.csv

This CSV file summarizes the individual release notes documented above in the "Improvements, Resolved Issues, 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.