Merative ™ Social Program Management 7.0.9.0 Refresh Pack

 

 

 

 

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

 

 

 

Release Notes

 

 

Abstract

 

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

 

 

Introduction

 

Welcome to the Merative Social Program Management 7.0.9.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.9.0 Refresh Pack release includes new functionality, for detailed information about these new features, see the What's new in Version 7.0.9.0 topic in the product documentation.

 

For more information about version 7.0.9.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.

 

This 7.0.9.0 Refresh Pack release incorporates content from previous 7.0.X releases, which is documented separately in the following set of online 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 https://www.merative.com/support/spm.

 

 

Installation

 

This 7.0.9.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.5.0 iFix2
  • 7.0.6.0 Refresh Pack
  • 7.0.6.0 iFix1
  • 7.0.7.0 Refresh Pack
  • 7.0.7.0 iFix1
  • 7.0.7.0 iFix2
  • 7.0.7.0 iFix3
  • 7.0.7.0 iFix4
  • 7.0.8.0 Refresh Pack
  • 7.0.8.0 iFix1
  • 7.0.8.0 iFix2

 

Prior to running the 7.0.9.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 https://www.merative.com/support/spm

 

 

Improvements, Resolved Issues and Third Party Updates

 

Third Party Updates
Cúram Enterprise Framework
Cúram Modules
Solutions
Code Removal

 

 

Third Party Updates

 

WorkItem:160329 - Introduce support for Oracle WebLogic Server 12cR2 (12.2.1)

 

The Merative Social Program Management (SPM) application now supports Oracle WebLogic Application Server 12.2.1 and higher fix packs.


The following changes were made to the SPM application to enable this support:

 

  • Annotation processing was turned off on the generate-texthelpers target when compiling text helpers.
  • Removed implementation.jar from the classpath of the coreinf-ejb.jar.
  • Removed (javax.ws.rs.*) from the preferred packages in the Rest weblogic-application.xml.
  • A new initial parameter was added in the Rest web.xml to set the Jackson packages as a provided package for the Jersey Servlet.
  • A new initial parameter was added in the Rest web.xml to disable Eclipse Moxy as a default JSON parser for the Jersey Servlet.

 

Technical:


The following files have been updated:

  • ../CuramCDEJ/bin/build.xml
  • ../CuramSDEJ/bin/app_buildEAR.xml
  • ../EJBServer/components/Rest/resources/ear/wls/META-INF/weblogic-application.xml
  • ../EJBServer/components/Rest/resources/ear/war/WEB-INF/web.xml
  • ../EJBServer/components/Rest/script/rest_build.xml

 

WorkItem:250451 - Introduce support for Oracle 19c (12.2.0.3)

 

Merative Social Program Management has now certified the usage of the Oracle 19c (12.2.0.3) database. Oracle Database 19c is the Long Term Support Release or 'Terminal Patch Set' for the Oracle Database 12.2 Release. This means that for the Merative Social Program Management 7.0.9.0 release, the following Oracle versions are supported:

 

  1. Oracle Database 12c Release 1 (12.1)
  2. Oracle Database 12c Release 2 (12.2)
  3. Oracle Database 19c (12.2.0.3)

 

WorkItem:253824 - 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 u231

 

WorkItem:253825 - Browser Support Update

 

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



Case Worker Application Browser Support

  • Google Chrome updated to 78

 

Universal Access Application Browser Support

  • Google Chrome updated to 78
  • Mozilla Firefox updated to 70
  • Apple Safari updated to 13

 

WorkItem:253826 - Tablet Accessibility Support

 

The certified version of Apple VoiceOver has been updated to iOS 13.2.2 This has been certified against Chrome 78.
 

WorkItem:253883 - Update the versions of the Jackson JARs

 

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 utilize these utilities.

The versions of these JARs have now been updated from 2.9.9.3 to 2.9.10.1. As a result of this upgrade, the following changes have been made in the JDE and REST deliverables.

 

  • ../CuramSDEJ/lib/third_party_version.properties - the versions of the specified Jackson JARs have been updated.

 

  • ../CuramSDEJ/lib/jackson-databind-2.9.10.1.jar - new JAR added.
  • ../CuramSDEJ/lib/jackson-databind-2.9.9.3.jar - old JAR removed.

 

  • ../CuramCDEJ/lib/ext/jar/jackson-databind-2.9.10.1.jar - new JAR added.
  • ../CuramCDEJ/lib/ext/jar/jackson-databind-2.9.9.3.jar - old JAR removed.

 

  • ../EJBServer/components/Rest/restlib/dependencyLibsExt/jackson-databind-2.9.10.1.jar - new JAR added.
  • ../EJBServer/components/Rest/restlib/dependencyLibsExt/jackson-databind-2.9.9.3.jar - old JAR removed.

 

WorkItem:253920 - Update the version of the commons-beanutils JAR

 

Apache Commons BeanUtils provides easy-to-use wrappers around the Java Reflection and Introspection APIs. The Java Development Environment (JDE) utilizes this.

The versions of this JAR have now been updated from 1.9.3 to 1.9.4. As a result of this upgrade, the following changes have been made to the JDE deliverable.

 

  • ../CuramSDEJ/lib/third_party_version.properties - the versions of the specified commons-beanutils JAR have been updated.

 

  • ../CuramSDEJ/lib/commons-beanutils-1.9.4.jar - new JAR added.
  • ../CuramSDEJ/lib/commons-beanutils-1.9.3.jar - old JAR removed.

 

  • ../CuramCDEJ/lib/ext/jar/commons-beanutils.jar - new JAR added.
  • ../CuramCDEJ/lib/ext/jar/commons-beanutils.jar - old JAR removed.

 

 

Cúram Enterprise Framework

 

Technical Services
Integrated Case Management
Application Development Environment
Business Services

 

PO08438, WorkItem:250707 - The facade operation searchUserHistory is called twice when using the Smart Navigator

 

Issue Description:


When a user places focus on the Smart Navigator search bar, the searchUserHistory facade operation is called twice. The second call results in the initial call being canceled. It was also discovered that removing a keyword from the Smart Navigator search bar, via clicking or keyboard, also results in the searchUserHistory facade operation being called twice, again with the second call canceling the initial call.

User Interface Impact: No

Steps to Reproduce:

Scenario 1:

 

  1. Login as a caseworker.
  2. Open Chrome Developer Tools and navigate to the Network tab.
  3. Place focus on the Smart Navigator search bar.
  4. Observe the server calls in the Network tab of Chrome Developer Tools.
  5. Issue: The searchUserHistory facade operation is called twice, with the first call being canceled.

 

Scenario 2:

 

  1. Login as a caseworker.
  2. Open Chrome Developer Tools and navigate to the Network tab.
  3. In the Smart Navigator search field, add a keyword without adding any text.
  4. Remove the keyword added by either clicking the X next to the keyword or focusing on the keyword and pressing ENTER via the keyboard.
  5. Observe the server calls in the Network tab of Chrome Developer Tools.
  6. Issue: The searchUserHistory facade operation is called twice, with the first call being canceled.

 

Resolution:


The first issue was caused by a function carrying the same name as a default function. When the default function was called, the code redirected the call to the custom function, causing the second server call. This issue was resolved by changing the custom function name from the default _onFocus() to _givenFocus().

The second issue was caused by a call to _doQuickSearch when the keyword element was destroyed. This call was performed regardless of whether or not the Smart Navigator search bar was populated. The issue was resolved by ensuring the call to _doQuickSearch is only performed when a value exists in the Smart Navigator search bar.
 

PO08443, WorkItem:250833 - Delete attachment takes too long to cancel the record (OpenText CMIS) due to an unnecessary full read

 

Issue Description:


When a large attachment is deleted, the delete operation takes a long time.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a caseworker and navigate to any Person home page.
  2. Click on the Client Contacts tab and then select Attachments.
  3. Create a new Attachment (use a big size file) using the page action and click Save.
  4. Delete the attachment using the row-level action.
  5. Issue: It takes too long to cancel the record.

 

Resolution:


When an attachment is deleted, the full attachment details are read before deletion which can cause performance issues when reading large attachments. This issue has been resolved by updating the delete function to perform a narrower read where only the attachment header details and not the full content of the attachment are read.

 

PO08451, WorkItem:250986 - Narrow text fields within modals are causing truncation

 

Issue Description:


Some of the modals across the application contain text fields which are not wide enough and are causing truncation of data which makes the data only partially visible to the user.

User Interface Impact: No

Steps to Reproduce:

Scenario 1:

 

  1. Login as an administrator.
  2. Navigate to the shortcuts menu within the Administration Workspace.
  3. Expand the Users section and select New User.
  4. Enter details in all the fields within the Contact section.
  5. Issue: The details entered are truncated in multiple fields.

 

Scenario 2:

 

  1. Login as a caseworker.
  2. Navigate to the shortcuts menu within Cases and Outcomes.
  3. Expand the Registration section and select External Party.
  4. Enter an External Party Name, select 'Community Based Organization' from the Type drop-down, and enter a value for Address Line 1 and select Next.
  5. Select No for Verification Indicator and click Save.
  6. Navigate to the Offices tab and click New.
  7. Enter a Name and Address for the new office and click Save.
  8. From the Office action menu select New Office Phone.
  9. Enter details in all the Phone and Extension fields.
  10. Issue: The details entered are truncated.

 

Scenario 3:

 

  1. Login as a Provider Management Resource Manager.
  2. Navigate to the shortcuts menu within Providers and Services.
  3. Expand the Provider Groups section and select Enroll Provider Group.
  4. Click next to go to the Provider Group Details Page.
  5. Enter details for the Provider Group Name, Address, Payment Method and Frequency fields and click Finish.
  6. From the tab level actions menu add a New Member to the Provider Group.
  7. Click the Credentials tab and click Training. Click New Non managed Training Program.
  8. From the list actions menu select Edit.
  9. Enter details in all the fields.
  10. Issue: The details entered are truncated in multiple fields.

 

Resolution:


The modal size and field widths have been adjusted in multiple pages to fix the issues.

Technical:


The issues were resolved by updating modal size and field widths in the following pages:

 

  • ../webclient/components/core/Organization/User/Organization_createUser.uim
  • ../webclient/components/core/ExternalParty/ExternalParty/Register/Wizard/RegisterExternalParty_registerWizardView.vim
  • ../webclient/components/core/ExternalParty/ExternalPartyOfficePhoneNumber/Create/ExternalParty_createOfficePhoneNumber.uim
  • ../webclient/components/CPM/ProviderGroup/ProviderGroupMember\ProviderManagement_createProviderGroupMember.uim
  • ../webclient/components/CPM/ProviderGroup/TrainingProgram/ProviderManagement_recordCompletedTrainingForProviderGroup.uim
  • ../webclient/components/CPM/ProviderGroup/TrainingProgram/ProviderManagement_updateCompletedTrainingForProviderGroup.uim
  • ../webclient/components/Appeal/Hearing/Phone Contact/UserAppeal_createPhoneNumber.uim
  • ../webclient/components/Appeal/Hearing/Phone Contact/Appeal_modifyPhoneContactViewIC.vim

 

PO08543, WorkItem:253116 - When using Smart Navigator, keyword search displays duplicate items

 

Issue Description:


There is an issue when searching for a person who has at least five different aliases using the Smart Navigator. When a user searches for this person by first and last name and uses a keyword, the Smart Navigator displays duplicated items for each record.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Register a Person.
  3. Open the Evidence tab inside the created person.
  4. Click New and select Names.
  5. Insert first and last name, which must be similar to the first and last name of the person.
  6. Select Alias as type.
  7. Click Save.
  8. Add four more aliases as Names evidence by repeating steps 4 to 7.
  9. Type the first and last name into the Smart Navigator.
  10. Type the keyword 'evidence' into the Smart Navigator.
  11. Issue: The drop-down list shows duplicated items for each record.

 

