7.0.8.0 Refresh Pack release notes

Release Notes

Abstract

Merative Social Program Management 7.0.8.0 Refresh Pack Release Notes

Content

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

Important Note

Merative Social Program Management 7.0.8.0 is a Refresh Pack.

Introduction

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

This 7.0.8.0 Refresh Pack release includes new functionality. For more information, see the What's new in Version 7.0.8.0 topic in the product documentation.

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

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

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

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

Merative Social Program Management 7.0.7.0 Refresh Pack
Merative Social Program Management 7.0.6.0 Refresh Pack

System Requirements

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

Download

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

Installation

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

7.0.5.0
7.0.5.0 iFix1
7.0.6.0 Refresh Pack
7.0.6.0 iFix1
7.0.7.0 Refresh Pack
7.0.7.0 iFix1

Prior to running the 7.0.8.0 Refresh Pack installer please ensure all files in your Merative Social Program Management installation are writable.

The installation steps are as follows:

Extract the contents of the zip file to a local drive location.
Run the Merative Social Program Management installer, which can be found in the INSTALLER folder at that location.
After installing, the appropriate build targets must be run as necessary for your installation.

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

Upgrading

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

To download the appropriate version of the Merative Social Program Management Upgrade Helper, see the download instructions at /support/curam

Improvements, Resolved Issues and Third Party Updates

Third Party Updates

WorkItem:250358 - Update the versions of the Jackson JARs to the latest version

The Jackson API contains multiple functions to read and build JSON using Java. It has very powerful data binding capabilities and provides a framework to serialize custom Java objects to JSON strings and deserialize JSON strings back into Java objects. The Java Development Environment (JDE) and the REST infrastructure utilizes these utilities.

The versions of these JARs have now been updated from 2.4.2 and 2.9.5 to the latest version. As a result of this upgrade, the following changes have been made in the JDE and REST deliverable.

CuramSDEJ\lib\third_party_version.properties - the versions of the specified Jackson JARs have been updated.
CuramSDEJ\lib\jackson-annotations-2.9.9.jar - new JAR added.
CuramSDEJ\lib\jackson-core-2.9.9.jar - new JAR added.
CuramSDEJ\lib\jackson-databind-2.9.9.3.jar- new JAR added.
CuramSDEJ\lib\jackson-annotations-2.9.5.jar - old JAR removed.
CuramSDEJ\lib\jackson-core-2.9.5.jar - old JAR removed.
CuramSDEJ\lib\jackson-databind-2.9.5.jar- old JAR removed.
CuramCDEJ\lib\ext\jar\jackson-annotations-2.9.9.jar - new JAR added.
CuramCDEJ\lib\ext\jar\jackson-core-2.9.9.jar - new JAR added.
CuramCDEJ\lib\ext\jar\jackson-databind-2.9.9.3.jar - new JAR added.
CuramCDEJ\lib\ext\jar\jackson-annotations-2.9.5.jar - old JAR removed.
CuramCDEJ\lib\ext\jar\jackson-core-2.9.5.jar - old JAR removed.
CuramCDEJ\lib\ext\jar\jackson-databind-2.9.5.jar - old JAR removed.
EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-annotations-2.9.9.jar - new JAR added.
EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-core-2.9.9.jar - new JAR added.
EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-databind-2.9.9.3.jar - new JAR added.
EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-annotations-2.4.2.jar - old JAR removed.
EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-core-2.4.2.jar - old JAR removed.
EJBServer\components\Rest\restlib\dependencyLibsExt\jackson-databind-2.4.2.jar - old JAR removed.

WorkItem:250672 - Tablet Accessibility Support

The certified version of Apple VoiceOver has been updated to iOS 12.4 This has been certified against Chrome 76.

WorkItem:250674 - Browser Support Update

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

Case Worker Application Browser Support

Google Chrome updated to 76

Universal Access Application Browser Support

Google Chrome updated to 76
Mozilla Firefox updated to 68

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

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

JRE 1.8 u221

Cúram Enterprise Framework

PO07997, WorkItem:240031 - When the text inside a File upload Browse button is bigger than 58 pixels, the characters that do not fit inside the button wrap down to the next line just beneath it

Issue Description:

When the text inside a File upload Browse button is bigger than 58 pixels, the characters that do not fit inside the button wrap down to the next line just beneath it.

**User Interface Impact: **No

Steps to Reproduce:

Login as a caseworker on a German or RPX SPM server.
Search for and open a Person page.
Select the Evidence tab.
Select Verifications from the Page group navigation bar.
Click the Verify Page action control and scroll to the bottom of the modal dialog.
Issue: The characters do not fit inside the File upload Browse button and wrap down to the next line just beneath it.

Resolution:

The styling of File upload Browse button has been updated so that it's width will adjust as needed to fit in line with the text that will be displayed inside it.

PO08279, WorkItem:247055 - Injury and participant information can incorrectly be modified within an Incident that has been closed

Issue Description:

When an Incident is recorded against a Provider or Person, the user can still edit the participant and injury details on the Incident after it has been closed.

User Interface Impact: No
Steps to Reproduce:

Login as a caseworker.
Register a new Person.
Click on the Issues and Proceedings tab and select Incidents.
On the Incident list page, click on the New page action.
Enter the mandatory fields and click Save.
On the newly created Incident, select Injuries and select New.
Enter the mandatory fields and click Save.
Select Home and Close the Incident.
Enter the mandatory fields and click Save.
Notice that the Incident has a status of Closed and that the Close and Delete options are now disabled.
Return to Participants and / or Injuries and try to edit or delete the records.
Issue: The Edit and Delete actions for both the Participants and Injuries are still available when the incident is closed.

Resolution:

The Edit and Delete actions for both Participants and Injuries have been updated to no longer be selectable once the Incident has been closed.

WorkItem:250080 - The Due Date and Time fields in the Add Action Modal are not displaying properly within Internet Explorer 11 and Microsoft Edge

Issue Description:

When recording meeting minutes, actions that resulted from the meeting may be assigned to user activities. The Due Date and Time fields in the Add Action Modal are not properly aligned when the user is using Internet Explorer 11 or Microsoft Edge.

User Interface Impact: No

Steps to Reproduce:

Open the application with an Internet Explorer 11 or Microsoft Edge browser.
Login as a caseworker.
Register a person.
Create an outcome plan for the newly registered person.
On the Admin tab of the created outcome plan navigate to Meeting Minutes and click the Record Meeting Minutes page action control.
Click Next to create a new meeting and record the meeting minutes.
Complete the required fields in the Meeting Details wizard.
Open the Add Action Modal by selecting Add Action on the Actions menu next to the meeting.
Issue: The Due Date and Time fields in the Add Action Modal are not properly aligned.

Resolution:

The Due Date and Time fields have been realigned in the Add Action Modal when using Internet Explorer 11 or Microsoft Edge browsers.

PO08446, WorkItem:250990 - Some fields are not aligned or the correct size - New Special Caution modal

Issue Description:

Some of the fields on the New Special Caution modal are either misaligned or are the wrong size.

User Interface Impact: No

Steps to Reproduce:

Login as a caseworker.
Open a Person page.
Select the Issues and Proceedings tab and then click on Special Cautions in the page group navigation bar.
Click on the New page action control.
Issue: The Category and Type fields are not aligned correctly, and the Start Date and End Date are not the correct sizes on the New Special Caution modal.

Resolution:

This issue has been resolved and the fields are now correctly aligned and are the correct size on the New Special Caution modal.

Technical Services

RULES INFRASTRUCTURE

CÚRAM RULES

PO08002, WorkItem:246478 - Thread blocking and performance issues with Classic rules

Issue Description:

The application performance may degrade due to blocked threads when large classic rules calculations are used in very high volumes. Threads may get blocked on this method:

curam.util.rules.RuleSetCache.getDynamicRulesRoot

This is due to a high load on the classic rules transaction level cache.

User Interface Impact: No

Steps to Reproduce:

Configure a classic ruleset that requires a large number of classic rules calculations in high volumes. This issue is also dependent upon a number of environmental conditions including:

number of classic rulesets
size of rulesets
number of threads
rules and evidence

Resolution:

By default, classic rules are cached per transaction, and if very high numbers of transactions are repeatedly loading large rulesets then a performance bottleneck may occur during the cache load.
It is now possible to switch the classic rules cache from transaction level to global which may mitigate this performance issue, should it arise.

The steps to do so are as follows:

Login as the system administrator.
Click on the Administration Workspace application tab.
Select Property Administration under Application Data in the shortcuts panel.
Click on the New page action to add a new application property.
In the New Property dialog:
1. Set Name to 'curam.rules.classic.cache.scope'.
2. Set Category to Application - Cache Settings.
3. Set Type to String.
4. Set Technical ID to 'curam.rules.classic.cache.scope'.
5. Click Save.
Search for and set the application property 'curam.rules.classic.cache.scope' to GLOBAL (this is case sensitive).
Use the Publish page action to publish the changes.

If necessary, when in GLOBAL mode, the cache can be tuned using the following parameters:

curam.cache.curam-group.RuleSetInformationCache.timeToIdle
curam.cache.curam-group.RuleSetInformationCache.timeToLive
curam.cache.curam-group.RuleSetInformationCache.size (default value is 200)
curam.cache.curam-group.RuleSetInformationCache.evictionPolicy

For more information on Global Caches please refer to the documentation at:
https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

Note that the GLOBAL cache mode is only supported for classic rules which do not use parameterized rulesets.

SECURITY MANAGEMENT

WorkItem:245742 - Session timeout warning is not working in a clustered environment

Issue Description:

The session timeout warning feature does not work in a clustered environment when the WebSphere attribute 'Set session cookies to HTTPOnly', which helps prevent cross-site scripting attacks, is set to true.

User Interface Impact: No

Steps to Reproduce:

Login to the WebSphere application admin server console.
Navigate to the Cookie configuration in Session management.
Enable the option 'Set session cookies to HTTPOnly' to prevent cross-site scripting attacks.
Enable the option to Restrict cookies to HTTPS sessions.
Login as a caseworker.
Issue: The warning dialog doesn't show up after the user has been inactive on the application for the configured session timeout.

Resolution:

The session timeout warning is now independent of the cookie configuration and can work with HTTPOnly set to true.

Technical:

The previous versions used a cookie to store the session expiry timing data. Session expiry timing cookie has been replaced by a session storage object. HTML5 Web Storage is a better choice since, unlike cookies, the storage limit is far larger and information is never transferred to the server.

Integrated Case Management

WorkItem:231476 - After setting Display Case Clients On Case List Pages to true Recently Viewed Cases & Cases Recently Assigned to Me Views still shows Primary Client in the Clients column

Issue Description:

An application property can be used to control whether the primary client or all case clients are displayed on various case list pages. Currently when the application property is set to display all case clients, the clients displayed in the Clients column are incorrect. In some cases only the primary client is displayed and in others no clients are displayed.

User Interface Impact: No

Steps to Reproduce:

Login as a system administrator.
Navigate to System Configurations.
Navigate to Property Administration within Application Data.
Search for the property 'Display Case Clients On Case List Pages' and change the value to true. Save and Publish.
Login as a caseworker.
Create an integrated case.
Navigate to 'My Cases' and search.
Issue: In Results the Clients column appears empty and does not display any names.

Resolution:

The Clients column now correctly displays all case clients on the case list pages.

WorkItem:251141 - Case search shows the column label 'Primary Client' when configured to display 'Clients' instead

Issue Description:

An application property can be used to control whether the primary client or all case clients are displayed on various case list pages. Currently, on the Case Search page, the search results show the column label 'Primary Client' when the system is configured to display the label 'Clients'.

User Interface Impact: Yes

Steps to Reproduce:

Login as a system administrator.
Navigate to System Configurations.
Navigate to Property Administration within Application Data.
Search for the property 'Display Case Clients On Case List Pages' and change the value to true. Save and Publish.
Login as a caseworker.
Navigate to Case Search and search.
Issue: In Search Results, the label 'Primary Client' is displayed instead of the label 'Clients'.

Resolution:

The label 'Clients' was set after performing the case search. Now the landing page shows the correct label on the landing page of Case Search before the search is run.

EVIDENCE MANAGEMENT

PO07785, WorkItem:223930 - Progress spinner is displayed on the Evidence Dashboard when there are no evidence categories configured

Issue Description:

The Evidence Dashboard view does not render properly for an Integrated Case or Product Delivery Case when there are no evidence categories configured. Instead, a progress spinner is displayed. If an Integrated Case or Product Delivery Case has been configured with evidence categories then the Evidence Dashboard displays successfully and there is no progress spinner displayed.

User Interface Impact: No

Prerequisite(s):

An Integrated Case or Product Delivery Case has been created with no evidence categories.

Steps to Reproduce:

Login as a caseworker.
Register a new Person and create a case of the type defined above.
On the newly created case, click on the Evidence tab and then on the Dashboard in the left menu.
Issue: The Evidence Dashboard does not load properly and the progress spinner remains on the page.

Resolution:

The Evidence Dashboard has been modified to display successfully when there are no evidence categories defined for an Integrated Case or Product Delivery Case. The following information message has been added to the Evidence Dashboard: "No evidence types have been defined for this case type".

COMMON

PO07935, WorkItem:238154 - The progress spinner remains after a warning modal is displayed on the Frequency Pattern Editor

Issue Description:

The progress spinner continues to display when creating a new recurring activity with an invalid frequency that causes a warning modal to be displayed on the Frequency Pattern Editor.

User Interface Impact: No
Steps to Reproduce:

Log in as a caseworker.
Register a new Person.
Create a new Social Assistance case for the Person.
Go to the Events tab on the Social Assistance case.
Choose New Recurring Activity from the page action menu.
Click on the Frequency icon to choose a frequency pattern.
On the Frequency Pattern Editor, choose Bi-monthly with 'Days 1 and 1 of every month'.
Click Save.
The following warning modal is displayed: 'Days must be different for bi-monthly frequency pattern!'.
Issue: After this modal is closed, the progress spinner appears over the modal and continues to display. The modal cannot be interacted with and the only option available is to close it.

Resolution:

****The Frequency Pattern Editor has been fixed to prevent the progress spinner from being displayed by ensuring the page is not submitted if there is a validation modal with an invalid frequency displayed.

Administration Suite

ORGANIZATION

PO08422, WorkItem:250280 - When all active announcements are deleted for the organization, the pods on the home page of any user are not displayed

Issue Description:

When all active announcements are deleted for the organization, the pods on the home page of any user are not displayed.

User Interface Impact: Yes

Steps to Reproduce:

Login as an administrator.
Navigate to the Administration Workspace and select Organization.
Select My Organization and navigate to the Announcements tab on the page.
Delete all the existing announcements on the list.
Login as a caseworker.
Navigate to the home page.
Issue: No pods are visible.

Resolution:

This issue has been resolved by updating the underlying javascript to handle the situation where there are no active announcements associated with the organization.

