Skip to content
Product Support Cúram

Merative ™ Social Program Management 7.0.6.0 Refresh Pack

Release Notes

Abstract

Merative Social Program Management 7.0.6.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.6.0 is a Refresh Pack.

Introduction

Welcome to the Merative Social Program Management 7.0.6.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.6.0 Refresh Pack release includes new Universal Access functionality. For detailed information about these new features, see the What's new in Version 7.0.6.0 topic in the product documentation.

For more information about version 7.0.6.0 Refresh Pack, see the full product documentation in documentation.

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

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

System Requirements

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

Download

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

Installation

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

The installation steps are as follows:

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

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

Upgrading

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

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:241548 - Browser Support Update

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

Case Worker Application Browser Support

  • Google Chrome updated to 72

Universal Access Application Browser Support

  • Google Chrome updated to 72
  • Mozilla Firefox updated to 65

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

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

WorkItem:243946 - 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 u201

WorkItem:243952 - Tablet Accessibility Support - Certify Apple VoiceOver with Chrome 72 on iOS 12.1.4

The certified version of Apple VoiceOver has been updated to iOS 12.1.4. This has been certified against Chrome 72.

Cúram Enterprise Framework

Technical Services

WORKFLOW

PO07832, WorkItem:232364 - Import Workflow Process Version modal fails to close when the Overwrite Existing Workflow Process checkbox is selected

Issue Description:

When the Overwrite Existing Workflow Process checkbox is ticked in the Import Workflow Process Version modal and the user clicks the Import button, the modal fails to close properly.

User Interface Impact: Yes

Steps to Reproduce:

  1. Login as an administrator.
  2. Navigate to the Workflow section in the Shortcuts panel.
  3. Select 'Import Process'.
  4. Select the Overwrite Existing Workflow Process checkbox and select a file to import from the workflow folder.
  5. Click the Import button.
  6. Issue: A modal unexpectedly appears with the title 'Closing dialog - refresh parent' and the modal fails to close.

Resolution:

This issue was resolved by updating the related UIM page.

Technical:

The issue was resolved by updating the Javascript ACTION, closeDialogRefresh, on the following UIM page to pass an argument rather than an event:

  • ProcessDefinitionTool_closeModalAutomatically.uim

Integrated Case Management

PO07970, WorkItem:238973 - Some fields are misaligned while editing an integrated case note

Issue Description:

When editing an integrated case note, some fields are misaligned in the Edit Note modal.
User Interface Impact: Yes

Steps to Reproduce:

  1. Login as a caseworker.
  2. Register a new Person.
  3. Create an integrated case for the new Person.
  4. Create a new note on the integrated case.
  5. Edit the note.
  6. Issue: Some of the fields are misaligned on the Edit Note modal.

Resolution:

This issue has been resolved by adjusting the field widths in the underlying VIM. The fix will apply to all pages using that VIM page.
Technical:

The VIM page that was updated is Case_modifyNoteView1.vim.

ELIGIBILITY & ENTITLEMENT

PO07102, WorkItem:194618 - IndexOutOfBounds exception thrown inside CaseReassessment

Issue Description:

An issue occurs during the reassessment of CREOLE based cases whereby an IndexOutOfBounds exception is thrown when accessing the list of decisions belonging to a period that is no longer covered by the case start and end dates, primarily because the period of certification is moved back or forward in such a way that there is no overlap between the new certification period and the old certification period. The issue manifests itself on a subsequent reassessment of the case, when the case is made ineligible, for example.
**User Interface Impact: **No

Steps to Reproduce:

Prerequisite:

  1. Update the CREOLE product so that it is not open-ended. This can be achieved by running the following SQL:
    • UPDATE CREOLEPRODUCT SET ALLOWOPENENDEDCASES = '0' WHERE PRODUCTID = <productID>;
  2. Set the system date to be 10th January 2019.

Scenario (Generic)

  1. Register a new Person.
  2. Create a new integrated case for the Person.
  3. Create an associated, certifiable product delivery setting the delivery pattern to 'Monthly By Check In Advance On 1st'.
  4. Add a certification from 10th January 2019 to 31st January 2019.
  5. Add the necessary evidence to make the product eligible.
  6. Activate the evidence.
  7. Submit, approve and activate the product delivery.
  8. Verify that an eligible current determination exists.
  9. From the Financials tab, issue the payment for January.
  10. On the Certifications tab, move the certification start and end dates back to cover the month of September.
  11. Verify that a Benefit Underpayment has been created.
  12. Now update the evidence to make the case ineligible.
  13. Issue: The final step should make the case ineligible and generate an overpayment but this step fails due to the IndexOutOfBounds error being encountered during case reassessment.

Resolution:

The logic for retrieving the decisions associated with each reassessment period has been updated to handle business scenarios where a period is being included that is no longer covered by a current (up-to-date) decision. In this instance, the previous decisions that would have been included for that period are included.

PO08067, WorkItem:242057 - Excess overpayments displayed in the overpayment header from previous periods

Issue Description:

An incorrect reassessment amount is calculated when a gap exists between two eligible periods that have been paid. When the first eligible period is reassessed to give an overpayment and a subsequent reassessment occurs at the start of the second eligible period, another overpayment is created for that (later) period. It is this later overpayment that contains an incorrect overall amount.
User Interface Impact: No

Steps to Reproduce:

  1. Login as a caseworker.
  2. Register a new Person.
  3. Create a product delivery case paying 'Monthly By Check In Advance On 1st' for the Person from November 2017 for 18 months.
  4. Issue payments monthly on the case for a year up to and including November 2018.
  5. Modify the evidence in such a way to produce an overpayment for November 2018 while making December 2018 ineligible at the same time.
  6. Issue the payment for January 2019.
  7. Perform a change of circumstance that makes January 2019 ineligible.
  8. Issue: An incorrect (excessive) overpayment is created as the reassessment includes the financial detail for the month of November twice.

Resolution:

One of the key aspects of the reassessment engine when a change of circumstance occurs retrospectively is the determination of the set of dates over which the case must be reassessed. The next key consideration is the processing of these dates in pairs so that the actual financial line items covering those periods are successfully determined. These dates essentially make up the detail that can be found in the 'Actuals' column on the reassessment statement. There was a defect in the handling of those dates as pairs for a period which directly preceded an ineligible period. This resulted in the period being considered twice. The logic has been updated to prevent this from happening and the reassessment amount is now calculated correctly for the above scenario.

EVIDENCE MANAGEMENT

PO08020, WorkItem:240550 - Update with Incoming wizard throws an error with incorrect evidence date '01/01/0001' shown

Issue Description:

Updating with Incoming correction was incorrectly using the incoming evidence's effective date to verify the integrity of the expected timeline for all evidence in a timeline. However for the first record in a timeline where no effective date is populated, it should instead use the period start date. This resulted in an incorrect validation message occurring using the null effective date in the message.

**User Interface Impact: **No

