System Requirements

 

For information about the supported software and hardware for this release, see the Merative Social Program Management Prerequisites.

 

 

Installation

 

Install the Merative Social program Management software and supported related software according to the Installing a development environment instructions in Merative Documentation.

 

Additional installation instructions can be found in the Development Environment Installation Guide.

 

Upgrading

 

If you are upgrading from a previous version, the Merative Social program Management Upgrade Helper contains documentation and tooling to help you to upgrade your Merative Social program Management application codebase and database to work with your new version of Merative Social program Management. The Merative Social program Management Upgrade Guide describes a recommended process for performing application and database upgrades. The Upgrade Helper contains tools to assist you with implementing the upgrade, including tooling to produce a schedule of required migrations for your upgrade, tooling to provide information about database schema changes and tooling to generate initial SQL scripts for applying changes to your database.

 

To download the appropriate version of the Merative Social program Management Upgrade Helper, see the download instructions at https://www.merative.com/support/spm.

 

 

Improvements, Resolved Issues, Third Party Updates and Code Removals

 

Accessibility
Look and Feel
Curam Enterprise Framework
Curam Modules
Solutions
Product Documentation
Code Removal
Third Party Updates

 

 

Accessibility

 

WorkItem:257943 - A user is unable to navigate across the content area tab navigation bar using the Up and Down arrow keys

 

Issue Description:

When a user is on the content area tab navigation bar on an intake case in Child Welfare, the user should be able to navigate across the tab navigation bar pressing the Up Arrow key and the Down Arrow key. The user is unable to navigate from one tab to another pressing the Up Arrow key and Down Arrow key.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a Child Welfare Structured Decision-Making intake worker.
2. Navigate to an existing Intake home page.
3. Press the Tab key to navigate to the Home tab in the tab navigation bar.
4. Press the Down Arrow key to move to the next tab.
5. Issue: The user is unable to navigate between the tabs pressing the Up Arrow key and Down Arrow key.

 

Resolution:

The issue has been resolved. The user is now able to navigate through the tab navigation bar using the Up arrow key and the Down arrow key for the Child Welfare intake case.

Technical:

Intake cases in Child Welfare had been configured so that when a new navigation tab is selected, the parent application tab is refreshed. When the parent application tab is refreshed, a dynamic tab loader Java class is invoked which subsequently causes tabs in the tab navigation bar to be reloaded via Javascript. When the currently selected navigation tab is reloaded on the page, the browser focus moves from the selected tab to the top of the screen.

The Javascript related to navigation tabs has been updated so that browser focus remains on the selected tab after the tabs within the tab navigation bar have been reloaded. An attempt to address this issue was previously implemented where a custom Javascript file, CFSS/webclient/components/ChildServices/WebContent/CDEJ/FixTabFocus.js, was invoked by three UIM pages in order to reset the browser focus back to the selected tab after the page was navigated to. The references to this custom Javascript file have been removed from these UIM pages and the custom Javascript file has been removed.
 

WorkItem:263021 - There are a number of accessibility issues in the tooltip dialog that is opened from an icon in a context panel

 

Issue Description:

There are several accessibility issues with the tooltip dialog that can be opened from an icon in a context panel, for example, the Special Caution icon.

 

There are issues for keyboard users who interact with the tooltip dialog. These are as follows:

 

• When the Esc key is pressed while the tooltip dialog is open, the tooltip dialog does not close.
• When opening the tooltip dialog pressing the Space key in the Google Chrome browser; when opened for the first time there is no issue, but when opened pressing the Space key for the second time, the tooltip dialog will close immediately.
• When the tooltip dialog is open and a user navigates by pressing the Tab key, the tab order is not consistent. For example, even though the close button is in the title section, it is last in the tabbing order.
• When the keyboard focus is on the container element of the tooltip dialog and a user presses Shift+Tab, the focus will move outside of the tooltip dialog.

 

There is also an issue for screen reader users when they are using Internet Explorer 11.

 

• When the tooltip dialog is opened, no contextual information is announced, only the close button is announced as that is the element that receives focus when the tooltip dialog opens.

 

User Interface Impact: No

Steps to Reproduce:

Scenario 1:

 

1. Login as a caseworker.
2. Register a new Person.
3. Click on the Issues and Proceedings tab and select Special Cautions.
4. Use the New page action to create a Special Caution.
5. When the context panel has refreshed, navigate to the Special Caution icon.
6. Using the keyboard, open by pressing the Space key.
7. Try to close the dialog by pressing the Esc key.
8. Issue: The dialog does not close.

 

Scenario 2:

 

1. Login as a caseworker using the Google Chrome browser.
2. Register a new Person.
3. Click on the Issues and Proceedings tab and select Special Cautions.
4. Use the New page action to create a Special Caution.
5. When the context panel has refreshed, navigate to the Special Caution icon.
6. Using the keyboard, open by pressing the Space key.
7. Close the dialog by pressing the Space key when the focus is on the close button.
8. Open the dialog again by pressing the Space key.
9. Issue: The dialog closes as soon as it is opened in the Google Chrome browser.

 

Scenario 3:

 

1. Login as a caseworker using the Google Chrome browser.
2. Register a new Person.
3. Click on the Issues and Proceedings tab and select Special Cautions.
4. Use the New page action to create a Special Caution.
5. Create a new Incident and two Investigations from the Incidents and Investigations menus, respectively.
6. Navigate to the Investigation case created second.
7. Open the tooltip dialog from the Investigation or Incident icons.
8. Click inside the tooltip dialog. Press Tab.
9. Issue: The tabbing order is confusing as the close button receives focus last, but it's contained in the title section.
10. Open the tooltip dialog from the Incident icon.
11. Click inside the tooltip dialog. Press Shift+Tab.
12. Issue: The keyboard focus moves outside the tooltip dialog.

 

Scenario 4:

 

1. Enable a screen reader.
2. Login as a caseworker using Internet Explorer 11.
3. Register a new Person.
4. Click on the Issues and Proceedings tab and select Special Cautions.
5. Use the New page action to create a new Special Caution.
6. When the context panel has refreshed, navigate to the Special Caution icon.
7. Using the keyboard, press Space on the Special Caution icon.
8. Issue: When the tooltip dialog opens, there is no contextual information announced and only the close button is announced.

 

Resolution:

The accessibility issues with the tooltip dialog have now been resolved and a user can now close the tooltip dialog by pressing the Esc key. The tab order inside the dialog has been ordered correctly, and when a user is focused on the container element of the tooltip dialog, if the user presses the Shift+Tab keys, the focus will move to an element within the dialog.

In the Google Chrome browser, the tooltip dialog will remain open after a user has pressed the Space key to open the tooltip dialog. In the Internet Explorer 11 browser when a user is using a screen reader, the tooltip title and content is announced when the dialog is opened.

Technical:

The Javascript for the tooltip dialog widget has been updated to address the accessibility issues that occur when interacting with a tooltip dialog in a context panel.
The JavaScript classes that have been updated are:

• ../webclient/components/CEFWidgets/WebContent/CDEJ/jscript/curam/DelayedTooltipDialog.js
• ../webclient/components/CEFWidgets/WebContent/CDEJ/jscript/curam/DelayedTooltipDialog.js.uncompressed.js

 

PO08596, WorkItem:265093 - The screen reader does not announce the details of error messages on modal pages

 

Issue Description:

The screen reader does not announce the details of error messages on modal pages. On non-modal pages, the browser tab title does not indicate there are error messages present.

User Interface Impact: No

Steps to Reproduce:

Scenario 1: Modal pages

 

1. Enable a recommended screen reader.
2. Login as a caseworker.
3. Launch the Register Person wizard.
4. From the Registered Person Check page, click Search without specifying any criteria.
5. Issue: An error message is displayed on the modal but its content is not read by the screen reader.

 

Scenario 2: Non-modal pages

 

1. Login as a caseworker.
2. Search for a Person.
3. Navigate to the Search button and run an empty search.
4. Issue: The browser tab title is not updating to display the presence of error message(s).

 

Resolution:

The screen reader will announce the details of error messages present on modal pages. On non-modal pages, the browser tab title indicates when there are error messages present.

 

WorkItem:265367 - The browser focus indicator for links in context panel is not visible

 

Issue Description:

When a user navigates to the links in the side pane of the context panel pressing the Tab key, such as Items to Verify and Issues, for example, the focus should highlight the link. Instead, the focus is lost and the links are not clearly highlighted.

User Interface Impact: No

Steps to Reproduce (Generic):

 

1. Login as a caseworker using a supported browser.
2. Navigate to the Case and Outcomes section and register a Person and create an integrated case.
3. Open the integrated case and pressing the Tab key from the keyboard, navigate to the link ‘Items to verify’ inside the context panel.
4. Issue: The focus is not visible on the links in the side pane of the context panel.

 

Resolution:

The issue has been resolved. When the user navigates to the side pane of a context panel pressing the Tab key, the links are now highlighted.
 

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

 

Issue Description:

 

In the Universal Access classic application when a supported screen reader is used, the date fields are not announced correctly. Also, the Date Picker widget is not accessible using 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 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 pop-up.
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) that are defined in the product documentation.

 

Resolution:

The product documentation has been updated to specify 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 has been updated so that the screen reader announces the field correctly.

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

 

WorkItem:265372 - Combo boxes are not announced correctly by a supported screen reader

 

Issue Description:

When a supported screen reader is used, combo boxes are not announced correctly. The screen reader incorrectly announces combo boxes as list boxes. Users are therefore not provided with sufficient context.

User Interface Impact: No

Steps to Reproduce:

 

1. Start a screen reader.
2. Login as a caseworker.
3. Open the Register Person page.
4. Navigate to the Gender combo box on the first page of the wizard.
5. Issue: The combo box is not announced correctly by the screen reader.

 

Resolution:

Now when a screen reader user navigates to a combo box, the screen reader correctly announces the combo box.
 

WorkItem:265373 - Screen reader issue on search when using the Edge Chromium browser

 

Issue Description:

When a supported screen reader is used, there is a search issue when using the Edge Chromium browser. When a search is performed, the number of search results returned is not announced by the screen reader.

User Interface Impact: No

Steps to Reproduce:

 

1. Enable a supported screen reader.
2. Login as a caseworker using the Edge Chromium browser.
3. Click on the Search for a Person quick link on the home page.
4. Search for an existing person.
5. Issue: The number of records returned by the search is not announced by the screen reader when the page has reloaded.

 

Resolution:

This issue has been resolved. Now, when a screen reader user performs a search using the Edge Chromium browser, the number of search results returned is announced by the screen reader.

 

WorkItem:265374 - When navigating column headers on a sortable list using the Edge Chromium browser, column headers are incorrectly announced by a screen reader

 

Issue Description:

On the Edge Chromium browser, when a column header on a sortable list is selected by using the keyboard navigation, the screen reader incorrectly announces the header as 'Unlabelled zero button'. Screen reader users are therefore not provided with sufficient context about the sortable list column.

User Interface Impact: No

Steps to Reproduce:

 

1. Start a supported screen reader and open the Edge Chromium browser.
2. Login as a caseworker.
3. Click on the Search for a Person quick link on the home page.
4. Perform a search using criteria that returns several people.
5. Navigate to the second column header for the returned list of people.
6. Navigate back to the first column header for the list of people.
7. Issue: The screen reader announces the column header as 'Unlabelled zero button'.

 

Resolution:

This issue has been resolved. Now on the Edge Chromium browser, when a column header on a sortable list is selected using the keyboard navigation (Tab or Shift and Tab keys), the screen reader correctly announces the column header and the current sorted column order.

 

WorkItem:265376 - The browser focus goes to the next element on the page when the Enter key is pressed on the File Upload browse button

 

Issue Description:

In the Edge Chromium browser, when a supported screen reader is used and the file upload browse button is selected by pressing the Enter key, the browser focus moves to the next element on the page.

 

User Interface Impact: No

Steps to Reproduce:

 

1. Start a screen reader.
2. Login as a caseworker using the Edge Chromium browser.
3. Register a new person and go to the Client Contact tab on the navigation bar.
4. On the Client Contact page, go to Attachment.
5. Click on the New page action control.
6. Go to the file upload browse button and press the Enter key.
7. Issue: The screen reader moves the focus to the next element on the page.

 

Resolution:

Now when you use a screen reader and you select the file upload browse button by pressing the Enter key, the screen reader announces the appearance of a pop-up window and you can select a file to upload.

 

WorkItem:265377 - Search results and keywords link in the Smart Navigator widget are not announced by the screen reader

 

Issue Description:

When a supported screen reader is used and you search by using the Smart Navigator widget, the search results, and the content of the keywords list, are not announced.

User Interface Impact: No

Steps to Reproduce:

Scenario 1:

 

1. Start a screen reader.
2. Login as a caseworker.
3. Press the Tab key to navigate to the keywords link in the Smart Navigator widget and press Enter.
4. Issue: The content of the keyword list is not announced by the screen reader.

 

Scenario 2:

 

1. Start a screen reader.
2. Login as a caseworker.
3. Press the Tab key to navigate to the Smart Navigator widget.
4. Search for an existing person.
5. Issue: The search result is not announced by the screen reader.

 

Resolution:

Now when a screen reader user searches by using the Smart Navigator widget, the search results, and the content of the keywords list, are announced to the user.

Technical:

The following files were updated as part of addressing the accessibility issues with the Smart Navigator widget:

• TI/client/components/client-inf/jscript/src/internal/curam/widget/SearchMultipleTextBox.js
• TI/client/components/client-inf/jscript/src/internal/curam/widget/templates/SearchMultipleTextBox.html
• TI/client/components/renderer-plug-ins/src/main/java/curam/util/client/render/component/ApplicationSearchPanelRenderer.java

 

WorkItem:265759 - The summary content of tables with headers is announced incorrectly by a screen reader when using Internet Explorer 11

 

Issue Description:

When a supported screen reader is used and a visually impaired user navigates to a table with headers, the screen reader announces the default summary content of tables as 'Table for formatting purpose only' when using Internet Explorer 11 (IE11).

Note:

All of the reported instances of this issue occur in Child Welfare.

User Interface Impact: No

Steps to Reproduce (Child Welfare):

Scenario 1:

 

1. Start a screen reader.
2. Login as a Child Welfare caseworker by using IE11.
3. Register a new Person.
4. Click the Background tab and select Education.
5. Issue: The screen reader announces the table on the Education page incorrectly.

 

Scenario 2:

 

1. Start a screen reader.
2. Login as a Child Welfare caseworker by using IE11.
3. Register a new Person.
4. Click the Background tab and select Employment.
5. Issue: The screen reader announces the table on the Employment page incorrectly.

 

Scenario 3:

 

1. Start a screen reader.
2. Login as a Child Welfare caseworker by using IE11.
3. Register a new Person.
4. Click the Background tab and select Gang Affiliation.
5. Issue: The screen reader announces the table on the Gang Affiliation page incorrectly.

 

Scenario 4:

 

1. Start a screen reader.
2. Login as a Child Welfare caseworker by using IE11.
3. Select Register Person and Create Case under Cases in the shortcuts panel.
4. Enter person details and select Ongoing Case in the Type drop-down.
5. Click Save.
6. On the Ongoing Case, click the Contact tab and select Contact Logs.
7. Issue: The screen reader announces the table on the Contact Logs page incorrectly.

 

Scenario 5:

 

1. Start a screen reader.
2. Login as a Child Welfare caseworker by using IE11.
3. Select Register Person and Create Case under Cases in the shortcuts panel.
4. Enter person details and select Ongoing Case in the Type drop-down.
5. Click Save.
6. On the Ongoing Case, click the Administration tab and select Related Cases.
7. Issue: The screen reader announces the table on the Related Cases page incorrectly.

 

Scenario 6:

 

1. Start a screen reader.
2. Login as a system administrator by using IE11.
3. Click Property Administration below Application Data in the shortcuts panel.
4. Enter 'curam.evidence.pdc.personenabled' in the Name field and click Search.
5. Use the Edit Value row-level action to update the value of the returned property to NO and click Save.
6. Use the Publish page action to publish the changes.
7. Login as a Child Welfare caseworker using IE11.
8. Register a new Person.
9. Click the Identity tab and select Alternate Names.
10. Issue: The screen reader announces the table on the Alternate Names page incorrectly.

 

Scenario 7:

 

1. Start a screen reader.
2. Login as a system administrator by using IE11.
3. Click Property Administration below Application Data in the shortcuts panel.
4. Enter 'curam.evidence.pdc.personenabled' in the Name field and click Search.
5. Use the Edit Value row-level action to update the value of the returned property to NO and click Save.
6. Use the Publish page action to publish the changes.
7. Login as a Child Welfare caseworker using IE11.
8. Register a new Person.
9. Click on the Identity tab and select Alternate IDs.
10. Issue: The screen reader announces the table on the Alternate IDs page incorrectly.

 

Resolution:

This issue is now resolved and a screen reader no longer announces the content of tables with headers incorrectly as it is not necessary information for visually impaired users.

Technical:

A javascript page generator file was updated to prevent a screen reader from announcing the summary content of a table with headers. This is a generic fix and will address every instance of this problem, not just for the examples provided above.

 

WorkItem:266244 - The browser focus is not visible on the icon that was used to launch a window after the window is closed

 

Issue Description:

After a window is closed, the browser focus is not visible on the icon that was used to open the window. For example, when a user creates a new activity in the Calendar section, the New Activity modal is launched and from this page when the user navigates to the Location search link icon and presses the Enter key, a window appears. After searching, the window closes and the user is returned to the New Activity modal. The browser focus should be on the Location search link icon. However, the focus does not return to the Location search link icon, which causes an issue for accessibility users. This issue was also seen on the New Evidence modal.

User Interface Impact: No

Steps to Reproduce:

Scenario 1

 

1. Login as a caseworker.
2. Go to the Calendar section and launch the modal to create a new activity.
3. Go to the Location search icon pressing the Tab key and press Enter.
4. When the window appears, navigate to the close button and press Enter.
5. Issue: The browser focus returns to the previous modal and the focus is not on the original Location search link icon after the Locations modal is closed.

 

Scenario 2

 

1. Login as a caseworker.
2. Search for a person and select a person from the list.
3. Go to the Evidence tab and click the New link to create new evidence.
4. When the modal appears, navigate to the close button and press Enter.
5. Issue: The browser focus returns to the previous page and the focus is not on the original New link after the New Evidence modal is closed.

 

Resolution:

This issue is now resolved. After a window is closed, the browser focus is visible on the icon that was used to open the window.
 

WorkItem:266247 - Browser focus is not moving to the top of the list when a new page number or page size is selected

 

Issue Description:

The browser focus is not moving to the top of a list when a new page number or page size is selected in the list control panel of a paginated list.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as an administrator.
2. Select the Cúram Express Rule Sets link in the Rules and Evidence section in the shortcuts panel.
3. Perform a blank search to return a large number of results.
4. Navigate to the paginated list control panel at the bottom of the list.
5. Select the link to bring you to the next page in the paginated list and press Enter.
6. Issue: The browser focus does not move to the top of the list.

 

Resolution:

Now when a user selects a new page number or page size in the list control panel of a paginated list, the browser focus moves to the top of the list.

 

WorkItem:266249 - Screen reader announces the header of sortable columns in a list as a button

 

Issue Description:

When a supported screen reader is used, and a user navigates back to a sortable column header of the Search Results by pressing the Shift+Tab key, the screen reader incorrectly announces the column header as a ‘button’ rather than reading the name of the column header. The column header should be read the same way whether pressing the Tab key or Shift+Tab keys.

User Interface Impact: No

Steps to Reproduce:

 

1. Start a supported screen reader and open a supported browser.
2. Login as a caseworker.
3. Select Search for a Person from the Quick Links pod.
4. Perform a search using criteria that returns a list of several person names. The screen reader correctly announces the header name as Person.
5. Navigate to the second column header by pressing the Tab key.
6. Navigate back to the first column header by pressing the Shift+Tab key.
7. Issue: The screen reader announces the column header as a 'button'.

 

Resolution:

The issue has been resolved. When a user navigates back to the sortable column header of the search result, the screen reader announces the column header name and column sort order correctly.

 

WorkItem:266250 - The screen reader announces the error messages on a page as the list box element in the Edge Chromium browser

 

Issue Description:

When a supported screen reader is used and there is an error message on the page, the screen reader announces the contents of the error message and announces 'list box to move to an item use arrow keys', which is incorrect.

User Interface Impact: No

Steps to Reproduce:

 

1. Start a supported screen reader.
2. Login as a caseworker by using the Edge Chromium browser.
3. Select the Search a Person link under the Quick Links pod.
4. Leave all the fields empty and click the search button.
5. Issue: An error message displays and is announced by the screen reader, followed by the message 'list box to move to an item use arrow keys'.

 

Resolution:

The issue has been resolved. When a screen reader user goes to a page that contains error messages, the error messages are not announced as a list box element.

 

WorkItem:266663 - The screen reader announces 'alert' when opening any modal from the Registration section of the shortcuts panel

 

Issue Description:

The screen reader incorrectly announces 'alert' upon opening modal pages from the Registration section of the shortcuts panel when using the Microsoft Edge Chromium browser.

User Interface Impact: No

Steps to Reproduce

 

1. Enable a screen reader on Microsoft Edge Chromium browser.
2. Login as a caseworker.
3. Select Person under Registration in the shortcuts panel.
4. Issue: The word 'alert' is incorrectly announced by the screen reader.

 

Resolution:

This issue was resolved by updating the HTML template that is used by modal pages. The screen reader no longer announces 'alert' upon the opening of a modal when using the Microsoft Edge Chromium browser.

Technical:

The following file has been changed:

• TI/client/components/client-inf/jscript/src/internal/curam/layout/resources/Dialog.html

 

WorkItem:267516 - Date fields in the Universal Access classic application are not announced properly using a supported browser and a supported screen reader

 

Issue Description:

When a supported screen reader is used and the user navigates to a Date field in the Universal Access classic application, the Date field is not announced correctly as being a combo box component by the screen reader and its list items cannot be navigated as expected by pressing the arrow keys.

User Interface Impact: No

Steps to Reproduce:

 

1. Start a supported screen reader.
2. Login as an external user to the Universal Access classic application using a supported browser.
3. Apply for healthcare assistance.
4. Navigate to a date field on the page in the application pressing the Tab key.
5. Issue: The screen reader announces the date field incorrectly as a textbox.

 

Resolution:

Now when a screen reader user navigates to a Date field in the Universal Access classic application, the field is announced correctly by the screen reader and the arrow keys can be used to expand the calendar and navigate through the calendar component.

 

WorkItem:267546 - Navigating the list items of a combo box with the keyboard is not working correctly

 

Issue Description:

When a user navigates to a list of items of a combo box by pressing the Down Arrow key, the focus indicator moves to the next field. The user is unable to navigate through the list of items.

User Interface Impact: No

Steps to Reproduce:

 

1. Start a supported screen reader.
2. Login as a caseworker using a supported browser.
3. Click the Register a Person link.
4. Navigate to the Gender combo box on the first page of the wizard.
5. Use the Arrow keys to expand the combo box and navigate to its list items.
6. Issue: Navigating the list items of a combo box by pressing the Down Arrow key is not working correctly.

 

Resolution:

When a screen reader user navigates to a combo box field, the Arrow keys can be used to expand the combo box and navigate to its list items.

Technical:

The following files were updated as part of addressing this issue:

• TI/client/components/client-inf/jscript/src/internal/curam/widget/FilteringSelect.js

 

WorkItem:267839 - Combo boxes in the Universal Access classic citizen application are not announced properly and cannot be correctly interacted with using Edge Chromium and a supported screen reader

 

Issue Description:

When a supported screen reader is used by a visually impaired user, and the user navigates to a combo box field in the Universal Access classic citizen application, the combo box is not announced correctly by the screen reader. The list items cannot be navigated as expected by using the Arrow keys.

User Interface Impact: No

Steps to Reproduce:

 

1. Start a screen reader.
2. Login as an external user to the Universal Access classic citizen application.
3. Apply for healthcare assistance.
4. Navigate to a page in the assessment where a combo box is present and use the keyboard to navigate to the combo box.
5. Issue: The screen reader does not announce the combo box correctly as a combo box. Using the keyboard, the combo box cannot be expanded to reveal its list items.

 

Resolution:

Now when a screen reader user navigates to a combo box field in the Universal Access classic citizen application, the field is announced correctly by the screen reader. The arrow keys can be used to expand the combo box and navigate through its list items.

 

WorkItem:268079 - The screen reader is not announcing any page content when navigating in a frame that has been reloaded in the Edge Chromium browser

 

Issue Description:

When a supported screen reader is used and a page is reloaded, the screen reader stops announcing the page content when the user tries to navigate throughout the page.

User Interface Impact: No

Steps to Reproduce:

 

1. Start a supported screen reader.
2. Login as a caseworker by using the Edge Chromium browser.
3. Perform a person search which causes the page to reload.
4. Issue: The screen reader stops announcing the content inside the reloaded page.

 

Resolution:

Now when a page is reloaded, the screen reader announces the content of the page that is reloaded when the user tries to navigate throughout the page.
 

WorkItem:268623 - On an intake case, browser focus is moved to the informational message on the Recommendation page instead of remaining on the Recommendation tab

 

Issue Description:

When a user navigates to the Recommendation tab on an intake case, the browser focus is moved to the informational message on the Recommendation page instead of remaining on the Recommendation tab in the tab navigation bar.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a Structured Decision-Making Child Welfare intake worker.
2. Navigate to an existing Intake home page.
3. Press the Tab key to navigate to the Home tab in the tab navigation bar.
4. Press the Down Arrow key to move to the Recommendation tab.
5. Issue: Browser focus is moved to the informational message on the Recommendation page instead of remaining on the Recommendation tab in the tab navigation bar.

 

Resolution:

Javascript related to navigation tabs has been updated to ensure browser focus remains on the Recommendation tab in the tab navigation bar after the Recommendation page loads and the informational message is displayed.
 

WorkItem:269099 - When a screen reader is enabled, the widget type is announced when opening a tooltip dialog and selecting the close button does not close the dialog

 

Issue Description:

When a supported screen reader is used, and the Special Caution tooltip of the context panel is opened, the screen reader announces the widget type along with the tooltip dialog title and content. Also, when a user navigates to the close button of the tooltip dialog and presses the Enter or Space key, the tooltip dialog does not close.

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 Special Cautions.
5. Create a New Special Caution for the person.
6. Navigate to the Special Cautions icon in the Context Panel by pressing the Tab key.
7. Open the Special Caution tooltip by pressing the Enter key.
8. Issue: The dialog widget type is announced as well as the tooltip dialog title and content.
9. Navigate to the Close button and press the Enter or Space key to Close the tooltip dialog.
10. Issue: The tooltip dialog does not close.

 

Resolution:

This issue has been resolved. When a user navigates to open the Special Cautions icon, the screen reader correctly announces the content of the tooltip dialog. The tooltip dialog now closes when a user presses the Enter or Space key on the close button.

Technical:

The Javascript for the tooltip dialog widget has been updated to address the accessibility issues that occur for screen reader users when they open and close a tooltip dialog in a context panel by using the keyboard.

 

WorkItem:270897 - The page actions toolbar is not announced as a toolbar by a screen reader

 

Issue Description:

The page toolbar containing the Refresh, Print, and Help page action icons is not announced as being a toolbar by a screen reader.

User Interface Impact: No

Steps to Reproduce:

 

1. Start a supported screen reader.
2. Login as a caseworker.
3. Navigate to the Calendar section.
4. Navigate to the first page action icon within the toolbar.
5. Issue: The toolbar is not announced as a toolbar by the screen reader.

 

Resolution:

This issue has been resolved and the page actions toolbar is now announced as a toolbar by a screen reader.
 

WorkItem:271038 - The home page toolbar is not announced as a toolbar by a screen reader

 

Issue Description:

The home page toolbar is not announced as a toolbar by a screen reader.

User Interface Impact: No

Steps to Reproduce:

 

1. Start a supported screen reader.
2. Login as a caseworker.
3. On the home page, press the Tab key to navigate to the first icon in the toolbar.
4. Issue: The icon is announced by the screen reader but the toolbar that contains the icon is not announced as a home page toolbar by the screen reader.

 

Resolution:

This issue has been resolved and the home page actions toolbar is now announced as a home page toolbar by a screen reader.

 

 

Look and Feel

 

PO07593, WorkItem:219669 - Supporting Information text is truncated when the page is being printed

Issue Description:

A typographical error appears when a user prints a Notification page. The letters 'S' and 'u' from the text 'Supporting Information' are missing. The term 'Supporting Information' is truncated and the text is missing.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a new Person.
3. Create any integrated case for the person.
4. Click the Inbox section and select My Notifications under Notifications in the shortcuts panel.
5. Expand the Notification that was created by assigning the role of case owner for the newly created integrated case.
6. Click the Print button on the upper right side of the page.
7. Issue: On the print preview, the term 'Supporting Information' is truncated. The letters 'S' and 'u' from the term and the text is missing.

 

Resolution:

With the new components and Carbon styling that is implemented in the UI, this issue has been resolved. The text 'Supporting Information' is no longer truncated, is spelled correctly, and the text is now visible.

 

PO07825, WorkItem:232150 - Drop Down Default Text is not displayed completely

 

Issue Description:

When an insurance affordability caseworker is creating an insurance affordability application, if a drop-down input field is used, the default text is not displayed completely in the drop-down field.

User Interface Impact: Yes

HCR:

Steps to Reproduce:

 

1. Login as an insurance affordability caseworker.
2. Open the HCR Cases and Outcomes tab.
3. In the Shortcuts panel, open the Registration toggle.
4. Select Person and then register a new person.
5. On the newly registered person's page, in the page action commands on the top right, start a new application.
6. Navigate through the application by providing the required mandatory answers for each page until you reach a page with a drop-down input field.
7. Issue: The default text string in the drop-down is not fully displayed in the field.

 

Resolution:

With the new components and Carbon styling implemented in the user interface the issue has been resolved. The default drop-down text is now displayed fully in the input field.


Intelligent Evidence Gathering:

 

Prerequisite(s):

A custom configuration IEG script definition question page containing:

• A question whose input field is a drop-down box with default text.

 

Steps to Reproduce:

 

1. Launch the custom configured IEG script definition.
2. Navigate to the drop-down field with default text.
3. Issue: The default text string in the drop-down is not fully displayed in the field.

 

Resolution:

With the new components and Carbon styling implemented in the user interface the issue has been resolved. The default drop-down text is now displayed fully in the input field.

 

PO07911, WorkItem:237125 - The header 'undefined' is printed at the top of the page when the page has expandable list items

 

Issue Description:

When a user selects the page level Print icon, the word 'undefined' is printed on the page when the page contains expandable list items.

User Interface Impact: No

Steps to Reproduce:

 

1. Login is a caseworker.
2. Register a Person.
3. Navigate to the Client Contact tab.
4. Collapse the Context Panel by clicking on the Toggle.
5. Create a New Note.
6. Click the toggle to expand the inline page of the Note record.
7. Select the Print icon to print the content.
8. Issue: Page prints with ‘undefined’ on the page, instead of the page title.

 

Resolution:

With the new components and Carbon styling implemented in the UI, this issue has been resolved and the printed page now correctly displays the titles of the page.

 

PO08046, WorkItem:241414 - The page title and page level action link text gets truncated when printing a page in Portrait mode in the Google Chrome browser

 

Issue Description:

When a user selects the page level Print icon and sets the print orientation to Portrait mode, the page title and the page actions link text on the printed page is truncated.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a caseworker using the Google Chrome browser.
2. Register person.
3. Navigate to Special Cautions page in the Issues and Proceedings tab.
4. Click on the Print icon and set the print orientation mode to Portrait.
5. Issue: The page title and link text at the top of the main content page is truncated.

 

Resolution:

With the new components and Carbon styling implemented in the UI, this issue has been resolved. The text on the printed page is displayed correctly.

 

WorkItem:243298 - When printing on a case with multiple case members, the layout of the Print page is displayed incorrectly

 

Issue Description:

When a user selects the Print icon to print multiple case members that are displayed in the Context Panel, the layout of the Print page is incorrectly displayed.

User Interface Impact: No

Steps to Reproduce (Generic):

 

1. Login as a caseworker.
2. Register a person.
3. Create a new integrated case.
4. Go to the Participants tab and add two more case members.
5. Select the Print icon.
6. Issue: The layout of the Context Panel and the case members are incorrectly displayed on the Print page.

 

Resolution:

With the new components and Carbon styling that is implemented in the UI, this issue has been resolved. The Context Panel and the case members are now correctly displayed on the Print page.

PO08135, WorkItem:243719 - When a scroll bar is present in the page-group navigation bar, the text truncation indicator (ellipsis) is not displayed for page titles that are too long to display fully

 

Issue Description:

When the scroll bar is present in the page-group navigation bar, the text truncation indicator (ellipsis) is not displayed for page titles that are too long to display fully. This issue does not occur if a scroll bar is not present in the page-group navigation bar.

User Interface Impact: No

Steps to Reproduce:

 

1. Login is a caseworker.
2. Search for a Registered Person and open a Person Page.
3. Click on the Client Contact tab.
4. Resize the browser window for the scroll bar to display in the page-group navigation bar.
5. Issue: Page titles in the page-group navigation bar are truncated without the ellipsis when they are too long to display fully.

 

Resolution:

With the new components and Carbon styling implemented in the UI, this issue has been resolved. The ellipsis is now displayed when a page title in the page-group navigation bar is too long to display fully.
 

PO08283, WorkItem:247043 - The content within the drop-downs and text area are truncated within the 'Add Related Family' page in a German deployment

 

Issue Description:

The drop-downs and the text area contain truncated text in the Add Related Family page in the German localisation.

User Interface Impact: Yes

Steps to Reproduce:

 

1. Build and deploy the application in German.
2. Login as a Child Welfare intake worker.
3. Create a new Intake.
4. Navigate to Participants tab.
5. Select Add Related Family.
6. Issue: The content within the drop-downs and the text area are truncated.

 

Resolution:

The content within the drop-downs, and the content within the text area are no longer truncated when selecting Add Related Family.

 

PO08411, WorkItem:249475 - Wrapping, spacing and truncation issues with modal dialogs

 

Issue Description:

In the Social Program Management (SPM) product, when viewing some modal dialogs there are wrapping, spacing and truncation issues such as:

 

1. The gap between the field label and its corresponding value is too large.
2. Field labels are wrapping.
3. Drop-down menus and field values are truncated.

 

User Interface Impact: No

Steps to Reproduce:

The following steps refer to one of the multiple scenarios where the issues occur:

 

1. Login as an Adoption Worker.
2. Register a Person that is a child aged 10 years old.
3. Click on the Care and Protection tab and select Cases.
4. Use the New page action to create an Adoption Case.
5. Select Edit from the tab action menu.
6. Issue: On the Edit Case modal, the field label is wrapping and the drop-down menu is truncated.

 

Resolution:

With the new components and Carbon styling implemented in the UI, these issues have been resolved. In the following modal dialogs, field labels are no longer wrapping, there is sufficient space between field labels and the corresponding values, drop-down menus, and field values are not truncated.

 

• Edit Case
• Edit Reason
• Update Completion Details
• Edit Assessment
• New Attendee
• New Service
• Person Search
• New Text Translation
• Edit Contact

 

PO08538, WorkItem:252763 - Incorrect list action menu height for home study records

 

Issue Description:

The list action menu height for an existing home study record is such that the caseworker can't see all the possible actions that can be taken.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a Provider Management Resource Manager.
2. Click on My Providers under Providers in the shortcuts panel.
3. Open an existing provider by clicking on the Reference hyperlink.
4. Click on the Credentials tab and select Home Studies.
5. Use the New page action to create a new home study record.
6. Select the row-level actions for the newly created home study record.
7. Issue: The entire actions menu does not display, so it is difficult for the caseworker to see all the options available so the correct action can be selected.

 

Resolution:

With the new components and Carbon styling implemented in the UI, this issue has been resolved. The actions menu displays all possible actions that can be selected by a caseworker.

 

PO08904, WorkItem:252964 - Comments label wrapped on Close Outcome Plan & Close Assessment modals

 

Issue Description:

On the Close Outcome Plan and Close Assessments modals, the Comments labels are wrapped.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as an administrator.
2. Navigate to the Shortcuts Panel.
3. Click Outcome Management and select Assessment definitions.
4. Select Child Strengths and Needs, navigate to the Cases tab and add a Child Welfare Outcome Plan - Basic Version.
5. Login as a Child Welfare caseworker and register a child.
6. Select the Care and Protection tab, navigate to Cases, click New, and select Ongoing Case.
7. Click Save.
8. Open the Ongoing case and navigate to the Outcome Plans tab.
9. Create a New Outcome Plan.
10. From the Actions menu, select close.
11. Issue: Comments label is wrapped on the Close Outcome Plan modal.
12. Click and open the new outcome plan case and navigate to the Assessments & Factors tab.
13. Click Assessments and a New Assessment.
14. Click the Assessment to open it. From the Actions menu, select close.
15. Issue: Comments label is wrapped on Close Assessment modal.

 

Resolution:

With the new components and Carbon styling that is implemented in the UI, this issue has been resolved. All labels and fields display as expected.
 

PO08610, WorkItem:254975 - Attendee name is truncated on the Invite Attendee modal

 

Issue Description:

When creating a New Activity on the Calendar page, the user can choose to Save & Invite. On the Invite Attendee modal, the name of the attendee is truncated to 2-3 characters.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a supervisor and click on the Calendar workspace.
2. Select the New Activity page action to create a new activity.
3. Enter the mandatory details and click Save & Invite.
4. On the Invite Attendee modal, click on the Search icon to select a person.
5. Issue: The selected person's name is truncated and only two or three letters appear.

 

Resolution:

With the new components and Carbon styling implemented in the UI, this issue has been resolved. The selected person's name fully appears in the Attendee field of the Invite Attendee modal.

 

PO08497, WorkItem:255357 - Narrow drop-down fields within pages are causing truncation

 

Issue Description:

When viewing some modal dialogs the following issues exist:

1. Field labels are wrapping
2. Drop-down menus and field values are truncated.

 

User Interface Impact: Yes

Steps to Reproduce:

The following steps refer to one of the multiple scenarios where the issues occur:

 

1. Login as an Administrator.
2. Navigate to Administration Workspace, Provider Management, and then Training Courses.
3. Select Edit.
4. Issue: The field labels are wrapping and the drop-down menus are truncated.

 

Resolution:

With the new components and Carbon styling implemented in the user interface these issues have been resolved. In the following modal dialogs, field labels are no longer wrapping, there is sufficient space between field labels and the corresponding values, drop-down menus, and field values are not truncated.

 

• Existing Recurring Activity
• Provider Participant
• General Settings
• New Training Requirement
• Edit Evaluation Criteria
• Edit Training
• Service Evaluation Criteria
• Forward Tasks

 

WorkItem:256228 - Inconsistent display of page titles when printing notes

 

Issue Description:

When creating a new Note or Communication from the Client Contacts tab, then using the toggle option to expand the inline page and click the Print icon, the print layout is not consistent with the titles displayed on the inline page.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a new Person.
3. Click the Client Contact tab and select Notes from the Page Group Navigation Bar.
4. Create a new Note by using the New page action.
5. Click the toggle to expand the inline page of the Note record.
6. Click the Print icon to print the content.
7. Issue: Print layout displays the text 'Notes - Merative Social Program Management’ at the top of the page instead of the page title.
8. Click Communications from the Page Group Navigation Bar.
9. Create a new Record Communication from the Actions Menu.
10. Select 'Client is Correspondent' on the first page of the Record Communication wizard and click Next.
11. On the second page of the wizard, enter the mandatory fields and click Save.
12. Click the toggle to expand the inline page of the newly created record.
13. Click the Print icon to print the content.
14. Issue: Print layout displays the text 'undefined' at the top of the page instead of the page title.

 

Resolution:

With the new components and Carbon styling that is implemented in the UI, this issue has been resolved. When the Notes and Communications list item is expanded and the Print icon is clicked the titles displayed are consistent.

 

PO08770, WorkItem:259913 - The screen reader is reading action buttons in a modal window as 'Link'

 

Issue Description:

When a supported screen reader is used and a user navigates to an action button on a modal window by pressing the Tab key, the screen reader incorrectly announces the contents of the action button.

User Interface Impact: No

Steps to Reproduce:

 

1. Start a supported screen reader.
2. Login in as an eligibility worker using a supported browser.
3. Search for a Registered Person.
4. Navigate to the Financial Transactions tab.
5. Click on the New Account Adjustment page action.
6. Navigate to the Save button of the modal pressing the Tab key.
7. Press the Enter key.
8. Issue: The screen reader announces the Save button as ‘Save Link’.

 

Resolution:

With the new components and Carbon styling implemented in the UI, this issue has been resolved. When a user navigates to an action button, the screen reader announces the action button correctly.

 

PO08835, WorkItem:261634 - Labels and data for fields are improperly wrapped to a second line when selecting View All on the Milestones page

 

Issue Description:

When selecting to view all milestones within a case, the labels displayed in the column header and also the data that is displayed are improperly wrapped to a second line.

User Interface Impact: Yes

Steps to Reproduce:

 

1. Login as an Insurance Affordability caseworker.
2. Register a new Person.
3. Select New Application from the tab action menu.
4. Submit and Authorize the application.
5. Navigate to the Milestone page under the Administration tab in the integrated case.
6. Select View All.
7. Issue: The labels displayed in the column header and also the data that is displayed are improperly wrapped to a second line.

 

Resolution:

With the new components and Carbon styling implemented in the user interface these issues have been resolved. The labels and data displayed when selecting the View All action on the Milestones page now display in one line.

 

PO08877, WorkItem:263221 - User Preferences page does not display with a scroll bar on Internet Explorer (IE) 11

 

Issue Description:

The User Preferences page does not display a scroll bar when the page size is reduced. Users with smaller screens and lower resolution encounter this issue. This occurs only when using Internet Explorer (IE) 11.

 

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a caseworker by using Internet Explorer 11.
2. Click User Preferences from the upper-right menu.
3. Resize the browser window to be smaller for a scroll bar to display.
4. Issue: The text gets overlapped instead of having a scroll bar.

 

Resolution:

With the new components and Carbon styling that is implemented in the UI, this issue has been resolved. The scroll bar is now displayed regardless of the browser size and resolution.

 

PO08932, WorkItem:264488 - Sensitivity drop-down menu is truncated on the Edit Note modal

 

Issue Description:

When a caseworker edits a newly added Note, the Sensitivity and Priority drop-downs are truncated.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a new Person.
3. Click the Client Contact tab and select Notes.
4. Click the New page action.
5. In the New Note modal, enter Subject, Priority, Sensitivity, and enter some comments in the Rich Text field.
6. Click Save.
7. Select the Edit row-level action of the newly created note.
8. Issue: The Sensitivity and Priority drop-downs are truncated on the Edit Note modal.

 

Resolution:

With the new components and Carbon styling that is implemented in the UI, this issue has been resolved. The Sensitivity and Priority drop-down menus of the Edit Notes modal correctly displays the values that are entered and the drop-down menus are not truncated.
 

PO08971, WorkItem:265327 - Refresh button is different on the home page

 

Issue Description:

The Refresh button icon on the home page is different from the Refresh button icon on other pages. The Refresh icon arrow is anti-clockwise on the home page but on all other pages it is clockwise.

User Interface Impact: No

 

Steps to Reproduce:

 

1. Login as a caseworker.
2. Select the Home Application section, check the Refresh icon image.
3. Select the Cases and Outcomes Application section.
4. Select Person Search from the shortcut panel, check the Refresh icon image.
5. Issue: The Refresh button icon is different on the home page compared to the Refresh button icons on the other screens.

Resolution:

With the new components and Carbon styling implemented in the UI, this issue has been resolved and the Refresh button icons are consistent across the application.

 

WorkItem:271330 - Carbon design user interface updates

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. An improved layout removes wrapping labels and truncation so that it is easier to read the information that is presented on screens. With the new responsive UI experience, caseworkers can, for example, resize the window or zoom in to see content while readability is maintained. Social Program Management has adopted a number of components from the Merative Carbon Design System and has enhanced the layout.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

The following UIM components have been updated with the new Carbon equivalent components:

 

• Modal dialogs
• Text input and text area components
• Dropdowns
• Date pickers
• Time pickers
• Date and time components
• Checkboxes
• Multi-selection checkboxes
• Modal Buttons
• CodeTable hierarchy: The CodeTable hierarchy has been updated to match the Carbon Combobox style and continues to work the same as in previous versions. The CodeTable hierarchy has not been updated to a Carbon component. Users must click directly on the chevron to open the drop-down.

 

The following Carbon addons have been created using the Carbon system:

 

• Cluster
• Search Popup

 

Global styling:

 

• The Social Program Management application has been updated to use the Carbon CSS for font, color, and icons for an immediate visual impact to the caseworker.
• The Social Program Management application has been updated to use the IBM Plex font.

 

Upgrade impact:

The underlying HTML structure of the application has been updated to use the Social Program Management components library to replace the existing UI components with Merative 's Carbon Design System by using modern JavaScript development. Consequently, when you upgrade to 8.0.0, the updates to the HTML structure might impact customizations that you have implemented in previous versions. In particular, the following customizations might be affected by upgrading to 8.0.0:

 

• You have implemented custom widgets that add new HTML to the default application. To obtain the new look and feel for custom widgets, see the color palette section.
• You have previously added CSS rules to customize the look and feel of the default application.
• You have previously implemented custom JavaScript code and Java Renderers.
• You have previously added new icons to the application.

 

For more information about Carbon, see https://www.carbondesignsystem.com.
For more information about configuring Carbon elements, see the UIM pages and the View section in the product documentation at https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

 

WorkItem:271924 - Modal layout updates based on Carbon design user interface

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. The modal component has been updated with the new Carbon equivalent component. Modal dialogs are heavily used by caseworkers in data entry forms, for example, when caseworkers register a new person.

User Interface Impact: Yes

 

Steps to Reproduce: N/A

Resolution:

The modal component has been updated with the new Carbon equivalent component. The new modal layout provides better form interaction throughout the application: 

 

• Standard modal sizes across the application provide caseworkers with a seamless experience when they navigate the application. Each modal is one of five sizes: extra small, small, default, large, extra large. In previous versions, modals had not been standardised, which resulted in arrow modals causing truncations and wrapping in labels.
• Labels are displayed over fields and are left aligned on a single column. In previous versions, labels were aligned next to fields in forms and often there was a large amount of space between them, which made them difficult to read. 
• Input text fields, for example text fields, date pickers, and drop downs are bigger and sized appropriately based on the expected data, which provides sufficient space and avoids truncation, which in turn helps caseworkers to input data into forms more easily.
• Buttons are left aligned to maintain UI consistency with input fields, and to provide a clear path to form completion. Also, the size of the buttons in modals and wizards has increased, which makes it easier to click them.
• Reduced white space between labels and values, and between labels and inputs, helps caseworkers with data entry in forms. Caseworkers can spend less time reading forms because the labels and values are closer together.
• Caseworker can zoom out by using the browser zoom controls, which helps caseworkers to see more content on the screen and requires less scrolling. Caseworkers can zoom in on modals and increase the text size, which is a benefit to caseworkers who find it difficult to read small text on screens.
• Modals are now responsive, so that caseworkers can use different devices and still preserve the updated modal layout experience. The new design enables caseworkers to work wherever and whenever they need.
• Caseworkers can also resize the browser to view another document parallel to the data entry view. In previous versions, caseworkers were able to have a document open but it was more difficult to resize the browser and see the full content displayed on the screen.

 

WorkItem:271926 - Cluster component updates based on Carbon design user interface

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. The Cluster component has been created using the Carbon system. The new Cluster component makes it easier for caseworkers to use them. Caseworkers interact with clusters everywhere in the application. For example, the Register Person screen has a cluster that displays the input fields. Another example of input fields in clusters is the Add Note screen that caseworkers use when they need to add a new note. When caseworkers create an Income Support Application, the Clients tab also displays a list that is nested in a cluster.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

The Cluster component has been created using the Carbon system. Clusters are the primary layout element in UIM and are extensively used in the application. Clusters are used to layout and display fields, labels, and form controls such as drop-down lists, date pickers, and lists.

Key benefits:

 

• The new clusters provide effective use of space across different screen sizes, which helps caseworkers to see what is most important.
• An increased visual contrast between labels and values in clusters helps caseworkers to read Social Program Management screens. Also, labels are always positioned on top, which reduces eye movements and cognitive load. This is a benefit to all caseworkers because it decreases form completion time.
• Fields and labels are positioned closer together, which reduces white space. To ensure that the fields and labels are fully responsive, they are either laid out inline when enough space is available or with labels on top when space is constrained. Therefore, the improved experience is preserved as caseworkers use different devices.
• Clusters are easier to collapse and expand because the entire title of the cluster is clickable, therefore a larger clickable area is available to caseworkers.
• When a cluster is nested inside another cluster, only the top-level cluster is collapsible. Previously, values were positioned too far from the labels and forms were difficult to interact with because of label wrapping, field truncations, and so on. This problem is now solved because fields and labels are positioned closer together, as described previously.

 

WorkItem:271932 - Text and area input field components updates based on Carbon design user interface

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. The text input and text area components have been updated with the new Carbon equivalent components. The components text input and text area are present in almost all the screens in the application, especially data entry forms.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

The text input and text area components have been updated with the new Carbon components. The components are part of the form controls and are heavily used by caseworkers across the application.

 

• The new layout that has labels above the input fields makes it easier for caseworkers to read and complete forms.
• Text inputs have been optimized based on the expected number of characters in the field to avoid truncations.
• The new Carbon style reduces visual noise, which makes it easier for caseworkers to complete forms.
• An increase in padding makes it easier for caseworkers to read input values in forms.

 

These benefits help caseworkers to complete tasks with faster completion times.
 

WorkItem:271933 - Date picker component updates based on Carbon design user interface

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. The Calendar widget has been updated with the new Carbon date picker component. The date picker is heavily used by caseworkers for data entry in forms. An example of the component can be seen in the Register Person screen when caseworkers need to enter the date of birth of the person as a mandatory field for the registration. Caseworkers also use the component when recording evidence in the application.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

The new Carbon date picker component has better alignment with the calendar icon, which makes it easier for caseworkers to select dates and correct mistakes when they enter dates.

 

• The new date picker opens in the same modal and remains open until either a date is selected, or the focus is removed from the date picker. 
• The calendar icon is now visually positioned inside the input field, which improves alignment with other inputs.
• The new date picker now drops down from the field within the open modal, which makes it faster to use and keeps it within the context of the input field. Previously, the Calendar widget was slow because it opened in a new modal, which made it easier for caseworkers to lose the context of the data that they wanted to enter.
• Caseworkers can select a date by either entering a date in the text input field, clicking on a date in the calendar menu, or navigating to a date by using the arrow keys and pressing Enter, all within the same modal.
• Another benefit is that date fields have been configured with a minimum width to avoid truncations or clipping.

 

WorkItem:271934 - Time picker component updates based on Carbon design user interface

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. The time picker component has been updated with the new Carbon equivalent component. The time picker is mainly used by caseworkers when they schedule a meeting or when they need to specify the time of an event.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

The time picker component has been updated with the Carbon Combobox component. The benefits of the new time picker component are:

 

• It is easier for caseworkers to select times or correct mistakes because of the new clear button (x) that is now available.
• The time input also has a minimum width to avoid truncation. Caseworkers can use the arrow keys to highlights options in the list that they can then select by either pressing the enter key or by clicking the mouse.

 

Extra benefits:

 

• Supports existing time properties, timeformat, and timeseparator.
• The time field format supports existing timeformat configuration, h m s a, h m a, H m, hh mm a, HH mm, hhmm a, or HHmm. Where not specified, HH mm is the default.

 

WorkItem:271935 - Date and time component updates based on Carbon design user interface

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. The date-time component has been updated with a combination of the new Carbon date picker and Carbon time picker components. The date-time component is used in various parts of the application, for example scheduling a task, creating contact logs, meeting details, and meeting minutes.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

The date-time component has been updated with a combination of the Carbon components. The date-time component has the same key benefits as the new Carbon date picker and Carbon time picker components. The new style of the date-time component consistently matches the look and feel of the new UI.

 

WorkItem:271936 - Drop-down component updates based on Carbon design user interface

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. The drop-down component has been updated with the Carbon combo box component. Dropdowns are heavily used by caseworkers in forms for data entry, for example, when a caseworker registers a new person or creates new evidence. Drop-downs are also used in the search criteria for search screens, for example, when a caseworker searches for an application or for a case.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

The drop-down component has been updated with the Carbon combo box component.

 

• Drop-down sizes have been enhanced based on the longest option to avoid clipping or truncation and to improve readability. The improvement helps caseworkers to view a long list of available options in a drop-down without truncations, for example, country names.
• Another benefit for caseworkers is the increased click target of the new combo box, which makes it easier and faster for caseworkers to select and open the combo box.
• The menu opens by clicking anywhere in the field, not just directly on the chevron. The Carbon combo box does not filter but highlights the best match based on options that "contain" the entered text. Caseworkers can now use the arrow keys to highlight options in drop-downs, which they can then select either by pressing the Enter key or by clicking the mouse.
• A Carbon Combobox indicates the selected item in the menu with a checkmark and a background color change that highlights the selection.

 

WorkItem:271937 - New styling of the CodeTable hierarchy based on Carbon CSS

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. The styling of the CodeTable hierarchy component has been updated based on Carbon CSS. An example of a CodeTable hierarchy can be seen in the application when caseworkers register a new person and need to add a special caution. Category and Type fields are an example of a Codetable hierarchy in the New Special Caution screen.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

The component itself is unchanged and continues to work the same as in previous versions. The new style of the CodeTable hierarchy consistently marches the look and feel of the new UI.

 

WorkItem:271938 - Checkbox component updates based on Carbon design user interface

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. The checkbox component has been updated with the Carbon checkbox component. The checkbox is often used in forms when a Boolean value needs to be selected. Examples of this component can be found in the Person Search and Register Person screens. These two screens are heavily used by Caseworkers.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

The checkbox component is part of the form controls and helps caseworkers with data entry in the application. The checkbox component has been updated with the Carbon checkbox component.

• The new Carbon checkbox component has better mouse interaction. Caseworkers can select an item either by clicking the checkbox directly or by clicking the checkbox label. The implementation of both regions as interactive creates a more accessible click target and helps caseworkers to complete tasks faster.
• Checkbox labels are positioned to the right of their inputs, which reduces white space between them. Compared to previous versions, the new component enables the improved positioning of labels for a single checkbox by reducing the space between the label and the checkbox.

 

WorkItem:271939 - Multi selection checkbox component updates based on Carbon design user interface

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. The multi-selection checkbox component has been updated with the new Carbon equivalent component. An example of this component can be seen when caseworkers apply changes to evidence, for example in a social assistance case when new address evidence is added to the case. This scenario is heavily used by caseworkers when performing a change of circumstances.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

The multi-selection checkbox component has been updated with the new Carbon equivalent component. The component is used to provide a list of options where caseworkers can select multiple options, including all or none.

 

• The new multi-selection checkbox component has better mouse interaction. Caseworkers can select an item either by clicking the checkbox input directly or by clicking the checkbox label. The implementation of both regions as interactive creates a more accessible click target.
• Checkbox labels are positioned to the right of their inputs.
• The multi-select component now displays the specified number of items correctly.

 

WorkItem:271940 - Search pop-up component updates based on Carbon design user interface

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. The search pop-up component has been created using the Carbon system by using a combination of a text input Carbon component plus the search icon, which then triggers a modal dialog of search results. Examples of the component can be seen when caseworkers need to search for a case participant or assign a task to another caseworker.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

Searching is an important part of the application and caseworkers often use the search functionality when they do not want to manually type the information. The search pop-up component has been created by using the Carbon system.

 

• The search and clear buttons are now visible inside the input search field, which improves alignment with other inputs fields and makes it easier for caseworkers to click the buttons.
• The new component uses the Carbon search input styles to consistently march the look and feel of the new UI.

 

WorkItem:271943 - Modal button component updates based on Carbon design user interface

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. The modal button component has been updated with the new Carbon equivalent component. Modal buttons are heavily used by caseworkers in the application.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

The button component in modals has been updated with the new Carbon equivalent component. The changes apply to only buttons in modals, the rest of the buttons have been limited to color and typeface changes to maintain consistency with the rest of the new UI.

 

• Modal buttons have increased in size, compared to their previous smaller size. The change benefits caseworkers by enabling them to click the buttons faster, which increases usability in the application.
• Each page has one primary modal button, which is triggered by the ENTER key. Any remaining calls to action are represented as lower emphasis buttons.
• The primary modal button is the right button, and the secondary button is the left button.
• Secondary modal buttons can be used only in conjunction with a primary modal button as part of a pair. The secondary modal button’s function is to perform the negative action of the set, such as “Cancel” or “Back”.
• For the lesser-used actions, such as in a progress flow, a ghost button can be added to a primary and secondary button set. The primary button is for the forward action, the secondary button is for “Back”, and the ghost button is for “Cancel”.

 

WorkItem:271944 - Color palette updates based on Carbon design user interface

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. Caseworkers can benefit from a consistent look-and-feel experience that reduces visual noise and helps them to focus on information that is presented in screens. The color palette has been updated to new color properties defined in Carbon Design System.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

The UI has a new color palette, with the new color properties defined in the Color – Carbon Design System. The Neutral Gray family is dominant in the default themes, which uses subtle shifts in value to help organize content into distinct zones. The core Blue family serves as the primary action color across the UI. Extra colors are used sparingly and purposefully.

 

Key benefits:

 

• Less visual noise in screens that helps caseworkers to focus, and guides them to complete end-to-end workflows.
• The primary action color has increased contrast, at least 3:1 compared to the surrounding text.
• All colors and graphics meet WCAG level AA color contrast requirements.
• Simplified and subtle use of color reduces visual noise, eye fixation, and decreases cognitive load for all users.

 

WorkItem:271945 - Typography updates based on Carbon design user interface

 

Issue Description:

The Social Program Management application has been updated to use the IBM Plex font.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

Typeface

IBM Plex is used in the new UI to keep font consistency with the rest of the components that have been updated to Carbon, IBM Plex has been carefully designed to meet the needs of modern users and provides the following capabilities:

 

• IBM Plex is designed to read well and easily on screens of all sizes.
• IBM Plex is open source.
• IBM Plex covers over 100 languages with extended Latin versions.
• IBM Plex comes with some additional basic features, such as ligatures across Sans and Serif as well as fractions, arrows, alternate glyphs, and global currency symbols.

 

Type style

 

• The new UI consolidates font weights to just regular and semi-bold.
• Light-weight font has been replaced with regular weight font, which makes text easier to read at small sizes.
• Medium-weight font has been replaced with regular weight font, which creates a greater distinction between regular weight text and semi-bold text.
• Bold-weight font has been replaced with semi-bold font, which improves legibility at small sizes.

 

WorkItem:271946 - Icon updates based on Carbon design user interface

 

Issue Description:

The Merative Social Program Management user interface (UI) has been updated to provide caseworkers with a modern UI. Icons have been updated to use the new Carbon icon suit for an immediate visual impact to the caseworker. Icons form part of the global style of the UI. The new icons contribute to a more contemporary look and feel in the UI, while consistency is maintained with the rest of the UI components that have been replaced with Carbon components in 8.0.0.

User Interface Impact: Yes

Steps to Reproduce: N/A

Resolution:

Icons have been updated to use the new Carbon icons in the application. Caseworkers use icons pervasively throughout the application as shortcuts to functionality.

 

• Icons effectively become common metaphors for functions as caseworkers use the system. When caseworkers see the icons anywhere in the application, they know the expected functionality and that it's available for them to use. The new icons help caseworkers to re-enforce established metaphors that communicate messages at a glance. 
• The new icons render clearly when zoomed in, on all Social Program Management screen sizes. This is a benefit to all users, especially to caseworkers. Previous icons can render as blurry in high screen resolutions, which make it difficult for caseworkers to see the icons. 
• Icon colors have been updated to be consistent with the new IBM Design Language color palette, with improved consistency and color contrast that helps caseworkers to focus on the content.
• The default "star" icon on the page-level actions menu has been removed because the "star" icon was not always relevant to the action on the page and might be confusing to caseworkers.

 

These benefits help caseworkers to complete tasks with faster completion times.

 

 

Curam Enterprise Framework

 

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

 

WorkItem:185556 - The Flex Widget for Citizen Context Viewer is replaced with modern JavaScript

 

Issue Description:

The Social Program Management (SPM) product no longer has any dependency on Adobe Flash. The Flash-dependent widget for the Citizen Context Viewer (CCV), which reduces the amount of navigation that is needed to understand the relationships between people and cases, is replaced with a responsive version based on modern React JavaScript components. The previous functionality of the CCV is maintained.

 

User Interface Impact: Yes

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a new Person.
3. Create an integrated case for the person.
4. Click the Citizen Context Viewer icon to navigate to the CCV for the case member.

 

Resolution:

The Flash-dependent widget for the CCV is now replaced with a responsive version based on modern React JavaScript. Viewing client information for family members by opening a new CCV for each family member was enhanced to improve the user experience for the CCV users and to make the CCV accessible. The right-click action to view a new CCV for a family member is now replaced by an overflow action (...) for each family member. Select the overflow action (...) to display a hidden overflow menu and then select the View Citizen Context option. The drag and drop interaction to change the existing CCV client with a family member was also enhanced to improve the user experience. When a user drags a family member to the top panel of the CCV, the allowable drop area is now highlighted.

 

WorkItem:185557 - The Flex Chart for Horizontal Bar Chart is replaced with modern JavaScript

 

Issue Description:

The Social Program Management (SPM) product no longer has any dependency on Adobe Flash. The Flash-dependent chart for the Horizontal Bar Chart, which is used throughout the application, for example, to provide supervisors with an easy way of seeing what tasks are due for users in the next week or month, is replaced with a responsive version based on modern React JavaScript components. The previous functionality of the Horizontal Bar Chart is maintained.

User Interface Impact: Yes

Prerequisite(s):

 

1. Ensure there are tasks due for a particular user.

 

Steps to Reproduce:

 

1. Login as a supervisor.
2. Select My Users under Users in the shortcuts panel.
3. On the list of all users displayed, click on the hyperlink of the user for whom there are tasks due to launch the users workspace tab.
4. The Horizontal Bar Chart is displayed on the Home page.

 

Resolution:

The Flash-dependent chart for the Horizontal Bar Chart is now replaced with a responsive version based on modern React JavaScript. To improve the user experience and to make Horizontal Bar Chart accessible, an enlarge button for maximizing and minimizing the Chart is available. Labels are truncated to better maintain the scale and readability of the Chart. Users can click the enlarge button to see a larger view and to read truncated labels. A new color scheme from the Merative Carbon Design System was also introduced for the Horizontal Bar Chart, which provides an accessible and enhanced user experience. The colors are applied in a specific sequence to maximize the contrast between neighboring colors.

Technical:

The bar colors are now customizable. These colors are defined in the CuramCDEJ/lib/curam/xml/xsl/chart/charts.xsl as follows:

<ibm:colors>
<ibm:color>6929C4</ibm:color>
<ibm:color>1192E8</ibm:color>
<ibm:color>005D5D</ibm:color>
<ibm:color>9F1853</ibm:color>
<ibm:color>FA4D56</ibm:color>
<ibm:color>570408</ibm:color>
<ibm:color>198038</ibm:color>
</ibm:colors>

 

PO08959, WorkItem:226839 - File not found errors are being reported in the server logs for the Smart Navigator javascript file

 

Issue Description:

The server log file shows multiple 'File not found' instances for the Smart Navigator JavaScript file. This results in an avoidable increase in the server log file size, further leading to maintenance overheads. The error that is reported is 'File not found: /CDEJ/jscript/curam/application/nls/en_us/SmartNavigator.js'.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a new Person.
3. Enter the registered person's name in the quick search field and click the result to open the person home page.
4. Check the server log.
5. Issue: The message 'File not found: /CDEJ/jscript/curam/application/nls/en_us/SmartNavigator.js' is logged.

 

Resolution:

The issue has been resolved by fixing the locale format on the Smart Navigator component. There should now be no instances of the reported error found in the server logs, which means that it should not contribute to the overall size of the server logs.

Technical:

The underlying issue here was the format of the locale that was used to look up the resource bundles. This was en_US instead of en-us, for example, which is the format that is required when looking up resource bundles for Dojo constructs. When the wrong format is used, the reported error is written to the server logs.

 

WorkItem:252848 - The Flex Chart for Vertical Bar Chart is replaced with modern JavaScript

 

Issue Description:

The Social Program Management (SPM) product no longer has any dependency on Adobe Flash. The Flash-dependent chart for the Vertical Bar Chart, which provides supervisors with an easy way of seeing various graphs of functions that they need to monitor, is replaced with a responsive version based on modern React JavaScript components. The previous functionality of the Vertical Bar Chart is maintained.

User Interface Impact: No

Prerequisite(s):

 

1. A completed and/or not completed Intake exists for the Child Welfare intake supervisor.

 

Steps to Reproduce:

 

1. Login as a Child Welfare intake supervisor.
2. Select Intake Screening Rates under Users in the shortcuts panel.
3. Enter a Start Date and an End Date for the search criteria.
4. Select Search from the page action menu.
5. The Vertical bar chart is displayed.

 

Resolution:

The Flash-dependent chart for the Vertical Bar Chart is now replaced with a responsive version based on modern React JavaScript. A new color scheme from the Merative Carbon Design System was also introduced for the Vertical Bar Chart, which provides an accessible and enhanced user experience. The colors are applied in a specific sequence to maximize the contrast between neighboring colors.

Technical:

The bar colors are now customizable. These colors are defined in the CuramCDEJ/lib/curam/xml/xsl/chart/charts.xsl as follows:

<ibm:colors>
<ibm:color>6929C4</ibm:color>
<ibm:color>1192E8</ibm:color>
<ibm:color>005D5D</ibm:color>
<ibm:color>9F1853</ibm:color>
<ibm:color>FA4D56</ibm:color>
<ibm:color>570408</ibm:color>
<ibm:color>198038</ibm:color>
</ibm:colors>

 

PO08813, WorkItem:261073 - Incorrect localization of text on the Person evidence list page

 

Issue Description:

The text in the Source column of the Person evidence list page is not localized according to the user's locale. Instead, it remains in the default server locale.

User Interface Impact: No

Prerequisite(s):

 

1. The Spanish language pack is installed.
2. The default server locale is en_US and the caseworker's locale is in Spanish.

 

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a new Person.
3. Click the Evidence tab and select the Evidence page.
4. Issue: The Source column displays the text in English instead of Spanish.

 

Resolution:

The Source column on the Person evidence list page is now displayed correctly in the user's locale.

 

WorkItem:261397 - Enhancement of Cross-Site Request Forgery (CSRF) protection in Social Program Management

 

Issue Description:

Cross-Site Request Forgery (CSRF) is an attack that forces an end user to execute unwanted actions on a web application in which they’re currently authenticated.
Security hardening of the referrer header check was required to mitigate against CSRF.

User Interface Impact: No

Steps to Reproduce: N/A

Resolution:

The domain validation feature has now been extended to all URI requests to provide enhanced protection against CSRF events.

 

• What are the advantages of using the feature?
  • The feature provides a central location for domain validation across SPM web applications and RESTful web services.

• Where does the feature fit in the product?
  • The feature applies to all URI requests through SPM web pages and RESTful web services that validate whether the request is from a trusted source.

• How is the feature accessed?
  • The feature is accessed through URI requests through SPM web pages and RESTful web services in both development and deployed environments.

• What does the feature do?
  • The feature provides CSRF defense measures by validating the referrer header for all HTTP verbs in both SPM web pages and RESTful web services CSRF defense measures validate the 'Referrer' header from the request to see if it is from a trusted source. Non-trusted sources are blocked.
  • This new defense measure validates the HTTP referrer header for all incoming requests against a list of trusted domains that are contained within a new string system property called 'curam.referer.domains'.
  • This property takes a comma-separated list of trusted domains.
  • The curam.referer.domains property must contain the domain or partial domain where the application is hosted. For example, if the SPM application is deployed to https:example.ibm.com:8080, then you must add 'example.ibm.com' or 'ibm.com' as a value for curam.referer.domains. The default value of the property is 'localhost'.

• What are the impacts to customers?
  • Initially, access to the application will be limited to localhost users only. Refer to the documentation link below for the steps required to configure the feature and the application.
  • Automated test scripts may be impacted as HTTP referrer header checks have been added to the SPM UI infrastructure.

 

The SPM product documentation has been updated to provide the relevant details about this feature and its configuration. see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation
 

WorkItem:262780 - Rewrite Milestone Delivery batch processes to use the Batch Streaming infrastructure

 

Issue Description:

ScanMilestoneDeliveryEndDate is a batch process that monitors milestone delivery records where the expected end date is in the past and the milestone is not yet completed. If an error occurs when running the batch process for any reason, the entire process rolls back and no records are processed. This happens because the ScanMilestoneDeliveryEndDate batch process does not use the batch streaming infrastructure available with the SPM product. The same issue is observed when running ScanMilestoneDeliveryStartDate.

User Interface Impact: No

Steps to Reproduce: N/A

Resolution:

The ScanMilestoneDeliveryStartDate and ScanMilestoneDeliveryEndDate batch processes are now deprecated and are replaced by two new batch processes: ScanMilestoneDeliveryStartDateBatch and ScanMilestoneDeliveryEndDateBatch. These provide the same functions but make use of the batch streaming infrastructure.

For more information about the new batch processes, including steps to run them, see the Merative Social Program Management batch process reference at https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation
 

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

 

PO08921, WorkItem:263058 - Date selector widget does not display the title in French

 

Issue Description:

User language preferences are ignored on the date selector widget, which results in untranslated text.

User Interface Impact: No

Prerequisite(s):

 

1. The French language pack is installed.
2. The default server locale is en_US and the caseworker's locale is in French.

 

Steps to Reproduce:

 

1. Login as a caseworker.
2. Click the shortcut to register a person in the shortcuts panel.
3. Open the date selector widget for the Date of Birth field.
4. Issue: The title of the date selector widget is not displayed in French. Instead, the text that is displayed is in English.

 

Resolution:

The title of the date selector widget now displays text in French.

 

WorkItem:263097 - Deprecate an unused facade method that processed email meeting responses as part of Meeting Minutes PIM integration

 

An unused processMeetingResponses() process and associated artifacts that are used to process responses returned to the configured email account and update the meeting attendee response data are now deprecated. See Integrating Meetings with External Email Accounts in the Calendaring Guide and Configuring Meetings and Minutes in the Configuring Calendaring Guide for a description of the deprecated functions.

 

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

 

PO09016, WorkItem:265778 - The PRODUCTDELIVERY.INSERT event is not raised by the application

Issue Description:

The PRODUCTDELIVERY.INSERT and PRODUCTDELIVERY.MODIFY events are not raised when a product delivery is created or modified.

User Interface Impact: No

Prerequisite(s):

 

1. Create and register an event listener for the PRODUCTDELIVERY.INSERT event.
2. Create and register an event listener for the PRODUCTDELIVERY.MODIFY event.

 

Steps to Reproduce (Generic):

 

1. Register a new Person.
2. Create an integrated case for the person.
3. Add an associated product delivery to the integrated case for the person.
4. Issue: The event listener that is registered for the PRODUCTDELIVERY.INSERT event is not enacted.
5. Modify the product delivery case by selecting Edit from the Actions menu.
6. Issue: The event listener that is registered for the PRODUCTDELIVERY.MODIFY event is not enacted.

 

Resolution:

This issue is now resolved. Creating or modifying a product delivery now triggers the correct event.

Technical:

The PRODUCTDELIVERY.INSERT event is now raised during the post-insert of a product delivery and the PRODUCTDELIVERY.MODIFY event is now raised during the post-modify of a product delivery.
 

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

Technical Services

 

CMIS Adapter
Rest
Web Services
Workflow

 

WorkItem:268106 - Merative Social Program Management timer-based JMX statistics updated to use Java Timers in WebSphere® Liberty deployments

 

Issue Description:

Java™ Management Extensions (JMX) is the system that provides operational data, for example URLs, business methods, and SQL statements, from a running application. Social Program Management has been updated to use shared Enterprise Java Beans (EJB) persistent timer tables to store timer information. To leverage shared Enterprise Java Beans (EJB) persistent timer tables Merative Social Program Management timer-based JMX statistics have been updated to use Java timers instead of EJB Timers in WebSphere® Liberty deployments only on Kubernetes. This change does not apply to traditional WebSphere Application Server or WebLogic Server. 

For more information about shared (EJB) persistent timer tables for WebSphere Liberty, see the What's new section in the product documentation at https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

 

For information about Merative Social Program Management JMX statistics in Kubernetes,  see the Monitoring performance using JMX statistics section in the runbook at  https://merative.github.io/spm-kubernetes/monitoring/jmx-statistics-performance-monitoring/

User Interface Impact: No

Steps to Reproduce:

For information about how to configure Merative Social Program Management JMX statistics, see the Monitoring performance using JMX statistics section in the runbook at https://merative.github.io/spm-kubernetes/monitoring/jmx-statistics-performance-monitoring/

CMIS ADAPTER

 

PO07900, WorkItem:236602 - Listing attachments calls the external Document Management System unnecessarily

 

Issue Description:

The attachment list page retrieves all attachment details. When using an external Document Management System (FileNet, for example), this results in many external calls and can result in performance problems.

User Interface Impact: No

Prerequisite(s):

 

1. Configure SPM with an external Document Management System such as FileNet.

 

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a person and create an integrated case for them.
3. On the integrated case, click the Contact tab and select Attachments.
4. Using the New page action, create a new attachment.
5. Issue: The list attachments page will make calls to the external Document Management System for each attachment listed. If there are many attachments listed, the calls to the external Document Management System can result in performance overhead.

 

Resolution:

The attachments list page only displays attachment metadata and does not need to retrieve full attachment contents. This call has been corrected to populate only the relevant information for the page.

 

PO08352, WorkItem:248749 - Merative Social Program Management is making multiple calls to FileNet for a single attachment upload

 

Issue Description:

When using FileNet and CMIS for document storage, the application is making multiple calls to the FileNet service when uploading documents.

User Interface Impact: No

Prerequisite(s):

 

1. Login as a system administrator.
2. Select Target Systems under Application Data in the shortcuts panel.
3. Configure SPM with a target system entry for the FileNet server.
4. Select Property Administration under Application Data in the shortcuts panel.
5. Select Content Management Settings in the Category drop-down and click Search.
6. Configure the Content Management properties as required.
7. Publish the changes.

 

Steps to Reproduce:

 

1. Login as a caseworker.
2. Navigate to a Person home page.
3. Click on the Client Contact tab and select Attachments.
4. Use the New page action to add an attachment.
5. Provide the necessary attachment details and click Save.
6. Issue: The attachment will be uploaded to the FileNet server, but the version will be 2. There will have been two calls made to the FileNet server instead of one.

 

Resolution:

 

The CMIS file upload code has been updated to make only one call during the upload of a document.

REST

 

APIs

APIS

 

WorkItem:264291 - New API introduced to the REST Infrastructure to log out a user and invalidate their session

 

Issue Description:

The REST infrastructure did not have an API to log out a user and invalidate their session.

User Interface Impact: N/A

Steps to Reproduce: N/A

Resolution:

The REST infrastructure has been enhanced and a new API has been added which will log out a user and invalidate their session. REST Infrastructure developers can utilize this API by sending an HTTP POST request to the following endpoint:

• Rest/logout

 

WEB SERVICES

 

PO09167, WorkItem:267689 - The compile web service implementations step of building the SPM server is failing due to a ClassNotFoundException

 

Issue Description:

The 'build server' application target is failing with a ClassNotFoundException ('curam.util.exception.SvrRemoteException') when attempting to compile any custom web service implementations.

Note that this issue is not present in any of the web services provided in the SPM application. It is exposed if you are a customer who has exposed additional web services.

User Interface Impact: No

Steps to Reproduce:

 

1. Add a custom web service implementation class in a location under the 'EJBServer/custom' component. The functions within this class should contain references to the 'curam.util.exception.SvrRemoteException' class.
2. Execute a clean server build ('build clean server').
3. Issue: The build fails with an error stating that the 'curam.util.exception.SvrRemoteException' class cannot be found.

 

Resolution:

The underlying problem was a missing JAR file entry in the classpath for building custom web service connectors. The JAR file entry which is missing is 'jar.coreinf.ejb.interfaces'. The classpath for building custom web service connectors has been updated to include the reference to the 'jar.coreinf.ejb.interfaces' JAR file which contains the missing classes.

Technical:

The 'wsconnector.classpath' classpath has been updated in the following properties file:

• ../CuramSDEJ/bin/app_properties.xml

 

WORKFLOW

 

PO07951, WorkItem:238576 - The Workflow Graphical View is no longer displaying transition condition expressions in a tooltip when a user hovers over them

 

Issue Description:

The Workflow Graphical View denotes that a transition contains a condition expression by displaying an asterisk on that transition. Therefore, some transitions within the workflow will contain asterisks on the transitions while others will not. When a user hovers over these asterisks by using the mouse, the condition expression for that transition should be displayed as a tooltip. This is useful as the user can see the condition expression in place and in the context of the overall workflow. When the user clicks the actual transition between two activities, the list on the Transitions page is navigated to. Similarly, if an activity is clicked on within the graphical view, the details of the activity in the Process Definition Tool are displayed. Currently, none of these three features are working in the Workflow Graphical View.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as an administrator.
2. Navigate to the Administration Workspace.
3. Click Released Workflows under Workflow in the shortcuts panel.
4. Find and open the workflow process definition named Manual. Click on the Graphical View. This process definition contains two nodes representing the manual activities, with both inbound transitions containing condition expressions denoted by an asterisk.
5. Hover over either asterisk with the mouse.
6. Issue 1: The condition expression does not appear as a tooltip.
7. Click on a transition between two activities in the graphical view.
8. Issue 2: The user is not navigated to the List Transitions page.
9. Click on either of the nodes on the graph that represent manual activities.
10. Issue 3: The details of the activity in the Process Definition Tool do not display.

 

Resolution:

The Workflow Graphical View has been updated to ensure that if a user hovers over an asterisk which denotes a transition condition expression in a workflow, that expression is displayed as a tooltip to the user. If the user clicks on a transition in the view, they are navigated to the list on the Transitions page. If the user clicks on any activity within the Graphical View, they are navigated to the details of the activity in the Process Definition Tool.

 

WorkItem:269448 - Replace the icons in the Workflow Graphical View with more modern versions

 

Issue Description:

The structure of a workflow process is determined by the activities in the process and the transitions between them. The workflow process is visualized in a graph where the activities are vertices and the transitions are arcs. This graph can be viewed by using the Graphical View feature in the Process Definition Tool. Currently, the icons that are used to represent the various workflow activity types in the Workflow Graphical View are not consistent with the styles that are associated with the current modern Social Program Management (SPM) user interface.

User Interface Impact: Yes

Steps to Reproduce:

 

1. Login as an administrator.
2. Navigate to the Administration workspace.
3. Click Released Processes under Workflow in the shortcuts panel.
4. Find and open the workflow process definition named Manual. Click the Graphical View. This process definition contains two manual activities.
5. Issue: Note that the style of the icons which represent the manual activities is not consistent with the current modern SPM user interface.

 

Resolution:

The Workflow Graphical View has been updated to ensure that the icons that are used to represent the activity types are styled consistently with the modern SPM user interface. The following activity type icons have been updated:

 

• Automatic
• Decision
• Endprocess
• Eventwait
• Loopbegin
• Loopend
• Manual
• Notification
• Parallel
• Route
• Startprocess
• Subflow

 

 

Integrated Case Management

 

Eligibility & Entitlement
Evidence Management
Common
Investigations
Participant Management

 

WorkItem:246035 - Expose CaseHomeMenuLoader as an external class to facilitate compliant customization

 

Issue Description:

The case home page menu displays different options depending on the status of the case. It is not currently possible to customize the CaseHomeMenuLoader class compliantly to display additional details, as it is not marked as external.

User Interface Impact: No

Steps to Reproduce: N/A

Resolution:

To support compliant customization, the access restriction on the following class was updated to @AccessLevel(EXTERNAL):

• curam.core.sl.tab.impl.CaseHomeMenuLoader

The class can now be called and extended compliantly by custom implementations.
 

PO08332, WorkItem:248432 - SPM v6 notes that contain supplementary characters do not display correct in later releases

 

Issue Description:

Notes created in Social Program Management (SPM) v6 that include supplementary characters, such as emojis, are not visible in later releases such as SPM v7.

User Interface Impact: No

Steps to Reproduce:

 

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

 

Resolution:

When an organization upgrades to SPM v7 and has Notes that contain supplementary characters, the characters in SPM Notes are now visible in the upgraded SPM version.

Technical:

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

 

PO08449, WorkItem:250982 - Generated PDF files do not retain the same table format as entered in rich text fields

 

Issue Description:

When copying data from applications like Microsoft Excel, to a rich text field such as the narrative in a contact log, the same format is not retained in the generated PDF file when the contact log is printed.

User Interface Impact: No

Prerequisite(s):

 

1. In a Microsoft Excel worksheet, enter any data in 3x2 cells.
   • Note: Do not use the Merge & Center feature to merge the cells.

 

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a new Person.
3. Click on the Issues and Proceedings tab and select Investigations.
4. Use the New page action to create a new Investigation.
5. Click on the Contact tab and select Contact Logs.
6. Use the New Contact page action to create a new contact log.
7. Enter the mandatory details on the first page of the wizard and click Next.
8. Copy the data created in the prerequisite(s) above as-is into the narrative free text field.
9. Click Save & Exit.
10. Click the checkbox for the new contact log and then select the Preview Selected Contacts page action.
11. Verify the format of the data on the Narrative History field of the contact log.
12. Use the Print Log page action to print the contact log.
13. Save and open the generated PDF.
14. Issue: The Narrative field in the PDF does not retain the same table format as expected.

 

Resolution:

The generated PDF now renders the data in a simply formatted plain text representation of the narrative content.

For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation. See also the related sample XSL template for guidance about using or updating the default XSL templates that are provided with the Merative Social Program Management product.

 

WorkItem:254839 - Refresh and Help buttons are not mirrored on the Integrated Cases list page on an Arabic (Right to Left) build

 

Issue Description:

When a user whose locale is Arabic logs into the Administration Application and clicks on the Integrated Cases shortcuts link, the Refresh and Help icons are not mirrored on the list page. When the locale is Arabic, the icons are displayed in reverse order from other locales and the icon graphics should be mirrored.

User Interface Impact: No

Prerequisite(s):

 

1. The Arabic language pack is installed.
2. The caseworker's locale is in Arabic.

 

Steps to Reproduce:

 

1. Login as an administrator.
2. Click on Integrated Cases under Case in the shortcuts panel.
3. Issue: The Refresh and Help icons are not mirrored on the list page.

 

Resolution:

CSS styling has been updated to ensure the Refresh and Help icons on the Integrated Cases list page are mirrored when the user's locale is Arabic.
 

PO08760, WorkItem:259461 - Balance outstanding amount is incorrect on the context panel of the Payment Correction overpayment

 

Issue Description:

In the context panel of the Payment Correction case for an overpayment a BIRT chart is displayed providing a visual representation of the balance outstanding, the payments allocated and the write off total. In certain circumstances, the outstanding amount displayed in the context panel doesn’t match with that in the graph.

User Interface Impact: No

Prerequisite(s):

 

1. Login as an administrator.
2. Navigate to Product Delivery Cases under Cases in the shortcuts panel.
3. Select any benefit product and open its home page.
4. Click on the Financial tab and select Deductions.
5. Use the Add Existing page action to configure a Liability Repayment deduction.

 

Steps to Reproduce (Generic):

 

1. Login as a caseworker.
2. Register a new Person and create an integrated case that relates to the product referenced in the prerequisite(s).
3. Add a product to the integrated case, payable weekly by check.
4. Add the necessary evidence to make the product eligible.
5. Submit, approve, and activate the case.
6. Click on the Financials tab and select Transactions.
7. Issue financials using the page action.
8. Navigate to the integrated case and update and activate evidence as required in order to generate an overpayment.
9. Navigate to the Payment Correction overpayment case.
10. Click on the Financial tab and select Transactions.
11. Issue financials using the page action. This will generate the liability.
12. On the product delivery case, click on the Financials tab and select Deductions.
13. Select New Applied Deduction (Fixed) from the page action menu.
14. Select the participant in the Case Member drop-down and click Search.
15. Select the Payment Correction returned in the search results.
16. On the Deduction Details page of the wizard, provide the following details:
    • Deduct from Nominee: The primary nominee
    • Type: Liability Repayment
    • Start Date: Current date
    • Amount: $10
    • Assign Next Priority: Check this box
17. Click Save & Activate.
18. Navigate to the integrated case and modify and activate evidence in order to generate an underpayment.

 

First batch run:

 

1. Login as a system administrator and execute ‘Generate Instruction Line Items’ batch with processing date 1 month in the future.
2. Now execute ‘Generate Instruments’ batch.

 

Check graph after first batch run:

 

1. Login as a caseworker and navigate to the payment correction case created above.
2. Verify that the deduction is successfully created.
3. The graph in the context panel displays deduction and outstanding amounts correctly.

 

Second batch run:

 

1. Login as a system administrator and execute ‘Generate Instruction Line Items’ batch with processing date 3 months in the future.
2. Now execute ‘Generate Instruments’ batch.

 

Check graph after second batch run:

 

1. Login as a caseworker and navigate to the payment correction case created above.
2. Verify that a new deduction is successfully created.
3. Issue: The graph in the context panel still displays old deduction and outstanding amounts, and does not match the total overpaid values in the context panel.

 

Resolution:

The graph query has been updated to retrieve the correct amounts for the payment allocations so that the BIRT chart now correctly displays the allocated amounts and outstanding balance of the overpayment.

 

PO08786, WorkItem:260459 - When 12-hour AM/PM time is used, the time is still displayed in 24-hour military format in the Assessment PDF Report Generation, Collaboration Case Transaction History, and Collaboration Case Discussions

 

Issue Description:

It is not possible to override the time format from the default 24-hour military format to the 12-hour AM/PM format for Assessment PDF Report Generation, Collaboration Case Transaction History, and Collaboration Case Discussions.

User Interface Impact: No

Steps to Reproduce:

Scenario 1: Assessment PDF Report Generation

 

1. Login as a caseworker.
2. Register a new Person.
3. Create an instance of an integrated case that has been configured for Outcome Plans.
4. Click on the Outcome Plans tab.
5. Use the New page action to create a new outcome plan.
6. On the Outcome Plan, click on the Reviews tab.
7. Use the New page action to create a new review.
8. From the row-level action for the newly created review, choose View Printable Document.
9. Issue: The time displayed in the generated PDF is always military time.

 

Scenario 2: Collaboration Case Transaction History

 

1. Login as a caseworker.
2. Register a new Person.
3. Create a new Social Enterprise Folder for the person.
4. Click on the Admin tab and select Transaction History.
5. Issue: The time in the Date column is always displayed as military time.

 

Scenario 3: Collaboration Case Discussions

 

1. Login as a caseworker.
2. Register a new Person.
3. Create a new Social Enterprise Folder for the person.
4. Click on the Discussions tab.
5. Use the New page to create a new discussion.
6. Issue: The time in the Posted column is always displayed as military time.

 

Resolution:

This issue has been resolved. Two new properties have been introduced to customize the time format to enable the use of the 12-hour AM/PM format in the above scenarios.

For more information see updated documentation sections that list the  new bootstrap properties:

• https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

 

Technical:

The following two new properties can be set in Bootstrap.properties:

 

• curam.environment.default.timeformat
• curam.environment.default.timeseparator

 

The following values are allowed:

 

• curam.environment.default.timeformat: 'hh mm ss a', 'hh mm a', 'HH mm', 'HH mm ss'
• curam.environment.default.timeseparator: ':', '.'

 

The default value of the time format remains as HH:mm:ss.
 

PO09031, WorkItem:265853 - French translation is missing for the My Cases tab description

 

Issue Description:

Several French translation words are missing for the My Cases tab description. In general, not all words in the My Cases tab description are being translated as per the user's locale.

User Interface Impact: No

Prerequisite(s):

 

1. The French language pack is installed.
2. The default server locale is en_US and the caseworker's locale is in French.

 

Steps to Reproduce:

 

1. Login as a caseworker.
2. Navigate to My Cases.
3. Issue: The description in the My Cases tab is only partially translated in line with the default server locale.

 

Resolution:

This issue is now addressed and now the tab description is translated in line with the user's locale.

 

PO09112, WorkItem:267020 - French translations are missing in Overpayment and Underpayment correction cases

 

Issue Description:

French translations are missing in Overpayment and Underpayment correction cases.

User Interface Impact: No

Prerequisite(s):

 

1. The French language pack is installed.
2. The default server locale is en_US and the caseworker's locale is in French.
3. Login as a system administrator.
4. Under property administration search for 'curam.miscapp.checkforliveliabilities'.
5. Change value to NO and Publish.

 

Steps to Reproduce:

Steps to Reproduce the Overpayment correction case issue:

 

1. Login as a caseworker.
2. Register a new Person
3. Create a Product Delivery Case
4. Add and activate evidence such that the client is eligible for payment.
5. Activate the case and issue a payment.
6. Go to Certifications page in Financials Tab and edit the Certification to start on the next payment date.
7. See that an Overpayment case is generated.
8. Open the newly created Overpayment case .
9. Issue: On the context panel the English text 'Overpaid' is not translated into French.

 

Steps to Reproduce the Underpayment correction case issue:

 

1. Register a new Person
2. Create a Product Delivery Case
3. Add and activate evidence such that the client is eligible for payment.
4. Activate the case and issue a payment.
5. Go to Certifications page in Financials Tab and edit the Certification to start from the previous date.
6. See that an Underpayment case is generated.
7. Open the newly created Underpayment case .
8. Issue: On the context panel the English text 'Underpaid' is not translated into French.

 

Resolution:

The Overpayment and Underpayment texts are now translated in line with the user's locale.

 

WorkItem:268038 - Deprecate legacy employment contribution entity structs

 

Entities that enabled customers to implement contribution-based solutions in employment areas such as pensions and unemployment insurance tax were deprecated in v7.0.0.0.
The structs of the deprecated entities have now also been deprecated.
 

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

 

 

ELIGIBILITY & ENTITLEMENT

 

PO08931, WorkItem:264441 - French translations are missing for the eligibility timeline view

 

Issue Description:

The eligibility timeline view does not display localized text.

User Interface Impact: No

Prerequisite(s):

 

1. The French language pack is installed.
2. The default server locale is en_US and the caseworker's locale is in French.
3. Configure the Member Eligibility Viewer (MEV) for a product that has been localized.
4. Submit an application for that product type.

 

Steps to Reproduce:

 

1. Login as a caseworker.
2. Search for and navigate to the home page of the applicant.
3. Click the Eligibility tab.
4. Issue: The eligibility timeline is displayed in English.

 

Resolution:

The eligibility timeline is now displayed in French.
 

PO09099, WorkItem:266655 - French translation missing after payment is reissued

 

Issue Description:

The type code of a financial transaction may not be correctly localized on the financial transactions page.

User Interface Impact: No

Prerequisite(s):

 

1. The French language pack is installed.
2. The default server locale is en_US.

 

Steps to Reproduce (Generic):

 

1. Login as a caseworker whose locale in English.
2. Register a Person.
3. Click on the Care and Protection tab.
4. Use the New page action to create a new integrated case.
5. Add the necessary evidence to make the client eligible.
6. Activate the evidence.
7. Add a product to the integrated case.
8. Add certification from this week to some date in the future.
9. Submit, approve, and activate the product delivery case.
10. Click on the Financials tab and select Transactions.
11. Use the Issue Payment page action to generate the payment.
12. Login as a caseworker whose locale is French.
13. Search for the product delivery created above and click on the Financials tab.
14. From the row-level menu choose the Cancel Payment action. Do not invalidate the payment.
15. On the canceled payment row-level menu choose Reissue.
16. Issue: The reissued payment field displays in English instead of French.

 

Resolution:

The financial transactions listed on the person and case transaction pages have been corrected to ensure they are displayed in French.
 

WorkItem:267965 - Performance optimization for method CaseNomineeObjective.searchObjectiveHistoryForCase

 

Issue Description:

The SQL query currently used by the method CaseNomineeObjective.searchObjectiveHistoryForCase can have very high CPU consumption in the Oracle Automatic Workload Repository Report. This can have an impact on the performance of bulk reassessment after rate and threshold changes, as well as online reassessments resulting from evidence changes.

User Interface Impact: No

Steps to Reproduce:

This change relates to a performance optimization of the CaseNomineeObjective.searchObjectiveHistoryForCase API. It is highly dependent on user data and as such is not directly reproducible.

Resolution:

The SQL query has been refactored into two separate queries and the version of the query which is used now depends on whether the toDate parameter is specified. This enables the database to apply the most optimal access plan for the query.
 

WorkItem:268434 - Improve reassessment performance when using CER rules

 

Issue Description:

During a case reassessment, EvidenceDescriptor records for the case are read as multiple single reads resulting in increased load on the database.

The following two entity reads are executed unnecessarily during a case reassessment, resulting in increased load on the database:

• EvidenceChangeHistory.readUserForLatestChange
• EDApprovalRequest.readCurrentApprovalRequestDetails

 

User Interface Impact: No

Steps to Reproduce: N/A

(This issue is dependent on user data and as such is not directly reproducible).

Resolution:

To provide optimizations for the reassessment of cases that are long-lived and have many static evidences with many changes, the approach to retrieving static evidence has now been enhanced and it is now possible to disable two reads that retrieve unneeded data during a reassessment.

Evidence Descriptor caching is now used to retrieve static evidence. During a reassessment transaction SQL searches from the EvidenceDescriptor table, which includes case ID
or succession set ID, resulting in all the EvidenceDescriptor records for the case being cached in the current transaction. The first read populates the cache and subsequent reads in that transaction will fetch the records from the cache. The three transaction-level caches which store this data are as follows:

• curam.cache.transaction-group.evidencedescriptorcache.bycase
• curam.cache.transaction-group.evidencedescriptorcache.byrelatedidandtype
• curam.cache.transaction-group.evidencedescriptorcache.successionIDToCaseID

 

As with all transaction-level caches, each of these can be tuned with a timeToIdle and/or timeToLive setting. This cache mechanism is active for reassessment transactions only - for example it does not operate for online transactions which modify or edit a piece of evidence. By default, this cache mechanism for reassessment transactions is enabled. If necessary it can be disabled by adding the following application property:

• curam.evidence.evdescripcache.disabled=TRUE

 

A change was also made to the following two entity reads which are now suppressed during a reassessment to improve the case reassessment transactions:

• EvidenceChangeHistory.readUserForLatestChange
• EDApprovalRequest.readCurrentApprovalRequestDetails

 

For all other transactions, these reads are executed as normal. If necessary, the suppression of either of these reads can be disabled by setting the following two application properties respectively:

• curam.evidence.disable.suppress.userforlatestchange=TRUE
• curam.evidence.disable.suppress.evidenceapprovalrequeststatus=TRUE

 

For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

 

EVIDENCE MANAGEMENT

 

PO08992, WorkItem:265630 - Progress spinner is not getting dismissed when opening the Change History evidence page for a French user

 

Issue Description:

On an evidence record home page, a Change History tab is available, which allows the caseworker to view a history of changes for that evidence record. However, as a French user, when the change history tab is selected, a progress spinner is displayed and the change history evidence page does not appear.

User Interface Impact: No

Prerequisite(s):

 

1. The French language pack is installed.
2. The default server locale is en_US and the caseworker's locale in French.

 

Steps to Reproduce (Generic):

 

1. Login as a caseworker.
2. Register a new Person.
3. Create an integrated case for the person.
4. From the tab navigation bar, click the Evidence tab and add new Address evidence through the evidence dashboard.
5. Activate the evidence.
6. From the page group navigation bar, select Active Evidence and click the Description of the Address evidence.
7. Go to the Change History tab (Historique des changements).
8. Issue: The progress spinner keeps spinning and the page does not load.

 

Resolution:

This issue is now resolved. The Change History evidence page is displayed when the Change History tab is selected.

Technical:

 

One of the row-level menu items on the evidence history page is to Continue Editing. In French, this is translated as 'Poursuivre l'édition', which when rendered caused an error in the HTML of the page. The page renderer has been fixed to correctly escape any single quotes in the page elements.
 
COMMON

 

PO09160, WorkItem:267616 - Communication drop-down value 'All' does not display in accordance with the logged-in user's locale

 

Issue Description:

On an integrated case, an issue exists on the Contact tab of the Communications page. The Regarding Case Member drop-down always displays English text instead of the properly localized text. For example, the drop-down value contains the English text 'All' instead of French text 'Tous' for users with the French locale.

User Interface Impact: No

Prerequisite(s):

 

1. The French language pack is installed.
2. The default server locale is en_US and the caseworker's locale is in French.

 

Steps to Reproduce (Generic):

 

1. Login as a caseworker.
2. Register a new Person.
3. Use the New Case tab action to create a new integrated case for the person.
4. Click the Contact tab and select Communications.
5. Issue: The Regarding Case Member drop-down contains the English text 'All' instead of French text 'Tous'.

 

Resolution:

The Regarding Case Member text values now fully display in the language of the currently logged-in user.

 

WorkItem:267866 - Reinstate the Referrals feature from a deprecated state in the Social Program Management application

 

Issue Description:

The Referrals feature that allows for the capture of basic information that is related to the referral of a client to the Service Supplier participant type is to be reintroduced into the product.

For more information see the deprecation task 'WorkItem:159371 - Deprecate Referrals (Legacy) functionality in the V7.0 external release notes.

User Interface Impact: N/A

Prerequisite(s):

 

1. Login as a system administrator.
2. Under the Application Data shortcut section, select the Property Administration shortcuts menu item.
3. Search for the 'curam.cpm.isinstalled' application property. Set the value to 'No'. Publish changes.

 

Steps to reproduce:

Steps to access the reinstated functions

 

1. Login as a caseworker.
2. Navigate to an existing integrated case.
3. Navigate to the Events tab.
4. Select the New Referral tab level menu item.

 

Resolution:

Referrals are now reintroduced into the product and can be created from the case calendar.

The following list contains the features being un-deprecated:

 

1. Creating a referral
2. Modifying a referral
3. Viewing Referral Details from the Events Calendar View and List View
4. Creating a Case Referral Notification

 

PO09259, WorkItem:268814 - Performance Issue - Long running SQL when searching an employer

 

Issue Description:

Performance can be affected when searching for an employer or prospect employer where there are a large number stored in the database, impacting the return of search results.

User Interface Impact: No

Prerequisite(s):

 

1. The system contains a considerable number of prospect employers or registered employers (in the order of 1000's).

 

Steps to Reproduce:

 

1. Login as a caseworker.
2. Click on Employer under Search in the shortcuts panel.
3. Input some partial search criteria, such as part of the registered name and the city.
4. Click Search.
5. Issue: The query takes a long time to execute before the results are returned.

 

Resolution:

The search query has been optimized and split into two distinct queries, one for Employers and one for Prospect Employers. A new field has also been added to the Employer Search page to allow a user to decide if Prospect Employers should be returned in the search results or not.
 

INVESTIGATIONS

 

PO09178, WorkItem:267214 - A user is still able to view and download attachment documents after deleting an allegation

 

Issue Description:

Attachments can be associated with allegations within an investigation case and the attachments may also include an uploaded document. Currently, when an allegation is deleted from an investigation, users are still able to view and download the documents that were uploaded when creating the attachment.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as an Investigator and click on the Investigator workspace.
2. Click on New Investigation under Investigations in the shortcuts panel.
3. On the New Investigation modal, select the 'person or prospect person' option.
4. Search for an existing person and select the record returned in the search results.
5. Fill in the mandatory fields and click Save.
6. Navigate to the Allegations tab and create a new allegation.
7. Using the action menu of the allegation, add a new attachment that includes an uploaded document.
8. Using the action menu of the allegation, delete the allegation.
9. Issue: The user can view and download the document that was uploaded with the attachment.

 

Resolution:

This issue has been resolved. When an allegation is deleted, all attachments associated with the allegation are now also deleted. This prevents a user from being able to view or download any associated documents.
 

PO09179, WorkItem:267699 - New attachment can be added after the allegation is deleted

 

Issue Description:

Attachments can be associated with allegations within an investigation case. Currently, when an allegation is deleted from an investigation, users are able to add a new attachment.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as an investigator.
2. Click New Investigation under Investigations in the shortcuts panel.
3. From the New Investigation modal, select 'a person or prospect person?' hyperlink.
4. On the Person Search page, search for and select an existing person.
5. On the New Investigation modal set the mandatory fields and click Save.
6. Click the Allegations tab.
7. Select the New page action and create a new allegation.
8. Click Save.
9. Use the Delete row-level action of the allegation to cancel the allegation.
10. Use the Add Attachment row-level action of the allegation to add a new attachment.
11. Click Save.
12. Issue: The attachment is added even though the allegation is canceled.

 

Resolution:

This issue has been resolved. When an allegation is deleted and the status is set to canceled, the user is not able to add a new attachment.
 

PARTICIPANT MANAGEMENT

 

PO07536, WorkItem:215004 - Assessments in-page navigation issue for duplicate clients

 

Issue Description:

In the Social Program Management (SPM) product, when a client is marked as a duplicate of another, a caseworker can view case-related information for the duplicate client along with the information of the original client. After creating an integrated case and an assessment for both the duplicate client and original client, a number of issues are observed on the original client’s home page under the Care and Protection tab:

 

1. The old look and feel is displaying for the in-page navigation tabs within the Assessment section.
2. The duplicate client’s assessment tab incorrectly displays a list of all case types related to the client.
3. The caseworker is incorrectly navigated to the Cases section when the original clients tab within the assessment section is selected.
4. The Assessment section is incorrectly displaying the duplicate client in-page navigation tab.

 

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 Soft Links Displayed' in the Name field and click Search.
4. Use the Edit Value row-level action to update the value of the property to YES and click Save.
5. Use the Publish page action to publish the changes.
6. Login as an administrator.
7. Click Integrated Cases under Cases in the shortcuts panel.
8. Click any of the integrated cases listed to open its configuration.
9. Click the Assessments tab and use the Add Existing page action to add the following assessments:
   • Asthma Assessment
   • Juvenile Detention Assessment

 

Steps to Reproduce (Generic):

 

1. Login as a caseworker.
2. Register a new Person and create an instance of the integrated case configured for assessments.
3. Click the Assessments tab.
4. Use the New page action to create one of the assessments configured.
5. Register another Person and create an instance of the integrated case configured for assessments.
6. Again, use the New page action to create one of the assessments configured.
7. On the first person's home page, click on the Administration tab and select Duplicates.
8. Select the Mark New Duplicate page action.
9. Search for and select the second person.
10. On the Mark Duplicate modal page, click Save.
11. Click the Care and Protection tab and select Assessments.
12. Issue 1: The old look and feel is displayed for the in-page navigation tabs.
13. Click the duplicate person's in-page navigation tab.
14. Issue 2: The incorrect case types are listed for the duplicate client.
15. Click the original person's in-page navigation tab.
16. Issue 3: The caseworker is incorrectly navigated to the Cases section.
17. Login as a system administrator.
18. Click Property Administration under Application Data in the shortcuts panel.
19. Enter 'Client Merge Soft Links Displayed' in the Name field and click Search.
20. Use the Edit Value row-level action to update the value of the property to NO and click Save.
21. Use the Publish page action to publish the changes.
22. Login as a caseworker.
23. Search for and open the first person's home page.
24. Click the Care and Protection tab and select Assessments.
25. Issue 4: The in-page navigation tab for the duplicate person is still visible.

 

Resolution:

These issues have been addressed. With the new components and Carbon styling that is implemented in the UI, the look and feel for the original client and duplicate client in page navigation tabs has been updated. The duplicate client’s tab is correctly listing the assessments related to the client and the link on the assessment tab for the original client has been updated. The visibility of the in-page navigation tabs for the duplicate client in the assessments sections has been brought under the influence of the application property 'Client Merge Soft Links Displayed’. This application property allows the caseworker to view a client's duplicate records alongside the original records and is set to NO by default.
 

 

Administration Suite

 

Dynamic Evidence

DYNAMIC EVIDENCE

 

WorkItem:269655 - Definition text on the Edit Dynamic Evidence Type page is not localized

 

Issue Description:

The definition text on the Edit Dynamic Evidence Type page is not localized correctly.

User Interface Impact: No

Prerequisite(s):

 

1. Any language pack is installed.
2. The administrator's locale is set to the installed language pack.

 

Steps to Reproduce:

 

1. Login as an administrator.
2. Click Dynamic Evidence under Rules and Evidence in the shortcuts panel.
3. For any of the evidence types in the Dynamic Evidence list, click the Edit row-level action.
4. Issue: The definition text on the Edit Dynamic Evidence Type page is not localized. It appears in English to the user.

 

Resolution:

 

The Edit Dynamic Evidence Type page has been corrected to ensure that the definitions are localized and that the correct translations appear in accordance with the logged-in user's locale.
 

Intake

 

PO05754, WorkItem:117222 - Search modal is not defined for the Business Object Type of Application on the Task Search tab

 

Issue Description:

When trying to search for a Task by specifying a related Application, the Application Search modal does not display. This prevents the user from completing the search by specifying the application.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a caseworker.
2. Navigate to the Inbox section.
3. Select Task Search under Tasks in the shortcuts panel.
4. Select the value of Application in the Business Object Type drop-down.
5. Click the search icon.
6. Issue: The Application Search modal does not display.

 

Resolution:

 

The Application Search modal now displays when the search icon is clicked. For customers that do not use Insurance Affordability (HCR) module, the search is disabled because Merative Social Program Management (SPM) currently does not associate tasks with an application. For customers that do have the HCR module, this search is enabled.
 

Application Development Environment

 

Client Development Environment
Core Development Infrastructure
Server Development Environment

 

WorkItem:262881 - Update the Entity Relationship Diagram (ERD) with entities that have been added, removed or deprecated in recent SPM releases

 

Issue Description:

Merative Social Program Management uses Entity Relationship Diagrams (ERDs) to illustrate how data is stored and to show dependencies between entities. The Entity Relationship Diagrams are provided in PDF format, however some of the Entity Relationship Diagrams do not reflect the entities that have been added, removed or deprecated in recent SPM releases.

User Interface Impact: No

Steps to Reproduce:
N\A

Resolution:

The Entity Relationship Diagrams are now updated to reflect entities that have been added, removed and deprecated in recent SPM releases. The following updates have been made:

ERD-CaseandParticipantIndex

• The Case and Participant Index section and related entity CPIData have been marked as deprecated.

 

ERD-ChildCare

• This ERD has been removed as the logic is no longer shipped with the SPM deliverable.

 

ERD-ContentManagement

• The section specified in this ERD was called Evidence Broker in error. This has been updated to Content Management.

 

ERD-Core-AbstractEntities

• The Contributions section has been removed to reflect the removal of that feature in SPM. This has also resulted in the following entities being removed:
  • InsuranceConsolidation
  • InsuranceRetLineItemDetail
  • InsuranceReturnLineItem

 

ERD-Core

• The Contributions section has been removed. This has led to the removal of the following entities:
  • InsuranceConsolidation
  • InsurancePeriodControl
  • InsuranceRetLineItemDetail
  • InsuranceReturnHeader
  • InsuranceReturnHeaderDetail
  • InsuranceReturnLineItem
  • InsurConsolidationDetails
• The AttachmentInfo entity has been added to the Concern section.
• The OverviewTabConfig entity has been added to the Case section.
• The following entities have been added to the Case section:
  • GuidedChangeCOC
  • GuidedChangeCOCAction
  • GuidedChangeStatus
• The following entities have been added to the Rules section:
  • ReassessmentQueue
  • ReassessmentQueueControl

 

ERD-EvidenceBroker

• The following entities have been added to the Evidence Broker section:
  • AESActionedEvidence
  • AESDeliveryPlan
  • AESErrorMessage
  • AESMatchedEvidence
  • AESShareItem
  • AESShareSet
  • AESShareSetPull

 

ERD-GlobalIncomeSupport

• A new section called Cross-Cascade has been added and a new entity called NonMagiEligibility has been added to that section.

 

ERD-Infrastructure

• The Classic IEG section has been removed. The following entities associated with that section have also been removed:
  • GroupInformation
  • IEGDefinitionInfo
  • IEGExecutionInfo
  • ScriptGroupRels
  • ScriptInformation
• The section called Generic Search Server has been marked as deprecated. The following entities are part of that deprecated section:
  • GSSEntity
  • GSSMapperType
  • SearchService
  • SearchServiceField
  • SearchServiceRow
  • SearchSrvcRowExt
• The following entities have been added to the Code tables section:
  • CodeTableView
  • CodeTableViewCode
• The following entities have been removed from the Rules section:
  • CREOLEAttributeValueHash
  • CREOLERAMatchDependency
  • CREOLEReadAllDependency
• The following entities have been added to the Rules section:
  • CREOLERuleSetGroup
  • Dependency
  • DependencyTrace
  • PrecedentChangeItem
  • PrecedentChangeSet
  • PrecedentChangeSetBatchCtrl

 

ERD-ProviderManagement

• The Service Planning Admin section and associated entity ContractTextLink have been removed. This entity exists in a different ERD diagram.
• The AffectedRelatedReference entity has been added to the Products section.
• The ProviderDeductionCDILink entity has been added to the Provider section.

 

ERD-SmartNavigator

• This is a new ERD Diagram that has been added and contains the SmartNavigatorSearchHistory entity.

 

ERD-UniversalAccess

• The CitizenCommSendByPostTracker entity has been added to the CitizenSelfService section.

 

ERD-Verification

• The AttachmentInfo entity has been added to the Concern section.

 

WorkItem:267864 - Configure WebLogic application server to use the urandom device on Linux machines

 

Issue Description:

On Linux operating systems, a performance issue occurs with WebLogic application server instances when the random device pool of the Linux operating system runs into low entropy and the application server must wait for new I/O operations to occur to increase the random bits in the random device pool before it continues. This is a common pattern on virtualized environments or headless boxes where the cryptographic operations of the OS consume random bits faster than the I/O operations can populate random bits into the random device pool.

User Interface Impact: No

Steps to Reproduce: N/A

Resolution:

The startserver target now sets any WebLogic application server instance it starts to use the urandom device for random data on Linux operating systems by default instead of the random device. The urandom device falls back to pseudo-random numeric algorithms when its pool is depleted rather than waiting for new I/O operations to repopulate its random bits pool before it allows the application server instance to continue.

Technical:

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

• CuramSDEJ/bin/app_runtimewls.xml

 

PO09070, WorkItem:268380 - The implementation JAR missing from class loader in coreinf-ejb EJB Module on WebLogic 12.2

 

Issue Description:

In Merative Social Program Management deployed on WebLogic 12.2, classes in the implementation.jar can no longer be sourced from the coreinf-ejb.jar EJB Module. This means that classes extended by customers that require the implementation.jar in the coreinf-ejb.jar EJB Module are returning errors when attempting to call custom methods that reference methods in out-of-the-box classes.

Customers may experience a java.lang.AbstractMethodError at runtime when calling custom methods in extended classes.

User Interface Impact: No

Steps to Reproduce:

 

• Model an extension class, for example, CaseAttachmentLinkExt.
• Add an nsmulti method with custom key and return struct and add custom SQL to read from the extension class table, for example, searchCaseAttachmentLink().
• Link the extension class with the out-of-the-box class with Extension in class diagram, for example, CaseAttachmentLink.
• Create a custom facade and service layer class with each having a method call, for example, getCaseAttachmentLinkForDisplay().
• Save changes and run build server.
• Implement the custom facade so it calls the service layer implementation class.
• Implement the service layer class and create an object of the out of the box class that calls the created nsmulti method, for example, code snippet:

 

   curam.core.intf.CaseAttachmentLink link = curam.core.fact.CaseAttachmentLinkFactory.newInstance();
   CustomSearchClientAndPartnerDocumentsKey searchDocumentsKey = new CustomSearchClientAndPartnerDocumentsKey();
   searchDocumentsKey.primaryConcernRoleID = key.concernRoleID;
   CustomDocumentDetailsList publishedScannedDocumentsList = link.searchCaseAttachmentLink(searchDocumentsKey);

 

• Create a UIM to call the created custom facade method.
• Build and deploy the application on a WebLogic 12.2 server.
• Access the custom UIM from the application.
• Issue: An un-handled server exception appears in the application and an AbstractMethodError appears in application server logs.

 

Resolution:

This issue was resolved and it is now possible to call custom methods on an extended class of an out-of-the-box entity without a java.lang.AbstractMethodError occurring.

Technical:

WebLogic 12.2 implemented a fix that ensured the application server followed the class loading policies of the J2EE specification correctly. This fix caused conflicts with EJBs in the SPM implementation.jar during deployment of SPM applications on WebLogic 12.2 and the initial resolution was to remove the SPM implementation.jar from offending EJB Module classpaths which introduced this issue. A Bundled Library has been added to EAR files during the EAR building process and this library is populated with the SPM implementation.jar. This library allows EJB Modules on these EAR files to reference classes within JARs located in the library and as the EJB Modules can now reference the SPM implementation.jar, this resolves the java.lang.AbstractMethodError appearing when calling a custom nsmulti search method.
 

WorkItem:270643 - Support for secure integration with IBM Watson Assistant

 

Social Program Management now supports secure integration with IBM Watson™ Assistant. If enabled, communication between SPM and IBM Watson Assistant is secured by using a JSON Web Token (JWT). This JWT is required for both outbound and inbound requests between SPM and IBM Watson Assistant.
A chat widget has been optionally included in the caseworker application screens. The chat widget can be configured to connect to an instance of IBM Watson Assistant.
New functionality has been added to the SPM application to generate and sign a JWT and to add it to each outbound request to IBM Watson Assistant. In addition, the ant build scripts have been updated to generate a keystore, a self-signed certificate, and a public key certificate file. These are used for both signing the JWT in the outbound requests and for verifying the JWT on the incoming requests from IBM Watson Assistant.
An issue with Weblogic 14.1.1 has been identified where a class in the provided Oracle Security Developer Tools, which is used to validate the JWT signature, references an older version of Jackson packages. However these packages have been removed from Weblogic 14.1.1. Until this issue is resolved, it is not possible to fully integrate with IBM Watson Assistant for applications running on Weblogic 14.1.1.
For more information, see the product documentation at https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

 

WorkItem:270711 - Add bouncycastle packages to the prefer-application-packages list in the weblogic-application.xml for the Web Services EAR

 

Issue Description:

A change in the Oracle JDK 1.8_261, or later, led to conflicts with packages on the Oracle WebLogic Application Server when starting Merative Social Program Management Web Services.

User Interface Impact: No

Steps to Reproduce: N/A

Resolution:

A configuration change was introduced by adding org.bouncycastle as a preferred package to the Web Services weblogic-application.xml to resolve these conflicts.

Technical:

The following files have been updated:

• ../CuramSDEJ/ear/webservices/wls/ear/weblogic-application.xml

 

CLIENT DEVELOPMENT ENVIRONMENT

 

Widgets

 

WorkItem:260058 - The default user interface font for Social Program Management has been updated to IBM Plex

 

Issue Description:

Social Program Management no longer ships the Helvetica Neue font with the product due to the introduction of new components and Carbon styling in the user interface.

User Interface Impact: N/A

Steps to Reproduce: N/A

Resolution:

The default user interface font in Social Program Management (SPM), Helvetica Neue, has been updated to the IBM Plex font.
The Social Program Management font-faces that are used to load font throughout the application are defined in the following location:
JDE/CuramCDEJ/lib/curam/web/themes/curam/fonts

The Helvetica specific file 'helvetica-neue-ibm.css' has been removed from this location. Use 'main-ibm-font.css' instead to load IBM font-faces in your application pages.

For more information about IBM Plex, see: https://www.ibm.com/plex.

 

PO08941, WorkItem:264586 - The logout screen does not translate based on the user's locale

 

Issue Description:

The logout screen does not translate based on the user's locale. Instead, the translation is based on the default server locale.

User Interface Impact: No

Prerequisite(s):

 

1. The French language pack is installed.
2. The default server locale is en_US and the caseworker's locale in French.

 

Steps to Reproduce:

 

1. Login as a caseworker.
2. Select logout.
3. Issue: The logout page is displayed in English, which is the default server locale.

 

Resolution:

The logout page is now correctly translated based on the user's locale.
 

PO08832, WorkItem:266881 - The Close all tabs button does not always close all the application tabs that are opened

 

Issue Description:

In the Internet Explorer 11 browser, the Close all tabs button, which is supposed to close all application tabs that are open in the caseworker application, does not always work as intended. If there is more than one application tab open, or if the Close all tabs button is selected from a tab whose content is not currently displayed, some of the tabs may remain open.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a caseworker using the Internet Explorer 11 browser.
2. Open three application tabs.
3. Right-click on a tab whose content is not currently displayed.
4. Select Close all tabs.
5. Issue: Only the application tab that was clicked is closed.

 

Resolution:

This issue was resolved by updating the JavaScript executed when the Close all tabs option is selected.

Technical:

The following file has been changed:

• TI/client/dojo-overrides/jscript/src/dijitl/ayout/ScrollingTabController.js

 

WIDGETS

 

WorkItem:262396 - Opening and closing a tooltip dialog in a context panel becomes increasingly slower when using the keyboard

 

Issue Description:

In the Google Chrome and Internet Explorer 11 browsers, opening and closing a tooltip dialog in a context panel becomes increasingly slower when using the keyboard. An example of where this occurs is the Special Caution icon.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a new Person.
3. Click on the Issues and Proceedings tab and select Special Cautions.
4. Use the New page action to create a Special Caution for the person.
5. When the context panel has refreshed, navigate to the context panel using the keyboard. Press the Tab key to move to the Special Caution icon.
6. Open the Special Caution tooltip pressing the Enter key.
7. Close the Special Caution tooltip pressing the Enter key.
8. Repeatedly open and close the Special Caution tooltip with the keyboard.
9. Issue: It becomes increasingly slower to open and close the tooltip dialog.

 

Resolution:

The Javascript for the tooltip dialog widget has been updated to address the performance issues that occur when opening and closing a tooltip dialog in a context panel using the keyboard.

Technical:

The JavaScript classes that have been updated are:

• ../webclient/components/CEFWidgets/WebContent/CDEJ/jscript/curam/DelayedTooltipDialog.js
• ../webclient/components/CEFWidgets/WebContent/CDEJ/jscript/curam/DelayedTooltipDialog.js.uncompressed.js

 

CORE DEVELOPMENT INFRASTRUCTURE

 

WorkItem:260386 - In a clustered SPM deployment, a ClassNotFoundException is thrown if an attempt is made to invoke an outbound web service in an IEG custom function

 

Issue Description:

In a clustered SPM deployment, a ClassNotFoundException is thrown if an attempt is made to invoke an outbound web service in an Intelligent Evidence Gathering (IEG) custom function. The missing class, net.sf.cglib.proxy.MethodInterceptor, is present in the cglib-nodep JAR file that is shipped as part of the Java Development Environment (JDE). The JAR is also present when a server code EAR file is built but is not specified in the manifest file of the implementation.jar file and is therefore not on the classpath. This results in a ClassNotFoundException when logic within that JAR is required and invoked by the application.

User Interface Impact: No

Steps to Reproduce:

There are no out-of-the-box steps that can reproduce this issue. This is due to the fact that there are no out-of-the-box IEG scripts that contain references to custom functions that invoke an outbound web service. If that scenario is satisfied, the issue would manifest itself when the IEG custom function was invoked which would lead to the ClassNotFoundException as the cglib-nodep JAR is not present on the classpath.

Resolution:

 

The cglib-nodep JAR file is now included on the classpath in the manifest file of the implementation.jar contained within a server code EAR file. This ensures that the logic contained within that JAR is available to be invoked when executing an outbound web service in an IEG custom function.

SERVER DEVELOPMENT ENVIRONMENT

 

PO07915, PO08317, PO08919, WorkItem:237326 - Some form fields are being rendered incorrectly in the caseworker application after an Intelligent Evidence Gathering (IEG) script has been loaded

 

Issue Description:

On specific evidences, the Frequency drop-down field does not work correctly when the evidence is opened on an integrated case after using an Intelligent Evidence Gathering (IEG) script. This issue occurs for specific evidence pages after completing an Income Support application script, where the Frequency drop-down field will be displayed incorrectly and the 'Please Select' placeholder text of the drop-down will appear below the field after it is clicked. The same issue occurs with the State drop-down field when creating an External Agency Referral.

User Interface Impact: No

Steps to Reproduce:

Scenario 1 (Income Support):

 

1. Login as an Income Support caseworker.
2. Register a new Person.
3. Create and submit an Income Support application for the person.
4. Navigate to the Income Support integrated case evidence dashboard and create new General Insurance evidence.
   • Note that the Frequency drop-down field displays the 'Please Select' placeholder text in a light gray color.
5. Issue: When the Frequency drop-down is clicked, the 'Please Select' placeholder text will be displayed below the drop-down.

 

Scenario 2 (Income Support):

 

1. Login as an Income Support caseworker.
2. Register a new Person.
3. Create and submit an Income Support application for the person.
4. Navigate to the Income Support integrated case and expand the tab actions menu.
5. Select the Guided Change menu item and Add Member from the sub-menu.
6. Navigate through the wizard until the Income Details section is reached.
   • Note that the Frequency drop-down field displays the 'Please Select' placeholder text in a light gray color.
7. Issue: When the Frequency drop-down is clicked, the 'Please Select' placeholder text will be displayed below the drop-down.

 

Scenario 3 (Platform):

 

1. Login as a caseworker.
2. Register a new Person.
3. Click on the Referrals tab and select the New External Agency Referral page action.
   • Note that the State field is rendered as expected.
4. Select the New Application Form menu item from the tab menu.
5. Select a form and once a script has loaded, close the modal.
6. Navigate back to the Referrals tab and click on the New External Agency Referral page action again.
7. Issue: The State field is rendered incorrectly. When the State drop-down is clicked, the 'Please Select' placeholder text will be displayed below the drop-down.

 

Resolution:

The Frequency drop-down field on specific evidence pages and the State drop-down field when creating an External Agency Referral display and behave correctly after using an Intelligent Evidence Gathering script.

Technical:

Domains are data type definitions that resolve to either a primitive data type or another domain. Domains that are used in the caseworker application are typically modelled, while domains that are used by Intelligent Evidence Gathering (IEG) scripts are created via configuration files, known as datastore schemas, and are uploaded.

When an IEG script is loaded in the application, all the domains that are defined within the associated datastore schemas are loaded into the application. After the IEG script has been completed and a user navigates to a page in the application, if the page contains a field whose domain type is the same as one loaded in a datastore schema, the field is rendered incorrectly.

The application domains that share the same name as those defined in IEG datastore schemas have now been deprecated and any references to these have been updated with a new corresponding domain definition that shares the same name but has '_STATIC' appended. For example, the FREQUENCY_CODE and FREQUENCY_CODE_NO_IEG_OVERRIDE domain definitions have been deprecated and a new FREQUENCY_CODE_STATIC domain definition has been added. All references to FREQUENCY_CODE and FREQUENCY_CODE_NO_IEG_OVERRIDE have been updated to FREQUENCY_CODE_STATIC.

The following domains have been deprecated:

 

• ADDRESS_STATE
• FREQUENCY_CODE
• CW_MOTIVATION_RESULTS_MEMBER_STATUS
• PLAN_LEVEL
• CITIZENSHIP_STATUS_NO_IEG_OVERRIDE
• FREQUENCY_CODE_NO_IEG_OVERRIDE
• INCOME_TYPE_NO_IEG_OVERRIDE
• ADDRESS_STATE_NO_IEG_OVERRIDE
• CITIZENSHIP_STATUS
• INCOME_TYPE
• INCOME_SOURCE
• COVERAGE_CODE
• COC_TYPE
• BENEFIT_TYPE

 

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

 

PO08064, WorkItem:241922 - Product Delivery Evidence Attribution produces error messages in the logs under normal operation

 

Issue Description:

Evidence attribution refers to the assignment of a time period to a piece of evidence during which that piece of evidence is used for entitlement calculations. During evidence attribution, attribution records are created to establish the period over which the evidence is considered effective within the product delivery case.

When evidence is modified as part of a succession and activated, re-attribution of the evidence records in the succession set then occurs and existing attribution records are modified and created as required.

Currently when evidence is modified as part of a succession and activated, even when the attribution records are correctly updated for the product delivery case, error messages related to duplicate records are created in the logs.

User Interface Impact: No

Steps to Reproduce (Generic):

 

1. Login as a caseworker.
2. Register a new Person.
3. Click on the Care and Protection tab.
4. Click on the New page action to create an integrated case that relates to a product.
5. Create product delivery.
6. Create a new evidence record on the integrated case and activate the evidence.
7. Make an effective-dated change to this evidence record and activate the evidence.
8. Issue: Inspect the logs and view an error message about a unique constraint on CUR_OWNER.ATTRIBUTEDEVIDENCE.

 

Resolution:

This issue has been resolved by enhancing the code to no longer create unnecessary error messages in the logs during evidence re-attribution.
 

WorkItem:256509 - The version of the logging framework used by the SPM product has been updated from Log4j 1 to Apache Log4j 2

 

Apache Log4j is a Java-based logging utility that is used as the logging provider for the Social Program Management (SPM) product.

Due to Apache Log4j 1 reaching the end of support, the version of Apache Log4j used by SPM has been updated to Log4j 2 - specifically from 1.2.17 to 2.13.0.

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 Log4j JARs have been updated.
• CuramSDEJ/xmlserver/third_party_version.properties - the versions of the Log4j JARs have been updated.
• CuramCDEJ/lib/ext/jar/third_party_version.properties - the versions of the Log4j JARs have been updated.

 

The changes to the Log4j JAR files include:

 

• CuramSDEJ/lib/log4j-api-2.13.0.jar
• CuramSDEJ/lib/log4j-core-2.13.0.jar
• CuramSDEJ/lib/log4j2-config.jar
• CuramSDEJ/xmlserver/log4j-api-2.13.0.jar
• CuramSDEJ/xmlserver/log4j-core-2.13.0.jar
• CuramCDEJ/lib/ext/jar/log4j-api-2.13.0.jar
• CuramCDEJ/lib/ext/jar/log4j-core-2.13.0.jar
• CuramCDEJ/lib/curam/jar/log4j2-config.jar

 

It should be noted that any references in custom scripts and other artifacts to the newly versioned JARs should be updated to point to the new versions of the JAR files as specified above.

The differences between Apache Log4j 1 and Apache Log4j 2 are documented in detail on the Apache website. The main impacts to SPM include:

Java classes being refactored into different packages. For example, the following classes have been moved to a different package:

 

• org.apache.log4j.Logger => org.apache.logging.log4j.Logger
• org.apache.log4j.Level => org.apache.logging.log4j.Level
• org.apache.log4j.Category => org.apache.logging.log4j.core.Logger

 

The configuration mechanism is different.

 

1. Specifically, Log4j 2 will search for configuration data in 'log4j2.properties' instead of 'log4j.properties', and in 'log4j2.xml' instead of 'log4j.xml', there are additional configuration file types (JSON, YAML) and, importantly, the syntax of these configuration files is different.
2. The default logging level in Log4j 2 is now ERROR, in Log4j 1 it was DEBUG.
3. Log4j 2 is now contained across two jar files instead of one.

 

More information about how to adapt to these differences is contained in the Merative Social Program Management Upgrade Guide.
 

WorkItem:267218 - The WebSphere Application Server configuration script now sets the custom security property 'com.ibm.ws.security.web.logoutOnHTTPSessionExpire' to 'false'

 

Issue Description:

For stand-alone deployments on WebSphere, the 'com.ibm.ws.security.web.logoutOnHTTPSessionExpire' property is set to 'true'. This means that if a user is logged in to the SPM application, the first time a request is made to an API in the REST application from the same browser, after either server startup or a user's http session expiry, the user is redirected to the REST application login page and asked to log in again.

User Interface Impact: No

Steps to Reproduce:

 

1. Log in to the SPM application, for example, at https:<server>:<port>/Curam, using a supported browser.
2. In the same browser, open a new browser tab and try to access a REST endpoint, for example, https://<server>:<port>/Rest. (An API request that is sent directly from a browser will not pass the Referer header validation, so the expected API response is an error message about the Referer header validation).
3. Issue: Although the browser sends the access token as a cookie in the request to the REST endpoint, it is not accepted as valid, and the user is redirected to the REST login page.

 

Resolution:

The WebSphere Application Server configuration script now sets the custom security property 'com.ibm.ws.security.web.logoutOnHTTPSessionExpire' to 'false'. This means that if the user logs in to the SPM application if the application calls a REST endpoint, the access token that is sent by the browser in the cookie for the REST endpoint will be accepted and the user is not asked to log in for a second time.
 

WorkItem:268426 - Java compiler runs out memory when building against log4j 2.13.0

 

Issue Description:

Compilation fails with java.lang.OutOfMemoryError: GC overhead limit exceeded when compiling a large number (20,000+) of Java files with Log4j 2 on the class path.

User Interface Impact: No

Steps to Reproduce:

Note when using the default maximum memory of 2 GB, this issue occurs only when an individual invocation of the Java compiler processes a large number (20,000+) of Java files, that is, struct classes, intf classes, and the implemented and remaining generated classes each have a separate Java compiler invocation.

 

• Force the garbage collection (GC) mode to Parallel by setting property cmp.gc to "-J-XX:+UseParallelGC" in Bootstrap.properties.
• Build the 'server' target of a version 8.0 SPM application that has more than 20,000 Java implementation files.
• Issue: Compilation will fail with java.lang.OutOfMemoryError: GC overhead limit exceeded.

 

Resolution:

 

The garbage collection (GC) mode that is used by the Java compiler has been set to G1 which has been proven to perform better when compiling large numbers of Java files. This change only affects the garbage collection of the compiler, it does not affect runtime garbage collection. It is also possible to specify a different garbage collection for the compiler by changing the build property to a different value from its default of '-XX:+UseG1GC'. For more information on garbage collection, see the Java documentation.
 

Business Services

 

Word Integration

WORD INTEGRATION

 

WorkItem:258119 - Extend existing Word Integration solution to work with Edge Chromium

 

Issue Description:

The FILE_EDIT widget available in Social Program Management (SPM) allows users to edit a Microsoft Word document on their local computer and then save it to the database. For more information about Microsoft Word Communications in SPM, see the product documentation at https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

In previous releases, the FILE_EDIT widget used either a Java applet to manage the interaction between the browser and Microsoft Word (for browsers such as Internet Explorer that support Java) or a native messaging implementation for Google Chrome.

The FILE_EDIT widget did not support the latest versions of Microsoft Edge (versions 79 and later).

User Interface Impact: N/A

Steps to Reproduce: N/A

Resolution:

The native messaging implementation consists of a browser extension (File Edit Native Messaging Bridge) and a native messaging host application (Word Integration Assistant application) installed on the client machine. The Word Integration Assistant is a Java application that requires a Java Runtime Environment (JRE) to be installed on the client machine.

The native messaging implementation has been extended so that it now also supports Microsoft Edge, versions 79 and later.

The extension can be installed on Google Chrome or Microsoft Edge through the Chrome Web Store from https://chrome.google.com/webstore/detail/jmhkbmmljlemjenoklondlldimojdgll.
The Word Integration Assistant can be installed on client machines by using the IBMCuramWordIntegrationAssistant.msi installer file that is distributed with the Client Development Environment (CDEJ).

For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.

NOTE: As covered in release note 259418, support for the Java applet implementation of the FILE_EDIT widget has now been dropped. Customers who are currently using Internet Explorer 11 with the Java applet to edit Microsoft Word communications in SPM must use either Google Chrome or Microsoft Edge with the native messaging implementation.

 

WorkItem:259418 - Support for the Microsoft Word Integration applet solution has been dropped

 

The FILE_EDIT widget available in Social Program Management (SPM) allows users to edit a Microsoft Word document on their local computer and then save it to the database. The user can automatically create a new document from a template that can be personalized.

In previous releases, the FILE_EDIT widget used either a Java applet to manage the interaction between the browser and Microsoft Word (for the browsers that support Java) or a native messaging implementation for the Chrome browser.

Support for the Internet Explorer browser is dropped for SPM (see release note 271849) and consequently support for the Java applet version of the FILE_EDIT widget has also been dropped for Word Integration.


NOTE: As covered in release note 258119, support for the native messaging implementation has been extended so that it now also supports Microsoft Edge, versions 79 and later.
 

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

 

PO08737, WorkItem:264432 - Microsoft Word Integration feature not working in Google Chrome if the client has more than one Chrome profile

 

Issue Description:

When using the Google Chrome browser and the Microsoft (MS) Word integration feature, sometimes MS Word does not start properly if the client has more than one Chrome profile set up.

User Interface Impact: No

Prerequisite(s):

 

1. Install the IBMCuramWordIntegrationAssistant.msi which is located in IBM/Curam/Development/CuramCDEJ/lib/curam/installers.
2. Set a JRE_HOME Environment variable to point to the location of an installed JRE.
3. Create a new browser profile in Chrome, as described here: https://support.google.com/chrome/answer/2364824.
4. Install the 'Curam File Edit Native Messaging Bridge' extension from the Chrome Web Store under each profile.
5. Switch to the new profile in Chrome.

 

Steps to Reproduce:

 

1. Login as a system administrator.
2. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
3. Choose a sample template that you would like to edit through the application.
4. Set the Category to be All Communication - All Communications and click Save.
5. Login as a caseworker.
6. Register a Person.
7. Click the Client Contact tab and select Communications.
8. From the page action menu, select New Microsoft Word.
9. On the first page of the New Microsoft Word Communication wizard, check the 'Client is Correspondent' checkbox and select Next.
10. Complete the mandatory fields and select the Microsoft Word template created previously.
11. Click Save.
12. Issue: Microsoft Word fails to open.

 

Resolution:

The Merative Social program Management File Edit Native Messaging Bridge assumed that the Chrome profile was called Default. When there is more than one profile, they are named Profile 1, Profile 2, and so on. The bridge has been fixed to properly identify the correct Chrome profile when attempting to launch Word.
 

WorkItem:268779 - Microsoft Word Integration Assistant enhancements

 

Issue Description:

The Microsoft Word Integration Assistant must be installed on client machines of those clients wishing to use Social Program Management Word Integration functionality through either the Google Chrome or Microsoft Edge Chromium browsers. The installation process for Word Integration Assistant required additional manual post-install configuration for some clients, depending on how they deployed the Java Runtime Environment. Additionally, troubleshooting of issues relating to Microsoft Word integration functionality in previous releases was a manual process with many steps.

User Interface Impact: N/A

Steps to Reproduce: N/A

Resolution:

The SPM Word Integration Assistant has been enhanced to provide better functionality when installing and troubleshooting the SPM Word Integration functionality.

These changes include the following:

1. Changes to the MSI installer for SPM Word Integration Assistant (IBMCúramWordIntegrationAssistant.msi)

• Configurable install location for the Word Integration Assistant.
• Support to allow the user to specify an existing Java Runtime Environment (JRE) that will be used to launch the Word Integration Assistant Java application.
• Added support for per-machine installation.
• Added pre-requisite checking.
• The install layout has been restructured.
• Creation of new environment variables.

 

2. The addition of new installable artifacts:

• A Must Gather batch script that delegates to a set of troubleshooting batch scripts.
• These troubleshooting scripts can be called to examine the client machine configuration to determine if anything in the configuration has changed that could prevent the Word Integration functionality from working.

 

3. Java code changes to add support for Microsoft Edge Chromium.

For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation
 

WorkItem:270272 - File Edit Control Panel says the File Edit Extension is available in browser when it is not

 

Issue Description:

When creating a Microsoft Word Communication in Merative SPM using the Google Chrome browser, the File Edit Control Panel modal always displays a message that the File Edit extension is available in that browser. This message displays even when the extension is not installed for that Chrome profile or is installed but disabled for that profile.

User Interface Impact: No

Steps to Reproduce:

 

1. Launch a Google Chrome browser using a Chrome profile that either does not have the Merative SPM File Edit extension installed or if it is installed, is disabled.
2. Login as a system administrator.
3. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
4. Select the New page action to create a new Microsoft Word template.
5. Enter a name and template document ID for the template and upload a file to be used as the template.
6. Select values from the Category drop-downs and click Save.
7. Click on the edit link for the newly created/configured template.
8. The Word File Edit Screen is loaded in the Tab Content page and the File Edit Control Panel modal displays.
9. Issue: The File Edit Control Panel displays a message that is not expected. A message displays that the File Edit extension is available: 'The File Edit extension is available in the browser and ready to use.' and 'Document editing session starting, please wait.'

 

Instead, it is expected that the File Edit Control Panel displays a message that says the extension is not available.

Resolution:

The issue has now been fixed so that the File Edit Control Panel displays the correct message if the extension is either not installed or not enabled. The message is 'The File Edit extension could not be found. Please contact the administrator to configure the supported File Edit extension in the browser.' When the extension is both installed and enabled, the File Edit Control panel displays the message, 'The File Edit extension is available in the browser and ready to use'.
 

WorkItem:270344 - Commit changes button on the File Edit Control Panel always looks enabled

 

Issue Description:

On the File Edit Control Panel, the Commit changes button always looks enabled. The styling of this button is the same for both enabled and disabled states.

User Interface Impact: No

Prerequisite(s):

 

1. Login as a system administrator.
2. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
3. Select the New page action to create a new Microsoft Word template.
4. Enter a name and template document ID for the template and upload a file to be used as the template.
5. Select a category of Participant and subcategory of Person and click Save.

 

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a new Person.
3. Click the Client Contact tab and select Communications.
4. From the page action menu, select New Microsoft Word.
5. Check the 'Client Is Correspondent' checkbox and click Next.
6. On the second page, complete the following fields:
   • Subject
   • Correspondent Type
   • Address
   • Template Name (the one configured in the prerequisites above)
7. Clicking Save opens the File Edit Control Panel and starts Microsoft Word.
8. Issue: The Commit changes button on the File Edit Control Panel always looked enabled and never disabled.

 

Resolution:

This issue is now resolved. Initially, the Commit changes button looks disabled. Only a save action from Microsoft Word enables the button. Clicking the Commit changes button while it is enabled disables it again. The enabled button has the same look and feel as before. The disabled button is white and has a gray border and text and no hover animation.
 

WorkItem:270345 - Incorrect severity of messages when creating documents using Microsoft Word templates

 

Issue Description:

There are issues with the severity of messages when creating documents using Microsoft Word templates. The File Edit Control Panel displays messages notifying users that changes are being saved. These messages are displaying as warning messages instead of displaying as informational messages.

User Interface Impact: Yes

Steps to Reproduce:

 

1. Open the Microsoft Word (MS) application and create a test document template and save it.
2. Login as a system administrator.
3. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
4. Select the New page action to create a new Microsoft Word template.
5. Enter a name and template document ID for the template and upload the previously saved template.
6. Fill in the mandatory fields and ensure to select All Communication from both Category drop-downs and click Save.
7. Login as a caseworker.
8. Register a new Person.
9. Click on the Client Contact tab and select Communications.
10. From the page action menu, select New Microsoft Word.
11. On the first page of the New Microsoft Word Communication wizard, check the 'Client is Correspondent' checkbox and select Next.
12. Fill in the mandatory fields and select the Microsoft Word template created previously.
13. The MS Word document will be launched in the MS Word application. If asked, allow your browser to interact with this control.
14. Make a change to the document and save it.
15. Issue: The messages that notify the user that the changes are saved are informational messages, yet are being displayed as warnings (we expect a blue icon, yet see a red icon).

 

Resolution:

The messages in the File Edit Control Panel are now displaying with the correct severity.
 

WorkItem:270346 - Issue with Hotspot JRE x64 and the Chrome Word Integration solution

 

Issue Description:

A problem was identified with the Native Messaging Microsoft Word Integration solution in the Google Chrome browser.
The issue was found when using more recent builds of the 64-bit version of the Java 8.0 Hotspot Java Runtime Environment (JRE).

 

• Oracle (Java VM: Java HotSpot(TM) 64-Bit Server VM (25.281-b09 mixed mode windows-amd64 compressed oops))
• OpenJDK (OpenJDK8U-jre_x64_windows_hotspot_8u242b08\jdk8u242-b08-jre) Java Runtime Environment)

 

The issue manifests itself with a fatal error log (hs_err_<processID>.log) appearing in the directory where the Java process was started from.

The log file reports an "EXCEPTION_ACCESS_VIOLATION" with the problematic frame in jacob-1.15-M4-x64.dll.

Prerequisite(s):

(The Word Integration solutions are only supported on Microsoft Windows)

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

 

Steps to Reproduce:

 

1. Login as a system administrator.
2. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
3. Click the edit link for the template that is configured.
4. The Word File Edit Screen is loaded in the Tab Content page, and the File Edit Control Panel modal is shown.
5. Issue: Microsoft Word does not launch with the updated document loaded. The JRE outputs a hs_err_<processID>.log file reporting an "EXCEPTION_ACCESS_VIOLATION".

 

Resolution:

The updated document loads in Microsoft Word. This issue has been resolved by upgrading the version of the JACOB JARs from 1.15-M4 to 1.20.

 

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

 

Issue Description:

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

User Interface Impact: No

Prerequisite(s):

 

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

 

Steps to Reproduce:

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

 

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

 

Resolution:

 

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

 

Common Intake

 

PO08974, WorkItem:265385 - Application Case search results switch between presenting French and English

 

Issue Description:

When searching for an Application Case the Type and Programs columns will alternate the results between multiple languages if there is a language pack installed that is different from the language of the default server locale.

User Interface Impact: No

Prerequisite(s):

 

1. The French language pack is installed.
2. The default server locale is en_US and the Intake Worker's locale is English.

 

Steps to Reproduce:

 

1. Login as an Intake Worker.
2. Select Application under Searches in the shortcuts panel.
3. Enter a set of search criteria that will return multiple results.
4. Click Search.
5. Issue: The values in the Type and Programs columns of the results are displayed in different languages. The same thing happens if the Intake Worker's locale is French.

 

Resolution:

The application case search wasn't considering the user's locale when returning the results. The Type and Programs columns are now either displayed in accordance with the user's locale, or the default server locale if no localizable text entries are present for the program types.

 

 

Curam Modules

 

Outcome Management
Social Enterprise Collaboration
Provider Management
Verification
Universal Access
Intelligent Evidence Gathering
Evidence Broker
Financial Management

 

Outcome Management

 

WorkItem:114547 - Administration property 'curam.outcomeplanning.referralForAgreementDays' is not working as expected

 

Issue Description:

The property 'curam.outcomeplanning.referralForAgreementDays' defines the number of days before the current date that a Referral should be displayed for selection when creating an Agreement. For example, if the configuration specifies 60 days then only referrals that have been created in the last 60 days are to be available for selection in a new agreement.
Currently, referrals that are created on a date that falls before the acceptable time period derived using the value of the application property and the current date are being displayed.

User Interface Impact: No

Prerequisite(s):

 

1. Login in as sysadmin.
2. Click on System Configurations and expand the shortcuts panel.
3. Expand the Application Data section and click on Property Administration.
4. Search for and check the value of the property 'curam.outcomeplanning.referralForAgreementDays' is set to 60 days.
5. Click on the Publish page action to publish any changes.

 

Steps to Reproduce:

 

1. Login in as a caseworker.
2. Register a new Person.
3. Create an Ongoing Case for the person.
4. Create a new Outcome Plan for the person.
5. Select the Activities tab and then select New Referral from the page menu.
6. Create a new Referral with a referral date 3 months before the current date.
7. Select the Agreements tab and create a new Agreement.
8. Populate the Clients page of the Agreement wizard. Click Next.
9. Issue: On the Activities page of the Agreement wizard the newly created Referral is displayed in the list even though the Referral date is 3 months before the current date.

 

Resolution:

The Agreement wizard has been corrected to only display Referrals that have a start date within the window of the property 'curam.outcomeplanning.referralForAgreementDays'.

 

WorkItem:185547 - The Flex Widget for Enhanced Client Selection is replaced with modern JavaScript

 

Issue Description:

The Social Program Management (SPM) product no longer has any dependency on Adobe Flash. The Flash-dependent widget for Enhanced Client Selection, which is used to select multiple clients when creating an Outcome Plan, is replaced with a responsive version based on modern React JavaScript components. The previous functionality of the Enhanced Client Selection is maintained.

User Interface Impact: Yes

Steps to Reproduce:

 

1. Login as a caseworker.
2. Select Preferences from the application menu.
3. Set Enhanced Outcome Plan Creation to Yes.
4. Register a new Person.
5. Create an instance of an integrated case that has been configured for outcome plans.
6. Click on the Outcome Plans tab.
7. Use the New page action to create a new outcome plan.

 

Resolution:

The Flash-dependent widget for Enhanced Client Selection is now replaced with a responsive version based on modern React JavaScript. Removing client information for a family member was enhanced to improve the user experience for the user and to make the Enhanced Client Selection Widget accessible. The right-click Remove action to remove a family member is now replaced by a Remove tertiary button for each family member. Selecting the Remove tertiary button removes the family member from the client list.

The drag and drop interaction to manage the clients for an outcome plan was also enhanced to provide an accessible and enhanced user experience. When a user drags the CCV Client, family component or a family member to the list of clients that make up the outcome plan, the allowable drop area is highlighted. An inline error message is displayed if a user drops on a disallowed area. In addition, a new option Add To Client List was added to the overflow action (…) for the CCV Client, family component and each family member. Select the overflow action (...) to display a hidden overflow menu and then select the Add to Client List option.
 

WorkItem:185554 - The Flex Chart for Assessment Delivery Results is replaced with modern JavaScript

 

Issue Description:

The Social Program Management (SPM) product no longer has any dependency on Adobe Flash. The Flash-dependent chart for the Assessment Delivery Results, which provides a view of assessment results on the Assessment Home and History pages, is replaced with a responsive version based on modern React JavaScript components. The previous functionality of the Assessment Delivery Results Chart is maintained.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a new Person.
3. Create an instance of an integrated case that has been configured for outcome plans.
4. Click on the Outcome Plans tab.
5. Use the New page action to create a new outcome plan.
6. On the Outcome Plan, click on the Assessment & Factors tab.
7. Use the New page action to create a new assessment.
8. From the Assessment list page, click on the Assessment Type hyperlink to view the Assessment Delivery Results Bar and Radar charts.

 

Resolution:

The Flash-dependent chart for the Assessment Delivery Results is now replaced with a responsive version based on modern React JavaScript. A new color scheme from the Merative Carbon Design System was also introduced for the Assessment Delivery Results Chart, which provides an accessible and enhanced user experience. The colors are applied in a specific sequence to maximize the contrast between neighboring colors. The default colors, which are defined by the 'curam.assessmentplanning.graphRGBColors' application property are updated as follows: 6929C4,1192E8,005D5D,9F1853,FA4D56,520408,198038. These values can be modified in the System Administration Application using the following steps: 

 

1. Login as a system administrator.
2. Click on the System Configurations tab.
3. Select Property Administration under Application Data in the shortcuts panel.
4. Enter 'curam.assessmentplanning.graphRGBColors' in the Name field and click Search.
5. Edit the values using the row-level action.

 

WorkItem:185555 - The Flex Chart for Assessment Delivery Details is replaced with modern JavaScript

 

Issue Description:

The Social Program Management (SPM) product no longer has any dependency on Adobe Flash. The Flash-dependent chart for Assessment Delivery Details, which provides a view of assessment results when the Assessment list item is expanded from the Assessment & Factors tab of the Outcome Plan, is replaced with a responsive version based on modern React JavaScript components. The previous functionality of the Assessment Delivery Details Chart is maintained.

User Interface Impact: Yes

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a new Person.
3. Create an instance of an integrated case that has been configured for outcome plans.
4. Click the Outcome Plans tab.
5. Use the New page action to create a new outcome plan.
6. On the Outcome Plan, click the Assessment & Factors tab.
7. Use the New page action to create a new assessment.
8. From the Assessment list page, click the toggle of the newly created assessment to view the Assessment Delivery Details Bar and Radar charts.

 

Resolution:

The Flash-dependent chart for Assessment Delivery Details is now replaced with a responsive version based on modern React JavaScript. To improve the user experience and to make the Assessment Delivery Details Chart accessible, an enlarge button for maximizing and minimizing the Chart is available. Labels are truncated to better maintain the scale and readability of the Chart. Users can click the enlarge button to see a larger view and to read truncated labels.

A new color scheme from the Merative Carbon Design System was also introduced for the Assessment Delivery Details Chart, which provides an accessible and enhanced user experience. The colors are applied in a specific sequence to maximize the contrast between neighboring colors. The default colors, which are defined by the curam.assessmentplanning.graphRGBColors application property are updated as follows: 6929C4,1192E8,005D5D,9F1853,FA4D56,520408,198038. These values can be modified in the System Administration Application using the following steps: 

 

1. Login as a system administrator.
2. Click the System Configurations tab.
3. Select Property Administration under Application Data in the shortcuts panel.
4. Enter 'curam.assessmentplanning.graphRGBColors' in the Name field and click Search.
5. Edit the values using the row-level action.

 

PO07949 , WorkItem:238435 - Unable to complete a review on an outcome plan with an expected end date in the past

 

Issue Description:

It is not possible to complete an outcome plan review when the outcome plan's expected end date is in the past. An un-handled server exception is thrown after attempting to complete the outcome plan review.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a new Person.
3. Use the New Case tab action to create a new Ongoing Case for the person.
4. Click on the Outcome Plans tab and use the New page action to create a new outcome plan.
5. Specify the mandatory fields ensuring to set the Expected End Date to any future date.
6. Select the client and click Save.
7. Click on the Reviews tab of the outcome plan.
8. Use the New page action to create a new review, ensuring to set the Review Period From and Review Period To to the current date.
9. Change the server date to a date after the expected end date of the outcome plan.
10. Navigate to the outcome plan review and complete it.
11. Issue: An un-handled server exception is thrown with the message: An un-handled server exception occurred. Please contact the administrator. In the logs files, the error message is curam.util.exception.InformationalException: The Expected End Date must be on or after today.

 

Resolution:

This issue is now resolved and now an outcome plan's review can be completed when the outcome plan's expected end date is in the past.
 

WorkItem:246932 - The Flex Widget for Factor Activities is replaced with modern JavaScript

 

Issue Description:

The Social Program Management (SPM) product no longer has any dependency on Adobe Flash. The Flash-dependent widget for Factor Activities, which is used on the Activities section of the Factor home page, is replaced with a responsive version based on modern React JavaScript components. The previous functionality of the Factor Activities widget is maintained.

User Interface Impact: Yes

Steps to Reproduce:

 

1. Login as a caseworker
2. Register a new Person.
3. Create an instance of an integrated case that has been configured for outcome plans.
4. Click the Outcome Plans tab.
5. Use the New page action to create a new outcome plan.
6. On the Outcome Plan, click on the Assessment & Factors tab.
7. Use the New page action to create a new assessment.
8. Click the Activities tab and select Activities from the page group navigation bar.
9. From the page action menu choose New Action.
10. Complete the mandatory fields and capture the factor details for the new action.
11. Click the Assessment & Factors tab and select Factors from the page group navigation bar.
12. Click the factor hyperlink for the Factor associated with the previously created action.
13. The Factor Activities widget is available on the Activities section of the Factor home page.

 

Resolution:

The Flash-dependent widget for Factor Activities is now replaced with a responsive version based on modern React JavaScript. To improve the user experience, a Today button, which brings the user back to the current date, was added to the Factor Activities widget.
 

WorkItem:252249 - The Flex Chart for Factor Ratings is replaced with modern JavaScript

 

Issue Description:

The Social Program Management (SPM) product no longer has any dependency on Adobe Flash. The Flash-dependent chart for Factor Ratings, which is available on the Ratings section of a Factor home page, is replaced with a responsive version based on modern React JavaScript components. The previous functionality of the Factor Ratings Chart is maintained.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a new Person.
3. Create an instance of an integrated case that has been configured for outcome plans.
4. Click on the Outcome Plans tab.
5. Use the New page action to create a new outcome plan.
6. On the Outcome Plan, click on the Assessment & Factors tab.
7. Use the New page action to create a new assessment.
8. Select Factors from the page group navigation bar.
9. Click on the factor hyperlink for any Factor in the list to open the Factor home page.
10. The Factor Ratings Chart is available on the Ratings section of the Factor home page.

 

Resolution:

The Flash-dependent chart for Factor Ratings is now replaced with a responsive version based on modern React JavaScript. A new color scheme from the Merative Carbon Design System was also introduced for the Factor Ratings chart, which provides an accessible and enhanced user experience. The default color, which is defined by the 'curam.outcomeplanning.factorGraphRGBColor' application property is updated to B28600. This value can be modified in the System Administration Application using the following steps: 

 

1. Login as a system administrator.
2. Click on the System Configurations tab.
3. Select Property Administration under Application Data in the shortcuts panel.
4. Enter 'curam.outcomeplanning.factorGraphRGBColor' in the Name field and click Search.
5. Edit the values using the row-level action.

 

 

Social Enterprise Collaboration

 

Case & Participant Index
Social Enterprise Folder

CASE & PARTICIPANT INDEX

 

WorkItem:265430 - Deprecate the Case Participant Index (CPI) and Client Access Features

 

Case & Participant Index (CPI) and Client Access functionalities that are provided as part of the Social Enterprise Collaboration Module to enable Master Data Management (MDM) capabilities and the display of information from an external system within Merative Social Program Managemenrt are deprecated.

 

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

 

SOCIAL ENTERPRISE FOLDER

 

WorkItem:185549 - The Flex Widget for Create Social Enterprise Folder is replaced with modern JavaScript

 

Issue Description:

The Social Program Management (SPM) product no longer has any dependency on Adobe Flash. The Flash-dependent widget for the Create Social Enterprise Folder (SEF), which is used to select multiple clients and cases, is replaced with a responsive version based on modern React JavaScript components. The previous functionality of the Create Social Enterprise Folder is maintained.

User Interface Impact: Yes

Steps to Reproduce:

 

1. Login as a caseworker.
2. Select Preferences from the application menu.
3. Set Enhanced mode to yes.
4. Click on New Social Enterprise Folder under Social Enterprise Folders in the shortcuts panel to navigate to the Social Enterprise Folder.

 

Resolution:

The Flash-dependent widget for the Social Enterprise Folder is now replaced with a responsive version based on modern React JavaScript. Removing cases and client information for a family member was enhanced to improve the user experience for the user and to make the Create Social Enterprise Folder Widget accessible. The right-click Remove action to remove a case or a family member is now replaced by a Remove tertiary button for each case and family member. Selecting the Remove tertiary button removes case or the family member from the appropriate list.

The drag and drop interactions to manage the clients and cases for a SEF were also enhanced to provide an accessible and enhanced user experience. When the user drags cases within the care and protection component to the list of cases, or the CCV Client, family component or a family member to the list of clients that make up a SEF, the allowable drop areas are highlighted. An inline error message is displayed if a user drops on a disallowed area. In addition, a new option Add to Case List was added to the overflow action (…) for each case and the option Add To Client List was added to the overflow action (…) for the CCV Client family component, and each family member. Select the overflow action (...) to display a hidden overflow menu and then select the Add to Case List or Add to Client List option.
 

WorkItem:260868 - Reinstate Social Enterprise Folder case from a deprecated state in the Social Program Management application

 

Issue Description:

The Social Enterprise Folder (SEF) case type that is provided as part of the Social Enterprise Collaboration (SEC) module to enable Multidisciplinary Teams (MDTs) to collaborate on cases and clients is to be reintroduced into the product.
For more information see the deprecation task 'WorkItem:159365 - Deprecate the Social enterprise folder (SEF) case in the V7.0 external release notes.

User Interface Impact: N/A

Steps to Reproduce:

Steps to Access the Reinstated Functionality

1. Login as a caseworker.
2. Select Cases and Outcomes. Select Shortcuts and select Social Enterprise Folders from the Shortcuts panel.
3. Create a new social enterprise folder.
4. Search for and select a person who is currently registered on the system.
5. Enter the Type of social enterprise folder from the drop-down menu, Fraud Investigation, for example, and click Create.
6. The following tabs display when the social enterprise folder is created" Home, Clients, Cases MDT, Incidents, Calendar, Discussions, Notes, Assessments, and Admin.

 

Resolution:

The Social Enterprise Folder (SEF) case type is now reintroduced into the product. The following list contains the features being un-deprecated:

 

1. Related administration properties
2. Shortcuts panel options/links
3. Home page
4. Clients
5. Cases
6. Multidisciplinary Team
7. Incidents
8. Calendars and meeting minutes
9. Discussions
10. Notes
11. Attachments
12. Communications
13. Other SEF-related administration tasks

 

Provider Management

 

Financials
Place Management

 

PO07109, WorkItem:194820 - Microsoft Word Integration is impacting the creation of a provider home study document

 

Issue Description:

Users can create a document for a home study that can be used to capture information such as the prior social history of the provider. Currently, after creating a home study document, users are unable to edit the document as the SPM Microsoft (MS) Word Integration document editing session is not launching.

User Interface Impact: No

Prerequisite(s):

 

1. Login as a system administrator.
2. Navigate to Microsoft Word Templates under Communications in the shortcuts panel.
3. Select the New page action to create a new Microsoft Word template.
4. Enter a name and template document ID for the template and upload a file to be used as the template.
5. Select a category and sub-category of Home Study and click Save.

 

Steps to Reproduce:

 

1. Login as a Provider Management Resource Manager.
2. Open an existing provider and select the Home Studies page from the Credentials tab in the navigation bar.
3. Use the New page action to create a new home study.
4. Select the New Document row-level action on the newly created home study.
5. Fill out the mandatory Description and Template fields on the New Document modal
   • Select the template that was configured in the prerequisite(s) section above.
6. Click Save.
7. Expand the list row for the Home Study and select the Documents in-page navigation tab.
8. From the row-level action of the newly created document, select Edit and then click on 'Save and Open Word' from the modal that opens.
9. Issue: The Microsoft Word editing session does not launch.

 

Resolution

Users are now able to create and save a Provider Home Study document as the SPM Microsoft Word Integration document editing session launches as expected.

Technical:

Below is the list of files changed to fix this issue:

 

• SPM-EntMods/EJBServer/components/CPM/data/initial/SECURITYGROUPSID.dmx
• SPM-EntMods/EJBServer/components/CPM/model/Packages/Facade/Home Study/Home Study Document/HomeStudyDocument_cat.efx
• SPM-EntMods/EJBServer/components/CPM/source/curam/cpm/facade/impl/HomeStudyDocument.java
• SPM-EntMods/EJBServer/components/CPM/source/curam/homestudy/impl/HomeStudyDocument.java
• SPM-EntMods/EJBServer/components/CPM/source/curam/homestudy/impl/HomeStudyDocumentImpl.java
• SPM-EntMods/webclient/components/CPM/HomeStudy/HomeStudyDocument/HomeStudy_controlMSWord.uim
• SPM-EntMods/webclient/components/CPM/HomeStudy/HomeStudyDocument/HomeStudy_listHomeStudyDocumentView.vim
• SPM-EntMods/webclient/components/CPM/HomeStudy/HomeStudyDocument/HomeStudy_modifyHomeStudyDocument.uim
• SPM-EntMods/webclient/components/CPM/HomeStudy/HomeStudyDocument/HomeStudy_resolveControlMSWord.uim (New)
• SPM-EntMods/webclient/components/CPM/HomeStudy/HomeStudyDocument/jscript/SetJSSessionForWordEdit.js (New)
• TI/client/CoreInf/CuramCDEJ/lib/curam/web/jsp/FEBase-head.jsp
• TI/client/components/client-inf/jscript/src/internal/curam/util.js
• TI/client/components/word-file-edit/src/main/java/curam/util/tools/fileedit/applet/FileEditApplet.java

 

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

 

PO08242, WorkItem:246406 - The uniqueID of the email address that is associated with a Provider Service Center is generated using the DEFAULT key set instead of the EMAILADDSS key set

 

Issue Description:

The uniqueID of the email address that is associated with a Provider Service Center is generated with the wrong key set. The DEFAULT key set is used to generate the uniqueID instead of the EMAILADDSS key set.

User Interface Impact: No

Prerequisite(s):

 

1. Run the following SQL:
   • UPDATE KEYSERVER SET HUMANREADABLE = '1' WHERE KEYSETCODE = 'EMAILADDSS';
2. Restart the server.

 

Steps to Reproduce:

 

1. Login as an administrator.
2. Select New User below Users in the shortcuts panel.
3. Fill in all the mandatory details, as well as an email address.
4. Click Save.
5. Check the new email address on the Database. Its primary key is human-readable and was created by using the EMAILADDSS key set.
6. Login as a Provider Management manager.
7. Click My Providers below Providers in the shortcuts panel.
8. Click the reference hyperlink for any providers in the list to open the provider home page.
9. From the provider home page, click on the Services tab and select Service Centers.
10. Use the New page action to create a new Service Center.
11. Fill in all the mandatory details, as well as an email address.
12. Click Save.
13. Issue: Check the new email address on the Database. Its primary key is non-human-readable as is generated by using the DEFAULT key set.

 

Resolution:

This issue is now resolved. The uniqueID that is associated with a Provider Service Center email address is now generated by using the EMAILADDSS key set. Any potential collisions between new identifiers that are generated from the EMAILADDSS key set and pre-existing identifiers that are generated from the DEFAULT key set are automatically detected and avoided.
 

PO08385, WorkItem:249637 - Unnecessary notifications are being generated on the creation of placements

 

Issue Description:

When a placement is created, a product delivery case of type Provider Placement is created that is used to generate placement-based financials. Various notifications are created for product delivery cases, including notifications when the product delivery case is first created that notify users of their case assignment. Because the product delivery case is not intended to be interacted with by a caseworker, notifications are unnecessary and should not be created.

User Interface Impact: No

Steps to Reproduce:

 

1. Log on as a Child Welfare caseworker.
2. Register a child and create an Ongoing Case.
3. From the Ongoing Case home page, click the Removals and Placements tab.
4. In the page action menu, click New Removal.
5. Enter the mandatory information, and then click Save and Place.
6. Provide the following details for the Placement, then select the Provider and click Finish.
   • Select Foster Care for the type of placement.
   • Select a Category/Type of Foster Care Home when you search for the provider.
7. Click the Inbox tab, and click My Notifications under Notifications in the Shortcuts panel.
8. Issue 1: Two unnecessary notifications are created for the placement.
9. Log on as a Provider Management Resource Manager.
10. Click the Inbox tab and then click My Notifications under Notifications in the Shortcuts panel.
11. Issue 2: Up to four unnecessary notifications are created for the placement.

 

Resolution:

This issue has been resolved. Notifications are no longer generated for the 'Provider Placement' product delivery case that is created solely for the purpose of generating financials. Also, notifications are no longer created for the product delivery cases that are used to generate the other three types of provider payments: Provider Invoice, Provider Attendance, and Provider Contract. For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

Technical:

A new interface, NotificationExcludedCaseType, has been added that facilitates the listing of case types and product deliveries to be excluded when notifications are generated. The implementation that was provided in Provider Management filters the following product deliveries: Provider Placement, Provider Invoice, Provider Attendance, and Provider Contract.
 

PO08943, WorkItem:264651 - Updating the cover period of a Service Delivery does not update the cover period of the associated Service Authorization Line Item

 

Issue Description:

When a Service Delivery delivers a service whose associated delivery type is Product Delivery, modification of the Service Delivery cover period should propagate and keep in sync the cover period on the associated Service Authorization Line Item (SALI). Currently, this is not happening. The SALI cover period is not updated and its cover period gets out of sync with the Service Delivery cover period.

User Interface Impact: No

Prerequisite(s):

 

1. Login as an administrator.
2. Click on Services under Provider Management in the shortcuts panel.
3. Use the New Service page action to create a new service.
4. Specify the following details on the New Service modal page:
   • Name: Test Service
   • Reference: TestService
   • Unit of Measure: Dose
   • Start Date: Today
   • Referred By: Any User
   • Fixed Amount: 20
   • Fixed Amount Payment Option: Pay Fixed Amount
   • Delivery Type: Product Delivery
   • Owner To Be Specified: Any User
   • Authorized Rate: True
   • Provider/Provider Type Selection: Provider Mandatory
   • Product: Provider Attendance
5. Click Save.
6. Click on Product Delivery Cases under Case in the shortcuts panel.
7. Click on the Provider Attendance name hyperlink.
8. On the product home page, click on the Financial tab and select Delivery Patterns.
9. Use the New page action to add a new delivery pattern.
10. Specify the following details on the New Delivery Pattern modal:
    • Delivery Method: Cash
    • Delivery Frequency: Daily
    • Cover Pattern: Issue in advance
11. Click Save.
12. Click on Integrated Cases under Case in the shortcuts panel.
13. Use the New page action to add a new integrated case.
14. Specify the following details on the New Integrated Case Type modal:
    • Integrated Case Type: Service Delivery Test
15. Click Save.

 

Steps to Reproduce:

 

1. Login as a caseworker.
2. Register a new Person.
3. Click on the Care and Protection tab and select Cases.
4. Use the New page action to create a Service Delivery Test integrated case.
5. On the integrated case home page, click on the Services tab.
6. Use the New page action to add a service using the New Service wizard.
7. On the first page of the wizard, search for and select the newly configured service.
8. On the second page of the wizard, specify the following details:
   • Owned By Me: True
   • Authorized amount: 10
   • Sensitivity: 1
   • Reason: Test Reason
9. Click Next.
10. On the last page of the wizard, specify the following dates:
    • Start Date: Today
    • End Date: One week from today
11. Click Finish.
12. Login to the database and check the following:
    • The cover period on the Service Delivery and associated SALI are in sync.
    • The associated product delivery start and expected end dates are also in sync with the Service Delivery cover period.
13. From the Services list page, open the newly created service by clicking on the Service hyperlink.
    • The cover period start and end dates should be visible in the context panel.
14. Select Edit from the tab action menu.
15. On the Edit Service modal, update the From date to be tomorrow.
16. Click Save.
17. Issue: A check on the database will reveal that the SALI cover period start date has not been updated and is now out of sync with the Service Delivery cover period. The product delivery case start date is updated.

 

Resolution:

This issue is now resolved. When the Service Delivery cover period is updated, the associated SALI cover period is also updated so that the cover periods are kept in sync.
 

PO09081, WorkItem:267422 - Page becomes unresponsive when adding a third compartment to a provider facility

 

Issue Description:

The Manage Provider Facility page becomes unresponsive after adding a third child compartment to the top-level compartment.

User Interface Impact: No

Steps to Reproduce:

 

1. Login as a Provider Management Resource Manager.
2. Navigate to a provider and from the provider home page, select the Manage Facility action menu item.
3. From the Compartment Details page, select the New Compartment menu item.
4. Insert a name and save the compartment.
5. Add a second compartment with a unique name.
6. Add a third compartment with a unique name.
7. Issue: The page becomes unresponsive.

 

Resolution:

The Manage Provider Facility page behaves as expected after adding three or more child compartments to the top-level compartment.

Technical:

The data from the CompartmentLoader and FacilityLoader classes was not ordered when it was returned to the client. The page uses the curam.widget.FramesetWidget Dojo widget. The widget became unresponsive because when a new child compartment node is added to the root node, a dijit.tree.ForestStoreModel._requeryTop() function is called which triggers the curam.util.orgTreeStore.fetch() function to retrieve the child compartment data from the server. As the data was returned in a different order for each call, this lead to the ForestStoreModel._requeryTop() function being re-triggered and this flow repeated. This caused the page to become unresponsive after three or more child compartments were added to the root compartment. The data is now sorted before it is returned to the client.

The following files were updated as part of addressing this issue:

• SPM-EntMods/EJBServer/components/CPM/source/curam/place/impl/CompartmentLoader.java
• SPM-EntMods/EJBServer/components/CPM/source/curam/place/impl/FacilityLoader.java
• SPM-EntMods/EJBServer/components/CPM/source/curam/place/impl/LoaderUtility.java

 

WorkItem:268582 - External user who is member of only Provider 1 can access few details for Provider 2 by intercepting the request and modifying the ConcenrRleID

 

Issue Description:

In the Provider Management self-service application, an external user who is a member of a provider should have access only to details related to the provider of which they are a member. However, if this same external user knows the concern role identifier of another provider, they can access some information and functions of another provider by supplying that provider's concern role identifier in the URLs of some of the pages contained within the self-service external application. This should not be permitted.

User Interface Impact: No

Steps to Reproduce:

 

1. Log in as a caseworker.
2. Register two people.
3. Log in as an administrator.
4. Click on New External User under Users in the shortcuts panel.
5. For person 1 from above, enter the required details. In the Application field select ExternalProviderCustomHome as the application homepage, in the Role field select ExternalUserSecureRole, and enable the account.
6. Select the 'Link a Participant' action from the tab actions menu. In the External User Relationship field select 'Is associated with'. Search for Person 1 and save.
7. Repeat steps 4 - 6 for person 2.
8. Log in to application as a Provider Management Resource Manager.
9. Enroll and approve two providers.
10. Navigate to the Provider Members page under the Relationships tab and add Person 1 from above as a provider member to Provider 1. In the Role field select Employee.
11. Add Person 2 from above as a provider member to Provider 2.
12. Log in to CPM External Application as the newly created External User 1 from Step 4. URL: https://<server_name>:<port_number>/CPMExternalS
13. Navigate to Service Enquiries under My Details.
14. Right-click somewhere on the page (below the heading) and select View Frame Info
15. Observe the URL under Address and write down the concernRoleID number from concernRoleID URL parameter. This should be concernRoleID of Provider 1.
16. Log in to the CPM External Application as the newly created External User 2 from Step 4.
17. Navigate to Service Enquiries under My Details.
18. Right-click somewhere on the page (below the heading) and select View Frame Info.
19. Copy the URL listed under Address into a new browser window but substitute concernRoleID number with the concernRoleID from Provider 1.
20. Issue: The page is accessible, while it should give a user permissions error. This is also true for the following pages: Transactions (under Financials), Rosters, Reservations (under Facility), Wait Lists (under Facility).

 

Resolution:

External users can now view only the details for providers for which they are a provider member.

Technical:

This issue occurred due to the lack of a user permissions check in some of the facades that are used to service these pages in the Provider Management self-service application.
This issue has been resolved by adding a permissions check to the following facades:

 

• MaintainExternalServiceEnquiry.listWebServiceEnquiries
• ExternalProvider.readProviderSummaryDetails.

 

A new facade, ExternalProviderFinancial.listFinancialTransactions, has been added which contains the permissions check and this is now called from the following pages:

 

• PME_listProviderPaymentTransactions
• PME_listProviderGroupPaymentTransactions pages

 

Note that the page Requests (under My Details), and the actions New Service Invoice Request, Request Member Login Credentials, and Change Password do not show the error message. This is correct behavior as the data is always displayed for the logged-in user due to these facades not requiring a concernRoleID as a parameter and are thus not affected by this issue. As a result, if Provider 1 is logged into the CPM self-service application, but an attempt is made to pass in the concernRoleID of Provider 2 for these specific pages and actions, the data specific to Provider 1 is still displayed.
 

FINANCIALS

 

PO08955, WorkItem:264654 - Active deduction taken from payee in error but not from provider's next payment

Issue Description:

When a deduction of type Provider Invoice is created for a provider and a service invoice payment is generated for the provider where the payee for the service invoice line item is a different provider, a deduction is incorrectly being applied to the payment for the provider indicated as the payee.

User Interface Impact: No

Prerequisite(s):



Configure a new service and associate a legal action with the Ongoing Case

 

• Login as an administrator and click on Services under Provider Management in the shortcuts panel.
• Use the New Service page action to create a service with the following details:
  • Name: Test Service1
  • Reference: TestService1
  • Start Date: Today
  • Unit of Measure: Session
  • Minimum Amount: 0
  • Maximum Amount: 100
  • Maximum Amount Payment Option: Pay Maximum Amount
  • Minimum Amount Payment Option: Don't Pay
  • Fixed Amount Payment Option: Don't Pay
  • Delivery Type: Service Delivery
  • Owner to be Specified: Any User
  • Nominee to be specified: checked
  • Specify number of units: checked
  • Complete manually: checked
• Click on Legal Actions under Cases in the shortcuts panel.
• Select the Legal Status tab.
• Use the Add page action to add the Adjudicated legal status.
• Select the Configure Case Type in-page navigation tab.
• Use the Add Legal Status row-level action to add the Adjudicated legal status to the Ongoing Case.

 

Configure Deduction data

 

• Click on Deductions under Case in the shortcuts panel.
• If it doesn't already exist, use the New page action to create a new Liability Repayment deduction with details:
  • Name: Liability Repayment
  • Category: Applied Deduction
  • Default Percentage: 10
  • Action Type: Deduct Remaining
• Click on Product Delivery Cases under Cases in the shortcuts panel.
• Edit the Provider Placement product with the following details:
  • Use Rolled Up Reassessments: Uncheck this
  • Overpayment Case Processing: Create and Activate Payment Correction Case
• Again, click on Product Delivery Cases under Cases in the shortcuts panel.
• Edit the Provider Invoice product with the following details:
  • Use Rolled Up Reassessments: Uncheck this
  • Overpayment Case Processing: Create and Activate Payment Correction Case
• Click on the Financial tab of the Provider Invoice product and select Deductions.
• Use the Add Existing page action to add the Liability Repayment deduction.

 

Register providers

 

• Login as a Provider Management Resource Manager.
• Enroll a new Provider with the following details:
  • Provider Name: Provider1
  • Payment method: Check
  • Frequency: Every 1 Day
  • Provider Category: Foster Care Home
  • Provider Type: Traditional Foster Care Home
  • Physical Capacity: 4
  • Designated Capacity: 4
• Approve Provider1.
• Repeat the previous two steps for a second Provider, Provider2.
• Add services Traditional Foster Care and Test Service1 for Provider1, with a start date as Provider Enrollment Date.
• Repeat the previous step for Provider2.

 

Steps to Reproduce:

Create placement with a provider and issue financials

 

• Login as a Child Welfare caseworker.
• Register a new child and create an Ongoing Case.
• Click on the Legal tab and select Legal Status.
• Use the New page action to add a Legal Status of Adjudicated, with the start date in the past.
• From the Removals and Placements tab, select New Removal.
• Add a new removal with a start date of today and a placement with Provider1.

 

Run the financials

 

• Login as a system administrator.
• Click on Processes under Batch in the shortcuts panel.
• Search for and execute the following batch processes, specifying a 'processingDate' the first day of the following month:
  • GenerateInstructionLineItems
  • GenerateInstruments
• Run the batch jobs.

 

Verify placement payments for the provider

 

• Login as a Provider Management Resource Manager.
• Click on My Providers under Providers in the shortcuts panel.
• Locate Provider1 in the list and click on the reference hyperlink.
• Click on the Financial tab and confirm that financials have been generated.

 

Delete placement and ensure overpayment is created

 

• Login as a Child Welfare caseworker and delete the Provider1 placement created earlier.
• Click on Child Welfare Search under Search in the shortcuts panel.
• In the Primary Client field, enter Provider1 and click Search.
• Click on the liability case reference hyperlink in the search results.
• From the case home page context panel, observe that the case is a Payment Correction Overpayment.

 

Create an Outcome Plan

 

• Create an Outcome Plan from the Ongoing Case created in step 1, with details:
  • Type: Child Welfare Outcome Plan
  • Name: Test Plan1
  • Select the child client
• From the Outcome Plan home page, click on the Activities tab and use the New Service page action to create a service with details:
  • Service Name: Test Service1.
  • Units (Session): 10
  • Owned By Me: Check this box
  • Reason: <Some reason text>
  • Start date: Today
• When the service is created, open it by clicking on the hyperlink.
• Submit it for approval by using the Submit tab action.

 

Set up the provider deduction

 

• Login as a Provider Management Resource Manager and add a new applied deduction for Provider1 with details:
  • Payment Type: Provider Invoice
  • Select the newly created liability case
  • Start Date: Today
  • Percentage: 20
• Use the Activate row-level action to activate the deduction.

 

Add a new Service Invoice

 

• Login as a financial user and select New Service Invoice under Invoices in the shortcuts panel.
• Create a new service invoice with the following details:
  • External Reference: <Unique reference number>
  • Originator Name: Provider1
  • Originator Reference: Provider1's reference number
  • Receipt Date: Today
• Click on the Invoice Line Items tab and select Open Line Items.
• Use the New page action to create a new line item with the following details:
  • External Reference: Same unique reference number as used above
  • Service: Test Service1
  • Case Reference: <Reference number of the Outcome Plan>
  • From: Today
  • To: Today
  • Number of Units: 10
  • Unit Amount: $10
  • Amount Invoiced: $100
  • Set the Payee Details Reference to Provider2's reference number.
  • Set the Payee Details Name to Provider2.
  • Set the Provider Details Reference to Provider1's reference number.
  • Set the Provider Details Name to Provider1.
  • Set the Client Details Name to the name of the child.
  • Date of Birth: The date of birth of the child.
  • First Name: The first name of the child
  • Last Name: The last name of the child.
• Submit the line item for approval and approve it from the Pending Line Items tab.
• Run the financial batch jobs, with the processing date set to the first day of the following month.

 

Check the financials

 

• Login as a Provider Management Resource Manager.
• Issue: Observe from the Transactions tab that the Applied Deduction was created incorrectly for Provider2.

 

Resolution:

The deduction is no longer applied against the payment to the provider for which there has been no deduction created, and instead will be applied against the next payment generated for the correct provider.
 

PLACE MANAGEMENT

 

PO09105, WorkItem:266868 - Incorrect number of SALIs generated for certain dates when using the service delivery frequency 'Every 1 month(s) from start date'

 

Issue Description:

When a service delivery is created and submitted for approval, service authorization line items (SALIs) are generated to authorize the service delivery for payment. An incorrect number of SALIs are generated when the delivery frequency 'Monthly Every 1 month(s) from start date' is used for the service delivery and the start date of the service delivery is the 31st of March, May, July, October or December.

Also, the SALI cover period is incorrect. The from and to dates are always on the same date and don't reflect the period the SALI is covering.

User Interface Impact: No

Prerequisite(s):

1. Login as an administrator.
2. Select Services under Provider Management in the shortcuts panel.
3. Click on the New Service page action to create a new service.
4. Enter the following details in the New Service modal:
   • Name = Monthly Payment
   • Unit of Measure = Place
   • Fixed Amount = 50
   • Delivery Type = Service Delivery
   • Delivery Frequency = Monthly Every 1 month(s) from start date
   • For all other fields, accept the default values
5. Click Save.
6. Select Integrated Cases under Cases in the shortcuts panel.
7. Use the New page action to configure a new integrated case.

 

Steps to Reproduce:

 

1. Login as a Provider Management Resource Manager.
2. Select My Providers under Providers in the shortcuts panel.
3. Select any provider from the list.
4. From the provider home page, click on the Services tab.
5. Use the New page action to add an instance of the newly configured Monthly Payment service.
6. Login as a caseworker.
7. Register a new Person.
8. Click on the Care and Protection tab and select Cases.
9. Use the New page action to create an instance of the newly configured integrated case.
10. Click on the Services tab of the integrated case.
11. On the New Service modal, search for and select the service configured above and click Next.
12. On the second page of the wizard provide a reason and click Next.
13. On the last page of the wizard set the dates as follows:
    • Start date to the nearest problematic date after the configured service start date. For example, if the configured service start date was 1st July, set the start date to 31st July.
    • End date to 7 weeks after the start date.
14. Click Finish.
15. Click on the hyperlink of the newly created service.
16. Click on the Providers tab.
17. Search for the provider selected in Step 3 above.
18. On the search result, select the row-level action Select Provider.
19. Now select Submit from the service tab action menu and click Yes on the Submit Service confirmation page.
20. Issue: Log into the database and examine the number of service authorization line items (SALIs) created on the system for the newly created service invoice. There should be two created, but there is only one. Also, the from and to dates of the SALI are the same.

 

Resolution:

This issue has been resolved. The correct number of SALIs are now created when the service delivery frequency 'Monthly Every 1 month(s) from start date' is used and the start date is one of 31st March, May, July, October, or December. Other problematic dates using this frequency pattern are March 29th on non-leap years, as well as March 30th. Again, the correct number of SALIs are created when the start date falls on either of these dates. The logic has also been updated so that the SALIs reflect the period they are covering.

Technical:

No changes were made to the frequency pattern 'Monthly Every 1 month(s) from start date' as it is working as expected. The functionality was updated to swap in the 'Last day of every month' delivery pattern when the service delivery start date is one of 31st of March, May, July, October or December. For the other problematic dates of March 29th on non-leap years and March 30th, additional logic was added to ensure the correct number of SALI occurrences were created.