WorkItem:250383 - The Start Date and End Date fields in the New Announcement Modal are not displaying properly within Internet Explorer 11 and Microsoft Edge

Issue Description:

When using Internet Explorer 11 or a Microsoft Edge browser the Start Date and End Date fields in the New Announcement Modal do not display.

User Interface Impact: No

Steps to Reproduce:

Log in as administrator using Internet Explorer 11 or a Microsoft Edge browser.
Open the Shortcut menu.
Select Organization and then New Announcement.
Issue: The Start Date and End Date fields in the New Announcement Modal are not displayed.

Resolution:

When a user opens the New Announcement Modal the Start Date and End Date fields are properly displayed using Internet Explorer 11 or a Microsoft Edge browser.

Intake

PO08174, WorkItem:244768 - Buttons are not functioning in the Duplicate Person Merge Wizard after alternateID validation error thrown

Issue Description:

The Cancel, Back and Next buttons of the Person Merge Wizard stop functioning after a validation message is shown on the Identification page.

User Interface Impact: No

Prerequisites:

Login as a system administrator.
Click on Property Administration under Application Data in the shortcuts panel.
Search for the following environment variables and set their values to NO:
- curam.evidence.pdc.personenabled
- curam.participant.createpdc
- curam.pdc.demographicsenabled
- Workflow - Generate Service Plan Cloned Ticket
Publish the changes.

Steps to Reproduce:

Login as a case worker.
Register a new Person.
Register another Person with the same name.
On one of the Person home pages, go to Administration > Duplicates and select the Mark New Duplicate page action.
On the Duplicate Search Page, enter the criteria for the other person and click Search.
Select the Person from the search results and click on Save & Start Merge on the Mark Duplicate page.
On the Identification page, select the primary alternate ID of the other person. This will result in a validation message on the screen as the alternate ID must not overlap with an existing alternate ID of the same type.
Issue 1: Once the error is thrown on the screen, the Cancel, Back and Next buttons of the player stop functioning and a user cannot navigate to any other page.
Issue 2: An additional Save button also gets displayed on the screen within the player.

Resolution:

This issue has been addressed and now when validation is thrown, the buttons continue to function allowing a user to complete the merge process.

Application Development Environment

PO08251, WorkItem:246467 - The text of some long menu items within the page group navigation menu overlaps with the vertical scroll bar when viewed in minimum screen resolution

Issue Description:

When a caseworker is using the application in the minimum screen resolution, the text of some long menu items within the page group navigation menu overlaps with the vertical scroll bar.

User Interface Impact: No

Steps to Reproduce:

Change the screen resolution to 1366x768.
Login as a caseworker.
Search for a person and open their home page.
Navigate to the Client Contact tab.
Resize the browser window vertically to introduce a scroll bar in the page group navigation menu.
Issue: The text of some long menu items in the page group navigation menu overlaps with the vertical scroll bar.

Resolution:

When in minimum screen resolution, the text of long menu items on the page group navigation menu is now truncated with an ellipsis so that it does not overlap with the vertical scroll bar. Tooltip text displays the full menu item when hovered over.

CLIENT DEVELOPMENT ENVIRONMENT

WorkItem:248565 - It is not possible to sort a list that contains exactly two non-expandable rows

Issue Description:

For a list presented with rows and columns in a table format, each column will have a column header and selecting a column header sorts the list based on the column selected. When a list contains exactly two non-expandable rows, clicking a column header has no effect and does not reorder the rows.

User Interface Impact: No

Steps to Reproduce:

Login as a caseworker.
Open the Cases and Outcomes tab.
Open the toggle in the shortcuts menu labeled Registration.
Click Person. The Register Person modal will open.
Search for a person using criteria that will return exactly two search results.
Click on the column header within the table of returned results.
Issue: The list of search results remains in the same order, rows are not sorted based on the column selected.

Resolution:

Selecting a list column header will now sort the list, regardless of how many expandable or non-expandable rows the list contains.

ACCESSIBILITY

PO07944, WorkItem:238333 - HTML markup displayed for drop-down items on mouse hover, when type-ahead is used

Issue Description:

On a system administrator session when type ahead is used HTML markup text displays on the highlighted text within the drop down menu.
This happens on any drop down menu that accepts type-ahead matching.

User Interface Impact: No

Steps to Reproduce:

Login as a system administrator.
Navigate to system configurations > application data > property administration.
Type in "Appl" in Category dropdown.
Move the mouse over one of the highlighted items in the drop down list.
Issue: The popup tooltip contains the HTML markup used to provide the yellow highlighting.

Resolution:

The HTML no longer appears in the results of type ahead highlighted text. Tooltip now displays without HTML markup text.

PO08098, WorkItem:242763 - Drop-down fields are read as required even if the fields are not mandatory

Issue Description:

When a supported screen reader is used and a visually impaired user navigates to a drop-down field it reads 'required' even if the field is not mandatory.

User Interface Impact: No

Steps to Reproduce:

Enable a screen reader.
Login as a caseworker.
Open the Person Search page.
Use the tab button to get to the Gender drop-down field.
Issue: The screen reader states 'required' when reading the Gender drop-down field even though it is not a mandatory field.

Resolution:

Now when a screen reader user navigates to a drop-down field, if it is a non-mandatory field the screen reader will not announce it as 'required'. If a drop-down field is mandatory, the screen reader will announce it as being 'mandatory'.

PO08404, WorkItem:244205 - Focus is not staying within the calendar month field after the month has been selected

Issue Description:

When a supported screen reader is used the browser focus does not stay within the calendar month form field after the month option has been selected.

**User Interface Impact: **No

Steps to Reproduce:

Enable a screen reader.
Login as a caseworker.
Click on the Cases and Outcomes tab and select Person under Registration in the shortcuts panel.
Navigate to the Date of Birth field, and click on the icon to open the calendar.
Select a month in the month drop-down form field.
Issue: The focus moves to the year form field and then back to the month form field.

Resolution:

This issue has been resolved so that the focus no longer moves to the year field and back to the month field after a month has been selected.

PO08327, WorkItem:248333 - The browser tab title displays 'Page Not Found' when canceling the New Legal Action modal when using Internet Explorer 11

Issue Description:

The browser tab title displays 'Page Not Found' when a user clicks the Cancel button on the New Legal Action modal. This only happens when using Internet Explorer 11. This behavior does not adhere to the Web Content Accessibility Guidelines (WCAG) AA standards.

User Interface Impact: Yes

Steps to Reproduce:

Login as Structured Decision Making Child Welfare caseworker.
Click on the Cases and Plans tab.
Select Register Person and Create Case under Cases in the shortcuts panel.
Enter the Person details and select Ongoing Case from the Type drop-down.
Click Save.
From the case home page, select Legal and then Legal Actions.
Click New to launch the New Legal Action modal dialog.
Click Cancel.
Issue: The browser tab title displays as ‘Page Not Found - IBM Cúram Social Program Management’.

Resolution:

To resolve this accessibility issue, a change was made in the correspondent UIM page, establishing a correct link between canceling the modal and the previous Legal Actions page.

PO08049, WorkItem:248363 - Screen readers unable to read the contextual information for the following interactive controls in a list row: toggle arrows, action menu controls, fields rendering links and radio buttons

Issue Description:

Previously a screen reader did not read the contextual information for the interactive controls in a list, which made it difficult for the screen reader user to associate the control with the list row it belonged and applied to.

User Interface Impact: Yes

Steps to Reproduce:
Example of toggle arrows in an expandable list row:

Login as a caseworker.
Register a new Person.
Click on the Evidence tab to show all the evidence recorded for the Person.
Issue: All the toggle arrows in an expandable list row have the same alt text.

Example of an expandable list row with action menu controls:

Login as a caseworker.
Register a new Person.
Click on the Evidence tab to show all the evidence recorded for the Person.
Issue: All the action menu controls of an expandable list row have the same alt text.

Example of fields rendering links in a list row:

Login as a caseworker.
Register a new Person.
Create a case for the Person.
Add a new member to the case from the New Member action menu.
Search for a person, for example enter 'Smith' in Last Name and click Search.
Issue: All the rows have a 'select' option and the screen reader reads them out as 'select row header select link'.

Example of radio buttons:

Login as a caseworker.
Register a new Person.
Create a Social Assistance case for the Person.
Navigate to the Evidence tab on the case and add two Current Asset records of the same type.
Select to add an Asset Ownership and view the two current asset records listed.
Issue: The Asset Ownership displays the current asset records, but the aria-label is the same for each row.

Resolution:

The following types of interactive controls in a list row now include the list row number in the accessibility readings, allowing the screen reader users to understand the actual list context of the control:

Toggle arrows in an expandable list rows.
List row action menu controls.
Fields rendering links in a list row.
Radio buttons in a list with the single-select widget.

Technical:

Four new properties have been added to CDEJResources.properties to control the new accessibility readings:

listcontrol.reading.togglers - allows for customization/localization of the screen readings associated with the toggle controls in a list with expandable rows.
listcontrol.reading.menus - allows for customization/localization of the screen readings associated with the list row action menu controls.
listcontrol.reading.anchors - allows for customization/localization of the screen readings associated with links in a list row.
listcontrol.reading.selectors - allows for customization/localization of the screen readings associated with radio buttons in a list.

PO08369, WorkItem:249288 - Code-Table values are read with additional Java / HTML tags when entering characters to shorten the list, and then quickly selecting a value

Issue Description:

When a user types characters into a combo box to reduce the amount of options available for selection, a list of options beginning with those characters are returned. When a supported screen reader is enabled and a user focuses on an option from the list, a combination of the option title and HTML tags are announced by the screen reader.

User Interface Impact: No

Steps to Reproduce:

Enable a screen reader.
Login as a Structured Decision Making caseworker.
Navigate to the Participant search in the shortcuts panel.
Use the tab button to get to the State field and enter a letter, for example 'A'.
Don't fill the State field from the list of words returned.
Issue: The screen reader reads a combination of the title text and HTML tags.

Resolution:

When a screen reader is enabled and a user focuses on an option from a combo box list, the title of the option is announced by the screen reader.

PO08373, WorkItem:249365 - Disabled list action menu items for an existing removal are read with the elements from CSS

Issue Description:

When a supported screen reader is used and a user navigates to a menu with a disabled menu item, HTML markup is being read out when the user focuses on the disabled menu item.

User Interface Impact: No

Steps to Reproduce:

Enable a screen reader.
Login as a Structured Decision Making caseworker.
Select Register Person and Create Case under Cases in the shortcuts panel.
Register a new Person under 18 years of age and select Ongoing Case from the Type drop-down.
Click Save.
Select the Removals and Placements tab and click on the New Removal page action.
Enter the removal details on the New Removal page and click Save and Place.
Enter the placement details and click Next.
Search for a Provider using the Provider Search.
Select one of the Providers returned and click Finish.
Navigate to the list action menu for the removal and focus on the disabled Edit Discharge Date option.
Issue: HTML markup is read out by the screen reader.

Resolution:

This issue has now been addressed. When a screen reader user navigates to a menu with a disabled menu item, the menu item's label is read out when the user focuses on the disabled menu item.

PO08384, WorkItem:249556 - Focus is not set to the first field of the New Member page

Issue Description:

When a supported screen reader is used, if the first field in the page is a single search pop-up field such as a Person search field, the screen reader will not initially set the focus on the first field causing users to miss data entry.

This issue causes the focus to incorrectly be set to the Start Date field rather than the Name field on the New Member modal, which is used in cases to add case members.

User Interface Impact: No

Steps to Reproduce:

Enable a screen reader.
Login as a caseworker.
Navigate to an existing case.
Navigate to the tab action menu and select New.
Issue: The focus is set on the Start Date field.

Resolution:

The single search pop-up widget has been updated so that it correctly receives focus if it is the first input element on any page. When the New Member modal is opened, focus is now correctly set on the Name field.

PO08383, WorkItem:249558 - Focus is not set on the first field of the New Contact Log wizard

Issue Description:

Several pages include multi-select fields that allow a user to select from multiple values displayed within the field. When a supported screen reader is used, if the first field in the page is a multi-select field, the screen reader will not initially set the focus on the first field causing users to miss data entry.

This issue causes the focus to incorrectly be set to the Location field on the Details step of the New Contact wizard, which is used in cases to add contacts to a Contact Log.

User Interface Impact: No

Steps to Reproduce:

Enable a screen reader.
Login as a caseworker.
Navigate to an existing case.
Navigate to the tab action menu and select New Contact Log.
Issue: The focus is set on the Location drop-down field rather than on the Concerning multi-select field.

Resolution:

The multi-select widget has been updated so that it correctly receives focus if it is the first input element on any page. When the New Contact wizard is opened, focus is now correctly set on the Concerning multi-select field.

PO08386, WorkItem:249646 - Focus is not being set on the text area field of the Update Narrative modal

Issue Description:

When the Update Narrative modal page is opened, which contains just one text field, the focus is not being set on that field.

User Interface Impact: No

Steps to Reproduce:

Login as a Child Welfare intake worker and click on the New Intake link in the shortcuts panel.
Select Child Protection Services as the category and click Save.
Click on the Participants tab and select New Participant from the page menu.
Enter the participant details and click Next.
Click Finish.
Click Open Intake from the tab menu; the intake opens in a new tab.
Select Update Narrative from the intake tab menu.
Issue: The focus is not set on the text field.

Resolution:

This issue has been addressed and the focus is set on the text field when the Update Narrative modal page is opened.

PO08397, WorkItem:249740 - Screen reader does not distinguish between country code, area code and phone number fields when adding a participant to a Child Welfare intake

Issue Description:

When adding a new participant to an Intake case, a user can supply phone number details for the participant by inputting a country code, an area code, and a phone number, with each value having a separate input field within a container. When a supported screen reader is used and a user navigates to the phone number, the screen reader will read the same label for the country code, area code, and phone number fields.

User Interface Impact: No
Steps to Reproduce:

Enable a screen reader.
Login as a Child Welfare intake worker.
Navigate to an Intake case.
Navigate to Participants.
Select New Participant.
Navigate to the Phone Number.
Issue: The screen reader announces the label Phone Number for each field as the user navigates through the country code, area code, and phone number fields.

Resolution:

The title attribute for the country code, area code and phone number fields has been updated and screen reader users can distinguish between the fields when navigating between them.

PO08402, WorkItem:249741 - Screen reader does not distinguish between age from and to fields when adding a participant to a Child Welfare intake

Issue Description:

When adding a new participant to an Intake case, a user can supply an age range for the participant by inputting an age from value and age to value into two separate fields within a container. When a supported screen reader is used and the user navigates to the age range, the screen reader will read the same label for the age from and age to fields.
User Interface Impact: No

Steps to Reproduce:

Enable a screen reader.
Login as a Child Welfare intake worker.
Navigate to an Intake case.
Navigate to Participants.
Select New Participant.
Navigate to the Age Range.
Issue: The screen reader announces the label Age Range for each field as the user navigates through the age from and age to fields.

Resolution:

The title attribute for the age from and age to fields has been updated and screen reader users can distinguish between the fields when navigating between them.

PO08405, WorkItem:249991 - Browser tab title updates incorrectly after opening and closing a pop-up window from a modal dialog

Issue Description:

When a page, a modal dialog, and a pop-up window are opened in the application, the browser tab title is not updating with the modal dialog title once the pop-up window is closed. Instead, the browser tab title is being updated with the page title opened in the background. This causes misleading information to be read out by a screen reader. This issue can occur throughout Social Program Management.

User Interface Impact: No

Steps to Reproduce:

Turn the screen reader on.
Login as a caseworker and click on the Cases and Outcomes tab.
Click on My Cases under Cases in the shortcuts panel. Leave the My Cases tab open.
Now click on Person under Registration in the shortcuts panel.
Select the date picker for the Date of Birth field.
Close the date picker.
Issue: The browser tab title is updated to My Cases. This causes the screen reader to read out My Cases instead of Register Person, which is confusing to screen reader users.

Resolution:

The browser tab title now correctly updates with the title of the modal dialog once a pop-up window opened from the modal is closed. The screen reader reads the correct tab title.

PO08407, WorkItem:250041 - The tooltip on the calendar date icon misleads the impaired user on how to use it

Issue Description:

When a supported screen reader is used the calendar date icon tooltip asks the user to 'Click here to select a Date'. The term 'Click here' can be misleading for a visually impaired user.

User Interface Impact: No

Steps to Reproduce:

Enable a screen reader.
Login as a caseworker.
Register a new Person.
Hover over the Date of Birth field’s calendar icon on the Register Person modal.
Issue: The calendar date icon tooltip asks the user to 'Click here to select a Date'.

Resolution:

The calendar date icon tooltip has been modified to read 'Select a Date' throughout the application, which makes it more meaningful for a visually impaired user.

PO08408, WorkItem:250049 - Accessibility documentation on Pods

Issue Description:

The documentation wording in relation to the accessibility of pods was not clear.

**User Interface Impact: **No
**Steps to Reproduce:**N/A
Resolution:

An update has been made to the Pod page in the documentation Accessibility section, which highlights that the pods are not accessible. For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

PO08428, WorkItem:250439 - The shortcuts menu splitter element is incorrectly announced as a menu by screenreaders

Issue Description:

When a supported screen reader is used a shortcuts panel splitter element receives focus but it is incorrectly announced as a menu element.

User Interface Impact: No

Steps to Reproduce:

Enable a screen reader.
Login as a caseworker.
Click on the Cases and Outcomes application tab.
Expand the shortcuts panel and navigate to the end using the keyboard.
Navigate to the shortcuts panel splitter element by pressing the tab key.
Issue: The shortcuts panel splitter element is announced as a menu element by the screenreader.

Resolution:

This issue has been resolved. Now, when a screenreader user tabs from the end of the shortcuts menu, a shortcuts panel splitter element receives focus and will be correctly announced as a splitter element by the screenreader.

PO08486, WorkItem:251364 - Accessibility documentation on Modals

Issue Description:

The documentation wording in relation to accessibility and modals was not clear, in particular how to navigate through a modal page by using a supported screen reader and keyboard.

**User Interface Impact: **No

Steps to Reproduce: N/A

Resolution:

The Modals page in the documentation Accessibility section has been updated, which highlights the standard way to navigate through a modal page. For more information, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

PO08030, WorkItem:251380 - Windows operating system's high contrast mode removes icons from Person home page

Issue Description:

When high contrast mode is enabled on a Windows operating system (OS), a number of icons are not visible on the Person home page.

User Interface Impact: Yes

Steps to Reproduce:

On a Windows operating system, search for the High Contrast settings.
Enable high contrast mode.
Login as a caseworker.
Search for a person and navigate to the Person home page.
Issue: Observe the following icons are not visible when high contrast mode is enabled:
- Shortcuts section panel icon.
- Shortcuts menu items toggle arrows.
- Smart panel icon.
- Smart panel toggle arrows.
- Toggle button icon.
- Context viewer image link.
- Phone number icon on context panel.
- Email address icon on context panel.
- Toggle arrow icon on clusters in main page.

Resolution:

This has been resolved by updating the underlying code to use image tags instead of background images on links. These icons can now be viewed when high contrast mode is enabled on the Windows operating system.

Technical:

This issue was resolved by updating the JavaScript code on the shortcuts section and smart panel for the relevant icons. The email address, phone number and context viewer image link icons can be updated by updating the image source file path in the Image.properties file.

IconEmail
IconEmailHover
IconPhone
IconCCV
IconCCVHover

LOOK & FEEL

PO08300, WorkItem:247387 - Some standard text input fields appear misaligned with other form controls because they do not use 100% width within a cluster column on a page or modal dialog

Issue Description:

Some standard text input fields appear misaligned with other form controls because they do not use 100% width within a cluster column on a page or modal dialog. This is only for scenarios where both the standard input text fields and other form controls in a cluster column all rely on their default width.

User Interface Impact: No

Steps to Reproduce:

This can be observed on many pages within the application but the following steps describe how to see it on the first step of the Register Person wizard.

Login as a caseworker.
Navigate to the Register Person wizard.
Issue: On the first page of the Register Person wizard the text input fields in the first column on the 'Additional Search Criteria' appear misaligned on the right side with the 'Date of Birth' field because they do not use their 100% width setting.

Resolution:

In this scenario where the default width is set in UIM for a standard text input field, the issue is resolved by ensuring that the width is 100% for text input fields in the relevant CSS stylesheet.
Technical:

The curam_main.css CSS stylesheet has been updated to display standard text input fields correctly.

Business Services

TASK MANAGEMENT

PO08442, WorkItem:248213 - The Deadline Date and Time fields in the Edit Deadline Modal are not displaying properly within Internet Explorer 11 and Microsoft Edge

Issue Description:

The Date and Time fields in the Edit Deadline page of My Tasks list are not properly aligned when using Internet Explorer 11 or Microsoft Edge browsers.

User Interface Impact: No.

Steps to Reproduce:

Using Internet Explorer 11 or Microsoft Edge log in as a supervisor.
From the inbox create a new task and select the checkbox Add To My Tasks.
Navigate to My Tasks.
Click on the Actions menu next to a task and select Edit Deadline action.
Issue: The Date and Time fields in the Edit Deadline Modal are not properly aligned.

Resolution:

The Date and Time fields have been realigned and now display consistently on Internet Explorer 11 or Microsoft Edge browsers.

Cúram Modules

Outcome Management

WorkItem:245565 - Within an outcome plan a user is unable to record meeting minutes for a meeting

Issue Description:

In Outcome Management, from a scheduled meeting a user should be able to record meeting minutes for the meeting. The user is unable to record meeting minutes using the Admin tab Meetings link.

User Interface Impact: No

Steps to Reproduce:

Login as a caseworker.
Register a Person.
Create an Outcome Plan for the created person.
Open the created Outcome Plan.
Click on the Admin tab.
Select Meetings inside the Navigation Panel.
Click on the button New Meeting and schedule a new meeting.
Select List View inside the Meetings page.
Inside the List View, click on the action menu next to the meeting record and select Record Meeting Minutes.
Issue: Record Meeting Minutes wizard is frozen and does not allow the user to navigate forward and backward.

Resolution:

Now the Record Meeting Minutes wizard is displayed correctly when the Meetings Link from the Admin tab is selected and it allows the user to record the information about the meeting.

WorkItem:246539 - Time Attended and Time Absent fields are truncated when recording daily participation in an Outcome Plan

Issue Description:

Outcome Management allows the recording of daily participation times on an Action. The fields Time Attended and Time Absent in the Record Participation modal are too small and their values are truncated.

User Interface Impact: Yes.

Steps to Reproduce:

Login as a caseworker.
Register a person.
Create a child welfare outcome plan for the created person.
Open the created outcome plan.
Click on the activities tab.
Click on the action menu, then select New Action.
Select Become Self-Employed.
Navigate through the Action:
1. In step 3, insert as frequency an hour a day.
2. In step 5, select the checkbox Me under Owner and under Responsibility.
Click on the activity text link Become Self Employed.
Click on the Participation tab.
Click on the action menu and select Record Daily Participation.
Issue: The fields Time Attended and Time Absent in the Record Participation modal are too small and their values are truncated.

Resolution:

The issue has been resolved. Now when the user opens the Record Participant modal, the Time Attended and Time Absent fields are correctly displayed.

PO08304 , WorkItem:246941 - The latest progress point is not displayed in the progress graph or progress tooltip graph.

Issue Description:

When the number of progress points recorded for an objective is more than the value set in the system admin properties, the latest progress point is not visible on the tooltip progress graph of the outcome plan workspace. The latest progress point is also not visible on the progress graph of the objective itself.
User Interface Impact: Yes

Prerequisite(s):

Login as a system administrator.
Click on System Configurations and expand the Shortcuts panel.
Expand the Application Data section and click on Property Administration.
Search for and ensure the following property values are set (if property values are changed select the Publish page action control and confirm).
- curam.outcomeplanning.flexOutcomePlanWorkspaceEnabled = false
- curam.outcomeplanning.maxNumPointsInProgressTooltipGraph = 2
- curam.outcomeplanning.maxNumPointsInProgressGraph = 2
Login as an administrator.
Click on Administration Workspace and expand the Shortcuts panel.
Expand the Outcome Management section and click on Objectives.
Click on the Add Keyword row actions menu for the 'Address any accessibility issues for a person with a disability' objective.
Type Meditation and click on the Save button.

Steps to Reproduce:

Login as a caseworker.
Navigate to an Ongoing case and create an outcome plan.
Click the Objectives tab and select the New page action control.
Create the 'Address any accessibility issues for a person with a disability' objective using the keyword added in the Prerequisites above to search for it.
Record a progress point for the objective.
View the progress graph for the objective.
Result: The progress graph correctly displays the point. You can hover over the progress point to see the description.
Navigate to the outcome plan workspace.
Hover over the progress icon for the objective.
Result: The tooltip progress graph correctly displays the point.
Record another progress for the objective. Select a progress value different from the last one so that the line chart is clearly visible.
View the progress graph for the objective.
Result: The progress graph correctly displays the point. You can hover over the point to see the description.
Navigate to the outcome plan workspace.
Hover over the progress icon for the objective
Result: The tooltip Progress graph correctly displays the 2 progress points.
Record another progress for the objective. Select a progress value different from the last two so that the line chart is clearly visible.
View the progress graph for the objective.
Issue 1: The progress graph displays 2 points. However, the last point does not display the latest progress point, instead it displays the previous value. You can hover over the last point to see the description and confirm that the last one is missing.
Navigate to the outcome plan workspace.
Hover over the progress icon for the objective.
Issue 2: The tooltip progress graph displays 2 points. However, the last point does not display the latest progress point, instead it displays the previous value.

Resolution:

When viewing the progress graph tooltip on an outcome plan, the latest progress point is now visible. Also when viewing the progress graph of an objective on the Objectives tab, the latest progress point is now visible.

PO08319, WorkItem:248208 - The rating chart is not displayed in the Outcome Plan Factor list view

Issue Description:

Outcome Management displays charts that display the client's change in ratings and progress over time. The Ratings chart is not shown in the Factors list page when the caseworker updates the rating.
**User Interface Impact:**No

Prerequisite(s):

Login as an administrator.
Click on the Administration Workspace tab.
Open the Shortcuts panel and the Outcome Management section.
Click on Outcome Plans and select an outcome plan.
Click on the Factors tab, if there is no factor listed then add an existing factor.
Click on Factors in the Shortcuts panel.
Select the Factor that already existed or was added to the outcome plan above.
Click on the Classification tab, if there is classification listed then add one such as Low (Range 0-5).

Steps to Reproduce:

Login as a caseworker.
Click on the Cases and Outcomes tab.
Open the Shortcuts panel and the Outcome Plans section.
Click on New Outcome Plan and enter the details using the plan edited in the prerequisite section above.
On the outcome plan, click on the Assessments & Factors tab.
Select Factors from the page group navigation bar.
Click on the Add Factor page action control and add the factor edited in the prerequisite section above.
Select Update Rating from the Factor list action menu.
Enter a rating value and click Save.
Issue: The Ratings chart does not display.

Resolution:

The Factors list page now shows the Ratings chart when the caseworker updates the factor rating.

PO08366, WorkItem:249245 - Outcome Plan names displayed in context panels overlap the status field when the names are too long

Issue Description:

Outcome Plans include a variety of components such as goals and assessments, each of which has its own context panel. For those context panels that can include the display of multiple clients as well as a status for the component, if the name of the component is too long and multiple clients are displayed, the name overlaps with the status. This issue occurs with the context panels for the outcome plan, outcome plan assessments, outcome plan goals, and outcome plan actions, when the names of each are too long.

User Interface Impact: Yes

Steps to Reproduce:

Login as a caseworker, or any role with access to create Outcome Plans.
Register a new Person.
Click on New Outcome Plan under Outcome Plans in the shortcuts panel.
Search for a registered Person and select the person.
Give the Outcome Plan a Type and under Name, enter a name that is particularly long.
Click Finish.
Issue: The outcome plan name overlaps with the status field in the context panel of the case.

Resolution:

When a caseworker creates an outcome plan, an outcome plan assessment, an outcome plan goal, or an outcome plan action that has a very long name, the name displayed in the context panel is truncated so that it does not wrap down to the next line and overlap with the status. A hover tooltip has been added to show the full text of the name.

Technical:

These are the files impacted:

webclient/components/AssessmentPlanning/css/
OutcomePlanContextPanel.css
webclient/components/AssessmentPlanning/css/
OutcomePlanContextPanel_rtl.css

WorkItem:250077 - Application error occurs when the View Printer Friendly Minutes option for a Meeting with completed Meeting Minutes is selected

Issue Description:

Within an outcome plan, after recording meeting minutes for a meeting, a document containing details about the minutes of the meeting can be printed. When a user attempts to create the document by selecting the View Printer Friendly Minutes action item, an application error occurs.

User Interface Impact: No

Steps to Reproduce:

Login as Child Welfare Structured Decision Making caseworker.
Register a new Person.
Create a new Outcome Plan for the Person.
Open the new Outcome Plan.
In the Admin tab, click on Meeting Minutes.
Select Record Meeting Minutes and finish all the steps to record the minutes.
On the new minutes record, click on the actions menu next to the meeting and click on View Printer Friendly Minutes.
Issue: An application error is shown when the user clicks on the View Printer Friendly Minutes option related to the meeting with completed meeting minutes.

Resolution:

Now when the user clicks on the View Printer Friendly Minutes option related to the meeting with completed meeting minutes, the Meeting Minutes PDF is downloaded.