Steps to Reproduce:

  1. Login as an Insurance Affordability caseworker.
  2. Register a new Person.
  3. Submit an application with a past date (1st May 2018, for example) for a member with an Income of $500/monthly and start date of 1/1/2018.
  4. Authorize the Application Case.
  5. Navigate to the Insurance Affordability integrated case and edit the Income evidence with the following changes:
    • Edit the Effective Date Of Change to 1st March 2018 and the amount to $600 monthly.
    • Edit the Effective Date Of Change to 1st May 2018 and the amount to $700 monthly.
    • Edit the Effective Date Of Change to 1st July 2018 and the amount to $800 monthly.
    • Verify (if required) and Apply Changes.
  6. The Income evidence will have the following set of succession records on the integrated case:
    • 1/1/2018 to 2/28/2018 – $500 monthly.
    • 3/1/2018 to 4/30/2018 – $600 monthly.
    • 5/1/2018 to 6/30/2018 – $700 monthly.
    • 7/1/2018 to ongoing - $800 monthly.
  7. Submit a new application for the same member with an application date of 20th September 2018 and latest income set to $1000 monthly starting on 1st September 2018.
  8. Authorize the new Application Case selecting the existing Insurance Affordability integrated case during the authorization process.
  9. Navigate to the Incoming evidence tab on the Insurance Affordability integrated case.
  10. Expand the Income evidence and compare the timelines of the incoming evidence and the existing evidence.
  11. In the actions menu of the Existing Evidence, select Update with Incoming.
  12. Select the incoming Income evidence in the Update with Incoming wizard and click Next.
  13. Select the Correction option and click Next.
  14. Issue: The system throws an error message with an incorrect evidence date:
    • 'The effective dated incoming values may already exist on this case, please compare against existing evidence on 01/01/0001 and correct existing using incoming values if required.'

Resolution:

The validation has been updated to use either period start date or effective date as appropriate when validating the integrity of the expected timeline. If an effective date exists on the evidence it will be used. If no effective date exists on the evidence, in the scenario of initial record in a succession, the evidence period start date will be used instead. This results in the error message no longer occurring in this scenario and the correction can be performed.

PO08056, WorkItem:241879 - Adding new evidence from the External System category in an integrated case’s evidence dashboard results in an un-handled server exception

Issue Description:

When a user tries to add an evidence using the 'New Evidence' dialog from the Evidence tab of an integrated case, they are able to select an evidence displayed under the External System category even though it is configured as read-only. When the user tries to save this evidence, an un-handled server exception is thrown and the Evidence dashboard is no longer accessible. The 'New Evidence' dialog should filter out read-only evidences under the External System category so they are not available for selection, similar to other evidence type categories.
**User Interface Impact: **No

Prerequisites:

  1. Login as an administrator.
  2. Navigate to the Integrated Cases page by selecting 'Integrated Cases' from the Case section of the Shortcuts panel.
  3. Select an integrated case type.
  4. Select the Evidence tab, from the action menu select Edit for the evidence type that is external.
  5. Set Category to 'External System'.
  6. Click 'Save'.
  7. From the Shortcuts panel, navigate to Rules and Evidence > Dynamic Evidence.
  8. Expand the the same evidence type configured above.
  9. From the actions menu, select View Metadata from the current record.
  10. Under Evidence Properties, expand Options and select Read Only.

Steps to Reproduce:

  1. Login as a caseworker.
  2. Register a new Person.
  3. Create an integrated case for the Person.
  4. From the Evidence dashboard, select 'New Evidence' from the actions menu.
  5. Select the Category of External System.
  6. Select to add the configured external evidence type.
  7. Populate the necessary fields.
  8. Click 'Save'.
  9. Issue: An un-handled server exception occurs and the Evidence tab is no longer accessible.

Resolution:

The evidences under the External System category are no longer available for selection in the 'New Evidence' dialog when they are configured as read-only, and are now filtered in the API that populates the 'New Evidence' dialog.

PO08109, WorkItem:243150 - Modals become unresponsive when the Add Evidence and Transfer Evidence menu options are invoked

Issue Description:

There was an issue using the Add Evidence and Transfer Evidence menu options on the Evidence Dashboard. Once these menu options were launched, it caused a responsiveness problem across modals. These specific actions could be launched a second time in the same browser session but not a third time. Other actions would no longer launch. List pages continued to work and display data, and modals could be launched if the application was refreshed, but the lack of responsiveness affected caseworkers managing evidence.

User Interface Impact: Yes

Steps to Reproduce:

Scenario 1

1. Login as a caseworker.
2. Register a new Person.
3. Create an integrated case for the Person.
4. Open the Evidence tab.
5. Go to the actions menu and click on 'New Evidence'.
6. Add new evidence of type Address.
7. Repeat a second time; add another evidence record of type Address.
8. Issue: On the third time of adding a new evidence record, the modal doesn't open.

Scenario 2

1. Login as a caseworker.
2. Register a new Person.
3. Create an integrated case for the Person.
4. Open the Evidence tab.
5. Go to the actions menu and click on 'New Evidence'.
6. Add new evidence of type Address.
7. Issue: Now attempt to launch the Validate Changes modal from the menu option. The modal doesn't open.

Resolution:

This issue has been resolved by adding a new listener to submit the form when the page is loaded.

Technical:

The following javascript files have been updated to include a new listener to submit the form when the page is loaded.

  • evidenceTypeWorkspace.js
  • transferEvidence.js

PARTICIPANT MANAGEMENT

PO07938, WorkItem:238135 - Context Panel is not updated automatically after editing Person address evidence

Issue Description:

When a caseworker updates a Person's address evidence and changes the address that should be considered as the Preferred address, the Context Panel is not automatically updated to display the new Preferred address.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a caseworker.
  2. Register a new Person.
  3. Navigate to the Evidence tab from the Person home page and notice there is already a private address created for the Person with the Preferred indicator set to 'Yes'.
  4. Add new private address evidence and ensure the Preferred indicator is selected.
  5. Issue: The Context Panel does not refresh automatically to show the new preferred address. It still shows the old address.

Resolution:

****This issue has been resolved by automatically refreshing the context panel associated with the Person and ProspectPerson tabs when evidence is added.

Technical:

The following entries have been added to both the Person and ProspectPerson tab files:

  • <tc:onsubmit page-id="PDCEvidence_listEvidence" navigation="false" context="true" menu-bar="false"/>
  • <tc:onsubmit page-id="PDCEvidence_addNewEvidence" navigation="false" context="true" menu-bar="false"/>
  • <tc:onsubmit page-id="Evidence_resolveDynEvdModifyEvidencePage" navigation="false" context="true" menu-bar="false"/>
  • <tc:onsubmit page-id="Evidence_removeActive" navigation="false" context="true" menu-bar="false"/>
  • <tc:onsubmit page-id="Evidence_resolveDynEvdViewEvidencePage" navigation="false" context="true" menu-bar="false"/>

Administration Suite

ORGANIZATION

PO07435, WorkItem:209842 - Scroll bar overlapping time field in the New Recurring Organization Activity screen

Issue Description:

The vertical scroll bar on the 'New Recurring Organization Activity' modal overlaps with the time field in the modal.

**User Interface Impact: **Yes

Steps to Reproduce:

  1. Login as an administrator.
  2. Click on Administration Workspace.
  3. Navigate to the 'My Organization' page by selecting Organization > My Organization in the Shortcuts panel.
  4. Click on the Calendar tab and select to create a 'New Recurring Activity'.
  5. Issue: The vertical scroll bar on the right hand side of the 'New Recurring Organization Activity' modal is cutting off the time field.

Resolution:

This issue has been resolved and the user is now able to see the time field and its value without any overlapping of the vertical scroll bar.

Application Development Environment

PO07914, WorkItem:237058 - Description of the ScanMilestoneDeliveryEndDate batch job is incorrect in the Knowledge Center

Issue Description:

The ScanMilestoneDeliveryEndDate batch job was incorrectly described in the Knowledge Center.

The previous documentation text said that the batch job "Searches the system for all milestone deliveries which have a status of 'Not Started' and where the earliest start date has passed", which was incorrect. The batch job instead looks for milestone deliveries where the status is not 'Completed' and the earliest 'Expected End Date' has passed.
**User Interface Impact: **No

Steps to Reproduce: N/A

Resolution:

The description text of the ScanMilestoneDeliveryEndDate batch job has been updated to state that it searches the system for all milestone deliveries where the status is not 'Completed' and where the earliest 'Expected End Date' has been reached. It now also mentions that the batch job raises an event to notify the case owner of all milestone deliveries where the status is not 'Completed' and where the earliest 'Expected End Date' has been reached. Find more information at: https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

CLIENT DEVELOPMENT ENVIRONMENT

PO07428, WorkItem:208140 - Text area moves unexpectedly on mouse over

Issue Description:

The text area input field across the application moves slightly when the user hovers over the text area or tabs to this text area.
**User Interface Impact: **Yes

Steps to Reproduce:

  1. Login as a caseworker.
  2. Register a new Person.
  3. Create an integrated case for the Person.
  4. From the integrated case home page, select 'New Meeting' from the action menu.
  5. Slowly move the cursor up and down across on the Notes text area.
  6. Issue: The text area moves slightly.

Resolution:

This issue has been resolved by updating the CSS styling on this text area.

PO07719, WorkItem:226453 - Menu separators on are not visible in Internet Explorer 11

Issue Description:

The menu separators that display on an actions menu are not visible in Internet Explorer 11.

**User Interface Impact: **Yes

Steps to Reproduce:

  1. Login as a caseworker using the Internet Explorer 11 browser.
  2. Register a new Person.
  3. Navigate to the Person home page.
  4. Click on the actions menu.
  5. Issue: The menu separators are not displayed.

Resolution:

This issue has been resolved by updating the relevant CSS styling.

PO08100, PO08101, WorkItem:243601 - When printing inline pages containing tables, if the print preview includes a page break, the table header(s) are not being displayed on the top of the second page

Issue Description:

There was an issue printing an inline page containing a table which spanned beyond one page in length. The headers of the table which were displayed on the first page were not displayed at the start of the second page.
User Interface Impact: No

Steps to Reproduce:

  1. Login as a caseworker.
  2. Search for a Person.
  3. Click on one of the search results to open the Person home page.
  4. Click on the Evidence tab.
  5. Expand some Person evidence.
  6. Click on the page level print icon to print the page.
  7. Issue: The headings 'Type', 'Description', 'Source', 'Period', and 'Latest Activity' are not displayed at the top of the page.

Resolution:

This issue has been resolved by ensuring a table heading will be repeated at the top of the next page when a page break occurs within the content of the table.

PO08099, WorkItem:243602 - Overlapping first row when printing an Assessment Questionnaire

Issue Description:

There was an issue printing an Assessment Questionnaire which had enough questions to span onto a second page. The first row (question) on the second page overlapped the header on the second page. This could be seen on both the Google Chrome and Internet Explorer browsers.
**User Interface Impact: **No

Steps to Reproduce:

  1. Login as an administrator.
  2. Open the 'Administration Workspace'.
  3. Expand the Case section.
  4. Select 'Integrated Cases'.
  5. Using the New action menu, configure a new integrated case type.
  6. Click on the newly configured integrated case type hyperlink.
  7. Open the 'Assessments' tab.
  8. Select 'Add Existing...'.
  9. Search for and select an Assessment (Example: 'Juvenile Detention Assessment').
  10. Click 'Save'.
  11. Login as a caseworker.
  12. Click on the 'Cases and Outcomes' tab.
  13. Open the 'Shortcuts' panel.
  14. Expand 'Searches".
  15. Select 'Person..'
  16. When the 'Person Search' tab opens, search for a person and click on a search result to open the Person home page.
  17. Select 'New Case...'.
  18. Select the new integrated case type from the drop-down.
  19. From the case home page, select the 'Assessments' tab.
  20. Click on the 'New Assessment' page level menu.
  21. Create a new 'Juvenile Detention Assessment'.
  22. Once created, click on the Assessment link.
  23. Under the Questionnaires section, click on the 'Answer' row level menu for the Juvenile Detention Questionnaire.
  24. Answer the questions in the questionnaire.
  25. Click 'Close' on the last page of the questionnaire.
  26. Click on the Juvenile Detention Questionnaire link.
  27. Click on the page level print icon.
  28. If required, change the layout to 'Landscape' in the browser Print window so that the questions span onto a second page.
  29. Issue: The first row (question) on the second page overlaps the header on the second page.

Resolution:

This issue has since been resolved by ensuring question rows break correctly between pages when printing.

PO07956, WorkItem:243603 - When printing expanded evidence the details displayed are truncated

Issue Description:

When using the page level Print icon to print a list of evidence details, certain information was missing. When the evidence was expanded to display the full details, only the header information was printed. No information from the evidence details page was printed.

**User Interface Impact: **No

Steps to Reproduce:

  1. Login as a caseworker.
  2. Register a new Person.
  3. Create an integrated case for the Person.
  4. From the Evidence dashboard, create a new evidence.
  5. Activate the evidence.
  6. Navigate to the Active Evidence list page to view the new evidence.
  7. Click the toggle to view the header information for the evidence.
  8. Click the toggle on the header row to view the evidence details.
  9. Print the page using the print button in the options menu of the page.
  10. Issue: The only information present in the print preview is the header information.

Resolution:

This issue has been resolved by adding specific styling for evidence pages when they are printed. This ensures all the visible evidence information is printed correctly.

ACCESSIBILITY

PO07752, WorkItem:228026 - JAWS consistency issue when selecting the Month in the Calendar

Issue Description:

The JAWS screen reader announces the month list from the Date Selector component in an inconsistent manner.
**User Interface Impact: **No

Steps to Reproduce:

  1. Login as a Child Welfare intake worker using the Internet Explorer 11 browser.
  2. Select the New Intake link from the Quick Links pod.
  3. The New Intake modal should open with the cursor focus on the Category field.
  4. Tab to move to the Calendar icon, and then press the Enter key.
  5. The Select a Date modal should open with the cursor focus on the Month field.
  6. Start the JAWS 2018 screen reader.
  7. Press the down arrow key.
  8. Issue: JAWS will not behave consistently when reading the Month field:
    • sometimes JAWS reads 'January' or 'February' or 'March'
    • sometimes JAWS reads 'January list box item' or 'February list box item' or 'March list box item'
    • sometimes JAWS reads 'October' or 'November'... which is not the starting month (January)

Resolution:

This issue has been resolved by making JAWS read the month list consistently by the order that it will be displayed on the list. The Month field was redesigned to address the accessibility issue. Now, the user can search for specific options by typing the first letter(s) of a matching option when the drop-down menu is opened.

  • For example, typing the letter ‘m’ will find the next option that begins with the letter ‘m’, starting with the current option.
  • If typed without pauses, multiple letters can also be used to search.
  • Typing the 2 letters ‘a’ and ‘b’ within 1 second of each other will search for an option that begins with ‘ab’.
  • However, pausing between letters would result in searching for an option that begins with ‘a’, and then subsequently an option that begins with ‘b’.

WorkItem:239512 - Tablet Accessibility: When using screen reader drop-down list does not close when navigating away

Issue Description:

A user using a screen reader in the mobile (tablet) environment might unintentionally navigate from the drop-down selection list without closing it and it can remain open on the page.

**User Interface Impact: **Yes

Steps to Reproduce:

  1. Enable the VoiceOver screen reader.
  2. Open the Merative Social Program Management application on the tablet.
  3. Navigate to any page which requires a drop-down selection.
  4. Open the drop-down list using the supported tap or key combination.
  5. Issue: The drop-down remains open even when the focus is moved away from it.

Resolution:

The drop-down accessibility in the mobile environment has been improved so that the user is now informed by the screen reader that they have reached the beginning or end of the choices in the list and instructed to either close the list or return to it.

Technical:

Two new localizable properties have been introduced to inform the user if they have reached the end of the selection list in a drop-down:

  • ‘text.select.outlist.forward’ and
  • ‘text.select.outlist.back’

These properties are localized in the same way as other entries in CDEJResources.properties.

PO08042, WorkItem:241183 - JAWS screen reader instruction to 'Press tab to activate the modal' on a modal window is causing confusion

Issue Description:

When opening a modal dialog in the application, the JAWS screen reader reads out the text 'Press tab to activate the modal' after the modal link has been clicked. This results in the second field of the modal being in focus.

**User Interface Impact: **No

Steps to Reproduce:

  1. Login as a caseworker.
  2. From the Cases section of the Shortcuts panel, select 'New Case Query'.
  3. When the JAWS screen reader reads out the details for the modal that opens up, it says 'Press tab to activate the modal'.
  4. Press the tab key.
  5. Issue: The focus is on the second field of the modal.

Resolution:

This has been resolved by removing the message 'Press tab to activate the modal' so that the user isn't prompted to press the tab key, thereby resulting in the focus remaining on the first field of the modal.

PO08044, WorkItem:241236 - JAWS screen reader reads frame titles as 'undefined'

Issue Description:

Some user interface frame titles in the application are read as 'undefined' by the JAWS 2018 screen reader.

**User Interface Impact: **Yes

Steps to Reproduce:

  1. Login as a caseworker using Internet Explorer 11.
  2. Register a new Person.
  3. Start the JAWS 2018 screen reader.
  4. Change focus to the Home tab of the newly registered Person.
  5. The Home tab should be selected (underlined) and in focus.
  6. Press the right arrow key until the 'Issues and Proceedings' tab is selected.
  7. Issue: JAWS reads out (among other things) 'Content Panel undefined'.

Resolution:

****This issue has been resolved by updating the JavaScript code concerning the title of the content panel in screens that contain in-page navigation links.

LOOK & FEEL

PO07292, WorkItem:202569 - Unable to set 12 hour time format in the Calendar view

Issue Description:

When the CalendarConfig DAY_VIEW_TIME_FORMAT is set to 12, the time displayed is in 24 hour format. The time should be displayed in the Calendar in 12 hour format hh:mm with either AM or PM.

**User Interface Impact: **Yes

Steps to Reproduce:

  1. Edit the relevant CalendarConfig.xml and set DAY_VIEW_TIME_FORMAT to 12
  2. Build the client.
  3. Login as any user.
  4. Create an Activity in the Calendar and select a time that should be displayed in 12 hour format, an activity from 19:00 to 20:30, for example.
  5. Issue: The time displayed is in 24h format.

Resolution:

This issue has been resolved and the time now displays in the Calendar in 12 hour format hh:mm with either AM or PM.

Technical:

Sample CalendarConfig.xml code:

<CALENDAR TYPE="User">
<DESCRIPTION_LOCATION>Activity_resolveView
StandardUserActivityPage.do</DESCRIPTION_LOCATION>
<CREATE_LOCATION>Activity_resolveCreateUserActivity
Page.do</CREATE_LOCATION>
<DAY_VIEW_TIME_FORMAT>12</DAY_VIEW_TIME_FORMAT>
</CALENDAR>

PO07861, WorkItem:234386 - Special characters such as quotes and the ampersand (&) are escaped in Announcement messages

Issue Description:

Announcements allow the agency to set an application-wide message that can be displayed on an application home page for a set period.
When an Announcement contains text which has special characters, single-quotes ('), double-quotes (") or an ampersand (&), for example, they are shown as escaped when rendered in the browser. That is, they appear as \’, \”, and \u0026, respectively.

**User Interface Impact: **Yes

Steps to Reproduce:

  1. Login as an administrator.
  2. Navigate to the 'New Announcement' dialog by selecting 'Organization' followed by 'New Announcement...'
  3. Write a message in the text field with single quotes, double quotes and an ampersand character, for example, 'Office 'closed' due to "storm" for today & tomorrow'. Provide earliest future date and time, the nearest half-hour increment from now, for example.
  4. Log out and login as a caseworker user to view the Announcement message.
  5. Issue: The Announcement message on the home page is shown as: Office \'closed\' due to \"storm\" for today \u0026 tomorrow.

Resolution:

Special characters entered for an Announcement are no longer escaped when viewing the Announcement message on an application home page. That is, the message appears as it was entered on the 'New Announcement' dialog.

PO07750, WorkItem:238882 - Additional ellipses are being shown in the Open Task actions menu

Issue Description:

Additional ellipses are being shown in the Open Task actions menu in the user's inbox.

**User Interface Impact: **Yes

Steps to Reproduce:

  1. Login as a caseworker.
  2. Register a new Person.
  3. Navigate to the Inbox tab.
  4. Select the New Task menu option from the My Open Tasks page.
  5. Fill in all the mandatory details and add the registered Person in the Case Participant field.
  6. A new task entry will display under Open Tasks.
  7. Click on the row level menu beside the task.
  8. Issue: Six ellipses are shown in the menu items instead of three.

Resolution:

This issue is now resolved and the user sees three ellipses as expected for the menu items.

PO07986, WorkItem:239756 - The pop-up that displays information about a holiday renders the label Holiday over multiple lines

Issue Description:

In the Administration Workspace, when adding a New Location Holiday the label and holiday name entered are word-wrapped onto separate lines.

User Interface Impact: No

Steps to Reproduce:

  1. Login as an administrator.
  2. From Quick Links select Search for a User and search for a case worker. Select a case worker.
  3. Select the Location of the case worker from the details on the Home tab. The Location workspace should open.
  4. Select the Location Calendar tab.
  5. Select New Location Holiday.
  6. Enter a holiday, for example Thanksgiving Day with Date 11/22/2018.
  7. Click Save.
  8. Login as the case worker selected above and select the Calendar tab.
  9. Go to the date for the holiday added above on the calendar (Thanksgiving Day).
  10. Issue: Select Thanksgiving Day and observe the words are misaligned in the pop-up that opens.

Resolution:

This issue has been resolved and the label Holiday and the name of the holiday are now aligned.

MISCELLANEOUS

PO07665, WorkItem:215828 - File not found error while accessing CaseWorkerCustomHome page

Issue Description:

The image file 'digit/themes/tundra/images/validationInputBg.gif' is referenced but cannot be found resulting in a File not found error in the server logs while accessing the CaseworkerCustomHome page.
**User Interface Impact: **No

Steps to Reproduce:

  1. Login as a caseworker.
  2. Open the developer tools on the browser.
  3. Navigate to the Network view on developer tools.
  4. Issue: An error is displayed indicating that the image file 'digit/themes/tundra/images/validationInputBg.gif' could not be found.

Resolution:

This issue has been resolved by removing the dependency on the stylesheet referencing the file 'digit/themes/tundra/images/validationInputBg.gif'.

Technical:

The issue can also be seen in the Application Server logs while accessing the CaseworkerCustomHome page. For example, the following error is seen in WebSphere's stdout, stderr, and ffdc logs:

SRVE0190E: File not found: /CDEJ/jscript/dojotk/dijit/themes/tundra/images/validationInputBg.gif

SERVER DEVELOPMENT ENVIRONMENT

PO08009, WorkItem:235065 - Support for special characters viewed through the Notes History page

Issue Description:

Case Notes are typically created in the application as a result of using the Rich Text Editor. Therefore the manipulation of the data in the Case Notes functionality, for both the storage and the viewing of such notes, is tailored for use with that editor in that the data is expected to be in the format specific to data entry through the Rich Text Editor. An issue arose for a customer who used an alternative mechanism to input a case note. A custom screen contained a text input field which was designated as a standard Comments field at the screen level, but on the server side was stored as a Note. When the text entered via the Comments field and stored as a Note contained a special character such as '&' or '$', it was not stored in the format that was compatible with the manipulation of Case Notes data. This meant it was not displayed correctly when reading back from the database and viewed through the Notes History page.
**User Interface Impact: **No

Steps to Reproduce:

**Note: **As the scenario which resulted in this issue did not follow the expected usage of Case Notes infrastructure, there are no examples of this issue in the out-of-the-box Platform application. To reproduce the issue:

  1. Create a custom UIM page with a standard text entry field which does not use the NOTE_TEXT domain, such as a Comments field.
  2. In the server interface associated with this page, assign the text entered in the Comments field to a database field with a domain type of NOTE_TEXT.
  3. Navigate to this page on a built and deployed server and enter text in the Comments field, including the '&' character, and click 'Save'.
  4. Navigate to a Notes list page and select the Note corresponding to the text entered above.
  5. Open the toggle to view the Notes History.
  6. Issue:The comments text entered previously is not fully displayed.

Resolution:

This issue has now been resolved and the Notes History page correctly displays comments which include special characters such as '&' or '$'.

Technical:

WorkItem 240981 introduced the Jsoup library into the Social Program Management application. This library enables improved handling of HTML documents and strings. This ticket updated the Notes History Renderer code to make use of these new classes. Data entered as Notes but without using the Rich Text Editor is now in a format that is compatible with being displayed on the Note History screens.

PO08059, WorkItem:241886 - Clarify in the Communication Guide what special characters cannot be used to populate Microsoft Word Templates

Issue Description:

The File Edit widget feature has a limitation as to the special characters that can be used to populate Microsoft Word Templates. Documentation stated that the data content that is passed to the template to populate the variables is limited to only alphanumeric characters.

**User Interface Impact: **No

Steps to Reproduce: N/A

Resolution:

The documentation has been updated to list the characters that are not permitted. Find more information at: https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

Business Services

CALENDARING/SCHEDULING

PO07755, WorkItem:228286 - Usernames with numeric characters causing unhandled server exception in a meeting invite

Issue Description:

When a user with one or more numeric characters in their username is added to a meeting invite, an unhandled server exception occurs.

User Interface Impact: No

Steps to Reproduce:

  1. Login as an administrator.
  2. Navigate to the Shortcuts and expand the Users section.
  3. Select New User and create a user with a username consisting of only numeric characters.
  4. Login as a caseworker.
  5. Navigate to the workspace Calendar and select New Meeting from the action menu on the Calendar View page.
  6. Navigate to the List View page and select Invite Attendees from the action menu for the newly created meeting.
  7. Search for the newly created user and choose Select to add them as an attendee from the search results.
  8. Issue: An unhandled server exception is displayed on the screen.

Resolution:

This issue has been resolved by allowing users to have usernames which contain numeric characters.

TASK MANAGEMENT

PO01124, WorkItem:238956 - Unexpected error on the 'My Tasks', 'Available Tasks', 'Recent Notifications' and 'Work Queues' Pods

Issue Description:

An error is displayed on the Available Task, My Tasks, Recent Notifications and Work Queues Pods when special characters such as []{} are inserted in the subject field.

User Interface Impact: No

Steps to Reproduce the My Tasks Pod issue:

  1. Login as a caseworker.
  2. From the My Tasks Pod on the caseworker workspace, select the Create Task option.
  3. Create a new Task filling the subject field with special characters (e.g. "[,task").
  4. Issue: An unexpected error displays in the My Tasks Pod when the Home page refreshes.

Steps to Reproduce the Available Tasks Pod issue:

  1. Login as an administrator.
  2. Navigate to Personalized Pod Pages by selecting the User Interface and then the Personalized Pod Pages menu item from the Shortcuts panel.
  3. Select to edit the list item for CaseworkerCustomHome where the User Role is SUPERROLE.
  4. In the Configure a Personal Page wizard that opens, select the Available Tasks Pod in Available Pods, and Default Pods pages.
  5. Click Save.
  6. Login as a caseworker.
  7. Click on the Customize icon and check the Available Tasks option.
  8. Click Save.
  9. From the Inbox, select New Task from the action menu on the My Open Tasks page.
  10. Create a new Task filling out the subject field with special characters (e.g. "[,task").
  11. Select the Make Available action menu item against the task created above and click Save on the modal.
  12. Navigate to the Home tab.
  13. Click on the refresh icon to reload the Pods.
  14. Issue: An unexpected error displays in the Available Tasks Pod.

Steps to reproduce 'Recent Notifications' Pod issue:

  1. Login as a caseworker.
  2. Navigate to the caseworker Home page.
  3. Click on the Customize icon and check the Recent Notifications option.
  4. Click Save.
  5. Ensure that a notification exists containing special characters such as []{}.
  6. Issue: An unexpected error displays in the Recent Notifications Pod.

Steps to Reproduce 'Work Queues' Pod issue:

  1. Login as a caseworker.
  2. Navigate to the caseworker Home page.
  3. Click on the Customize icon and check the Work Queues option.
  4. Click Save.
  5. Ensure that a Work Queue exists containing special characters such as []{}.
  6. Issue: An unexpected error displays in the Work Queues Pod.

Resolution:

This issue has been resolved and tasks, recent notifications and work queues with special characters such as []{} in the subject now appear in the appropriate Pods on the home page without any errors.

Cúram Modules

Outcome Management

PO07743, WorkItem:227821 - New Referral wizard pages contain a number of formatting issues

Issue Description:

When creating a new referral within an outcome plan, pages in the New Referral wizard contained a number of formatting issues.

**User Interface Impact: **Yes

Steps to Reproduce:

  1. Login as a caseworker.
  2. Navigate to the Shortcuts panel under Cases and Outcomes tab.
  3. Register a new Person.
  4. In the Shortcuts panel, navigate to Outcome Plans.
  5. Create a new Outcome Plan for the Person.
  6. On the newly created Outcome Plan, navigate to Activities tab.
  7. Select New Referral from the page level action menu.
  8. Issues: The following formatting issues are seen on the second and third pages of the New Referral modal wizard:

The Referred By Me, Warning Days, and Phone number area code input fields are too narrow to display the appropriate length of input text. Additionally, the Address field labels are too narrow to display the label text.
Resolution:

The formatting issues were resolved by updating the layout of the relevant UIM pages and CSS styling.

PO07747, WorkItem:227931 - Highlight Differences and Clear Differences buttons incorrectly close Compare modal when comparing two assessments

Issue Description:

When running a comparison between two selected assessments from the Compare Modal page, when either the Highlight Differences or Clear Differences button was clicked, the modal unexpectedly closed down. Some other issues found on this page were that:

  • The differences found in the comparison were automatically highlighted in the result page, instead of highlighting the differences on demand when the Highlight Differences button was clicked by the user.
  • The Close button at the bottom of the modal page was not working properly when the Reset button on that page had previously been clicked. It took two attempts to close the modal page using that button.

**User Interface Impact: **No

Steps to Reproduce:

  1. Register a child less than sixteen years old.
  2. Navigate to Shortcuts, Outcome Plans, then New Outcome Plan.
  3. Select the child you just registered.
  4. Give a name to the Outcome Plan. Select Type 'Child Welfare Outcome Plan'.
  5. Go to Assessments & Factors tab. Click New.
  6. Select Child Strengths and Needs.
  7. Select the Role of child and start the assessment. Select random results. Select Save. Select Complete.
  8. Select to reassess the assessment. Select Save. Select Complete.
  9. Refresh the window.
  10. On the assessment, select Compare.
  11. Click either the Highlight Differences or Clear Differences button.
  12. Issue: The modal unexpectedly closes.

Resolution:

Now, when a comparison is run for two assessments, the Highlight Difference and Clear Differences buttons no longer close the modal. The result page does not highlight differences automatically. When the Highlight Differences button is clicked by the user, the differences in the comparison results are now highlighted. Also the Clear Differences button has also been fixed, removing any highlighted rows effected. The Close button is now working as expected, closing the modal on the first attempt even after the Reset button has been used.

PO07940, WorkItem:238220 - Validation error on an Outcome Plan's Record Scheduled Attendance or Record Absence Period modal results in the Client dropdown list becoming empty

Issue Description:

Within an Outcome Plan, the drop-down for the Client field gets cleared when any validation is thrown on the Record Scheduled Attendance and Record Absence Period modals.

**User Interface Impact: **No

Steps to Reproduce:

  1. Login as a caseworker.
  2. Register a new Person.
  3. Navigate to Shortcuts then Outcome Plans then New Outcome Plan. Select the person you added.
  4. Create a new outcome plan.
  5. From the Outcome Plan home page, select Activities.
  6. Create an activity of any type, action for example.
  7. In the outcome plan, click on the Participation sub tab.
  8. Click on the actions menu list and select Record Scheduled Attendance.
  9. Enter all details, including a date in the future in an invalid format.
  10. Click Save.
  11. A validation message displays to enter dates with the correct format.
  12. Issue: After the message displays, the drop-down for the Client field contains no values. The same issue is also observed in the Client drop-down field on the Record Absence Period modal

Resolution:

The participant values in the Client drop-down fields are now retained when a validation error occurs on the Record Scheduled Attendance and Record Absence Period modals that are initiated from within an Outcome Plan.

Technical:

Custom Javascript controls what gets displayed in the participants drop-down on both the Record Scheduled Attendance and Record Absence Period modals. This was getting reset when validations were thrown, as the respective pages reload. This issue has been resolved by updating the Javascript method calls to the ONLOAD events to the following UIM pages:

  • OutcomePlan_recordParticipation.uim
  • OutcomePlan_recordAbsencePeriod.uim

Universal Access

PO08021, WorkItem:241404 - Unable to withdraw the current user's application

Issue Description:

Users are unable to withdraw their own previously submitted applications through the Citizen Portal.
**User Interface Impact: **No
Steps to Reproduce:

  1. Login to the Citizen Portal.
  2. Apply for Benefits.
  3. Submit an application.
  4. From the Home screen click on ‘Apply for Benefits’. This will display a ‘Current Applications’ screen.
  5. Click the Withdraw link beside the application to be withdrawn.
  6. On the ‘Withdraw your Submitted Application’ screen, complete the details and click 'Yes'.
  7. Issue: A validation appears and the application cannot be withdrawn - 'You are not privileged to access this page'.

Resolution:

The withdraw application functionality has been updated to remove a validation that was preventing a user from withdrawing their own submitted applications.

Intelligent Evidence Gathering

WorkItem:244981 - Universal Access Responsive Web Application: When using a codetable hierarchy question in a List, the code is displayed instead of its value.

Issue Description:

When using a codetable hierarchy question in a List, the code is displayed instead of its value. This only affects users of the Universal Access Responsive Web Application.

User Interface Impact: No

Steps to Reproduce:

  1. Navigate to an IEG page which uses a codetable hierarchy question in a List
  2. Observe that the codetable code table is displayed instead of its value.

Resolution:

When using a codetable hierarchy question in a List, the value is now correctly displayed.

WorkItem:244982 - Universal Access Responsive Web Application: Issue with trailing zeros not displaying in field amounts

Issue Description:

Zeros at the end of decimal numbers are not displayed after navigating back to the page. This only affects users of the Universal Access Responsive Web Application.

User Interface Impact: No

Steps to Reproduce:

  1. Navigate to an IEG page with a decimal entry field.
  2. Enter a number with trailing zeros.
  3. Navigate back and then forward again to the same field. Observe that the trailing zeros are missing.

Resolution:

Trailing zeros are now correctly displayed.

WorkItem:244983 - Universal Access Responsive Web Application: IEG menus are showing incorrect values when the codetable domain name is duplicated.

Issue Description:

Menus are showing incorrect values when the codetable domain name is duplicated. This only affects users of the Universal Access Responsive Web Application.

**User Interface Impact: **No

Steps to Reproduce:

  1. Navigate to an IEG page which contains duplicate codetable domains.
  2. Observe that the values displayed are incorrect.

Resolution:

IEG menus are now showing the correct values when the code table domain name is duplicated.

WorkItem:245044 - Universal Access Responsive Web Application: Concurrent access to list on a page throwing Exception

Issue Description:

When an IEG script is running for two different users at the same time and a page that contained a list was accessed simultaneously, an error may result with no way to recover except to restart the JVM. This only affects users of the Universal Access Responsive Web Application.
**User Interface Impact: **No

Steps to Reproduce:

  1. Have multiple users simultaneously access a script containing a list.
  2. Observe that an error is thrown.

Resolution:

This issue is now resolved and multiple users can complete forms at the same time as expected.

WorkItem:245242 - Universal Access Responsive Web Application: Unsupported field schema error on read-only array questions

Issue Description:

When accessing an IEG script containing a read-only array question a parser error is thrown. This only affects users of the Universal Access Responsive Web Application.

User Interface Impact: No

Steps to Reproduce:

  1. Create an IEG script that contains a read-only array question.
  2. Access the IEG script and note that a parser error is thrown.

Resolution:

Read-only array questions are now displayed correctly.

WorkItem:245243 - Universal Access Responsive Web Application: Unable to distinguish between multiple household members

Issue Description:

When adding multiple house members in Universal Access is it not clear which person you are entering details for. This only affects users of the Universal Access Responsive Web Application.

User Interface Impact: No

Steps to Reproduce:

  1. Log onto Universal Access.
  2. Add multiple household members to an application.

Resolution:

Adding a household member and their details was enhanced to make it clearer who still needs to be added. On the household page, the current household members and their ages are now listed. Household members are displayed in the order in which they were added. While you are adding details for a household member, their name and age are displayed.

WorkItem:245244 - Universal Access Responsive Web Application: Codetable Hierarchy support

Issue Description:

Codetable hierarchies are not supported in the Universal Access Responsive Web Application.
**User Interface Impact: **No

Steps to Reproduce:

  1. Log onto Universal Access
  2. Attempt to use an IEG script which uses codetable hierarchies.

Resolution:

You can now use two-level code-table hierarchies in questions. Any question where the data type is a code table is displayed as two separate questions in vertically aligned drop-down menus. The first question menu corresponds to the root code table in the hierarchy, and displays the label that is specified for the question. The second question menu corresponds to the second-level code table in the hierarchy, and displays a label that corresponds to the code table display name. The second menu is disabled until a selection is made in the first menu. Summary pages display both questions. Displaying a code-table hierarchy value in a list, or the codetable-hierarchy-layout options, are not supported.

WorkItem:245245 - Universal Access Responsive Web Application: Argument substitution in message text fails when the placeholder type is ‘%1d’.

Issue Description:

Date values are not substituted correctly in the message text when the placeholder type is "%1d". This only affects users of the Universal Access Responsive Web Application.

**User Interface Impact: **No

Steps to Reproduce:

  1. Navigate to an IEG page and enter a date field.
  2. Observe that any message displaying this date will output "%1d" instead of the actual date.

Resolution:

This has now been resolved and date values are substituted correctly.

WorkItem:245246 - Universal Access Responsive Web Application: Issue with the Next and Save & Exit buttons on summary pages

Issue Description:

It is not possible to navigate to the next page by using the ‘Next’ or ‘Save & Exit’ buttons if an attribute has been defined using a custom domain definition derived from IEG_INT32. This only affects users of the Universal Access Responsive Web Application.

**User Interface Impact: **No

Steps to Reproduce:

  1. Navigate to an IEG page where an attribute is defined by using a custom domain definition derived from IEG_INT32.
  2. Attempt to navigate to the next page or use ‘Save & Exit’ .
  3. Observe that the navigation is blocked.

Resolution:

This issue has now been resolved and columns with type Integer are converted to type String for lists in summary pages.

PLAYER

PO07565, WorkItem:216550 - Mandatory fields are accepting blank spaces in an IEG script

Issue Description:

The IEG scripts with name and address fields allow a single blank space character to be entered into a mandatory field which was accepted as a valid character.

**User Interface Impact: **No

Steps to Reproduce:

  1. Login as a caseworker.
  2. Register a new Person.
  3. Launch any IEG script for this Person which contains name and address fields which are mandatory.
  4. Fill the fields 'First Name', 'Last Name', 'Street 1' and 'Zip' with a single blank space (" ") only.
  5. Issue: The IEG script incorrectly allows the user to proceed through the next IEG page.

Resolution:

This issue has been resolved by adding a new domain-specific condition to check if the mandatory field contains a single blank space. Please note that if there is a custom validation in place this change will take precedence over it.

PO08084, WorkItem:242529 - IEG conditional question responses are not cleared and drop-down field is displayed with the previous value

Issue Description:

In an IEG script, drop-down fields within a conditional cluster retain a previously selected value after they are hidden by closing their parent conditional cluster.

This issue can be seen when running an IEG script through the internal Merative Social Program Management application. It occurs when a user navigates back to an IEG script page displaying a drop-down which stores a previously selected value.

User Interface Impact: No

Health Care Reform Steps to Reproduce:

  1. Login as an Insurance Affordability caseworker.
  2. Register a Person.
  3. Start a new application for the new Person.
  4. Navigate through the application entering the necessary mandatory information until the citizenship status related questions are reached.
  5. Update the citizenship status related questions as follows:
    • Is <FirstName> a US Citizen? = 'No'
    • Is <FirstName> a US National? = 'Yes'
    • Supporting Document: '<Select any value>'
    • Is client currently enrolled on a health program or plan? = 'No'
  6. Click on the 'Next' button.
  7. Navigate back to the citizenship status screen (either via left hand section navigation links or using 'Back' button on the page, if available).
  8. Change the answer to the question 'Is <FirstName> a US Citizen?' from 'No' to 'Yes'.
  9. Change the answer to the question 'Is "<FirstName> a US Citizen?' from 'Yes' back to 'No'.
  10. Issue: The values for the conditional questions are retained from the first time the user entered them.

Prerequisite for Non Healthcare Reform Customers: If you are a customer who does not use the Healthcare Reform Solution, but have configured Intelligent Evidence Gathering scripts as an Intake mechanism, you can reproduce this scenario by configuring a valid Intelligent Evidence Gathering script and adding the following to a 'question-page' display element.

  1. A 'question' display element as a drop-down.
  2. A 'condition' flow-control element returning true or false based on the value of the 'question' display element.
  3. A 'cluster' display element within the 'condition' flow-control element. This 'cluster' should contain a second 'question' display element as a drop-down.
  4. A second 'condition' flow-control element returning true or false based on the value of the second 'question' display element.
  5. A second 'cluster' display element within the second 'condition' flow-control element. This 'cluster' should contain a third 'question' display element as a drop-down.
  6. A third 'condition' flow-control element returning true or false based on the value of the third 'question' display element.
  7. A third 'cluster' display element within the third 'condition' flow-control element. This 'cluster' should contain a fourth 'question' display element as a drop-down.
  8. A second 'question-page' display element.

Non Healthcare Reform Steps to Reproduce:

  1. Select the required value from the first question to display the conditional cluster containing the second question.
  2. Select the required value from the second question to display the conditional cluster containing the third question.
  3. Select the required value from the third question to display the conditional cluster containing the fourth question.
  4. Select any value from the fourth question.
  5. Click 'Next' to navigate to the next question page.
  6. Click 'Back' to navigate back to the original question page.
  7. Select the required value from the first question which will hide the first conditional cluster containing the second question.
  8. Issue: The value of the second question display element is retained, as can be seen by re-selecting the required value from the first question to display the conditional cluster containing the second question.

Resolution:

This issue has been resolved by ensuring the value of a drop-down within a conditional cluster is cleared each time it is hidden as a result of a user action.

Solutions

Income Support

PO07833, WorkItem:232547 - Not all Tax Filers are displayed for selection on Tax Dependent Information page when a household has a tax dependent and married couple who change their 'filing jointly' response to 'No' after completing Tax Dependent Information

Issue Description:

Not all Tax Filers are displayed for selection at the bottom of the Tax Dependent Information page when the household has a tax dependent (e.g. child) and a married couple who change their 'filing jointly' response from 'Yes' to 'No'. The expected behaviour is both Mother and Father should be available for selection there.

**User Interface Impact: **No

Steps to Reproduce:

  1. Login as an Insurance Affordability caseworker.
  2. Start a three member household application with Wife as the primary client (e.g. Wife Test, Husband Test and Child Test). Specify relationship as follows: Wife is the spouse of Husband, Wife is the parent of Child, Husband is the parent of Child.
  3. Navigate to the Tax Filer Information page. All three household members (Mother, Father and Child) are available for selection on the page. Select only the Husband as the tax filer and click Next to get to Married Couple Filing Status page.
  4. Answer Yes for 'Does Mother plan to file a joint federal tax return with Father next year?' question.
  5. Click Next.
  6. Use the left-hand navigation to move back to Applicant Details page then keep clicking Next until the Tax Filer Information page is reached again. Note this time both Mother and Father are selected as tax filers. This is expected behaviour (both applicants become tax filers when they choose to file taxes jointly). Click Next to get to Married Couple Filing Status page.
  7. Answer Yes for 'Does Father plan to file a joint federal tax return with Mother next year?' question. Note the Father and Mother are now swapped in the question (see Step 4 for comparison), this is expected behaviour because when both spouses are tax filers the second spouse from the left will always be asked to file taxes with the first spouse.
  8. Click Next to reach the Tax Dependent Information page. Do not make any selections on the page and click Back to return to the Married Couple Filing Status page.
  9. This time select No for 'Does Father plan to file a joint federal tax return with Mother next year?' question and click Next to get to the Tax Dependent Information page again.
  10. Answer Yes for 'Is anyone in this household expected to enter Child as a dependent on their tax return?' question.
  11. Issue: Only Wife is available for selection at the bottom of the page below the 'Who expects to claim Child as a dependent on their tax return?' question.

Resolution:

Both relevant tax filers are now appearing for selection when the Child Dependent question on tax income is asked.

Technical:

There is a custom function - updateSpouseInformation() in CustomFunctionUpdateFilingTogetherInformation.java. It sets filing jointly status for spouses when 'Yes' or 'No' is selected on the Married Couple Filing Status page. This condition has been fixed to allow the correct selection for this scenario.

PO08065, WorkItem:241938 - Reports section is incorrectly displayed when the Business Intelligence and Analytics for Income Support component is not installed

Issue Description:

The Reports section in the Income Support application was incorrectly displayed when the Income Support component was installed without the Business Intelligence and Analytics for Income Support component.

User Interface Impact: No

Steps to Reproduce:

  1. Run the installer for 'Merative Social Program Management Platform Development'.
  2. Run the installer for 'Merative Income Support Development', but de-select the Income Support Business Intelligence component.
  3. Build and deploy the application.
  4. Login as an Income Support caseworker.
  5. Select the Reports section
  6. Issue: An exception is thrown as the Business Intelligence and Analytics for Income Support component is not installed.

Resolution:

The Reports section no longer displays in the Income Support application when the Income Support component is installed without the Business Intelligence and Analytics for Income Support component.

Technical:

The reported problem has been resolved by removing the reference to IS Reports from the following application file:

  • EJBServer/components/ISProduct/tab/ApplicationViews/Combined
    Worker/COMWRAPP.app

and creating a new application file referencing the IS Reports section in the IncomeSupportBI component

  • EJBServer/components/IncomeSupportBI/tab/ApplicationViews/
    COMWRAPP.app
MEDICAL ASSISTANCE

PO07710, WorkItem:226280 - Address Evidence Preferred indicator not set on the integrated case and application case

Issue Description:

When an Insurance Affordability application was submitted, the preferred address attribute was not set correctly in 'Private Address' evidence.

**User Interface Impact: **No

Steps to Reproduce:

  1. Login as Insurance Affordability caseworker.
  2. Register a participant and enter the address in Private Address cluster.
  3. Submit an application for the registered person selecting 'Yes' for both of the following questions on the 'Information About You' page -
    • Do you have a fixed address?, and
    • Is the mailing address the same as home address?
  4. Authorise the application. The integrated case is created successfully.
  5. Navigate to the integrated case and select Evidence > Dashboard > Addresses and verify the private address.
  6. Issue: In “Address Details” section the Preferred indicator value is "No".

Resolution:

The preferred address attribute wasn't set during the evidence mapping. The preferred address attribute is now set correctly.

Child Welfare

PO07923, WorkItem:237723 - CCV does not load from context panel list view for child welfare Investigation, Ongoing and Adoption cases

Issue Description:

The Citizen Context Viewer (CCV) is not opening in the Context Panel list view for the Investigation, Ongoing and Adoption Child Welfare cases.

**User Interface Impact: **No

Steps to Reproduce:

  1. Login as a Child Welfare intake worker.
  2. Create and submit an intake, with the recommendation set to 'Screened In'.
  3. Login as a Child Welfare intake supervisor and approve the recommendation.
  4. Log back in as a Child Welfare intake worker and navigate to the approved intake.
  5. Click 'Start Investigation' from the actions menu and complete the process (be sure to select both participants); an Investigation Case is created.
  6. In the Context Panel, click on the list view icon (beneath the camera icon) to change the view from Photo View to List View.
  7. Click on the arrow icon to the left of either participant.
  8. Issue: the CCV will not launch.

Resolution:

This issue has been fixed and the CCV now launches in the Context Panel list view for the Investigation, Ongoing and Adoption Child Welfare cases.

WorkItem:238971 - Incorrect Visit Type displayed when modifying Medical Visit information

Issue Description:

When a Medical Visit is edited for a Person, Developmental Assessment always displays as the Visit Type regardless of the Visit Type that was saved initially.

**User Interface Impact: **Yes

Steps to Reproduce:

  1. Login as a Child Welfare intake worker.
  2. Register a Person.
  3. On the Person home page, select the Medical tab.
  4. Select Visits.
  5. Click on the New page level menu to create a new visit.
  6. Select the drop-down for Visit Type and choose Illness-Medical.
  7. Also populate the Visit Date and Description fields.
  8. Click Save.
  9. Select the Edit row level menu option on the Medical Visit.
  10. Issue: Developmental Assessment is now displayed as the Visit Type instead of Illness-Medical.

Resolution:

This issue is now resolved and the Visit Type previously saved is displayed when the caseworker selects to edit the Medical Visit.

Techical:

The following page has been updated so that the Visit Type is taken from the DISPLAY phase bean rather than being treated like it was on a create page and being attached to the ACTION phase bean:

  • CFSSMedicalVisit_modifyMedicalVisit.uim

Child Welfare SDM

PO08033, WorkItem:240897 - SDM Screening Assessment Questions Missing

Issue Description:

The screening assessment script for a Structured Decision Making (SDM) Child Welfare caseworker is missing the question labels for questions 1, 3, 5, 6, 7, 8 & 12.

User Interface Impact: Yes

Steps to Reproduce:

  1. Login as a Structured Decision Making Child Welfare intake worker.
  2. Select New Intake from the Quick Links Pod.
  3. Select Category: Child Protection Services, Types: Child Abuse or Neglect, Date: today's date.
  4. Click Save.
  5. The system will create the intake.
  6. Navigate to the Participant tab and from the actions menu select 'Create New Participant'.
  7. Add First Name, Last Name and select Role as 'Alleged Victim'.
  8. Select Next and select Finish on the following page.
  9. Navigate to the Assessments tab.
  10. There are no question labels defined for questions 1, 3, 5, 6, 7, 8 & 12.

Resolution:

The missing question labels have now been configured correctly for the screening assessment script.

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

Release Notes 7.0.6.0.csv

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

Document Information

More support for:

Merative Social Program Management

Software version:

7.0.6

Operating system(s):

Linux, Windows

Modified date:

21 March 2019