Resolution:


The issue has been resolved. Now when the Smart Navigator is used to search for a person with at least five aliases, by specifying the first name, last name, as well as a keyword, such as 'evidence', one evidence item for each record is displayed.
 

PO08549, WorkItem:253374 - When using Smart Navigator Search, arrow icons are displayed if at least six person records are returned and a non-person keyword such as 'reg' or 'register' is added to the search criteria

 

Issue Description:


When a user performs a search on the Smart Navigator which returns at least six different persons, unnecessary arrow icons are displayed on each person record when a non-person keyword is added to the search criteria. The following information message is displayed to the user, 'There are no matching items based on the Search Criteria entered'. If a keyword is entered to the search criteria which is related to a person, then this issue does not occur.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Register at least six different persons with a similar first and last name such as testOne, testTwo, etc.
  3. In the Smart Navigator, enter the first and last name of one of the created persons as the search criteria, test test, for example.
  4. Then add a non-person keyword such as 'reg' or 'register' to the search criteria.
  5. Issue: The Smart Navigator Search displays unnecessary arrow icons on each person record.

 

Resolution:


In this scenario, when the user performs a search which involves keywords that do not find a person record, the Smart Navigator Search has been updated to not display unnecessary arrow icons on each of the person records.
 

PO08550, WorkItem:253388 - Smart Navigator Recent Search displays the wrong person when the same reference number is assigned to multiple people

 

Issue Description:


When the same reference number is assigned to different people, searching for a person using first and last name using the Smart Navigator Search returns the correct results. However, the Smart Navigator Recent Searches does not return the right results and displays the wrong person.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Register two Persons.
  3. Navigate to the Evidence tab of the second registered Person.
  4. Add new Identifications evidence.
  5. On the Identifications evidence modal, enter the first person's reference number in the field ID Reference.
  6. Select Claim/Benefit Reference Number as Type.
  7. Select the Preferred checkbox.
  8. Click the Save & Next button.
  9. Set Evidence End date to current date.
  10. Select the old reference number from the list of records which require an end date and click Finish.
  11. Close all the tabs.
  12. Enter the first and last name of the second person in the Smart Navigator Search.
  13. Clear the Smart Navigator Search box.
  14. Click on the Smart Navigator Search box to list the recent searches.
  15. Issue: The Smart Navigator Recent Search displays the first person instead of the second person.

 

Resolution:


This issue has been fixed now and the Smart Navigator Recent Search displays the right person who has been previously searched for when the same reference number is assigned to different people.
 

WorkItem:254438 - Deleted attachment can be downloaded from the Edit Attachment modal

 

Issue Description:


After deleting an attachment, a user can download the file associated with the deleted attachment from the Edit Attachment modal.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Register a new Person.
  3. From the Person home page, select Client Contact and then Attachments.
  4. Click New to create a new attachment.
  5. Browse for a File and add the mandatory Description.
  6. Click Save.
  7. Select Delete from the row-level menu for the newly created attachment.
  8. Answer Yes on the Delete Attachment modal.
  9. Select Edit from the row-level menu to update the deleted attachment.
  10. Issue: The information in the Name field shows a link for the filename that allows the user to download the file.

 

Resolution:


The Edit Attachment modal has been updated so that if the status of the attachment is Canceled, the filename in the Attached File field is shown as normal text and not as a link.

Technical:


The following page has been updated to only show the filename as text if the attachment has been canceled:

  • ../core/Participant/Attachment/Participant_modifyAttachmentView.vim

 

Technical Services

 

PO08320, WorkItem:248175 - Communications created in Merative (SPM) v6 for a Prospect Person cannot be opened in Merative (SPM) v7

 

Issue Description:


After upgrading Merative Social Program Management (SPM) to v7 or higher, migrated communication records that were created for a Prospect Person in a previous version of Merative SPM cannot be opened. This issue is specific to Microsoft Word and Proforma communications.

User Interface Impact: No

Prerequisite(s):

 

  1. There is an installation of Merative SPM v6, or an earlier version, that contains Prospect Persons who have existing Microsoft Word or Proforma communication records.
  2. A successful upgrade to Merative SPM v7, or later, is performed.

 

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Search for a prospect person who has Microsoft Word or Proforma communications records on an integrated case.
  3. Open the integrated case.
  4. Select the Contact tab and select Communications.
  5. Select All in the Regarding Case Member drop-down and click Search.
  6. For any of the Microsoft Word communications, select Open Microsoft Word from the row-level action. Alternatively, for any Proforma communications select the Preview row-level action.
  7. Issue: An unhandled server exception is thrown.

 

Resolution:


This issue has been resolved by adding additional logic which correctly handles opening Microsoft Word or previewing Proforma communications that were created in older versions of the application.

Technical:


A new participant security check was added in Merative v7 when downloading Microsoft Word or Proforma communications. In the case of Microsoft Word communications, this refers to opening the Microsoft Word document. For Proforma communications, this refers to previewing the document. It was possible to create communications in an older version of SPM without specifying a concern role identifier. The new security check did not correctly handle this and an unhandled server exception was thrown. The security check logic has been updated and is now backward compatible.
 

Integrated Case Management

 

Eligibility & Entitlement
Evidence Management
Common
Participant Management

 

WorkItem:244924 - While printing inline view of Notes from a Person or Case, a placeholder text 'undefined' incorrectly displays at the top of a page

 

Issue Description:


While printing the inline view of Notes from a Person or Case, the print layout incorrectly displays the placeholder text 'undefined' at the top of the page instead of the page title.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Register a Person.
  3. Click on the Client Contact tab and select Notes.
  4. Add a new Note using the New page action.
  5. Click on the toggle to view the inline page of the record.
  6. Click on the print icon to print the content.
  7. Issue: Print layout displays the text 'undefined' at the top of the page instead of the page title.

 

Resolution:


When printing the inline view of Notes from a Person or Case, the page title now displays correctly.
 

WorkItem:252296 - Unable to record meeting minutes for a meeting on an integrated case

 

Issue Description:


A user can schedule a meeting for an integrated case but when trying to enter the details of the meeting, the Record Meeting Minutes wizard opens but the user cannot navigate forward or backward, the Meeting Details page is frozen.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Register a Person and create an integrated case.
  3. Open the created case.
  4. Select the Events tab.
  5. Select New Meeting from the menu and schedule a meeting.
  6. Change the Events view to List View.
  7. Click on the row-level action for the meeting activity created and select Record Meeting Minutes.
  8. Issue: Record Meeting Minutes wizard is frozen and does not allow the user to navigate forward or backward.

 

Resolution:


Now the Record Meeting Minutes wizard is displayed correctly from any integrated case and it allows the user to record the meeting details and to navigate forward or backward.
 

PO08599, WorkItem:254733 - The field label Reason is getting wrapped to next line when reopening an Integrated Case

 

Issue Description:


The field label Reason is getting wrapped to the next line on the Reopen Case modal of an integrated case.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Register a Person.
  3. On the Person home page, select New Case from the tab action menu and create an integrated case.
  4. On the integrated case home page, select Close Case from the tab action menu to close the case.
  5. Select Reopen Case from the tab action menu.
  6. Issue: Field label Reason is wrapped.

 

Resolution:


This issue is resolved and the field label Reason no longer wraps onto the next line.

Technical:


The following UIM file was updated to fix this issue:

  • ../webclient/core/Integrated Case/Core/Reopen/IntegratedCase_reopen.uim

 

The overall modal width was increased by setting the WINDOW_OPTIONS="width=500" and removing the width attribute from the Priority field.
 

ELIGIBILITY & ENTITLEMENT
 

PO08648, WorkItem:254211 - IndexOutOfBounds exception thrown during the reassessment of a CREOLE product

 

Issue Description:


An issue occurs during the reassessment of CREOLE based cases whereby an IndexOutOfBounds exception is thrown when accessing the list of decisions associated with the most recent determination due to an incorrect index being used when accessing those decisions. This issue only occurs when there is no overlap between old and new decisions being generated as a result of a reassessment, and there are more decisions associated with the latest determination than there were with the determination being superseded. An example of where this can occur is if the certification period is being moved from a period in the past to a period in the future, where that future period has more rates associated with it.

User Interface Impact: No

Steps to Reproduce:

Scenario (Generic)

 

  1. Login as a caseworker.
  2. Register a new Person.
  3. Create a new integrated case for the Person.
  4. Add a certifiable product to the integrated case, setting the delivery pattern to 'Monthly By Check In Advance On 1st'.
  5. Add a certification to cover the period 1st September 2018 to 30th September 2018.
  6. Add the necessary evidence to make the product eligible, ensuring that there are 3 different rates applicable during September.
  7. Activate the evidence.
  8. Submit, approve and activate the product delivery.
  9. Verify that an eligible current determination exists.
  10. From the Financials tab, issue the payment(s) for September.
  11. From the Certifications tab, modify the certification period to cover 16th January 2019 to 19th January 2019 and click Save.
  12. Verify that an overpayment has been created.
  13. From the Certifications tab, add a new certification to cover the period 23rd January 2019 to 24th January 2019.
  14. Issue: The final step should make the case eligible for the new certification period, but this step fails due to the IndexOutOfBounds exception error being encountered during case reassessment.

 

Resolution:


The logic for referencing the decisions associated with the most recent case determination in business scenarios such as the one outlined here has been updated to reference the correct index, thereby preventing the IndexOutOfBoundsException from occurring and allowing the reassessment to complete successfully.
 

EVIDENCE MANAGEMENT
 

PO08567, WorkItem:253775 - Incorrect evidenceID and evidenceDescriptorID identifiers returned by methods on the PDCPerson and Evidence facades

 

Issue Description:


Incorrect evidenceID and evidenceDescriptorID identifiers are returned when some of the list evidence operations on the PDCPerson facade class are called on an evidence that has successions. The APIs in question are:

 

  • listCurrentParticipantEvidenceByTypes
  • listParticipantEvidenceByTypes
  • searchParticipantEvidenceByDateRange

 

The same issue also affects the following facade operations:

 

  • Evidence.listAllEvidence
  • Evidence.listAllEvidence1

 

The above APIs are supposed to return the latest, or most up to date, record in a succession. Instead, they are returning the most recently updated record in a succession. This behavior is unintuitive and goes against the intended behavior/contract of these APIs.



Note:
None of the above APIs are being used by out-of-the-box functionality.


User Interface Impact: No

Steps to Reproduce:

 

  1. Register a new Person, Tom Smith, with a Date of Birth of 1st January 1980.
  2. Edit Names evidence for this Person, adding an Effective Date of Change of 1st January 1985 and modifying the First Name to Tommie. The following succession will now exist for Names evidence:
    • Tom Smith (null effective date of change)
    • Tommie Smith (effective date of change = 01/01/1985)
  3. Edit the older record in the succession, which is the first record for Tom Smith above, but do not change its effective date of change.
  4. Now call one of the affected methods, PDCPerson.listCurrentParticipantEvidenceByTypes, for example.
  5. Issue: The evidenceID and evidenceDescriptorID identifiers returned do not match the current active evidence record. The identifiers returned should be for the Tommie Smith record above. Instead, the evidenceID and evidenceDescriptorID identifiers of the older, Tom Smith, record are returned.

 

Resolution:

The logic in these APIs has been updated so that the evidenceID and evidenceDescriptorID identifiers of the most up to date record in a succession are returned.

COMMON
 

PO08514, WorkItem:249170 - Date field values are getting truncated in modal dialogs

 

Issue Description:


The date values are getting truncated in a number of date fields in the application modal dialogs. This results in the user being unable to see the full date value entered or pre-populated.
Some examples of modal dialogs where this issue can be seen are: New Bank, Edit Assessment, Edit Citizenship, Edit Foreign Residency, New Attendee, New Failure Reason, New Milestone, Create Activity and Edit Training.

User Interface Impact: No

Steps to Reproduce:


This is one scenario of a date field on the New Bank modal dialog that was affected by this issue:

 

  1. Login as an administrator.
  2. From the shortcuts panel, navigate to Financial, and then Banks.
  3. Click New to add a new Bank.
  4. In the New Bank modal dialog that opens, enter the date 12/30/2000 as the Start Date.
  5. Issue: The Start Date is truncated and the user is unable to see the full date value.

 

Resolution:


The CSS properties of the date field have been modified to prevent the truncation of dates. The user is now able to see full date values in the affected date fields in modal dialogs.
 

PARTICIPANT MANAGEMENT
 

PO05305, WorkItem:124035 - Notes display XML text after client merge

 

Issue Description:


When a client merge is completed and Notes are merged, the fields Subject and the Last Update contain XML metadata rather the actual notes text from the original client.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a caseworker.  
  2. Register two Persons.
  3. Add a new Note to each of them. Notes can be viewed under Client Contact.
  4. Go to the home page of the first Person and select the Administration tab.  
  5. Select Duplicates.  
  6. Select Mark New Duplicate.  
  7. Select the Person you want and then select Save & Start the Merge.
  8. Keep navigating through the wizard and in the Notes section, select the Notes from the duplicate.  
  9. Navigate to the end and select Complete Merge.
  10. Issue: When viewing the Notes, the Subject and the Last Update fields contain XML metadata.

 

Resolution:


This issue has been resolved by ensuring that the merged notes are exact replicas of the original ones.
 

WorkItem:253118 - Defect viewing the long format of Canadian addresses within the application

 

Issue Description:


The long format of an address is not being displayed when the address layout is set to Canadian.

User Interface Impact: No

Prerequisite(s):

 

  1. The default address format needs to be set to Canadian. This is a development task and requires the DEFAULT_COUNTRY_CODE and DEFAULT_FORMAT to be set to CA within the curam-config.xml file before the server is built and deployed.
  2. On the deployed server, login as a system administrator and search for and update the following system properties under Application Data > Property Administration in the shortcuts panel. Publish the changes using the Publish page action.
    • curam.address.addressLayout=CA
    • curam.address.addressDataLocaleForDefaultAddresses=en_CA

 

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Register two Persons. Each of these will have a Canadian address.
  3. For the first Person, click on the Client Contact tab and select Communications.
  4. Select Record Communication from the page action menu.
  5. Using the Person search, specify the second Person as the correspondent.
  6. Click Next.
  7. On the second page of the wizard, enter the Subject and Text.
  8. Click Save.
  9. From the Communications list page, use the toggle to view the details of the newly recorded communication.
  10. Issue: The long format of the address for the correspondent does not appear in the Correspondent Details cluster.

 

Resolution:


The implementation of the Canadian address has been updated so that the long format now renders correctly and is viewable on the client.
 

Application Development Environment

 

Client Development Environment

CLIENT DEVELOPMENT ENVIRONMENT
 

Accessibility
Look & Feel

 

PO08621, WorkItem:239509 - When printing a page containing a context panel on Internet Explorer, sometimes only the context panel can be printed

 

Issue Description:


For pages containing a context panel, printing the full page using the page level print icon requires two print dialogs to appear. The first dialog controls printing the context panel, the second dialog controls printing the main content area. In Internet Explorer, sometimes only the first print dialog appears meaning the full page cannot be printed.

 

User Interface Impact: No

Prerequisite(s):

 

  1. Set the Application Configuration property disable.context.panel.print=false

 

Steps to Reproduce:

 

  1. Open the Internet Explorer browser.
  2. Login as a caseworker.
  3. Search for a person and open their home page.
  4. Click on the page level print icon.
  5. Issue: Intermittently, only one print dialog appears.

 

Resolution:


This issue has been resolved and now a full page can be printed every time using the page level print icon by ensuring a print dialog for the context panel and a print dialog for the main content area always appear.
 

PO07918, WorkItem:246065 - Printing issues on Search Page results using Chrome browser

 

Issue Description:


When printing the results of a Person search with the browser's background graphics print option enabled, the toggle arrow button overlaps the cluster title making it difficult to read.

User Interface Impact: No

Steps to Reproduce:

 

  1. Use the Google Chrome browser.
  2. Login as a caseworker.
  3. Navigate to the Person Search page.
  4. Search for an existing person.
  5. Select Print.
  6. In the browser printing options, enable the background graphics option.
  7. Issue: The toggle arrow button overlaps the cluster title.

 

Resolution:


This issue has been resolved by APAR PO08030 which updated the background images of the toggle arrow button to an image element for accessibility purposes.
 

PO08416, WorkItem:250213 - Browser level loss of information dialog behaves inconsistently when users click either the back, refresh, or close browser buttons

 

Issue Description:


When users click either the Back, Refresh, or Close browser buttons on the browser, by default a warning message is displayed in a confirmation window. This dialog behaves inconsistently and sometimes it is not displayed to the user and when this happens, the user can lose the information entered on the page.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Navigate to the Person Search page.
  3. Click on the back, refresh or close browser button.
  4. Select the option to stay on the page in the warning dialog.
  5. Enter a name in the First Name field on the search page.
  6. Click on the back, refresh or close browser button.
  7. Issue: A dialog should display on the browser asking the user if they want to stay on the page or leave the page as requested. Sometimes this message is not displayed to the user.

 

Resolution:


This issue has been resolved by updating the underlying JavaScript for the event that controls the browser dialog confirmation. For more information on browser configuration, view our updated documentation on https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation
 

PO08468, WorkItem:251184 - Microsoft Word File Edit Control Panel modal cannot be dismissed after being relaunched from a previous session

 

Issue Description:


When a user is creating a Microsoft Word communication in Internet Explorer 11, there are issues if the system times out and the Microsoft Word File Edit Control Panel modal is still open. When the user logs in again after the session has timed out, the Microsoft Word File Edit Control Panel modal remains open and it cannot be closed.

User Interface Impact: No

Prerequisitie(s):

 

  1. Set the Application Configuration property tabSessionUpdateCountThreshold=10
  2. Set the Application Configuration property tabSessionUpdatePeriodThreshold=120

 

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Register a Person.
  3. Create an integrated case for the newly registered person and open it.
  4. Navigate to the Contacts tab and select the Communications navigation tab.
  5. Select New Microsoft Word from the options menu and create a new Microsoft Word Communication.
  6. With the File Edit Control Panel modal open, allow the application to time out.
  7. Login as a caseworker.
  8. Issue: The File Edit Control Panel modal opens again and cannot be closed.

 

Resolution:


This issue has been resolved by ensuring a record of the Microsoft Word File Edit Control Panel modal being opened is never stored in the tab session, therefore the File Edit will never be relaunched from a previous session following login.
 

PO08498, WorkItem:251863 - The Smart Navigator search result displays date of birth incorrectly

 

Issue Description:


The Smart Navigator search panel displays a person's date of birth with a date that is one day earlier than the actual date. The issue occurs when the time zone on the client machine is set to a value less than the Coordinated Universal Time (UTC).

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Register a new Person.
  3. Change the time zone on the client machine to EST (New York).
  4. Clear the browser cache and refresh the page.
  5. Enter the name of the Person in the Smart Navigator search field at the top of the page.
  6. Issue: The date of birth displayed in the Smart Navigator search result is one day earlier than the actual date of birth of the Person.

 

Resolution:


This issue is now resolved. The Smart Navigator processing will now take the browser's time zone into account when displaying dates of birth.

Technical:


The issue was addressed by updating the following file

  • ../CuramCDEJ/lib/curam/web/jscript/curam/date/locale.js

to include a curam.date.locale.parseDate(dateString) function which formats dates in the browser's time zone.
 

PO08484, WorkItem:253403 - The Internet Explorer 11 browser may quit unexpectedly when attempting to print a large number of Notes with different styles and formats

 

Issue Description:


When attempting to print a large number of Notes containing different styles and formats from the Client Contact tab on a Person page, it may cause the browser application to quit unexpectedly. This issue only occurs with Internet Explorer 11.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Register a new Person.
  3. Navigate to Client Contact tab.
  4. On the Notes tab, click on the New button and create 30 Notes containing different styles and formats of text.
  5. Scroll down to the bottom of the page and change the Page size to 45.
  6. For each Note click on the toggle arrow to expand the contents.
  7. Click the Print icon at the Notes tab level.
  8. Issue: The Internet Explorer 11 browser may quit unexpectedly when attempting to print a large number of Notes with different styles and formats.

 

Resolution:


In order to reduce issues when printing Notes using Internet Explorer 11, a new hidden window is populated with Notes content upon clicking the page level print icon. The HTML complexity of this new window has been reduced to optimize the memory handling when printing.
 

WorkItem:253922 - Cluster toggle arrows displaying on print pages

 

Issue Description:


Cluster toggle arrows on the user interface help a user expand and collapse a cluster. When printing a page with clusters, the cluster toggle arrows are displaying underneath the cluster headings.

User Interface Impact: No

Steps to Reproduce:


This is one scenario of a user interface cluster that was affected by this issue:

 

  1. Login as a caseworker.
  2. Navigate to the Person Search page using shortcuts panel.
  3. Search for an existing person.
  4. Select Print.
  5. Issue: The toggle arrow images are displaying under the cluster heading.

 

Resolution:


This issue has been resolved by updating the user interface styling to not display the toggle arrow images when printing the page.
 

PO08577, WorkItem:254244 - Date selector displays a duplicate date in the month where the clock goes back one hour for daylight saving

 

Issue Description:


The Date Selector displays a duplicate date in the month where the clock goes back one hour as part of daylight savings time adjustments. The date that is duplicated varies depending on the time zone of the client machine.

User Interface Impact: No

Steps to Reproduce:

 

  1. Ensure the time zone on the client machine is set to EST (New York).
  2. Login as a caseworker.
  3. Navigate to the Person Search page.
  4. Select the Date Selector icon beside the Date of Birth field.
  5. Navigate to November.
  6. Issue: A duplicate date occurs after the first Sunday of the month.
  7. Ensure the time zone on the client machine is set to GMT (Dublin).
  8. Login as a caseworker.
  9. Navigate to the Person Search page.
  10. Select the Date Selector icon beside the Date of Birth field.
  11. Navigate to October.
  12. Issue: A duplicate date occurs after the last Sunday of the month.

 

Resolution:


This issue has been resolved by updating the underlying JavaScript around the Date Selector to correctly handle daylight savings time.

Technical:


The following file was updated to resolve this issue

  • ../CuramCDEJ/lib/curam/web/jscript/curam/dateSelectorUtil.js

 

The logic for rendering the Calendar was continually adding 24 hours to calculate each day of the month. When Daylight Savings Time ends, the clock goes backward and creates a 25 hour day. This caused the Calender to insert the same day twice, as adding 24 hours was not enough time to advance to the next day. This has been updated to instead add 1 day to the JavaScript Date object which automatically handles Daylight Savings Time.

ACCESSIBILITY
 

PO08410, WorkItem:249952 - HTML markup is being announced for icons on modal pages when using a screen reader

 

Issue Description:


When a visually impaired user navigates to a modal page that contains icons while using a supported screen reader, the entire page will be read out by the screen reader if the user does not interact with the page. When the screen reader reaches an icon, HTML markup is announced.

User Interface Impact: No

Steps to Reproduce:

 

  1. Enable a screen reader.
  2. Login as a Child Welfare caseworker.
  3. Create an Ongoing Case and select the Contacts page navigation tab.
  4. Create a New Contact and leave the modal dialog page idle.
  5. Issue: HTML markup is announced by the screen reader for the three icons present on the page.

 

Resolution:


When a visually impaired user navigates to a modal page that contains icons while using a supported screen reader and the page is read entirely by the screen reader, only the title associated with each icon is announced.
 

PO08409, WorkItem:250096 - Browser focus does not move to search results after a search is performed

 

Issue Description:


When a user performs any search and gets multiple results, the browser focus is set back to the first editable field on the page. As a result, the user has to navigate through the search criteria to get to the search results.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a Child Welfare Structure Decision Making caseworker.
  2. Open the Cases and Plans section.
  3. Open the shortcuts panel.
  4. Click on Search, then Child Welfare Search.
  5. Select a category such as Integrated case.
  6. Select a type such as Ongoing case.
  7. Select Search.
  8. Issue: The browser focus is set to the first editable field of the page when the search results are shown to the user.

 

Resolution:


The issue has been solved. Now when search results are shown to a user, the browser focus is set to the search button to allow the user to navigate easily the search results without going through the search criteria.
 

PO08440, WorkItem:250734 - When using a screen reader with the Citizen Portal, the 'Save & Exit' button is referenced as the 'Navigation Panel Quit Save & Exit' button

 

Issue Description:


When entering a Citizen Portal application while using the screen reader, there is an issue with a button. The 'Save and Exit' button is read as 'Navigation Panel Quit Save & Exit'. This can cause confusion as to whether the updates on the page have been saved or the user is exiting the page without saving. Also when using the CTRL-Insert-B shortcut to open the 'Select a Button' dialog, the list displays 'Navigation Panel Quit Save & Exit'.

User Interface Impact: No

Steps to Reproduce:

 

  1. Enable a screen reader in Internet Explorer 11.
  2. Login to the Citizen Portal and start any application.
  3. Navigate to the 'Information About You' page.
  4. Use tabbing to reach the 'Save & Exit' button.
  5. Issue 1: The button reads 'Navigation Panel Quit Save & Exit button'.
  6. Issue 2: When using the CTRL-Insert-B shortcut on the page to open the 'Select a Button' dialog box it lists and reads the button as 'Navigation Panel Quit Save & Exit'.

 

Resolution:


This issue was resolved by updating an IEG configuration property. Now when a screen reader user navigates to form pages in the IEG scripts, the 'Save & Exit' button is read as 'Navigation Exit Panel Save & Exit' button.

Technical:


The following IEG configuration property located in ../EJBServer/components/IntelligentEvidenceGathering/data/initial/blob/ieg-config.properties was updated:

  • navpanel.quit.label=Navigation Exit Panel

 

PO08448, WorkItem:250878 - The application section tab name is not displayed in the browser tab title when the application section tab is the only tab currently open

 

Issue Description:


The application section tab name is not displayed in the browser tab title when the application section tab is the only tab currently open. This also causes misleading information to be read out to a visually impaired user who is using a supported screen reader.

User Interface Impact: No

Steps to Reproduce:

 

  1. Enable a screen reader.
  2. Login as a Child Welfare intake worker.
  3. Select the Cases and Plans section.
  4. Issue: The section name is not displayed in the browser tab title and is not announced by the screen reader.

 

Resolution:


This issue was resolved by updating the javascript around the tab titles. Now the browser tab title correctly updates with the application section tab name when the application section tab is the only tab currently open.
 

PO08445, WorkItem:250955 - Browser focus is moved to the top of the application screen instead of the next tab when viewing the Allegations tab on an intake

 

Issue Description:


When the JAWS screen reader is used and a visually impaired user navigates to the Allegations tab on an intake case, the browser focus is moved to the top of the application screen instead of the Allegations tab in the navigation bar.

User Interface Impact: No

Steps to Reproduce:

 

  1. Start JAWS screen reader and open Internet Explorer 11 browser.
  2. Login as a Child Welfare Intake Worker.
  3. Navigate to an existing intake's home page.
  4. Use the tab key to navigate to the Home tab in the navigation bar.
  5. Press down arrow key to move to the Allegations tab.
  6. Issue: The browser focus is set incorrectly to the top of the application screen and it is not possible to navigate to other tabs from the Allegations page using the up or down arrow keys.

 

Resolution:


The Allegations page has been updated so that the browser focus remains on the tab after page load. Now, the user can navigate to the Participants tab using the down arrow key.
 

PO08472, WorkItem:251147 - The screen reader does not announce that the help icon page link opens in a new window

 

Issue Description:


When a supported screen reader is used and a visually impaired user navigates to a help icon, it does not announce that the target help page opens in a new window. This can confuse the visually impaired user once the help page opens.

User Interface Impact: No

Steps to Reproduce:

 

  1. Enable a screen reader.
  2. Using Internet Explorer 11 login as a caseworker.
  3. On the home page, tab to the help icon link.
  4. Issue: The screen reader announces 'Help'. Additional context is missing for this icon to indicate that it will open in a new window.

 

Resolution:


This issue was resolved by updating the properties in the CDEJResources.properties file. Now when a visually impaired user navigates to a help icon, the screen reader announces 'Help (content opens in a new window)'.
 

PO08487, WorkItem:251289 - The screen reader in the application announces the Next or Save buttons as links initially and then as buttons when navigating with the down-arrow key

 

Issue Description:


When a supported screen reader is used and a visually impaired user navigates to the Next or Save buttons using the down-arrow key, the screen reader reads respectively 'link next' and then 'next button' or 'link save' and then 'save button'. This can confuse the user on how many buttons are on the page.

User Interface Impact: No

Steps to Reproduce:

 

  1. Enable a screen reader.
  2. Login as a caseworker.
  3. Navigate to the Register Person page.
  4. Use the down-arrow key to navigate to the Next button.
  5. Issue: The screen reader reads 'link next'. When navigating further it reads 'next button'.

 

Resolution:


This issue was resolved by updating the javascript around the submit buttons. Now when a screen reader user navigates to a Next or Save action control button using the down-arrow key, it only reads 'link next' or 'link save'. It should be noted that Merative Social Program Management accessibility guidelines state that users should not use arrow keys to navigate modals and should use the Tab key instead.
 

PO08474, WorkItem:251290 - The screen reader reads the application menu as person menu in the application banner

 

Issue Description:


When a supported screen reader is used and a visually impaired user navigates to the application menu in the application banner, the screen reader reads different text depending upon the keystrokes used. The screen reader reads 'person menu person menu button menu' when using the tab key and reads 'application help menu button menu' when using the down arrow key. This difference can cause confusion to the visually impaired user on how many buttons are on the banner.

User Interface Impact: No

Steps to Reproduce:

 

  1. Enable a screen reader.
  2. Login as a caseworker.
  3. Navigate to the menu on the application banner using the tab key.
  4. Issue: The screen reader reads 'person menu person menu button menu'.
  5. Navigate to the menu on the application banner using the down arrow key.
  6. Issue: The screen reader reads 'application help menu button menu'.

 

Resolution:


This issue was resolved by updating the java around the application menu in the application banner. Now when a screen reader user navigates to the application banner using either the down arrow key or the tab key, it reads as 'application button menu'.
 

PO08482, WorkItem:251481 - When navigating to the Contact tab within a case using arrow keys, the focus does not remain on the Contact tab

 

Issue Description:


When a supported screen reader is started and the user uses the down arrow key to navigate through the tabs within a case, when the user reaches the Contacts tab the focus is incorrectly set to the first editable field within the Contact Logs list page that allows a user to select all existing Contacts.

User Interface Impact: No

Steps to Reproduce:

 

  1. Start a screen reader.
  2. Login as a Child Welfare intake worker.
  3. Navigate to the Intake section.
  4. Navigate to the Home page of an Intake.
  5. Use the down arrow key to navigate through the Intake tabs to reach the Contacts tab.
  6. Issue: The focus should remain on the Contacts tab but is instead incorrect being set to the field within the Contact Logs list page that allows a user to select all existing Contacts.

 

Resolution:


When the user navigates through the tabs within a case and reaches the Contacts tab the focus now remains on the Contact tab itself.
 

PO08489, WorkItem:251649 - The mandatory text is not displayed or read for mandatory address fields

 

Issue Description:


When a screen reader user navigates to a required address field, the screen reader does not announce the field as being 'mandatory'.

User Interface Impact: No

Prerequisite(s):

 

  1. Configure the default address format to contain a mandatory field, for example, ADD1 with attribute MANDATORY="true".

 

Steps to Reproduce:

 

  1. Enable a screen reader.
  2. Login as a caseworker.
  3. Open the Register Person page.
  4. Navigate to a mandatory address field.
  5. Issue: The screen reader does not announce the field as being 'mandatory'.

 

Resolution:


This issue has been resolved by updating the logic around the address mandatory fields renderer. When a screen reader user navigates to a mandatory address field, the field will be announced as ‘mandatory’.
 

WorkItem:251956 - Focus is not being set on the text area field of Edit Agenda modal used when capturing Meeting Minutes

 

Issue Description:


When creating Meeting Minutes within a case, agenda information can be captured. After the meeting minutes are recorded, when the Edit Agenda modal is opened to update the agenda information, the focus is not set on the text area.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a Child Welfare caseworker.
  2. Register a new child.
  3. Create a new Ongoing Case for the child and create an Outcome Plan.
  4. Go to the Admin tab and Meeting Minutes navigation page.
  5. Create new Meeting Minutes using the Record Meeting Minutes wizard.
  6. On the row-level menu for the newly created meeting minutes click Edit Agenda.
  7. Issue: The focus is not set on the text area.

 

Resolution:


This issue has been addressed and the focus is set on the text area when the Edit Agenda modal is opened.
 

WorkItem:253974 - Image tags content on the help icon are being read by a screen reader

Issue Description:


When a supported screen reader is used and a visually impaired user navigates to the help icon on a home page, the screen reader reads the entire content of the image tag on the page. This can confuse the visually impaired user.

User Interface Impact: No

Steps to Reproduce:

 

  1. Enable a screen reader.
  2. Login as a caseworker.
  3. Navigate to the help icon on the home page using the tab key.
  4. Issue: The screen reader reads the image path associated with the icon images and other information that is not useful to the user.

 

Resolution:


This issue was resolved by updating the logic around the help icon renderer. Now when a visually impaired user navigates to the help icon on a home page, the screen reader only reads the title associated with the icon.
 

LOOK & FEEL
 

PO08539, WorkItem:253022 - Printing a context panel results in overlapping text and images, misaligned fields and loss of data on the printed page

 

Issue Description:


In Merative Social Program Management (SPM) version 7, printing a context panel results in overlapping text and images, misaligned fields and loss of data on the printed page. The issue occurs for multiple case and participant types.

User Interface Impact: Yes

Steps to Reproduce:

Scenario1:

 

  1. Login as an Income Support caseworker.
  2. Register a Participant.
  3. Create a Food Assistance application for this participant and when asked to add additional household members, answer 'Yes' and add a child.
  4. Complete the application.
  5. Open the application case for the member.
  6. Click the print icon on the page.
  7. Issue: Printing the context panel results in overlapping text and images, misaligned fields and loss of data on the printed page.
  8. Resolve any pending evidence issues and verify any outstanding verifications.
  9. Check participant is eligible for Food Assistance.
  10. Authorize the result from the Review Eligibility Result modal.
  11. Open Food Assistance case.
  12. Click the print icon on the page.
  13. Issue: Printing the context panel results in overlapping text and images, misaligned fields and loss of data on the printed page.

 

Scenario 2:

 

  1. Login as a caseworker.
  2. Register an Employer.
  3. Open the registered employer.
  4. Click the print icon on the page.
  5. Issue: Printing the context panel results in overlapping text and images, misaligned fields and loss of data on the printed page.

 

Scenario 3:

 

  1. Login as an Insurance Affordability caseworker.
  2. Register a Participant.
  3. Create an Insurance Affordability case for this participant.
  4. Open the registered Insurance Affordability case.
  5. Click the print icon on the page.
  6. Issue: Printing the context panel results in overlapping text and images, misaligned fields and loss of data on the printed page.

 

Resolution:


The issue has now been resolved. Printing a context panel no longer results in overlapping text and images, misaligned fields and loss of data on the printed page.
 

PO08540, WorkItem:253089 - Printed search results contain overlapping text and images and misaligned content

 

Issue Description:


When a user expands a row in a case search result list and prints the page, the expanded row on the resulting printed page contains overlapping text and images and the content is misaligned.

User Interface Impact: No

Steps to Reproduce:

 

Scenario 1:

 

  1. Login as an Income Support caseworker.
  2. Register a participant.
  3. Create an Income Support case for this participant.
  4. Open the case search page and search for the Income Support case that was created.
  5. Expand the row for the Income Support case in the search result list.
  6. Click the print icon on the page.
  7. Issue: The printed case search page contains overlapping text and images, misaligned fields and loss of data.

 

Scenario 2:

 

  1. Login as an Insurance Affordability caseworker.
  2. Register a participant.
  3. Create an Insurance Affordability case for this participant.
  4. Open the case search page and search for the Insurance Affordability case that was created.
  5. Expand the row for the Insurance Affordability case in the search result list.
  6. Click the print icon on the page.
  7. Issue: The printed case search page contains overlapping text and images, misaligned fields and loss of data.

 

Resolution:


This issue has been resolved and now when a user expands a row in a case search result list and prints the page, the expanded row on the resulting printed page does not contain overlapping text and images and the content is correctly aligned.
 

PO08560, WorkItem:253552 - The text inside the links panel of a context panel is cut off when printing in portrait mode from the Chrome browser

 

Issue Description:


The text inside the links panel of a context panel is cut off when printing in portrait mode from the Chrome browser.

User Interface Impact: No

Steps to Reproduce:

Scenario 1:

 

  1. Login as an Income Support caseworker.
  2. Register a participant.
  3. Create a Food Assistance application for this participant and when asked to add additional household members, answer Yes and add a child.
  4. Complete the application.
  5. Open the application case for the member.
  6. Click the print icon on the page.
  7. Issue: Printing the context panel results in overlapping text and images, misaligned fields and loss of data on the printed page.
  8. Resolve any pending evidence issues and verify any outstanding verifications.
  9. Check that the participant is eligible for Food Assistance.
  10. Authorize the result from the Review Eligibility Result modal.
  11. Open the Food Assistance case.
  12. Click the print icon on the page.
  13. Issue: Printing the context panel results in overlapping text and images, misaligned fields and loss of data on the printed page.

 

Scenario 2:

 

  1. Login as a caseworker.
  2. Register an employer.
  3. Open the registered employer home page.
  4. Click the print icon on the page.
  5. Issue: Printing the context panel results in overlapping text and images, misaligned fields and loss of data on the printed page.

 

Scenario 3:

 

  1. Login as an Insurance Affordability caseworker.
  2. Register a participant.
  3. Create an Insurance Affordability case for this participant.
  4. Open the registered Insurance Affordability case.
  5. Click the print icon on the page.
  6. Issue: Printing the context panel results in overlapping text and images, misaligned fields and loss of data on the printed page.

 

Resolution:


This issue has now been resolved by updating the styling specific to printing context panels. The text inside the links panel of a context panel is not cut off when printing in portrait mode from the Chrome browser.

Technical:


This issue has now been resolved by updating the styling specific to printing context panels. The context panels have been scaled down in size using CSS to avoid data loss when printing.
 

PO08576, WorkItem:254185 - The contact information in the Employer Context Panel is being cut off when using Internet Explorer 11

 

Issue Description:


The contact information in the Employer Context Panel is being cut off when using Internet Explorer 11. The fields cut off at the bottom of the panel are phone number, fax number, and email address.

User Interface Impact: No

Steps to Reproduce:

 

  1. Launch Internet Explorer 11.
  2. Login as a caseworker.
  3. Register a new employer with all the details including phone, fax, and email address.
  4. Open the newly registered employer and review the context panel.
  5. Issue: The text at the very bottom of the context panel is cut off and unreadable. This includes the 3 fields related to contact information.

 

Resolution:


The styling for the Employer Context Panel has been updated so the contact information is fully readable when using Internet Explorer 11.
 

Business Services

 

Task Management

TASK MANAGEMENT
 

PO07280, WorkItem:221957 - When tasks are forwarded to batch in bulk they are incorrectly still available for online forwarding

 

Issue Description:

Tasks that are queued in a batch process should not be available to be forwarded. If an attempt is made to forward tasks that are queued in a batch process then a validation error message should be shown.
This expected behavior does not happen and no validation error message is shown to prevent forwarding the tasks that are queued in a batch process.

User Interface Impact: No

Prerequisite(s):

 

  1. Need to ensure that tasks are queued for batch processing rather than deferred processing in the task forwarding flow using the following steps:
  2. Login as a system administrator.
  3. Click on System Configurations and expand the shortcuts panel.
  4. Expand the Application Data section and click on Property Administration.
  5. Search for and modify the value of the property 'curam.batch.bulktaskforward.deferredprocess.max.processing.count' to 1.
  6. Click on the Publish page action to publish the changes.

 

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Create 3 to 5 tasks from the Inbox actions menu and for each one select Add to My Tasks.
  3. Login as a supervisor and navigate to My Users under Users in the shortcuts panel.
  4. Select the Caseworker user.
  5. From the user workspace, navigate to Tasks and then select Open Tasks.
  6. Click Forward Reserved Tasks and select the Supervisor User from the My Users drop-down.
  7. Check the box for 'List all tasks reserved by the user' and click Search.
  8. Select all of the tasks and click Save.
  9. Return to the Caseworker Open Tasks screen.
  10. Open one of the tasks and click Forward from the tab actions menu.
  11. Select Auditor User from the My Users drop-down.
  12. Click Save. Note the validation message, 'This task cannot be forwarded manually as it has already been queued for forwarding. The new task assignee(s) will be notified once the forward completes.'
  13. Login as a caseworker again.
  14. Navigate to My Open Tasks from the user's Inbox.
  15. Open one of the tasks and click Forward from the tab actions menu.
  16. Select User from the drop-down and click the Search icon (magnifying glass).
  17. Enter Auditor into the First Name field and click Search.
  18. Select Auditor User from the search results.
  19. Click Save.
  20. Issue: Task is forwarded and no validation error message is shown to prevent forwarding the task that is currently queued in a batch process.

 

Resolution:


This issue has been resolved and the forwarding of tasks that are currently queued in a batch process is not allowed. The same validation error message that the supervisor is shown is now shown to the caseworker user if they attempt to forward a task currently queued in a batch process.

 

Technical:

The issue was resolved by adding a validateForward() function to curam.core.facade.impl.TaskManagement.java and adding a call to this new function in the forward() function in this class. This will throw an exception if the task is already queued in a batch process.
 

 

Cúram Modules

 

Outcome Management
Provider Management
Supervisor Workspace
Intelligent Evidence Gathering
Evidence Broker
Financial Management

Outcome Management

 

PO08499, WorkItem:251864 - Assessment factor ratings are plotted using an incorrect date in the Ratings Chart depending upon the timezone being used

 

Issue Description:


When a user runs an assessment within an outcome plan, ratings are given to each factor configured for the assessment. After the assessment is complete, users can then view the rating given to an individual factor on a Ratings Chart that displays the rating along the y-axis and the date of assessment along the x-axis. If the timezone used is less than Coordinated Universal Time (UTC) when the assessment is run, the factor is incorrectly being plotted along the x-axis on the day before the creation of the assessment rather than on the day of the assessment.

User Interface Impact: No

Prerequisite(s):

 

  1. Set the client timezone to GMT-5 (EST).

 

Steps to Reproduce:

 

  1. Login as a Child Welfare Structure Decision Making caseworker.
  2. Register an adult person.
  3. Using the actions menu, create an Ongoing case for the created person.
  4. Open the shortcuts menu and navigate to Outcome Plans.
  5. Click New to create a new Child Welfare Outcome Plan without selecting the Basic Version.
  6. Navigate to Assessment Factors, then Assessments.
  7. Click New to create a new Caregiver Strengths and Needs assessment.
  8. Complete the assessment by selecting the highest positive rating for each question.
  9. Navigate to the Factors page.
  10. From the list of factors, click on the Substance Abuse factor.
  11. Issue: The factor's rating chart shows the day before the creation of the assessment.

 

Resolution:


This issue has been resolved. Now when the user with a timezone less than Coordinated Universal Time (UTC) creates a factor, the factor rating chart displays the correct date on the x-axis based on the browser timezone.
 

Provider Management

 

PO08360, WorkItem:249081 - Unhandled server exception occurs when creating a Provider Member for a Provider

 

Issue Description:


An unhandled server exception occurs when searching for a person to add as a Provider Member on a Provider, where the person has a large number of alternate names.

User Interface Impact: No

Prerequisite(s):

 

  1. Login as a caseworker.
  2. Register a Person and create 6 alternate names for the person.

 

Steps to Reproduce:

 

  1. Login as a Provider Management Resource Manager.
  2. Select Providers and Services and expand the shortcuts panel.
  3. Select Enroll Provider in the Providers sub-navigation tab and click Next.
  4. Complete the required fields and click Finish.
  5. Select the Relationships tab.
  6. Select Provider Members and select New.
  7. Click on the magnifying glass to open the Person Search page.
  8. Enter a value in the First Name field for the person registered above and click Search.
  9. Issue: An unhandled server exception occurs.

 

Resolution:


This issue has been resolved and a user is now able to search for a person to add as a Provider Member on a Provider, where the person has a large number of alternate names.

Technical:


The search query has been updated to no longer access the AlternateName entity, as the query did not specify what data needed to be selected from this entity thereby resulting in a table scan and ultimately the unhandled server exception. It was also found that the search could be performed successfully without referencing the AlternateName entity.
 

Supervisor Workspace

 

PO06252, WorkItem:157515 - Case notifications are not sent to the previous owner when bulk case reassignment is completed in either deferred or batch processing

 

Issue Description:


During case re-assignment in either deferred or batch processing, the previous case owner does not get notifications in their Inbox of this case re-assignment when the property 'curam.supervisor.notification.reassigncasefromnotification' is set to YES.

User Interface Impact: No

Prerequisite(s):

 

  1. Login as a system administrator.
  2. Click on System Configurations and expand the shortcuts panel.
  3. Expand the Application Data section and click on Property Administration.
  4. Search for and ensure the following property value is set (if the property value is changed select the Publish page action control and confirm): curam.supervisor.notification.reassigncasefromnotification=YES.
  5. Login as a caseworker.
  6. Register a new Person and create a number of cases for them.

 

Steps to Reproduce:

 

  1. Login as a supervisor.
  2. Navigate to Users and selects My Users.
  3. Select the caseworker user.
  4. Navigate to the Cases tab under Case Worker workspace.
  5. Select the Reassign Cases link.
  6. Click on the magnifying glass beside the New Owner field.
  7. Enter the first name as Investigator and click Search.
  8. Select the user Investigator User.
  9. Click on the checkbox 'List all cases assigned to the user'.
  10. Click Search.
  11. Select one of the cases for the reassignment.
  12. Click Save.
  13. Logout and login as a caseworker.
  14. Navigate to the Inbox, then Notifications.
  15. Select My Notifications.
  16. Issue: The caseworker user does not receive a successful case re-assignment notification in the Inbox.

 

Resolution:


This issue has been resolved and now the previous case owner is getting notifications in their Inbox when case reassignment is completed in either deferred or batch processing and the property 'curam.supervisor.notification.reassigncasefromnotification' is set to YES.

PO07159, WorkItem:196781 - Supervisor is not able to reserve assigned tasks to a user from the Reserve Assigned Tasks screen

 

Issue Description:


When reserving tasks for a user selecting the criteria as Longest Assigned, the Reserve Assigned Tasks page reserves tasks currently assigned to work queues, positions or organization units before reserving tasks assigned to the user.

User Interface Impact: No

Prerequisite(s):

 

  1. Login as a supervisor.
  2. Navigate to the Inbox.
  3. Create a new task assign to the CCS INVESTIGATION organization unit.
  4. Create two more tasks and assign them to the SUPERVISORWORKQUEUE work queue.
  5. Create two more tasks and assign them to the caseworker user.
  6. Create two more tasks and assign them to the Board of Directors organization unit.

 

Steps to Reproduce:

 

  1. Login as a supervisor.
  2. Click on Team and Workloads.
  3. Navigate to Users, My Users and then select the caseworker user.
  4. Select the Tasks tab and then select Reserve Tasks from the tab action menu.
  5. Enter 3 as the Number of tasks and select Longest Assigned.
  6. Issue: Tasks assigned to work queues, positions and organization units are being reserved instead of the tasks assigned to the supervisor user.

 

Resolution:


This issue has been resolved and now when the supervisor reserves tasks based on the criteria Longest Assigned from the Reserve Assigned Tasks page, the application reserves the tasks assigned to the user only. Also, if the user reserves more tasks than those listed on the Assigned Task page, then the following informational message is displayed: 'Only 'X' tasks were assigned to this user. All tasks have been reserved.'
 

Intelligent Evidence Gathering

 

Player

 

PO08452, WorkItem:250964 - When an assessment is printed, any content which spans beyond the first printable page, or any text within a field which requires scrolling to be viewable, is cut off

 

Issue Description:


When printing an assessment question or summary page, only one printable page of assessment content is printed. Any assessment content on a question or summary page which spans beyond the first printable page is cut off. Any content within a scrollable text field that requires scrolling to view on the page is also cut off.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a Child Welfare caseworker.
  2. Register a person and create an Ongoing Case for them.
  3. From the Ongoing Case, select the Outcome Plans tab.
  4. Select the New page action to create a new Outcome Plan.
  5. Select Child Welfare Outcome Plan from the Type drop-down, enter a Name and select a Client.
  6. Click Save.
  7. From the Assessments and Factors tab in the Child Welfare Outcome Plan, select the New page action.
  8. Choose Caregiver Strengths and Needs and click Next.
  9. Choose a Primary Caregiver.
  10. Click Next to open the SDM Caregiver Strengths and Needs Assessment page.
  11. Enter multiple lines of text which require scrolling to view into the Comment field.
  12. Click Print.
  13. Issue: Only one printable page of assessment content is printed, any content spanning beyond one page is lost. Any content within the Comment field which requires scrolling to view on the page is also lost.

 

Non-Child Welfare Solution

Prerequisite(s):

 

  1. Configure an IEG Question Page within a script to contain multiple questions that will span the length of more than one page when printed. One question element should contain a layout element with its type set as flow and the number of rows set to 3.

 

Steps to Reproduce:

 

  1. Launch the configured IEG script.
  2. Answer the configured questions and navigate through the script by clicking the Next button.
  3. On the page configured to have a layout of type flow, enter multiple lines of text which require scrolling to view.
  4. Click Print.
  5. Issue: Only one printable page of assessment content is printed, any content spanning beyond one page is lost. Any content within the question field with the layout of type flow, which requires scrolling to view on the page, is also lost.

 

Resolution:


This issue has been resolved by adding print specific styling to assessment pages.
 

WorkItem:252401 - Merative Universal Access Responsive Web Application: Dynamic expressions using dates not working

 

Issue Description:


An issue was fixed where dynamic expressions in IEG (such as conditions or read-only-expressions) that were referencing date questions were not working as expected.) NB: this was only occurring in the React-based IEG.

User Interface Impact: No

Steps to Reproduce:

 

  1. Configure an IEG script with a page that contains a date question and a conditional cluster where the expression references that question
  2. Run that script
  3. When the date is entered and the condition is met, note the cluster is not displayed


Resolution:


Dynamic expressions in IEG that reference date questions now display the cluster.

 

WorkItem:253349 - Merative Universal Access Responsive Web Application: Improved display of number and date formats on IEG summary pages

 

Issue Description:


In the Universal Access Responsive Web Application, number and date formats were displayed inconsistently on IEG form and summary pages.

User Interface Impact: No

Steps to Reproduce:

 

  1. Update an IEG script to contain a question with currency and date data types.
  2. In the Universal Access Responsive Web Application, apply for a benefit using that IEG script.
  3. Issue: Observe that currency and date questions on the form have different formats than the question values displayed on the summary page.

 

Resolution:


Questions with number and date formats on the summary page now have the same format as on form pages. Also, currency and percentage symbol add-ons are now supported when they are added to IEG script summary pages by using 'layout' elements.
 

WorkItem:253609 - Merative Universal Access Responsive Web Application: Different questions types display inconsistently on IEG summary pages

 

Issue Description:


On IEG summary pages displayed in the Universal Access Responsive Web Application, questions in lists were not displayed like questions in clusters. This inconsistency was caused by layout elements on questions defined in lists not taking effect when the question was displayed on the summary page.

User Interface Impact: No

Steps to Reproduce:

 

  1. Update an IEG script to contain a question with a layout element inside a list on the summary page.
  2. In the Universal Access Responsive Web Application, apply for a benefit using that IEG script.
  3. Issue: Observe that the question is displayed without the defined layout.

 

Resolution:


Questions defined with a layout element in a list are now displayed with the expected layout on the summary page, so list and cluster questions now display consistently.

 

WorkItem:253609 - Merative Universal Access Responsive Web Application: Different questions types display inconsistently on IEG summary pages

 

Issue Description:


On IEG summary pages displayed in the Universal Access Responsive Web Application, questions in lists were not displayed like questions in clusters. This inconsistency was caused by layout elements on questions defined in lists not taking effect when the question was displayed on the summary page.

User Interface Impact: No

Steps to Reproduce:

 

  1. Update an IEG script to contain a question with a layout element inside a list on the summary page.
  2. In the Universal Access Responsive Web Application, apply for a benefit using that IEG script.
  3. Issue: Observe that the question is displayed without the defined layout.

 

Resolution:


Questions defined with a layout element in a list are now displayed with the expected layout on the summary page, so list and cluster questions now display consistently.
 

PLAYER
 

PO08471, WorkItem:251370 - Selected radio buttons and checkboxes on Intelligent Evidence Gathering pages do not appear as selected when printed

 

Issue Description:


When printing an Intelligent Evidence Gathering page that contains a selected radio button or a checkbox, the same radio button or checkbox appears as unselected on a printed version of the page. Therefore, users could be missing information when only reviewing a printed version of the page.

Prerequisite(s):

 

  1. Edit the browser settings so that printing background graphics is disabled.

 

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Register a Person.
  3. Launch any IEG script for the Person which contains checkboxes and radio buttons.
  4. Check any checkbox and radio button.
  5. Select the Print link at the top of the page.
  6. Issue: The previously checked checkbox and radio button appear unchecked when printed.

 

Resolution:


This issue has been resolved by adding print specific styling to the rendering of checkboxes and radio buttons to ensure that these are printed correctly.
 

WorkItem:252507 - Merative Universal Access Responsive Web Application: Display text defined inside conditional cluster with read-only expression produces application error

 

Issue Description:


A text display element that is defined inside a dynamically conditional cluster with a read-only expression produces an application error.

User Interface Impact: No

Steps to Reproduce:

 

  1. Update an IEG script to contain a text display element inside a dynamically conditional cluster with a read-only expression.
  2. In the Universal Access Responsive Web Application, apply for a benefit using that IEG script.
  3. Issue: Observe that an application error is displayed.

 

Resolution:


A text display element that is defined inside a dynamically conditional cluster with a read-only expression displays IEG page elements, as expected.
 

PO08341, WorkItem:252989 - When an Intelligent Evidence Gathering script contains a code-table hierarchy with three or more levels, the drop-down menus are not populating correctly

 

Issue Description:


When an Intelligent Evidence Gathering script contains a code table hierarchy with three or more levels and a user selects a value from the first drop-down menu, the adjacent drop-down menu is not populated with the related code table values.

User Interface Impact: No

Prerequisite(s):

 

  1. Create an Intelligent Evidence Gathering script with a code table hierarchy of three or more levels.

 

Steps to Reproduce:

 

  1. Login as an administrator.
  2. Click on the Administration Workspace tab.
  3. Select Scripts under Intelligent Evidence Gathering in the shortcuts panel.
  4. Import and run the previously created Intelligent Evidence Gathering script.
  5. Select a value from the drop-down menu which represents the highest level of the code table hierarchy.
  6. Issue: The adjacent drop-down menu is not populated with the related code table values.

 

Resolution:


When an Intelligent Evidence Gathering script contains a code table hierarchy with three or more levels and a user selects a value from the first drop-down menu, the adjacent drop-down menu is now populated with the related code table values.
 

Evidence Broker

 

Administration

ADMINISTRATION
 

WorkItem:212868 - Hard-coded strings are found in the Shared Instances Search page

 

Issue Description:


You can analyze how evidence has been shared around a system by searching for all instances of evidence sharing that have occurred on a particular case or are currently in progress between cases. Use the shared instances search to analyze any sharing problems that might occur. Hard-coded values are present in the tooltip description on the Shared Instances Search Graph View page for the following three headings: Evidence, Status and System Action. On translated applications, these headings still appear in English.

User Interface Impact: No

Prerequisite(s):

 

  1. A sharing configuration exists from an Integrated Case to another Integrated Case for Address evidence with Trusted Source set to Yes.
  2. The application is deployed using a supported language other than English.

 

Steps to Reproduce:

 

  1. Login as a caseworker.
  2. Register a new Person.
  3. Create two Integrated Cases for this person.
  4. Add Address evidence to one of the cases and Apply Changes. Note the case reference number.
  5. Login as an administrator.
  6. Navigate to Rules and Evidence and then choose Evidence Sharing.
  7. Select Shared Instances Search and enter the case reference of the case created above into the search field.
  8. Expand the search result details to view the graph. Hover over a node on the graph.
  9. Issue: Hard-coded strings are present in the tooltip.

 

Resolution:


This issue has been resolved by moving these hard-coded headings into a properties file that is translated.

Technical:


A new file has been added

  • ../webclient/components/AdvancedEvidenceSharing/jscript/curam/AESGraph/AESGraph.js.properties

The existing AESGraph.js file has been updated to read the heading values from the newly added properties file.

Financial Management

 

PO08475, WorkItem:251243 - Payment Correction case (Underpayment) generating payment on case closure

 

Issue Description:


When a newly created Payment Correction case, which has a status of Open, is closed or suspended, a live financial component is generated on it. This should not happen as it means that a caseworker cannot close a Payment Correction that was created in error without the financials being generated on it.

Prerequisite(s):

 

  1. Login as a system administrator.
  2. Navigate to system configurations > application data > property administration.
  3. Search for and update the property with the name 'curam.miscapp.checkforliveliabilities' to 'NO'.
  4. Use the Publish page action to publish the changes.

 

User Interface Impact: No

 

Steps to Reproduce:

 

  1. Register a new Person.
  2. Add a benefit product for the Person.
  3. Add the necessary evidence and certification.
  4. Activate the evidence.
  5. Submit, approve, and activate the case.
  6. Generate payments on the case.
  7. Update the certification and move the from date back. Reassessment results in 'Payment Correction - Underpayment' being created.
  8. Close the Payment Correction case.
  9. Issue: A live financial component is generated on the case.

 

Resolution:


When a case is either closed or suspended, the regeneration of financials process is invoked. An additional check has been added to this process to only regenerate financials on a Payment Correction if the case was originally progressed beyond the open state, through approval and activation. If the case was never approved and activated by a caseworker, the regeneration of financials process is not invoked.
 

WorkItem:254212 - The list page for displaying the financials for a participant is defaulted to one year

 

Issue Description:


The list page for displaying the financials for a participant defaults to one year. This should be configurable.

User Interface Impact: No

Steps to Reproduce:

Create the case:

 

  1. Login as a caseworker.
  2. Register a new Person.
  3. Create an integrated case for the Person.
  4. Add the necessary evidence to make the case eligible.
  5. Activate the evidence.
  6. Add a product to the integrated case with a delivery pattern of 'Monthly By Cash In Advance On 1st'.
  7. Add the following certifications:
    • 1st January 2018 to 31st January 2018.
    • 1st June 2018 to 30th June 2018.
    • 1st March 2019 to 31st March 2019.
  8. Submit, approve and activate the case.

 

Queue and run the batch processes:

 

  1. Login as a system administrator.
  2. Click on System Configurations.
  3. Click on Processes under Batch in the shortcuts panel.
  4. Enter GenerateInstructionLineItems into the Name / Description field and click Search.
  5. For the GenerateInstructionLineItems entry returned, click on the row-level action and select Execute.
  6. In the Execute Batch Process modal, specify the processingDate parameter as 20180101.
  7. Repeat steps 4, 5 and 6 for the GenerateInstruments batch process.
  8. Now run the batch processes to issue the payment.
  9. Repeat steps 4-8 for the second payment, specifying the processingDate parameter as 20180601.
  10. Again, repeat steps 4-8 for the third payment, specifying the processingDate parameter as 20190301.

 

Check the payments on the person:

 

  1. Login as a caseworker.
  2. Search for the person registered above and open the person case.
  3. From the home page, click on the Financial Transactions nav.
  4. Issue: The All Transactions list page does not display the first payment issued for January 2018 as the search only retrieves financial transactions for the last 365 days from the last payment, and this value is hardcoded.

 

Resolution:


The underlying API has been updated to leverage the same environment variable that governs how far back the case financials search goes. This environment variable is 'curam.financial.generatefinancialsdaterange'. As part of this work, the display name and description of this environment variable have also been updated. These now read:

 

  • Display Name = Display Financials Date Range
  • Description = Determines the period of time the case and concern financials searches cover

 

PO08477, WorkItem:255258 - Active Payment Correction case (Overpayment) cannot be found when setting up a new deduction

 

Issue Description:


When a Payment Correction case is activated, a live financial component is created on it. If the case in question is an overpayment, it will be available to a user to set up a deduction against either before or after the live financial component is realized into an instruction line item.

If the overpayment was closed before any such deduction was set up or financials were generated, the live financial component is canceled. If the case is subsequently reactivated, that is, reopened, reapproved and reactivated, a live financial component is not recreated on it. This means, in the case of an overpayment, that the liability is not available to set up a deduction against, which is the reported issue.

The same behavior is true when an active Payment Correction is suspended. Suspending the case cancels the live financial component. Unsuspending, reapproving and activating the case does not recreate the live financial component.

Prerequisite(s):

 

  1. Login as an administrator.
  2. Navigate to Product Delivery Cases under Case in the shortcuts panel.
  3. Click on a CER-enabled product in the Benefits list to navigate to the product home page.
  4. Click on the Edit tab menu option.
  5. On the Edit Product Page, scroll down to the 'Automatic Under and Overpayment Case Processing' cluster.
    • Set Overpayment Case Processing to 'Create Overpayment Case'
    • Set Use Rolled Up Reassessments to false
  6. Click Save.

 

User Interface Impact: No

Steps to Reproduce (Generic):

 

  1. Login as a caseworker.
  2. Register a new Person.
  3. Create a new integrated case for the Person.
  4. Add an associated product (the one referred to in the prereqs) to the integrated case.
  5. Add a certification period to the product delivery case.
  6. Add evidence and activate it.
  7. Generate payment(s).
  8. Now shorten the certification so that a Payment Correction Overpayment is created.
  9. Submit, approve, and activate the Payment Correction; this will result in a live financial component being generated.
  10. Close the Payment Correction case; this results in the live financial component being canceled.
  11. Reactivate the Payment Correction case; this causes the case to be reopened.
  12. Submit the case for approval and activate it.
  13. Issue: A live financial component is not regenerated on the case.

 

Resolution:


The underlying problem was with the financial generation process for Payment Correction cases. When a Payment Correction is being activated, a check is performed to see if a financial component already exists on the case. However, it did not perform a check to see if this financial component was ever realized into a line item. This logic has been updated to perform this additional sanity check. Now, if a closed financial component exists and that financial component was never realized into a line item, a new live financial component will be created.

 

Solutions

 

Income Support
Child Welfare

 

PO08124, WorkItem:243512 - Incorrect validations are displayed when income exclusion amounts are entered in the Insurance Affordability application

 

Issue Description:


When creating an application for Insurance Affordability within the citizen portal or internal application, the user is able to enter Scholarship Income details and indicate that the income is to be excluded. Likewise, an income of type American Indian Alaskan Native can be entered and also indicated as being excludable income. When either of these income types are entered and specified as excludable income, if the user navigates back to the pages in the script where the income information is displayed, validation messages indicating that the exclusion amounts exceed the income amounts are incorrectly being displayed and prevent the user from navigating to the next page in the application script.

User Interface Impact: No

Steps to Reproduce Scenario 1:

 

  1. Login as an Insurance Affordability caseworker.
  2. Register a Person.
  3. Start a new application dated 1/1/2019.
  4. Fill all the mandatory fields in Application Details, Household Information sections.
  5. Add Income of type Scholarship payments ($1000 yearly) with no Income Deductions.
  6. In Excludable Income select 'Yes' and add Scholarship Income details as $1000 yearly with Start Date 1/1/2019.
  7. Say ‘Yes’ in Excludable Income and add Scholarship Income details as $1000 yearly
  8. On the Annual Income page select 'Yes' for the $1000. Click Next.
  9. Now click ‘Household Information’ on the navigation section menu.
  10. Click Next until you reach the Scholarship Income Details page.
  11. Issue: The validation message 'The exclusion amount exceeds the reported scholarship income of $1000 for the coverage period' is incorrectly displayed on the page.

 

Steps to Reproduce Scenario 2:

 

  1. Login as an Insurance Affordability caseworker.
  2. Register a Person.
  3. Start a new application dated 1/1/2019.
  4. Fill all the mandatory fields in Application Details, Household Information sections making sure to select 'Yes' for Are you an American Indian/Alaska Native on the More About You page.
  5. Add Income of type American Indian Alaskan Native ($1000 yearly) with no Income Deductions.
  6. Say ‘Yes’ in Excludable Income and add Distributions from Alaskan Native details as $1000 yearly.
  7. Continue with the application to the Summary page.
  8. On the Summary page find the 'AI/AN Income Exclusions' section and click Change.
  9. Set the amount to $900 and click Next.
  10. Issue: The validation message 'The exclusion amounts exceed the reported AI/AN income of 1000$ for the coverage period' is incorrectly displayed on the page.

 

Resolution:


Both the external citizen portal and Internal caseworker script have been updated to no longer display the validation messages when the exclusion amounts do not exceed the income amounts.
 

Income Support

 

Medical Assistance

 

WorkItem:250705 - Coverage and Coverage Type Details evidence cannot be added to a case from the Incoming Evidence screens

 

Issue Description:


When attempting to use the Add To Case functionality on the Incoming Evidence screens for Coverage evidence, an Unhandled Server Exception is thrown and the evidence cannot be added to the case. A similar issue also occurs when trying to add Coverage Type Details from the Incoming Evidence screen. A validation message is incorrectly displayed preventing the evidence from being added to the case.

User Interface Impact: No

Prerequisite(s):


Evidence sharing should be configured from Income Support Integrated Case to Income Support Integrated Case for the following evidence types with Trusted Source set to No.

 

  • Medical Insurance
  • Coverage
  • Coverage Type Details

 

Steps to Reproduce:

 

  1. Login as an Income Support caseworker.
  2. Register a person and create an Income Support Integrated Case.
  3. Add Medical Insurance, Coverage and Coverage Type Details evidence and Apply Changes.
  4. Create another Income Support Integrated Case.
  5. Navigate to the Incoming Evidence screen.
  6. Expand the Medical Insurance evidence and select Add To Case from the Actions menu.
  7. Expand the Coverage evidence and select Add To Case from the Actions menu.
  8. Issue 1: An Unhandled Server Exception is thrown and the evidence cannot be added to the case.
  9. Expand the Coverage Type Details evidence and select Add To Case from the Actions menu.
  10. Issue 2: An error is displayed and the evidence cannot be added to the case.

 

Resolution:


This issue has been resolved by updating logic in the Coverage and Coverage Type Details evidence implementations to prevent these errors. Both types of evidence can now be correctly added to a case from the Incoming Evidence screen.

Technical:


The issue with the Coverage evidence happens within the implementation of Coverage static evidence, in CustomiseCoverage.preModify(). The logic searches for parents of type Coverage, but only searches for Active or In Edit records, it does not look for descriptors with a status of Identical Shared In-Edit. This search then returns an empty list, which causes an exception down the line, when the logic attempts to read the parent evidence type from the list. However, parent details are already available within the method call. In order to fix this issue, new logic has been added to use these parent details when the parent list is empty.

The issue with Coverage Type Details evidence occurs in CustomiseCoverageTypeDetails.preModify() implementation. The logic here goes through the parent evidence list and makes sure that the parent ID did not change. If it has changed it will cause an error. This logic did not account for when the parent ID is 0 which resulted in the error being triggered incorrectly in this scenario. This has been resolved by adding a zero check into the logic.
 

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

 

Issue Description:


Within an Income Support integrated case and associated Product Delivery, 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:

 

  1. Login as an Income Support caseworker.
  2. Register a new Person.
  3. Create a new Income Support case.
  4. In the Events tab, create a new meeting. Select List View. Then click on Meeting Minutes.
  5. In the action menu, select Record Meeting Minutes and finish all the steps to record the minutes..
  6. On the new minutes record, click on the actions menu next to the meeting and click on View Printer Friendly Minutes.
  7. 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.
 

MEDICAL ASSISTANCE
 

WorkItem:253655 - Update Open Enrollment Period for 2020

 

Issue Description:


No open enrollment period configuration for 2020 for Insurance Affordability is available.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as an administrator.
  2. Navigate to the Open Enrollment Period tab under the Health Care Reform shortcut.
  3. Issue: No open enrollment period for 2020 is configured.

 

Resolution:

 

A new open enrollment period configuration is now available. The configuration is: Start Date 11/1/2019, End Date 12/15/2019, Coverage Start Date 1/1/2020 and Coverage End Date 12/31/2020.

Child Welfare

 

WorkItem:249197 - Registered person that is already an intake participant can be selected as a probable match for a new intake participant

 

Issue Description:


When a registered person is already a participant on an intake, the intake worker is incorrectly able to select the registered person as a probable match when adding a new participant to the intake.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a Child Welfare intake worker.
  2. Register a child.
  3. Create a new Child Welfare Intake.
  4. From the Participants tab select New Participant.
  5. Enter the first name and last name of the registered child from above.
  6. Select the role of Alleged Victim, select the primary client checkbox and click Next.
  7. On the Potential Matches page, select Exact and click Finish.
  8. From the Participants tab select New Participant to add another participant to the intake.
  9. On the New Participant page enter the first name and last name of the registered child.
  10. Select the role of Alleged Victim and click next.
  11. On the Potential Matches page, select Probable and click Finish.
  12. The new participant is added to the intake as a prospect person and the registered child that is already an intake participant is now stored and displayed as a probable match for the prospect person on the Probable Matches tab.
  13. Issue: The Intake worker is able to action the probable match and select to match the prospect person with the registered child who is already a participant on the intake.

 

Resolution:


The following validation has been introduced to prevent the registered participant from being selected as a probable match when they are already a participant on the intake case: 'The participant that may be a match is already present in this Intake.'
 

WorkItem:249586 - Safety Factors fields in the Create Safety Plan modal dialog are clipped

 

Issue Description:


The Safety Factors fields in the Create Safety Plan modal dialog are clipped, with additional field wrapping and small field sizes when opened from the actions menu of a Completed Safety Assessment created during an Investigation.

User Interface Impact: No

Steps to Reproduce:

Creating the Assessment:

 

  1. Login as a Child Welfare Structured Decision Making (SDM) intake worker.
  2. Select New Intake under Intakes in the shortcuts panel.
  3. Set the Category to Child Protection Services and type to Child Abuse or Neglect and click Save.
  4. Click on the Open Intake tab action to open the intake.
  5. Select the Participants tab and select New Participant from the action menu to add a child participant.
  6. Enter a First Name, Last Name and Date of Birth as 1/1/2015 and a Role of Alleged Victim.
  7. Click Next and then click Finish.
  8. Select the Participants tab and select New Participant from the action menu to add an adult participant.
  9. Enter a First Name, Last Name and Date of Birth as 1/1/1985 and a Role of Alleged Maltreater.
  10. Click Next and then click Finish.
  11. From Participants list open each participant in a new tab.
  12. From the tab actions menu select Register to register the participant as a Person.
  13. Navigate back to the intake and select the Assessments tab.
  14. Enter all the information on the SDM Screening Assessment and click Finish.
  15. Select the Allegations tab and from the page action menu select New to add a new allegation.
  16. Set the Alleged Victim and Alleged Maltreater as the two participants entered.
  17. Select all types and enter the address and click Save.
  18. Select the Recommendation tab and from the page action menu select submit.

 

Approving the Recommendation:

 

  1. Login as a Child Welfare Structured Decision Making intake supervisor.
  2. Select the approval task from the Available Tasks pod on the home page.
  3. Select the Make Decision primary action on the task and select Approve.
  4. Enter comments in the Approve Recommendation modal and click Save.

 

Creating the Investigation:

 

  1. Login as a Child Welfare Structured Decision Making investigator.
  2. Select the 'Start an investigation for Intake..' task from the Available Tasks pod.
  3. Select the Create Investigation primary action on the task and click Start on the Start Investigation modal.
  4. Select the Assessments tab and select New Assessment.
  5. Select both client checkboxes and add roles Child and Primary Caregiver for the clients and click Next.
  6. Answer all the questions in the SDM Safety Assessment – this is approximately 5 pages of a script.
    • Do not select the option Create Safety Plan during the script process. Leave this to be completed after the Safety Assessment is completed.
  7. Once completed, click Complete.
  8. The Assessment of type Safety Assessment is created.
  9. From the row-level action of the Safety Assessment, select Create Safety Plan to display the Create Safety Plan modal.
  10. Issue 1: The Safety Factors fields are clipped at 100%.
  11. Issue 2: Once the full Safety Factors fields are fully displayed, there is an inner scroll bar set to a height of 4 to display the full list of Safety Factors.
  12. Issue 3: The field sizes are small at 100% including fields Name, Start, and Review.
  13. Issue 4: The Action cluster field label wrapping at 100%.

 

Resolution:


The layout of the Create Safety Plan modal dialog has been updated and the fields now appear correctly.

Technical Detail:


The page SafetyAssessment_addActionsFromList.uim has been updated to increase both its height and width, thereby removing the clipping of the field list of Safety Factors. A label width has been added to the cluster containing the fields Name, Start, Participants in Agreement, and Review, reducing the label size and increasing the size of the related input fields Name, Start and Review. The label width of the cluster containing the field action has been increased, which increases the label size and removes the wrapping of the field label. Finally, the Safety Factors field height has been removed, and the scrollable style has been removed from the related renderer resulting in the full list of Safety Factors being displayed without the inner scrolling option.
 

WorkItem:251025 - Text wrapping issues on Ongoing Case Reopen Case modal & Adoption Case Edit modal

 

Issue Description:


Field labels are wrapped on the Reopen Case modal of an Ongoing Case and Edit Case modal of an Adoption Case.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a Child Welfare caseworker.
  2. Register a Person.
  3. For the registered person, from the tab action menu, select New Case and create an Ongoing case.
  4. From the tab action menu select Close Case to close the case.
  5. From the tab action menu select Reopen Case.
  6. Issue 1: Field label Reason is wrapped.
  7. For the same person, from the tab action menu, select New Case and create an Adoption case.
  8. From the tab action menu select Close Case to close the case.
  9. From the tab action menu select Edit to update the case details.
  10. Issue 2: Priority label is wrapped and the drop-down values are truncated.

 

Resolution:


The issues on both the modals were resolved by increasing the overall modal width by setting the WINDOW_OPTIONS attribute for the modal.

Technical:

Two UIM files were changed to fix these issues:

  • CEF - IntegratedCase_reopen.uim

 

Increased the overall modal width by setting the WINDOW_OPTIONS="width=500" and removed the width attribute of the Priority field.

  • CFSS - CCSAdoption_modifyCase.uim

 

Increase the overall modal width by setting the WINDOW_OPTIONS="width=550".
 

WorkItem:252244 - Page layout issues occur when using the Back button while adding a provider to an Intake using the New Provider wizard

 

Issue Description:


When adding a provider to an Intake, if a user enters information about the provider on the Provider Information page in the New Provider Wizard, navigates to the next page in the wizard and then selects the Back button to navigate back to the Provider Information page, the width of the modal is reduced and the field labels of Name and Apt/Suite are wrapped. Also, the last digits of the Phone number are not displayed correctly.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a Child Welfare intake worker.
  2. Navigate to the shortcuts menu within Intakes.
  3. Expand the Intakes section and select New Intake.
  4. Select a Category and click Save.
  5. Navigate to the Participants tab and create a new participant.
  6. Select New Provider from the Participants page action menu.
  7. Enter a Name and a Phone number and click Next.
  8. Click the Back button to return to the Provider Information wizard page.
  9. Issue: The field labels of Name and Apt/Suite are wrapped and the last digits of the Phone number are truncated.

 

Resolution:


This issue has been resolved by increasing the width of the Provider Information screen after selecting the Back button.

Technical:


In the New Provider wizard, when selecting the Back button, a different Provider Information UIM page is loaded. The width of this Provider Information page (listed below) did not match the width of the Provider Information page that was loaded when originally opening the wizard. The width of this UIM page was increased to match the size of the original UIM page.

  • ../webclient/components/ChildServices/Common/Participant/CCSParticipantWizard_modifyParticipantDetails.uim

 

PO08545, WorkItem:253152 - Link to New Activity function incorrectly displayed on pages under Medical tab of Prospect Person when using Internet Explorer 11

 

Issue Description:


When using Internet Explorer 11 and viewing Medical information for a prospect person on the pages under the Medical tab, if the contents of the page such as the page title and field labels are selected and highlighted by moving the mouse over the text, the link for the New Activity function is incorrectly displayed on the page.

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a Child Welfare caseworker using the Internet Explorer browser.
  2. Navigate to an existing Prospect Person.
  3. Navigate to one of the four navigation pages under the Medical tab, Conditions, for example.
  4. Select all of the text in the page, moving the mouse to the right as the text is selected.
  5. Issue: The link for the New Activity function is incorrectly displayed in the far right of the page.

 

Resolution:


The New Activity link no longer displays on the Immunizations, Conditions, Visits, and Medication navigation pages.
 

PO08225, WorkItem:253657 - Modal dialog only launches once after completing an Assessment when using Internet Explorer 11

 

Issue Description:


After completing an Assessment, the New Objective modal dialog displays as normal. Once this modal dialog is closed, no further modal dialogs will launch and no action menus will display. This issue only happens when using Internet Explorer 11.

Related WorkItem(s): 251740

User Interface Impact: No

Steps to Reproduce:

 

  1. Login as a Child Welfare caseworker using the Internet Explorer 11 browser.
  2. Navigate to the shortcuts menu within Cases and Plans.
  3. Select Register Person and Create Case under Cases in the shortcuts panel.
  4. Select Ongoing Case from the Type drop-down, enter registration details for a child and click Save.
  5. From the case home page, select Outcome Plans.
  6. Click New and create a Child Welfare Outcome Plan.
  7. From the Outcome Plan page, select Assessments & Factors.
  8. Click New and create a Child Strengths and Needs assessment.
  9. Navigate to the Objectives tab and click New Objective.
  10. Close the New Objective modal.
  11. Click New again to relaunch the modal.
  12. Issue: The New Objective modal does not open as expected.

 

Resolution:


After completing an Assessment using the Internet Explorer 11 browser, all modal dialogs and action menus display as expected.

Technical:


This issue has been resolved by updates to the JavaScript for closing modals that were completed as part of the fix for 251740.
 

 

Code Removal

 

WorkItem:253483 - Duplicate classes in jde-commons JAR prevent successful deployment of SPM application on WebLogic 12.2

 

Issue Description:


The Merative Social Program Management application is unable to deploy on WebLogic (WLS) 12.2 application server due to the presence of a number of duplicate Java classes in the jde-commons JAR.

User Interface Impact: No

Resolution:


The duplicate classes have been removed from the jde-commons JAR to resolve issues when deploying the application on WebLogic (WLS) 12.2 application server. These classes are still available in the coreinf and coreinf-ejb JARs.

Technical:


The following classes have been removed from CuramSDEJ/lib/jde-commons.jar and CuramCDEJ/lib/curam/jar/jde-commons.jar:

 

  • DPEnactmentMDB.class
  • DPErrorMDB.class
  • WorkflowActivityMDB.class
  • WorkflowEnactmentMDB.class
  • WorkflowErrorMDB.class
  • CuramDestinationMDB.class
  • CuramQueueMDB.class
  • JMSConstants.class
  • MessageType.class

 

WorkItem:255279 - Remove commons-beanutils-core.jar from the Evidence Generator

 

Issue Description:


Apache Commons BeanUtils provides easy-to-use wrappers around the Java Reflection and Introspection APIs. This library is used by the Evidence Generator when running server builds. The version of the library used by Merative Social Program Management has been updated, and as part of this update the commons-beanutils-core JAR in the Evidence Generator has been replaced by the commons-beanutils JAR.

Related WorkItem(s): 253920

Resolution:


The commons-beanutils-core JAR has been removed from the Evidence Generator. It has been replaced by the latest version of commons-beanutils.


Technical:

 

  • ../Tools/Generators/EGTools/lib/commons-beanutils.jar - new JAR added.
  • ../Tools/Generators/EGTools/lib/commons-beanutils-core.jar - old JAR removed.

 

Note:
If any custom classpath is referencing the commons-beanutils-core.jar, it will need to be updated to reference the new commons-beanutils.jar instead.  

 

 

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.

 

Document Information

 

More support for:

Merative Social Program Management

 

 

Software version:

7.0.9

 

 

Operating system(s):

Linux, Windows

 

 

Modified date:

04 March 2020