WorkItem:250559 - A vertical scrollbar is visible in multiple participant outcome plan context panels with the minimum screen resolution set in browser

Issue Description:

A vertical scrollbar is visible in multiple participant outcome plan context panels with the minimum screen resolution set in the browser.

User Interface Impact: No

Steps to Reproduce:

Login as a caseworker.
Expand the Shortcuts panel and select New Outcome Plan from the Outcome Plans section.
Create a new outcome plan with multiple participants.
Issue: A vertical scrollbar is visible in the context panel.

Resolution:

The height of the Outcome Plan context panel has been increased to prevent a vertical scrollbar from appearing.

Technical Details:

Changes made in the following tab file:

EJBServer/components/AssessmentPlanning/tab/OutcomePlan.tab

Provider Management

PO08161, WorkItem:244288 - A user is unable to edit a provider offering even though the updated details do not create any conflict with an existing placement or service delivery

Issue Description:

Services that a provider is approved to provide to clients are designated through the creation of provider offerings for a provider, which include start and end dates for when the offering is valid.

Once a provider offering is used in the creation of a placement, placement reservation, or service delivery for a client, a validation prevents the modification of any information about the provider offering including information such as Comments or Intake Procedure Information that has no impact on the validity of the existing placement, placement reservation, or service delivery.

Related WorkItem(s): 249171

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

Login as a Child Welfare caseworker.
Navigate to Cases and Plans.
Select Register Person and Create Case under Cases in the shortcuts panel.
Register a Person with a date of birth of 1/1/2010 and select Ongoing Case from the type drop-down.
Navigate to Removals and Placements and select New Removal.
Add the necessary data and place the participant with an existing provider.
Login as a Provider Management Resource Manager.
Search for and navigate to the provider home page where the child is placed.
Navigate to the services page.
Click on the Edit action for the service associated with the placement.
Modify the Comments field by adding new information or updating the existing information, and click Save.
Issue: An error is encountered saying ‘The provider service offering cannot be modified as it is associated to an existing placement'.

Resolution:

In order to allow a user to modify information about the providing offering that will not impact existing placements, placement reservations, or service deliveries, the existing validation has been updated to only be thrown when a user attempts to modify the service associated to the provider offering.

To ensure that the association of the provider offering to the existing placement, placement reservation, or service delivery remains valid, new validations have also been introduced to prevent the start and end date for the provider offering from being modified to dates that are in conflict with the start and end dates of the existing placements, placement reservations or service deliveries that are using the provider offering.
See the related work item for details on these new validations.

PO08347, WorkItem:248651 - Outcome plan action participant images overlap with the outcome plan action details in the context panel at the minimum supported resolution

Issue Description:

When a caseworker navigates to an outcome plan action tab, the participant images and the outcome plan action details in the context panel overlap with each other. This happens when 4 or more participants are added to an outcome plan and is viewed using the minimum screen resolution.

User Interface Impact: No

Prerequisite(s):

Login as an administrator.
Configure an action under Outcome Management that allows for Multiple Clients.

Steps to Reproduce:

Login as a caseworker.
Select or create an outcome plan with 4 or more participants.
From the activities page create a new action.
Select the action that had previously been configured to accept multiple clients.
Select 4 or more participants, enter the remaining details in the wizard and click the Finish button to create the new action.
Click the newly created action in the activities list.
Change the screen resolution to the minimum supported and 100% screen zoom.
Issue: In the context panel, the participant images and the outcome plan action details overlap with each other.

Resolution:

When a caseworker navigates to an outcome plan action tab using the minimum supported resolution, the participant images and the outcome plan action details in the context panel no longer overlap.

Technical:

Changes made in:

webclient/components/CPM/css/
outcomeplan-actionservicereferral.css

WorkItem:249171 - The system allows the modification of service offering start / end dates to be after a placement / reservation / service delivery start date

Issue Description:

Services that a provider is approved to provide to clients are designated through the creation of provider offerings for a provider, which include start and end dates for when the offering is valid.

Once a provider offering is used in the creation of a placement, placement reservation, or service delivery for a client, there are no validations to prevent the user from modifying the start and end dates of the provider offering to dates that impact the validity of the existing placement, placement reservation, or service delivery.

**Related WorkItem(s): **244288

User Interface Impact: No

Steps to Reproduce:

Login as a Child Welfare caseworker.
Navigate to the Cases and Plans application tab.
Select Register Person and Create Case under Cases in the shortcuts panel.
Register a Person with a date of birth of 1/1/2010 and select Ongoing Case from the Type drop-down.
Select the Removals and Placements tab on the Ongoing Case and click on the New Removal page action.
Add any data and place the participant with an existing provider.
Login as a Provider Management Resource Manager.
Navigate to the home page of the Provider where the child is placed.
Navigate to the Services page.
Click on the Edit action for the service associated to the placement.
Modify the start date to be after the start date of the created placement.
Click Save.
Issue: There is no validation to stop the start date being modified to be after the placement start date.

Note: This issue is only reproducible after the fix for related work item 244288 is taken on. It was not reproducible before because the validation mentioned in 244288 was blocking all fields from being modified.

Resolution:

New validations have been introduced for modifying the start or end date so that there are no conflicts with existing placements, placement reservations or service deliveries.

Technical:

The following validations have been added to
EJBServer/components/CPM/message/ProviderOffering.xml:

The Provider Offering Start Date cannot be after an existing Placement Start Date.
The Provider Offering End Date cannot be before an existing Placement Start Date.
The Provider Offering End Date cannot be before an existing Placement End Date.
The Provider Offering Start Date cannot be after an existing Service Delivery Start Date.
The Provider Offering End Date cannot be before an existing Service Delivery Start Date.
The Provider Offering End Date cannot be before an existing Service Delivery End Date.
The Provider Offering Start Date cannot be after an existing Reservation Start Date.
The Provider Offering End Date cannot be before an existing Reservation Start Date.
The Provider Offering End Date cannot be before an existing Reservation End Date.

PO08446, WorkItem:250991 - Some fields are not aligned on the New Attendee modal

Issue Description:

Some of the fields on the New Attendee modal are misaligned.

User Interface Impact: No

Steps to Reproduce:

Login as a Provider Manager.
Open the Providers and Services tab.
Select My Providers under Providers in the shortcuts panel.
Click on the Reference hyperlink to open one of the Providers in the list.
Select the Credentials tab and then click on Home Studies in the page group navigation bar.
Click on the New page action control.
Enter all the mandatory information and click Save.
Select New Home Visit from the action menu for the home study record in the list.
Enter all the mandatory information and click Save.
Expand the home study record in the list and select the Home Visits in-page navigation tab.
Select New Attendee from the action menu for the home visit record in the list.
Issue: The Person and Name fields on the New Attendee modal are not correctly aligned.

Resolution:

This issue has been resolved and the fields are now correctly aligned on the New Attendee modal.

Supervisor Workspace

PO07031, WorkItem:192162 - Unable to view the details of a Position subscribed to a Work Queue in the Home tab of a Work Queue workspace

Issue Description:

Unable to view the details of a Position subscribed to a Work Queue. Instead, the warning 'The page you have requested is not available.' is displayed in the Home tab of a Work Queue workspace.

User Interface Impact: No

Steps to Reproduce:

Login as an administrator.
Click on the Administration Workspace tab.
In the shortcuts panel, select Workflow and click on Work Queues.
Select New Subscription from the actions menu of one of the existing work queues.
Select Position in the New Member drop-down and click on the search icon.
Search for Executive Chairperson and then select the result returned.
Click Save.
From the actions menu of the same work queue, select New Subscription.
Select Job in the New Member drop-down and click the search icon.
Select Executive and then click Save.
Login as a supervisor.
Click on the Team and Workloads tab.
In the shortcuts panel select Users.
Select My Work Queues and then click on Position Subscribed.
Click on the link in the Name column to open the Work Queue workspace.
Under the Organization Object Subscribers cluster, click on the Executive Chairperson link.
Issue: 'The page you have requested is not available.' is displayed when trying to view the details of the Position subscribed to a Work Queue.

Resolution:

This issue has been resolved and the Home tab of a Work Queue workspace displays the details of a Position subscribed to a Work Queue.

PO07187, WorkItem:197746 - Forward Tasks search results section displays Tasks that have been queued for Bulk Task Forwarding in batch

Issue Description:

All tasks assigned to a user are showing up in the Forward Tasks page, including tasks scheduled to be forwarded in batch.

**User Interface Impact: **No
Prerequisitie(s):

Login as a system administrator.
Navigate to Property Administration under Application Data in the shortcuts panel.
Search for the property with name 'curam.batch.bulktaskforward.
deferredprocess.max.processing.count'.
Use the Edit Value action to set the value of the property to 2.
Publish the changes.

Steps to Reproduce:

Login as a supervisor.
Click on the Team and Workloads tab.
Click on My Users under Users in the shortcuts panel to return a list of users.
Click on a name link for one of the users; this opens the user’s workspace in a new tab.
Click on the Tasks tab within the user workspace. By default, the Assigned Tasks list page is displayed.
Click on the Forward page menu action.
Check the 'List all tasks assigned to the user' check-box.
Click Search.
Select a different user from the My Users drop-down.
Select more than 2 tasks listed in the search results.
Click Save.
Click on the Forward page menu action again.
Check the 'List all tasks assigned to the user' check-box.
Click Search.
Issue: Tasks scheduled to be forwarded in batch are returned in the Forward Tasks search.

Resolution:

Tasks scheduled to be forwarded in batch are no longer returned in the Forward Tasks search.

PO07208, WorkItem:198448 - Case Reassignment Batch issue: The 'To' username is not getting displayed in the notification sent to the supervisor

Issue Description:

The notification sent to a supervisor as part of the Case Reassignment Batch process does not contain any information about the new case owner.

**User Interface Impact: **No

Prerequisite(s):

This step ensures that bulk reassignment using the batch process can be tested with only two cases instead of the default value of 100.

Login as a system administrator.
Click on the System Configurations tab.
Select Property Administration under Application Data in the shortcuts panel.
Type 'curam.batch.bulkcasereassignment.deferredprocess.max.
processing.count' into the Name field and click Search.
Modify the value of the record returned from 100 to 2 and click the Publish page action.

Steps to Reproduce:

Setting up the cases to be reassigned

Login as a caseworker.
Register a new Person.
Click on the Care and Protection tab on the Person.
Click on the New page action and create a new pre-configured case.
Repeat step 4 to create a second case for the Person.

Reassigning the cases

Login as supervisor and click on the Team and Workloads tab.
Select My Users under Users in the shortcuts panel.
Click on the hyperlink of a user who has cases assigned to them; the user workspace will open in a new tab.
Click on the Cases tab.
Click on the Reassign Cases page action.
Check the Auto Reassign and 'List all cases assigned to the user' check-boxes.
Click Search.
Select the number of cases required to process the auto reassignment in batch.
Click Save.
The following informationals are displayed:
- 2 Cases have been successfully queued for later reassignment.
- There are too many cases selected to reassign now. This reassignment will need to be performed in batch mode, please schedule with your administrator.

Queueing and running the Case Reassignment Batch process

Login as a system administrator.
Click on the System Configurations tab.
Click on Processes under Batch in the shortcuts panel.
Type 'Case Reassignment Batch' in the Name / Description field and click Search.
Select the Execute row level action for the Case Reassignment Batch.
Leave the parameters blank in the modal and click Execute to queue the batch process.
Run the batch process.

Checking the notifications

Login as a supervisor.
Click on Inbox and navigate to My Notifications under Notifications in the shortcuts panel.
Issue: None of the notifications generated from the Case Reassignment Batch process contain information about the new case owner.

Resolution:

The notifications received by a supervisor as part of the Case Reassignment Batch process now contain information about the new case owner.

PO07998, WorkItem:240026 - Assigned Tasks is displayed under the My Users tab instead of being displayed in its own tab

Issue Description:

When a supervisor selects the Assigned Tasks number hyperlink from the My Users page, the Assigned Tasks page opens inside the My Users tab instead of in its own tab.

User Interface Impact: Yes

Steps to Reproduce:

Login as a supervisor.
Select the Team and Workloads tab.
Select My Users under Users in the shortcuts panel.
For one of the users, select the number hyperlink for Assigned Tasks.
Issue: The Assigned Tasks page opens within the My Users tab instead of in its own tab.

Resolution:

This issue has been resolved. Now when a supervisor selects the number hyperlink for Assigned Tasks on the My Users page, the Assigned Tasks opens in its own tab.

WorkItem:247525 - Failure notifications are not sent from batch reassignment of tasks when tasks reassigned to users with an active task allocation blocking

Issue Description:

The Task Allocation Blocking function ensures that no tasks are assigned to an individual user for the specified period of time. When bulk reassignment of tasks occurs to this user and the allocation blocking period comes into effect prior to the batch process reassigning these tasks, the tasks fail to reassign as expected but the notification of this failure is not set to the supervisor.

User Interface Impact: No.

Prerequisite(s):

Login as a sysadmin.
Set the following property 'curam.batch.bulktaskforward.deferredprocess.
max.processing.count' to 2.
Publish the changes.
Login as a superuser.
Select Inbox.
Select Tasks.
Select Preferences.
Setup a Task Allocation Blocking for the Super User by selecting a date and time in the future when the batch job will be run.

Steps to Reproduce:

Login as a supervisor.
Select Team and Workloads.
Select Users.
Select My Users.
Select a user with some tasks assigned.
From the User workspace, forward three Tasks from the selected user to another user before the Task Allocation Blocking period is Active.
Wait until Task Allocation Blocking for the Super User is Active.
Run Task Forward Batch (TaskForwardBatch) and Assigned Task Forward Batch (AssignedTaskForwardBatch).
Issue: The supervisor user is not receiving a notification for failed task forwarding when there is an active task blocking allocation.

Resolution:

The issue has been resolved. Now when a batch process failed when there is a blocking allocation active, the Supervisor receives the notification with the following information:

Subject: Forwarding of tasks from X to Y was unsuccessful
Content: The following caused the forward to fail: <message> X and Y refer to the tasks reassigned from and to <message> refers to the failure in business logic or application exception, like, the task <<X>>, is closed and cannot be forwarded.

WorkItem:247786 - Selecting 'Reserve to Me' from the Available Tasks list on User Workspace doesn’t reserve the task to the supervisor as expected

Issue Description:

In order to manage workload, a supervisor should be able to reserve a caseworker's task to their supervisor queue. Within a supervisor's session, open a caseworker's workspace then navigate to the Available Tasks list. On selecting the "Reserve to Me" action menu from the available tasks, the task is not reserved to the supervisor as expected. Instead the task is reserved to the caseworker workspace.

User Interface Impact: No

Steps to Reproduce:

Login as a supervisor.
Navigate to Team and Workloads.
Open the Shortcuts Menu. Select Users, then My Users.
Look in the Assigned Tasks column for a caseworker that has few assigned tasks. This opens that caseworker's workspace.
Go to the Tasks tab, then click on Assigned Tasks.
Click on Actions Menu next to a task and select 'Reserve to me'.
Issue: The 'Reserve to me' action adds the task to the currently open workspace, not the supervisor workspace.

Resolution:

Now when the supervisor reserves a task using the 'Reserve to me' action, the task is reserved to the supervisor.

Intelligent Evidence Gathering

WorkItem:252610 - Merative Universal Access Responsive Web Application: Remove control questions from summary pages

Issue Description:

Control questions that are defined in a loop are shown when accessed from summary pages in the Universal Access Responsive Web Application.
User Interface Impact: No

Steps to Reproduce:

Update an IEG script to contain a loop with a control question where loop pages can be accessed from the summary page using 'Edit' or 'Add' buttons.
In the Universal Access Responsive Web Application, apply for a benefit using that IEG script.
Populate loop pages and observe that control questions are accessed as expected.
Continue up to the summary page and from here access already populated loop pages using 'Edit' button or new loop pages using 'Add' button.
Issue: The control question is displayed when it should be hidden.

Resolution:

Control questions that are defined in a loop are now hidden when accessed from summary pages.

WorkItem:252611 - Merative Universal Access Responsive Web Application: Informational messages missing for IEG clusters and lists

Issue Description:

Informational messages that are defined for a cluster or a list are not displayed.

User Interface Impact: No

Steps to Reproduce:

Update an IEG script to contain a cluster and a list with informational messages.
In the Universal Access Responsive Web Application, apply for a benefit using that IEG script.
Issue: Informational messages are not displayed for the cluster or list.

Resolution:

Informational messages that are defined for a cluster or a list are now displayed as expected.

WorkItem:252612 - Merative Universal Access Responsive Web Application: Issues with Read-only Conditional Fields

Issue Description:

An editable question that is defined in a conditional visible cluster is displayed as read-only.

User Interface Impact: No
Steps to Reproduce:

Update an IEG script to contain two dynamically conditional clusters where the first cluster does not meet the condition and is hidden and the second cluster meets the condition and is visible.
Add the same question to both clusters. Add the question to the first cluster as read-only, and add the question to the second cluster as editable.
In the Universal Access Responsive Web Application, apply for a benefit using that IEG script.
Issue: The editable question that is defined in the second cluster is displayed as read-only.

Resolution:

An editable question that is defined in a conditional visible cluster is now editable.

WorkItem:252613 - Merative Universal Access Responsive Web Application: Mandatory questions that use arrays and check boxes not marked as Required

Issue Description:

Mandatory IEG script questions with array type and check-boxes are not marked as required in the Universal Access Responsive Web Application.

User Interface Impact: No

Steps to Reproduce:

Update an IEG script to contain a question with array type and check-boxes and mark that question as mandatory.
In the Universal Access Responsive Web Application, apply for a benefit by using that IEG script.
Issue: The question does not display the required indicator next to the label.

Resolution:

Mandatory IEG script questions with array type and check-boxes are now marked as required in the Universal Access Responsive Web Application.

WorkItem:252614 - Merative Universal Access Responsive Web Application: IEG pages that contain conditional clusters with read-only expressions are not displayed

Issue Description:

An error message is displayed when trying to access IEG script pages that contain conditional clusters with read-only-expressions.User Interface Impact: No
Steps to Reproduce:

Update an IEG script to contain a conditional cluster with a read-only-expression.
In the Universal Access Responsive Web Application, apply for a benefit using that IEG script.
An error message is displayed: 'Something went wrong. Try again or go to home'.
Issue: The IEG pages that contain conditional clusters with read-only-expressions do not display.

Resolution:

IEG pages that contain conditional clusters with read-only-expressions are now successfully displayed.

WorkItem:252615 - Merative Universal Access Responsive Web Application: Mandatory questions that use arrays and check boxes do not show the client-side validation messages

Issue Description:

Mandatory IEG script questions with array type and check boxes do not show mandatory client-side field-level validation messages in the Universal Access Responsive Web Application.

**User Interface Impact: **No

Steps to Reproduce:

Update an IEG script to contain a question with array type and check boxes and mark that question as mandatory.
In the Universal Access Responsive Web Application, apply for a benefit by using that IEG script.
Progress to the page containing the check box question, do not select anything, and click 'Continue.
Issue: The mandatory server-side validation message is incorrectly displayed instead of the client-side field-level validation message.

Resolution:

Mandatory questions in IEG scripts with array type and check boxes now show client-side field-level mandatory validation messages.

PLAYER

PO08062, WorkItem:241804 - IEG does not use the full dialog width when Show Sections is disabled

Issue Description:

An Intelligent Evidence Gathering (IEG) script can be configured to not display sections, the effect of this results in content not expanding to the full width of the page.

User Interface Impact: No

Steps to Reproduce:

Create an Intelligent Evidence Gathering script with the attribute 'show-sections' set to false.
Login as an administrator.
Import and run the Intelligent Evidence Gathering script.
Issue: Content does not expand the full width of the page.

Resolution:

This issue was resolved by updating the associated CSS. Therefore for an Intelligent Evidence Gathering (IEG) script with the show-sections' set to false the content will now expand to the full width of the page

Technical:

The issue was resolved by updating the CSS class named no-sections. This class is applied to the HTML element with the ID page-content when an Intelligent Evidence Gathering script with the attribute 'show-sections' set to false is run. A width of auto is now applied in this scenario and margins have been adjusted so content expands the full width of the page.

PO08219, WorkItem:245663 - The Policy Type field overlaps the Policy Number field on the Insurance Summary page of the IEG Sample Script

Issue Description:

When an Intelligent Evidence Gathering script is configured with a Summary page to display a list with two fields, instead of wrapping, the text can stretch outside of its field causing it to overlap to the next field or move off the page.

User Interface Impact: No

Prerequisites:

Create an Intelligent Evidence Gathering script with a question page and a Summary page.
The question page should contain two questions, the Summary page should display answers to these questions in the form of a list with a field for each question's answer.

Steps to Reproduce:

Login as an administrator.
Click on the Administration Workspace tab.
Click on Scripts under Intelligent Evidence Gathering in the shortcuts panel.
Import and run the Intelligent Evidence Gathering script created above.
Enter a long answer to the first question.
Navigate to the Summary page.
Issue: On the Summary page, the long answer to the first question can overlap to the second answer.

Resolution:

This issue has been resolved by adding the word-break attribute to the fields in a list. A long answer to the first field will now wrap rather than overlapping onto the second field.

PO08311, WorkItem:247912 - When an Intelligent Evidence Gathering script configured not to display page titles is run in a modal, the print button does not work.

Issue Description:

When an Intelligent Evidence Gathering script is run in a modal with the property modal.hide.title.panel set to true, pages cannot be printed. The print button appears but does not function when selected.

User Interface Impact: No

Prerequisite(s):

Set the Intelligent Evidence Gathering configuration property modal.hide.title.panel to true.
Create an Intelligent Evidence Gathering script with a question page.

Steps to Reproduce:

Login as an administrator.
Click on the Administration Workspace tab.
Select Scripts under Intelligent Evidence Gathering in the shortcuts panel.
Click on Scripts.
Import and run your created Intelligent Evidence Gathering script in a modal.
Click Print.
Issue: A print dialog does not open, which means it's not possible to print the page.

Resolution:

The print button is now configured through JavaScript and a caseworker can now print on every page that the print button appears on.

Evidence Broker

PO08223, WorkItem:245861 - Income shares incorrectly from an Insurance Affordability integrated case to an Income Support integrated case despite the system determining that the evidence should not share

Issue Description:

When the following logically equivalent sharing configurations exist for sharing Income on an Insurance Affordability integrated case to evidence types on an Income Support integrated case

Income > Paid Employment
Income > Earned Income
Income > Benefit
Income > Unearned Income

and the system determines that only the Paid Employment > Earned Income business object should be created on the target, in line with the ShareWhen rule. Benefit and Unearned Income are also appearing on the Incoming Evidence screen even though the system initially determined that these should be ignored as the sharing rules for both types fail.

**User Interface Impact: **No

Prerequisite(s):

Login as a system administrator.
Click on Property Administration under Application Data in the shortcuts panel.
Search for a property with the name 'Advanced Evidence Sharing' and ensure its value is set to YES.
Login as an administrator.
Navigate to Evidence Sharing under Rules and Evidence in the shortcuts panel.
Configure a new evidence sharing configuration with the following details:
- Select Insurance Affordability as the source and Income Support as the target; and Integrated Case as both the source type and the target type.
- On the Add Logically Equivalent Evidence page of the wizard, select Income as the source evidence type and Paid Employment as the target evidence type.
- Share Verifications = Never, Trusted Source = No.
- Browse and upload the correct XML sharing file.
- Click Save & Exit.
Repeat step 3 for the other evidence mappings, uploading the appropriate XML sharing file for each one:
- Income > Earned Income
- Income > Benefit
- Income > Unearned Income

Steps to Reproduce:

Login as an Insurance Affordability caseworker.
Register a new Person.
Create a new Insurance Affordability application for the Person. Don't add any income as part of the application.
Authorise the application. This will create an Insurance Affordability integrated case.
Login as an Income Support caseworker.
Search for the Person created above.
Click on the Care and Protection tab.
Use the New Case page action to create an Income Support integrated case.
Login as an Insurance Affordability caseworker.
Go to the Insurance Affordability integrated case and create Income evidence. Add Income of type Wages and Salaries.
Activate the evidence.
Login as an Income Support caseworker and navigate to the Income Support integrated case.
Navigate to Incoming Evidence under the Evidence tab.
Issue: There is incoming evidence for Paid Employment > Earned Income, Benefit and Unearned Income when there should only be Paid Employment > Earned Income for the Wages and Salaries mapping. Wages and Salaries is not included in the ShareWhen mapping criteria for the Benefit or Unearned Income. evidence types.

Resolution:

This issue has been resolved and now when the above scenario is run, only Paid Employment > Earned Income is shared to the target case.

Technical:

The underlying problem here was that even though the system determined that sharing between Income and Benefit and Income and Unearned Income should have been ignored, as the sharing XML returned false from the ShareWhen clause, the delivery of the Paid Employment evidence threw an exception as some of the mandatory fields were not available. This forced the sharing to go down the resilience path. In this instance, the system action for Income to Benefit and Income to Unearned Income was updated to Caseworker Review. This is why these appeared in the Incoming Evidence screen.

The logic has been updated to not overwrite a system action of ignore when resilience is hit as part of evidence sharing. This means that in the above scenario, that neither Benefit nor Unearned Income will appear in the Incoming Evidence screen on the Income Support integrated case.

WorkItem:245979 - Income Support Earned Income types other than those configured to share to Insurance Affordability Income are appearing as in-edit on the target case

Issue Description:

For the logically equivalent sharing of Income Support Earned Income to Insurance Affordability Income, Earned Income types other than the one configured for sharing, which is Wages and Salaries, are being shared to the target case as In-Edit with a blank Income Type.

User Interface Impact: No

Prerequisite(s):

Login as an administrator.
Navigate to Evidence Sharing under Rules and Evidence in the shortcuts panel.
Configure a new evidence sharing configuration with the following details:
- Select Income Support as the source and Insurance Affordability as the target; and Integrated Case as both the source type and the target type.
- On the Add Logically Equivalent Evidence page of the wizard, select Earned Income as the source evidence type and Income as the target evidence type.
- Share Verifications = Never, Trusted Source = Yes.
- Browse and upload the sample XML file from DeveloperWorks (CGISSEarnedIncome_HCRIncome.xml). This file maps income type of 'Wages and Salaries' only.
- Click Save and Exit.

Steps to Reproduce:

Login as an Income Support caseworker.
Register a new Person.
Create a new Employment record for the person, with a start date in the past.
Select the Care and Protection tab and click on the New page action.
Create a new Income Support integrated case for the Person and add the following evidence:
- Household Member
- Head of Household
- Living Arrangement
Add Paid Employment evidence to the case to reflect the person's employment.
Add Earned Income of type Bonus and associate it with the Paid Employment.
Activate the evidence.
Login as an Insurance Affordability caseworker.
Search for the Person created above.
Select the Care and Protection tab and click on the New page action.
Create a new Insurance Affordability integrated case for the Person.
Issue: In-Edit Income evidence with a blank Income Type exists on the Insurance Affordability integrated case. This evidence should not have been shared as the sharing rules are only configured to share Earned Income of type Wages and Salaries.

Resolution:

This issue has been resolved and now Earned Income on an Income Support integrated case will only be shared to Income on Insurance Affordability integrated case when the income type is Wages and Salaries, and when the sample XML configuration referenced above is used.

Technical:

The underlying problem here is that there were two Evidence Mapping configurations specified in the logically equivalent XML, one for the parent evidence of Paid Employment and one for the child evidence of Earned Income. When processing this XML configuration, the system determined that there were two sharing rules, again one per evidence type, parent and child. However, the system could not determine categorically which sharing rule applied to which evidence type as the processing matched on the target evidence type and not on source evidence type.

PO08368, WorkItem:249044 - Unhandled server exception occurs on Income Support case when activating Pregnancy and Unborn Child evidence which was shared from Insurance Affordability case and added from the Incoming Evidence list page

Issue Description:

When logically equivalent sharing occurs between Pregnancy on an Insurance Affordability integrated case to Pregnancy > Unborn Child on an Income Support integrated case, an unhandled server exception is encountered when activating the evidence after adding it from the Incoming Evidence screen.
User Interface Impact: No
Prerequisitie(s):

Login as an administrator.
Navigate to Evidence Sharing under Rules and Evidence in the shortcuts panel.
Configure a new evidence sharing configuration with the following details:
- Select Insurance Affordability as the source and Income Support as the target; and Integrated Case as both the source type and the target type.
- On the Add Logically Equivalent Evidence page of the wizard, select Pregnancy as the source evidence type and Pregnancy as the target evidence type.
- Share Verifications = Never, Trusted Source = No.
- Browse and upload the correct XML sharing file.
- Click Save and Exit.

Steps to Reproduce:

Login as an Insurance Affordability caseworker.
Register a new Person.
Create a new Insurance Affordability application case for the Person. Don't specify any income.
Authorise the application case; an Insurance Affordability integrated case is created.
Login as an Income Support caseworker.
Submit an Income Support application for the Person registered above, for Medical Assistance with no income, but with benefit type Medicare Part A.
Check eligibility and activate the evidence.
Authorise the application.
Add Pregnancy evidence on the Insurance Affordability integrated case and activate it.
Navigate to the Income Support integrated case and add the incoming Pregnancy > Unborn Child evidence.
Activate the evidence on the Income Support integrated case, making sure to select Pregnancy and Unborn Child.
Issue: An unhandled exception is encountered when activating the evidence.

Resolution:

This issue has been resolved and it's now possible to activate Pregnancy and Unborn Child evidences on an Income Support case after they have been added to the case through from the Incoming Evidence screen.

Technical:

This problem here was caused by the Create action in the XML mapping between Pregnancy on Insurance Affordability and Pregnancy on Income Support. The Create action was incorrectly adding the Unborn Child evidence directly to the case even when Trusted Source was set to No. This creates a relationship between the incoming Pregnancy evidence and the Unborn Child evidence on the in-edit screen. When the Pregnancy record is added to the case it gets a new Evidence Descriptor. As the Unborn Child is already on the case and associated with an Evidence Descriptor that is not active or in-edit, it is effectively orphaned and neither the Unborn Child nor the Pregnancy can be activated.
To overcome this issue, the logic has been updated so that the Unborn Child evidence is given the same system action as its parent, Pregnancy, if that system action was CASEWORKER_REVIEW or MANUAL_INTERVENTION. With this fix in place, it is now possible to add both the Pregnancy and Unborn Child from the Incoming Evidence screen, and to activate them successfully.

PO08324, WorkItem:249275 - Evidence is being shared to both in-edit and active on an integrated case when using the application authorisation strategy

Issue Description:

An issue occurs when multiple programs are configured on a single application case which is configured to use an application level authorisation strategy. Following this strategy, when an application case gets authorised, duplicate evidence records are shared to the target Integrated Case.
User Interface Impact: No

Prerequisites:

Application Case has evidence types A, B, C and D associated with it.
Program 1 - Evidence types A, B and C are associated with this program.
Program 2 - Evidence types A, B, C and D are associated with this program.
Authorisation Strategy is 'Application'.
The integrated case has evidence types A, B, C and D associated with it.
There is evidence sharing set up between the application case and integrated case for the 4 evidence types.
Product X (i.e. the Product Delivery) to deliver Program 1 has no evidence associated with it.
Product Y (i.e. the Product Delivery) to deliver Program 2 has no evidence associated with it.

Steps to Reproduce:

Login as a caseworker.
Register a person.
Create a new application.
Add both programs to the application.
Add all 4 evidence types to the application.
Authorise the application.
Navigate to the Evidence tab on the newly created Integrated Case.
Issue: Evidence is shared to the Integrated Case as both active and in-edit.

Resolution:

This issue has been resolved and evidence is no longer duplicated on the integrated case during authorisation.

Technical:

During authorisation of an application case, evidence that is configured for sharing is pushed to the target case using the Evidence Sharing Push Workflow. When a person is added to a case, evidence that is configured for sharing is pulled onto the case using the Evidence Sharing Pull Workflow. A push and a pull happening at the same time cause evidence to be duplicated on the target integrated case. The authorise logic has been updated to prevent a pull from being triggered when evidence is already being pushed from that same authorisation.

PO08413, WorkItem:250190 - Logically equivalent evidence updates between Insurance Affordability and Income Support integrated cases are being shared back and forth endlessly

Issue Description:

Logically equivalent evidence is being shared back and forth endlessly between an Insurance Affordability integrated case and an Income Support integrated case.

User Interface Impact: No

Related WorkItem(s): 250212

Prerequisite(s):

Login as system administrator and click on Property Administration under Application Data in the shortcuts panel.
Search for a property with the name 'Advanced Evidence Sharing' and ensure its value is set to YES.
Now navigate to Code Tables under Application Data in the shortcuts panel.
Search for the LivingArrangementType code (default value is Home).
Use the New Item row level action to create a new code-table entry with the values:
- Item Name set to Incarceration.
- Technical ID (Code) set to LA10000, for example.
- Click Save.
Publish the changes.
Login as an administrator and navigate to Evidence Sharing under Rules and Evidence in the shortcuts panel.
Configure a new evidence sharing configuration with the following details:
- Select Income Support as the source and Insurance Affordability as the target; and Integrated Case as both the source type and the target type.
- On the Add Logically Equivalent Evidence page of the wizard, select Living Arrangement as the source evidence type and Incarceration as the target evidence type.
- Share Verifications = Never, Trusted Source = No.
- Browse and upload the correct XML sharing file, the key aspect being the ShareWhen which determines that sharing should occur when the Living Arrangement Type is set to Incarceration. There is also a Set action for creating Incarceration evidence on the target with default values specified for Charge Status (Convicted) and Incarceration Status (Incarcerated).
- Click Save and Exit.
Create a second evidence sharing configuration with the following details:
- Select Insurance Affordability as the source and Income Support as the target; and Integrated Case as both the source type and the target type.
- On the Add Logically Equivalent Evidence page of the wizard, select Incarceration as the source evidence type and Living Arrangement as the target evidence type.
- Share Verifications = Never, Trusted Source = No.
- Browse and upload the correct XML sharing file, the key aspect being a Set action which determines the creation of Living Arrangement evidence on the target with a default value specified for the Living Arrangement Type (Incarceration). There is also a maintenance style set on the XML of ENDDATE.
- Click Save and Exit.

Steps to Reproduce:

Login as an Income Support caseworker.
Register a new Person.
Create a Medical Assistance application for this Person, specifying the Living Arrangement to Home.
Submit the application and check eligibility.
Clear verifications and authorise the product delivery.
Activate the product delivery.
Login as Insurance Affordability caseworker and create an application for the same Person.
Authorise the application; this results in an Insurance Affordability integrated case being created.
Login as an Income Support caseworker.
End date the existing living arrangement using yesterday's date and add a new living arrangement starting the following day (today) of type Incarceration.
Activate the evidence.
Login as an Insurance Affordability caseworker.
Navigate to Incoming Evidence under the Evidence tab on the Insurance Affordability integrated case.
For the Incarceration evidence, select Add to Case. Once added to the case, activate the evidence.
Login as an eligibility worker and navigate to the Incoming Evidence on the Income Support integrated case.
Issue: The Incarceration evidence appears on the Income Evidence screen.

Resolution:

This issue has been resolved. Now when the Incarceration evidence is added to the Insurance Affordability case and activated, the evidence is not shared back to the Income Support integrated case.

Technical:

There were two issues that needed to be addressed when fixing this issue:

The first was a defect in the schema (AESXMLSchema.xsd) which prevented the uploading of the logically equivalent XML file for the sharing configuration of Living Arrangement to Incarceration. This is covered in the Related WorkItem referenced above.
The second was the fact that even though the system links the evidence when it's first shared, on subsequent sharing Ignore (Linked) is initially determined to be the system action but this is effectively discarded because the sharing is logically equivalent. The system then behaves like this is the first time the evidence is being shared.

To address the second point above, a further sanity check is performed to determine if the target entity has the same default values that are specified in Set action in the logically equivalent XML. If they are, then the Ignore (Linked) system action is persisted and no sharing will occur.

PO08415, WorkItem:250212 - Validation issue when trying to upload logically equivalent XML for evidence sharing

Issue Description:

When configuring evidence sharing, it's not possible to upload logically equivalent XML which contains a 'Set' action with more than one parameter specified. These parameters are used for defaulting values on the target entity during logically equivalent sharing, which can arise when the data isn't available from the source evidence. At least one parameter must be specified in the 'Set' action, and the schema to which the XML adheres, and which it's validated against, should allow for multiple parameters, not just one.

User Interface Impact: No

Steps to Reproduce:

Login as an administrator.
Navigate to Evidence Sharing under Rules and Evidence in the shortcuts panel.
Configure Logically Equivalent sharing between two evidence types on two case types.
Now browse and select a sharing XML file that contains a Set action with more than one parameter specified.
Click Save & Exit.
Issue: An exception is thrown and it's not possible to save the configuration.

Resolution:

This issue has been resolved and it's now possible to complete the configuration for logically equivalent sharing when there is more than one parameter specified for a Set action.

Technical:

The underlying problem was that maxOccurs was not specified for the parameter element for Set within the logically equivalent XML, and this defaults to 1. The issue has been addressed by including maxOccurs on the parameter element and setting it to 'unbounded'.

WorkItem:251097 - On the Incoming Evidence screen, it is not possible to remove a business object if part of the object has no action available

Issue Description:

When sharing evidence, it is not possible to remove a business object from the Incoming Evidence screen if part of the object has no action available because it is identical to what is already on the case.

User Interface Impact: No

Prerequisite(s):

Login as an administrator.
Navigate to Evidence Sharing under Rules and Evidence in the shortcuts panel.
Configure Evidence Sharing with Trusted Source set to No between two case types, A and B, that have Student and Student Expense evidence associated with them
Click Save and Exit.

Steps to Reproduce:

Share the first time:

Login as a caseworker.
Register a new Person.
Create an instance of case A for the Person.
Create an instance of case B for the Person.
Add Student and Student Expense evidence to case A.
Activate the evidence.
Navigate to the Incoming Evidence screen of case B.
For both the Student and Student Expense, select Add To Case.
Activate the evidence.

Share the second time:

On case A, add a new Student Expense record and associate it with the existing Student evidence.
Activate the evidence.
Navigate to the Incoming Evidence screen of case B.
Action the Student Expense records.
Issue: The actions are greyed out on the Student parent evidence, which means it is identical to the Student evidence already on the target case. After resolving the Student Expense records, it is not possible to remove the business object from the Incoming Evidence screen as the status of the Student record is 'Identical Shared In-Edit'.

Resolution:

This issue has been resolved and it is now possible to remove a business object when a part of the object has no actions available because it is identical to what is present on the target case.

Technical:

When presenting evidence on the Incoming Evidence list, a check is performed to see if the Incoming Evidence is identical to what is already on the target case. If it is identical, then the actions are greyed out on the incoming record. As part of this check, the status of the Incoming Evidence record is also changed from 'Identical Shared In-Edit' to 'Identical Shared Discarded'. This results in a caseworker being able to remove the business object when the other elements of the business object have been resolved.

Solutions

Income Support

MEDICAL ASSISTANCE

WorkItem:251711 - APIs to support HCR Change of Circumstance (CoC) processing on an Merative Universal Access Responsive Web Application

Merative Social Program Management Health Care Reform (HCR) includes Change of Circumstance (CoC) processing that allows the citizen to create and submit a CoC application through the Merative Universal Access Application citizen portal.
To support the ability to implement HCR CoC processing on the Merative Universal Access Responsive Web Application, the following APIs are now available for use.

The APIs enable the key business functions that form part of the Merative Social Program Management Health Care Reform (HCR) Change of Circumstance (CoC) processing, including the ability for a citizen to view their existing information and initiate an update to the information.

Note that the APIs do not cover the entire set of use cases that may be required to fully implement HCR CoC processing on the Merative Universal Access Responsive Web Application.

The following four APIs are available for use:

GET /hcr/information_summary
Returns a summary of personal and household information for the applicant, and whether they have other change of circumstances, life events, or health plan renewals in progress.

POST /hcr/change_of_circumstance_form
Starts a change of circumstance form.

POST /hcr/change_of_circumstance_form/motivation
Creates a motivation and runs the corresponding eligibility determination, based on the answers that are provided in the change of circumstance form.

POST /hcr/change_of_circumstance_form/sign_and_submit
Creates an e-signature for the change of circumstance form and submits the form to the agency.

For full specification details for the four new HCR Change of Circumstance (CoC) APIs, please see the Social Program Management Swagger specification, which is available from a running Social Program Management instance at http://<hostname>:<port>/Rest/api/definitions/v1.

Child Welfare

PO03296, PO03339, WorkItem:122585 - When a Child Welfare case is closed, the closure reason is not displayed in the Status History page

Issue Description:

When a Child Welfare case is closed, the closure reason is not displayed in the Status History page.
User Interface Impact: No

Steps to Reproduce:

Login as a Child Welfare caseworker.
Navigate to Cases and Plans.
Click on Register Person and Create Case under Cases in the shortcuts panel.
Register a Person and select Ongoing Case from the Type drop-down.
Select Close Case from the tab level actions menu.
Select a Reason and add Comments.
Click Save.
Go to the Administration tab and select Status History.
Issue: The closure reason is not displayed.

Resolution:

The Status History list page has been updated so that the closure reason now displays prepended to the comments in the Comments field.

WorkItem:224370 - The Child Welfare New Intake and Edit Basics modals have some truncation, alignment and scroll bar issues

Issue Description:

The Child Welfare New Intake and Edit Basics modals have Date fields that are truncated and not aligned correctly. An unnecessary scroll bar is shown when a menu item from the Category drop-down is selected.
**User Interface Impact: **Yes
Steps to Reproduce:

Log in as a Child Welfare intake worker.
From the Home page click on New Intake.
Issue 1: The Date field on the New Intake modal is truncated and not aligned correctly.
Select the Child Protection Services category.
Issue 2: The Types data area is resized to an even larger box causing an unnecessary scroll bar in order to reach the input fields now hidden at the bottom of the modal.
Save the Intake. In the Basics tab of the Assistant page click the Edit page action control.
Issue 3: The Date field on the Edit Basics modal is truncated and not aligned correctly.

Resolution:

The following changes have been made to the New Intake and Edit Basics modals:

The top padding has been updated to 4 pixels for transfer list and drop-down list menu items.
The New Intake and Edit Basics modal height and field alignments have been updated in line with the populated modal details.
The style CSS of the Date field has been updated for alignment of the field and to remove truncation within the Date field when populated.

Technical Detail:

To resolve this issue the padding-top and padding-bottom has been reduced to '4 px' by overwriting the style within CCSIntakeStyle.css for

body.curam.soria table.transfer-list select option,
body.curam.soria select.codetable option
{ padding-bottom: 4px; // other properties }

The modal height has been changed to ‘430’ to remove the modal outer scroll bar in CSSIntake_basicCreate.uim
Updated the Date field alignment and truncation of the date content. This has been applied by updating the style using specific selectors for the individual pages

@media screen and (max-width:770px) {
body#Curam_CCSIntake_basicCreate .date-time-exists {
width:200%;
display:table-row;
}
body#Curam_CCSIntake_basicModify .date-time-exists {
width:200%;
display:table-row;
}
body#Curam_CCSIntake_homeEditBasic .date-time-exists {
width:200%;
display:table-row;
}
}

The Method and Date fields have been updated in the CSSIntake_basicCreate.vim, CCSIntake_basicModifyInfo.vim and CSSIntake_homeEditIntakeBasicInfo.vim pages to align with the length with the date field
The height and width updates have been applied to the CSSIntake_basicCreate.uim, CCSIntake_basicModify.uim and CSSIntake_homeEditIntakeBasic.vim pages

WorkItem:232481 - The Child Welfare 'New Placement Request' and 'Edit Placement Request' modal dialogs contain fields with truncated contents and lists that are hard to distinguish

Issue Description:

The Child Welfare 'New Placement Request' and 'Edit Placement Request' modal dialogs contain fields with truncated contents and lists that are hard to distinguish.

User Interface Impact: Yes

Steps to Reproduce:

Log in as a Child Welfare intake worker.
Register a child.
Create an Ongoing case from the child's home page.
From the Ongoing case 'Removals and Placements' tab, select 'Placement Requests'.
Click on 'New'.
Issue 1: The 'New Placement Request' modal dialog date fields and Status dropdown can show truncated values depending on what the user enters into them.
Issue 2: The 'New Placement Request' modal dialog contains two lists displayed side by side that are hard to distinguish.
Save the placement request.
Select Edit from the placement row actions menu.
Issue 3: The 'Edit Placement Request' modal dialog date fields and Status dropdown can show truncated values depending on what the user enters into them.
Issue 4: The 'Edit Placement Request' modal dialog contains two lists displayed side by side that are hard to distinguish.

Resolution:

To address this issue, the following changes have been made to these modal dialogs:

The dialog heights have been increased.
The label width on some clusters has been increased where necessary.
They have been restructured by removing unnecessary clusters.
The styling of some clusters has been updated to remove unnecessary whitespace.

Technical Detail:

The following files have been updated:

webclient\components\ChildServices\Fostercare\Placement\
CCSPlacement_createChildPlacementRequest.uim
webclient\components\ChildServices\Fostercare\Placement\
CCSPlacement_modifyChildPlacementRequest.uim

PO08198, WorkItem:245078 - Some fields in the Child Welfare Incident context panel are not aligned or only partially visible

Issue Description:

Some fields in the Child Welfare Incident Context Panel are not aligned or only partially visible and long 'Reported by' usernames are not truncated with an ellipsis.

User Interface Impact: Yes

Prerequisite(s):

Set display to the minimum recommended screen resolution of 1366x768.

Steps to Reproduce:

Login as the resource manager supervisor user.
Open the Shortcuts panel and click My Providers.
Open a Provider by clicking a Reference link in the list of providers displayed.
Select the Incidents tab and click the New page action control.
Enter the mandatory information in the New Provider Incident modal.
Enter a long username in the Name field under the 'If the reported is not registered on the system please enter the details below.' guidance field.
Click the Save button.
Issue 1: On the Incident context panel some fields are not aligned and fully visible.
Issue 2: On the Incident context panel long 'Reported by' usernames are not truncated with an ellipsis.

Resolution:

All the fields in the Child Welfare Incident Context Panel are now correctly aligned and visible. Long 'Reported by' usernames are now truncated with an ellipsis and a tooltip is displayed with the full username when hovered over.

Technical Details:

A new stylesheet has been added to resolve this issue:

webclient/components/ChildServices/css/
cfss-incident-context-panel.css

PO08206, WorkItem:245090 - An unhandled server exception is thrown on the placements list page when creating a placement within an Outcome Plan in a customized environment

Issue Description:

Within the Child welfare module, the default product behavior is for an Investigation case to be created after an Intake is screened in and approved, and then for placements to be created within the Investigation case. For customers who have customized the Child Welfare module to create an Outcome Plan rather than an Investigation case after the Intake is screened in and then allow the user to create placements within the Outcome Plan, an unhandled server exception is thrown after the user creates a new placement and navigates to the placements list page.

Prerequisite(s):

The child welfare functionality must be customized so that Outcome Plans are created instead of Investigation cases.

User Interface Impact: No

Steps to Reproduce:

Create the Intake:

Login as a Child Welfare intake worker.
Register a new Person under 18 years of age.
Click on New Intake under Intakes in the shortcuts panel.
Select Child Protection Services as the category and click Save.
Click on the Participants tab and select the New Participant page action.
Enter the first name and last name of the Person registered above, and choose Alleged Victim as the Role.
Click Next.
For the entry returned on the Potential Matches page, select Exact Match and click Finish.
Select the New Reporter page action on the Participants page.
On the Capture Report page, select Anonymous as the Type and click Finish.
Click on the Allegations tab and select the New page action.
Choose the registered Person as the Alleged Victim, Physical Abuse as the Type and check Unknown Maltreater.
Click Save.
Open the intake using the Open Intake tab menu.
Click on the Recommendation tab and select the Capture page action menu.
Record a Screened-In recommendation and click Submit.

Approve the Intake:

Login as a Child Welfare intake supervisor and click on the approval task in the Available Tasks pod.
On the task home page, click on the Make Decision primary action.
Click Approve on the Make Decision modal.
Enter comments on the Approve Recommendation page and click Save.

Create the Investigation:

Login as a Child Welfare investigator.
Click on the task in the Available Tasks pod.
Click on the Create Investigation primary action on the task home page.
Click Start on the Start Investigation page; at this point, the custom functionality comes into play.
On the Outcome Plan home page, click on the Placements tab and select the New Removal page action.
Select Court as the Type, Physical Abuse as the Reason and Case and Protection Petition as the Sub Type.
Click Save and Place.
On the New Placement page, select Foster Care as the Type and click Next.
Search for a Provider on the Provider Search page.
Select a Provider and click Finish.
Issue: An unhandled server exception is thrown.

Resolution:

This issue has been resolved and it is now possible to add a placement to an Outcome Plan without an unhandled server exception being thrown.

Technical:

The underlying problem here was that the API 'curam.placement.sl.impl.FamilyServicesPlacement.list
FamilyServicesPlacementsByCaseIDConcernRoleID1()' called the facade 'curam.core.facade.impl.Case.listRelationship
ForCaseMember1()'. There is some logic in this facade operation which assumes that the underlying case is an integrated case, and this is what resulted in the unhandled server exception being thrown, as the underlying case is an Outcome Plan.

The issue has been addressed by updating 'curam.placement.sl.impl.FamilyServicesPlacement.list
FamilyServicesPlacementsByCaseIDConcernRoleID1()' to retrieve the case members through an alternative mechanism.

PO08266, WorkItem:246404 - If a participant is added to an Intake with either a '/' or '[' in their name, unexpected behaviour is observed

Issue Description:

On a Child Welfare Intake case, the system doesn't allow a participant with a name containing a '/' or '[' character to be added to the case. For a name containing the '/' character, the system creates a new Prospect Person and adds this new person to the Intake case. And for a name containing the '[' character, the system throws an application error.
**User Interface Impact: **No

Steps to Reproduce:

Scenario 1

Login as a Child Welfare intake worker.
Register a Person with first name 'James' and last name 'Smith/Smithwick'.
Create a new Intake case.
Select the Participants tab and click on the New Participant page action.
Search for a participant with first name of 'James' and Role of Adult.
Click Next.
Select the Exact option in the drop-down, next to 'James Smith/Smithwick'.
Click Finish.
Issue: The system registers a new Prospect Person and adds them to the Intake case.

Scenario 2

Login as Child Welfare intake worker.
Register a Person with first name 'James' and last name 'Smith[Smithwick'.
Create a new Intake case.
Select the Participants tab and click on the New Participant page action.
Search for a participant with first name of 'James' and Role of Adult.
Click Next.
Issue: The system throws an application error.

Resolution:

It is now possible to add a participant to an Intake case whose name contains a '/' or '[' character.

PO08348, WorkItem:248771 - Description field label is wrapping in the Attachments page of the Child Welfare Capture Contact Log wizard dialog

Issue Description:

The Description field label is wrapping in the Attachments page of the Child Welfare Capture Contact Log wizard dialog which also causes an unnecessary scroll bar to be displayed.

User Interface Impact: Yes

Steps to Reproduce:

Log in as a Child Welfare caseworker.
Select Cases and Outcomes tab and from the shortcuts panel, select Capture Contact Log from the Cases section.
Enter the details in the steps of the wizard until you reach the Attachments page.
Issue: The Description field label is displayed wrapping to a second line and a scroll bar is displayed on the modal.

Resolution:

This issue was resolved by increasing the width and removing the height from the last step on the Capture Contact Attachment wizard. It is displayed to the user with the default height. Additionally, the additional four pages of the wizard modal width have been updated to the width 'width=825' for consistency across wizard pages. The height on all pages has been removed relying on the page content to define the height except the narrative page where the height is required to display the narrative field in full.

Technical:

The CFSSContactLogWizard_addAttachments.uim file was updated so that its width was increased and its height removed, thereby removing the label wrapping issue. For consistency the remaining pages of the modal height and witdth updates have been applied to CFSSContactLogWizard_selectConcerns.uim, CFSSContactLogWizard_addContacts.uim, CFSSContactLogWizard_addNarrative, CFSSContactLogWizard_addParticipants.

PO08190, WorkItem:248900 - Vertical scrollbars are visible on Child Welfare case context panels when using the minimum recommended screen resolution

Issue Description:

A vertical scroll bar is visible on the context panels of Child Welfare Adoption, Ongoing with multiple participants, and Investigation cases when using the minimum recommended screen resolution of 1366x768.

User Interface Impact: Yes

Prerequisite(s):

Set display to the minimum recommended screen resolution of 1366x768.

Steps to Reproduce:

Scenario 1: Adoption Case

Login as a Child Welfare caseworker.
Create an Adoption Case.
Issue: Observe a vertical scroll bar on the Adoption Case Context panel.

Scenario 2: Ongoing Case with multiple participants

Login as a Child Welfare caseworker.
Create an Ongoing Case with multiple participants under the age of eighteen.
Issue: Observe a vertical scroll bar on the Ongoing Case Context panel.

Scenario 3: Investigation Case

Login as a Child Welfare Intake worker.
Create a new Child Protection Services intake.
Click the Participants tab and add a minimum of 2 participants to the intake (one with the Alleged Victim Role and the other as the Alleged Maltreater Role).
Create an allegation from Allegation tab.
Select Open Intake from the tab action menu.
Click the Recommendation tab and select Capture from the page action menu.
Select Screened In as the Recommendation and Submit.
Login as a Child Welfare Intake supervisor
From the Child Welfare Intakes pod open the intake that was submitted for approval.
Click the Recommendation tab and select Approve from the page action menu, enter the details and Save.
Login as Child Welfare Intake investigator.
From the Available Task pod click on the link to start an investigation for the intake that was approved.
Click on the Create Investigation link in the Primary Action section of the Home page.
In the Start Investigation modal select all participants listed and click the Start button.
Issue: Observe a vertical scroll bar on the Investigation Case Context panel.

Resolution:

****This issue has been resolved by increasing the height of the relevant context panels so that there is more space for the horizontal scroll bar when the contents of the panel exceeded the screen width.

Technical Details:

Changes have been made to the following:

/CFSS/EJBServer/components/ChildServices/source/curam/
cfss/ccs/common/facade/impl/CCSDetailsPanel.java
/CFSS/EJBServer/components/ChildServices/tab/Adoption/
CCSPreAdoptionCaseHome.tab
/CFSS/EJBServer/components/ChildServices/tab/Investigation/
CCSInvestigationHome.tab
/CFSS/EJBServer/components/ChildServices/tab/Ongoing/
CCSOngoingCaseHome.tab
/CFSS/EJBServer/components/ChildServices/tab/Person/
CCSPersonHome.tab
/CFSS/EJBServer/components/ChildServices/tab/ProspectPerson/
CCSProspectPersonHome.tab
/CFSS/webclient/components/ChildServices/css/cfss-adoption-
case-context-panel.css
/CFSS/EJBServer/components/ChildServicesSDM/tab/
Investigation/SDMInvestigationHome.tab
/CFSS/webclient/components/ChildServices/css/cfss-
investigation-case-context-panel.css

WorkItem:248999 - Layout issues on the Close Case and New Placement Request modal dialogs opened within Ongoing or Adoption cases

Issue Description:

When the Close Case modal dialog is opened from within an Ongoing or Adoption case the Sensitivity label is wrapped to a new line. Additionally, the menu items on the Status dropdown field on the New Placement Request modal dialog are clipped.

**User Interface Impact: **No

Steps to Reproduce:

Login as a Child Welfare caseworker.
Navigate to an existing Ongoing or Adoption case.
From the tab actions menu select Close Case. The Close Case modal dialog is displayed.
Issue: The Sensitivity label is wrapped to a new line.
From the tab actions menu select New Placement Request. The New Placement Request modal dialog is displayed.
Issue: The menu items on the Status dropdown field are clipped.

Resolution:

The width of the Close Case modal dialog has been increased so that the Sensitivity field does not wrap. The width of the Status dropdown field on the New Placement Request modal dialog has been increased so that it is displayed correctly.
Technical details:

Updates made to following files:

webclient/components/ChildServices/CaseManager/
CaseClosure/CCSCaseClosure_createClosure.uim
webclient/components/ChildServices/FosterCare/
Placement/CCSPlacement_createChildPlacementRequest.uim

PO08372, WorkItem:249370 - When creating a new participant within an Intake, it is possible to select more than one existing registered person as an exact match

Issue Description:

When adding a new participant to an Intake case, the participant's details are checked to see if there are any potential matches with existing registered persons or prospect persons in the system. If there are potential matches, a list of registered persons and prospect persons are returned and for each resulting person, the user can choose whether the participant is an exact match or a probable match by selecting a value from a drop-down menu in the list row. If a person is chosen as an exact match, the intake worker is still able to select additional persons as exact matches.
User Interface Impact: No

Steps to Reproduce:

Login as a Child Welfare intake worker.
Register 3 people using the exact same name for each.
Create an Intake.
Add a participant to the Intake, entering the same first name used in Step 2 above. Also enter the participant's role.
Navigate to the Potential Matches wizard page, where the 3 people registered previously will be listed.
Select Exact from the drop-down menu in the first list row.
Select Exact from the drop-down menu in the second list row.
Issue: The intake worker is able to select more than one registered person as an exact match.

Resolution:

When a user selects Exact from the drop-down menu on the Potential Matches wizard page, the drop-down menus for other potential matches are disabled, preventing the user from selecting more than one exact match.

PO08381, WorkItem:249520 - Child Welfare Case Search page is missing its page title

Issue Description:

When a Child Welfare intake worker navigates to the Child Welfare Case Search page, the page title is missing. This means that a screen reader is not able to read the page title of this page for visually impaired users.

User Interface Impact: No

Steps to Reproduce:

Login as a Child Welfare intake worker.
Click on Child Welfare Search under Searches in the shortcuts panel.
Issue: The Child Welfare Case Search page is missing its title, as no property for the title exists in the associated properties file for the page.

Resolution:

The correct page title, Child Welfare Case Search, has been added to the search page.

Technical:

Changes were required to the following artefacts. A property was added to the properties file and this is referenced in the UIM.

../webclient/components/CFSSCommon/Search/Case/
CFSSCase_search.uim
../webclient/components/CFSSCommon/Search/Case/
CFSSCase_search.properties

PO08380, WorkItem:249553 - The formatting and text of rich text content pasted into the Intake narrative of a Child Welfare case does not display correctly.

Issue Description:

When creating an Intake users are unable to paste rich text content into the Intake Narrative field. Additionally, when the Intake is opened, the Narrative displays just the first few characters of the text.

User Interface Impact: No

Steps to Reproduce:

Login as a Child Welfare intake worker.
Create an Intake of category Child Protection Services.
Copy and paste rich text into the Narrative field for example some data from a Microsoft Excel spreadsheet.
Save the Narrative.
Issue: The rich text does not get saved in tabular format.
Click on the Participants tab and add a Participant.
Open the intake using the Open Intake tab action.
Issue: The rich text copied into the Narrative field does not get displayed in the Intake narrative section.

Resolution:

A new property 'config.allowedContent' has been added to the narrative configuration to allow the copy and pasting of tables from word and excel.

WorkItem:249563 - The Comments label on the Child Welfare Close Investigation modal is wrapping to a new line

Issue Description:

When a Child Welfare investigator closes an investigation case the Comments label on the modal is wrapping to a new line.

**User Interface Impact:**No

Steps to Reproduce:

Login as a Child Welfare Intake worker.
Create a new Child Protection Services intake.
Click the Participants tab and add a minimum of 2 participants to the intake (one with the Alleged Victim Role and the other as the Alleged Maltreater Role).
Create an allegation from Allegation tab.
Select Open Intake from the tab action menu.
Click the Recommendation tab and select Capture from the page action menu.
Select Screened In as the Recommendation and Submit.
Login as a Child Welfare Intake supervisor
From the Child Welfare Intakes pod open the intake that was submitted for approval.
Click the Recommendation tab and select Approve from the page action menu, enter the details and Save.
Login as Child Welfare Intake investigator.
From the Available Task pod click on the link to start an investigation for the intake that was approved.
Click on the Create Investigation link in the Primary Action section of the Home page.
In the Start Investigation modal select all participants listed and click the Start button.
From the investigation case select the Allegations tab and click the Dispose Allegations page action control.
Select the participant checkbox, Substantiated from the Disposition drop-down menu and Save.
Click on the Contacts tab and click the New Contact page action control.
Enter the mandatory information in the New Contact wizard and click the Finish button.
Select Close Investigation from the tab action menu.
Issue: The Comments label on the Close Investigation modal is wrapping to a new line.

Resolution:

The width of the Close Investigation modal was increased so that the Comments label no longer wraps.

Technical:

Changes made in:

webclient/components/ChildServices/Investigation/
CCSInvestigation_close.uim

PO08421, WorkItem:250155 - When viewing participants using the Child Welfare Intake assistant, the page title is missing and there is an incorrect label on the Provider cluster

Issue Description:

When a Child Welfare intake worker opens a new Intake and navigates to the Participants page of the Intake assistant, the page title is missing. An additional issue on this page is the cluster title Provider is mislabeled as a singular noun.

User Interface Impact: No

Steps to Reproduce:

Login as a Child Welfare intake worker.
Create a new intake.
Select the Participants tab on the Intake assistant.
Issue 1: The page has no page title.
Issue 2: The cluster title Provider is mislabeled as a singular noun.

Resolution:

When a Child Welfare intake worker opens a new Intake and navigates to the Participants tab of the Intake assistant, a page title labeled Participants is now visible on this page. Additionally, the cluster title Provider has been updated to Providers.

Technical:

Changes made in:

webclient/components/ChildServices/IntakeAssistant/
CCSIntakeAssistant_listParticipantDetails.properties
webclient/components/ChildServices/IntakeAssistant/
CCSIntakeAssistant_listParticipantDetails.uim
webclient/components/ChildServices/IntakeAssistant/
CCSIntakeAssistant_listParticipantsView.properties

PO08425, WorkItem:250440 - During intake, the New Contact wizard does not list all participants if the primary client is changed on a day after the participants have been initially created

Issue Description:

When a new Intake is created, the first Intake participant that is added is identified as the primary client for the Intake. If multiple Intake participants are added to an Intake, for example, both an Alleged Victim and an Alleged Maltreater, and a different participant is then selected to become the primary client in the days following the creation of the Intake, then all participants are not listed during the New Contact creation process.

User Interface Impact: No

Steps to Reproduce:

Login as a Child Welfare intake worker.
From the shortcuts panel, select New Intake.
Set the Category to Child Protection Services and click Save.
Select the Participants tab and select New Participant from the page action menu.
Enter the First Name of the participant and select Role as Alleged Maltreater.
Click Next and then click Finish. The first intake participant is set to be the primary client of the Intake.
Create another participant and select Role as Alleged Victim.
Click Next and then click Finish.
Roll the server forward to the following day.
Edit information about the second intake participant and set this participant to now be the primary client. Click Save.
Open the Intake by clicking on the Open Intake tab action.
Select the Contacts tab on the Intake and click on the New Contact page action.
Enter contact details on the first page of the New Contact wizard and click Next.
Enter some narrative text and click Next.
Issue: On the Participants page of the New Contact wizard, the case participant list only contains the Alleged Victim. It should also contain the Alleged Maltreater.

Resolution:

This issue has been resolved and the case participant list displayed on the Participants page of the New Contact wizard now contains all case participants.

WorkItem:250586 - The Adoption case context panel does not display all participants on a case and the layout for each participant is not correct

Issue Description:

When a Child Welfare caseworker views an adoption case that has 4 or more members, the context panel is not showing all the case participants when they are displayed by their participant images, despite clicking the right or left arrow buttons to see the case participants. The context panel also contains insufficient spacing between the case participant image and the case participant name.
**User Interface Impact:**No

Steps to Reproduce:

Login as a Child Welfare caseworker.
Create an adoption case for a registered person and add 3 or more further case participants (all under 18 years old).
Issue1: One of the participant images is missing from the context panel.
Issue2: Spacing between the case participant name and participant image on the context panel is insufficient.

Resolution:

When a caseworker views an adoption case that has 4 or more members, all the case participants are available for display on the context panel by clicking the right or left arrow buttons. The spacing between the case participant image and the case participant name on the context panel is now sufficient.

Technical:

Changes were required in the following files:

webclient/components/ChildServices/css/
cfss-IntegratedCase_rtl.css
webclient/components/ChildServices/css/
cfss-adoption-subsidy-contract-context-panel.css

Child Welfare SDM

PO08074, WorkItem:242017 - A validation error is thrown when loading the Reunification IEG script against its schema in the administration application

Issue Description:

There is a validation error when running the Reunification IEG script from the administrator workspace.
User Interface Impact: No

Steps to Reproduce:

Login as an administrator and click on the Administrator Workspace tab.
Select Scripts under Intelligent Evidence Gathering in the shortcuts panel.
Search for a script called Reunification.
For the Reunification Version 2 result, select 'Run in Modal...' against the Reunification2 schema.
Issue: A validation message appears informing the user that the IEG script definition is invalid against the schema.

Resolution:

The validation is thrown as the IEG script schema mandates that an outer list contains at least one container or column element. In this Reunification script, the outer list only has a title and an inner list. It contains no column or container. It should also have a column; the grouping column in nested lists, typically the person name. The Reunification IEG script has been updated to add in a column to the outer person list that contains the person name. This ensures no validation is thrown when the script is run against the schema.

PO08377, WorkItem:249457 - Unable to view Structured Decision Making assessments on a closed Intake case

Issue Description:

When using Structured Decision Making (SDM) assessments, an Intake worker completes a Screening Assessment to assess whether the Intake should be screened in or screened out. Response Priority Assessment are also completed to determine the response priority for the Intake. When the Intake is subsequently closed, the user is no longer able to view information about the Screening Assessment or Response Priority Assessments within the Intake because the View and View Report functions are disabled.
User Interface Impact: No

Steps to Reproduce:

Login as a Structured Decision Making Child Welfare intake worker.
Select New Intake.
Set the Category to Child Protection Services and click Save.
Select the Participants tab and click New Participant from the action menu.
Enter a First Name and a Role of Alleged Victim.
Click Next and then click Finish.
Select the Assessments tab and choose Yes for question 2: 'Was the child a victim of cruel or excessive corporal punishment?', and select No or None for all other questions.
Select the Allegations tab and click New.
Check the Alleged Victim, Unknown Maltreater and Physical Abuse check-boxes and click Save.
Select Open Intake from the tab level actions menu.
Select the Recommendation tab and select Assess on the Response Priority.
Answer No for the 'Significant Bruises' section question 'Were severe or bizarre disciplinary measures used?' and Yes for the remaining three questions and click Finish.
Select Close Intake from the tab level actions menu.
Select Screened Out as the reason, enter comments and click Save.
Select the Assessments tab.
Issue: The options View and View Report are not enabled to be selected on the assessment.

Resolution:

The View and View Report action items were incorrectly being disabled when the Intake was closed. They now remain enabled and the user can view information about the Screening Assessment and Response Priority Assessments within a closed Intake.

PO08376, WorkItem:249460 - Response Priority Assessment does not display on closed Intake

Issue Description:

A user is unable to view the Response Priority Assessment on a closed Intake case.

User Interface Impact: No

Steps to Reproduce:

Login as a Structured Decision Making Child Welfare intake worker.
Select New Intake.
Set the Category to Child Protection Services and click Save.
Select the Participants tab and click New Participant from the action menu.
Enter a First Name and a Role of Alleged Victim.
Click Next and then click Finish.
Select the Assessments tab and choose Yes for question 2: 'Was the child a victim of cruel or excessive corporal punishment?', and select No or None for all other questions.
Select the Allegations tab and click New.
Check the Alleged Victim, Unknown Maltreater and Physical Abuse check-boxes and click Save.
Select Open Intake from the tab level actions menu.
Select the Recommendation tab and select Assess on the Response Priority.
Answer No for the 'Significant Bruises' section question 'Were severe or bizarre disciplinary measures used?' and Yes for the remaining three questions and click Finish.
Select Close Intake from the tab level actions menu.
Select Screened Out as the reason, enter comments and click Save.
Select the Assessments tab.
Issue: The Response Priority Assessment is not shown.

Resolution:

Response Priority Assessments are now enabled on closed Intake cases, enabling users to view them.

PO08375, WorkItem:249462 - Incorrect validation message displays on the Recommendation page of a closed Intake

Issue Description:

When using Structured Decision Making (SDM) assessments, an Intake worker must complete a Screening Assessment in order to help determine which allegations should be captured. Until the Intake worker completes the Screening Assessment within the Intake, the following validation message is displayed on the Recommendation page as a reminder that the Screening Assessment must be completed: "Please run the Screening Assessment before creating any Allegation(s)." Currently when an Intake case is closed, the validation message is incorrectly being displayed again on the Recommendation page.

User Interface Impact: No

Steps to Reproduce:

Login as a Structured Decision Making Child Welfare intake worker.
Select New Intake.
Set the Category to Child Protection Services and click Save.
Select the Participants tab and click New Participant from the action menu.
Enter a First Name and a Role of Alleged Victim.
Click Next and then click Finish.
Select the Assessments tab and choose Yes for question 2: 'Was the child a victim of cruel or excessive corporal punishment?', and select No or None for all other questions.
Select the Allegations tab and click New.
Check the Alleged Victim, Unknown Maltreater and Physical Abuse check-boxes and click Save.
Select Open Intake from the tab level actions menu.
Select the Recommendation tab and select Assess on the Response Priority (toward the bottom of the page).
Answer No for the 'Significant Bruises' section question 'Were severe or bizarre disciplinary measures used?' and Yes for the remaining three questions and click Finish.
Select Close Intake from the tab level actions menu.
Select Screened Out as the reason, enter comments and click Save.
Select the Recommendation tab.
Issue: An incorrect validation relating to allegations is displayed.

Resolution:

The validation was incorrectly displayed again when the Intake was closed. The functionality has been updated to no longer display the validation for closed Intakes.

Common Evidence

PO08439, WorkItem:250551 - Evidence cannot be added to a case via the Incoming Evidence screen if it contains a related case participant role field

Issue Description:

A validation occurs stating that a participant is not set when trying to add evidence to a case from the Incoming Evidence list page, where the evidence contains related participants.

User Interface Impact: No
Prerequisite(s):

Login as a system administrator.
Click on Property Administration under Application Data in the shortcuts panel.
Search for a property with the name 'Advanced Evidence Sharing' and ensure its value is set to YES.

The following logically equivalent sharing rules should be configured for an Insurance Affordability integrated case to an Income Support integrated case using the sample XML configurations from Merative DeveloperWorks with Trusted Source set to No.

Income to Paid Employment.
Income to Earned Income.

Steps to Reproduce:

Login as an Insurance Affordability caseworker.
Register a new Person.
Create an application with a monthly Income of type Wages and Salaries.
Authorize the application.
Login as an Income Support caseworker.
Create an Employment participant for the Person.
Create an Income Support integrated case.
Navigate to the Incoming Evidence screen for the Income Support integrated case.
Expand the incoming evidence record.
Click Actions on the Paid Employment evidence and select Add to Case.
Click OK.
Select the Employment record and click Next.
Click Finish.
Issue: A validation is thrown stating that the participant must be selected.

Resolution:

This issue has been resolved by correctly setting participants on evidence when using the Add to Case function on the Incoming Evidence screen.

Technical:

Code for handling related participants on certain evidence types was missing in the static evidence generator style-sheet(s). This caused the related participant identifier not to be set, which resulted in a validation preventing the evidence from being added to the case. The generator style-sheet(s) have been updated to include the necessary related participant logic in the Add to Case function. This means a caseworker is now able to successfully add such evidence to a case via the Incoming Evidence screen.

Youth Services

PO07775, WorkItem:228769 - Progress spinner remains after downloading a Youth Face Sheet

Issue Description:

The progress spinner continues to display after successfully completing the download of a Youth Face Sheet from the Youth Service Case Home tab.

User Interface Impact: No

Steps to Reproduce:

Login as a Child Youth Services caseworker.
Register a new child and create a new Youth Service case.
Open the case and select Youth Face Sheet from the action menu.
Create a Youth Face Sheet and then click Print.
On the print confirmation dialog click Yes.
Issue: The progress spinner appears over the Youth Service Case Home tab and continues to display although the file is downloaded with full contents.

Resolution:

The Print Youth Face Sheet confirmation dialog has been fixed now to download the report without displaying the progress spinner. The Youth Service Case Home tab displays with all of its contents.

Known Issues

See the Known Issues section in the 7.0.5.0 release notes.

Notices

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

CSV Release Notes

ReleaseNotes_7.0.9.0.csv

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

Release Notes

Abstract

Content

Important Note

Introduction

System Requirements

Download

Installation

Improvements, Resolved Issues and Third Party Updates

Known Issues

Notices

CSV Release Notes

Document Information

More support for:

Software version:

Operating system(s):

Modified date:

Merative ™ Social Program Management 7.0.8.0 Refresh Pack

Release Notes

Abstract

Content

Important Note

Introduction

System Requirements

Download

Installation

Improvements, Resolved Issues and Third Party Updates

Known Issues

Notices

CSV Release Notes

Document Information

More support for:

Software version:

Operating system(s):

Modified date: