IBM Support

IBM Cúram Social Program Management 7.0.10.0

Release Notes


Abstract

IBM Cúram Social Program Management 7.0.10.0 Release Notes

Content

Introduction
System Requirements
Download
Installation
Improvements, Resolved Issues, Third Party Updates and Code Removals
Notes on Deprecation
Known Issues
Notices

Introduction

Welcome to the IBM Cúram Social Program Management 7.0.10.0 release. Read this document to find important installation information, and to learn about product improvements and resolved issues in this release.

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

For more information about version 7.0.10.0, see the full product documentation in IBM Knowledge Center.

The IBM Support Portal always contains the most up to date version of these release notes.

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

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

To stay up to date with release note changes, security bulletins and other software support updates, you should sign up to My Notifications on the IBM Support Portal.

 

System Requirements

For information about the supported software and hardware for this release, see the Cúram Supported Prerequisites.

 

Download

Refer to the Download Document, which is available online at the IBM Support Portal.

 

Installation

Install the IBM Cúram software and supported related software according to the Installing IBM Cúram Social Program Management instructions in the IBM Knowledge Center.

Ensure that you install the IBM Cúram Social Program Management Platform, application modules and program-based offerings in the correct sequence as described in the Overview of the installation steps topic.

 

Upgrading

If you are upgrading from a previous version, the IBM Cúram Upgrade Helper contains documentation and tooling to help you to upgrade your Cúram application codebase and database to work with your new version of Cúram. The Cúram 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.

You can download the appropriate version of the IBM Cúram Upgrade Helper from IBM Fix Central.

 

Improvements, Resolved Issues, Third Party Updates and Code Removals

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

Third Party Updates

WorkItem:230383 - Update the version of Apache Ant to 1.10.6

The supported version of Apache Ant used in the Curam Development Environment has been increased from 1.9.9 to 1.10.6.
 

WorkItem:230388 - Drop Support for Oracle WebLogic Server 12cR1 (12.1)

Support for the Oracle WebLogic Server 12cR1 (12.1.3 and future fix packs) has been dropped from the product.

This means that the supported Oracle WebLogic Server version for the 7.0.10.0 release of SPM is as follows:

  • Oracle WebLogic Server 12cR2 (12.2.1 and future fix packs)
 

WorkItem:230402 - Drop Support for the Oracle Database 12c Release 1 (12.1) database

Support for both the Standard and Enterprise editions of Oracle Database 12c Release 1 (12.1.0.0.0) has been dropped from the product.

This means that the supported Oracle database versions for the 7.0.10.0 release of SPM are as follows:

  • Oracle Database 12c Release 2 (both Standard and Enterprise Editions)
  • Oracle Database 19c
 

WorkItem:255693 - Drop Support for Oracle JRE 7.0 used for Microsoft Word Integration

The installation of the Oracle JRE version 7.0 was listed in the SPM prerequisites as being required for the Microsoft Word Integration feature. The JRE was used to run the applet which is part of the Internet Explorer 11 version of the feature.

However, this version of the JRE has been discontinued and the last free public update was released in April 2015 (JRE 7.0 update 80).

Therefore, support for this version of the JRE for Microsoft Word Integration has been dropped. JRE 8.0 and future fix packs are now the only JRE version supported for this purpose and the SPM prerequisites have been updated to reflect this change.
 

WorkItem:255696 - 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 u241
 

WorkItem:255715 - Drop Support for Windows 7 as a platform for the design, development, testing, and building of the SPM application

Microsoft ended support for the Windows 7 platform on Jan 14th, 2020. (https:www.microsoft.com/en-ie/windows/windows-7-end-of-life-support-information).

Support for Windows 7 as a platform for the design, development, testing, and building of the SPM application has therefore been dropped. Windows 10 continues to be a supported platform for this purpose.

This has resulted in the following items being removed from the SPM prerequisites for the 7.0.10.0 release:

  • Windows 7 Enterprise
  • Windows 7 Professional
  • Windows 7 Starter
  • Windows 7 Ultimate
 

WorkItem:255716 - Drop Support for 32 bit Windows and RHEL platforms supported for the design, development, testing and building of the SPM application

The Linux platform is supported for the building of the SPM application. The Windows platform is supported for the design, development, testing and building of the SPM application.

The 32-bit version of these platforms was previously supported and listed in the prerequisites for the SPM product for the purposes described above. This 32-bit platform support has now been dropped and the 64-bit versions of these platforms should now be used.

This has resulted in the following entries being removed from the SPM 7.0.10.0 prerequisites:

  • Windows 10 Enterprise - x86-32
  • Windows 10 Pro - x86-32
  • Red Hat Enterprise Linux (RHEL) Server 6 (6.7) x86-32
 

WorkItem:255720 - Drop the documented support for Rational Application Developer for WebSphere Software (RAD for WebSphere) and Rational Software Architect Designer for WebSphere Software (RSAD for WebSphere) as development tools for SPM

Although technical support is not provided for any Integrated Development Environment (IDE), it should be possible to use any Java IDE for the development of the IBM Cúram Social Program Management (SPM) product. Support for IDEs should be sought from the relevant software vendor.

In previous releases of SPM, support for the usage of both Rational Application Developer for WebSphere Software (RAD for WebSphere) and Rational Software Architect Designer for WebSphere Software (RSAD for WebSphere) was listed under the Development Tools section in the associated prerequisites for the product. These entries have now been removed from the documented support for development tools although customers are still free to use them as per the support statement above.
 

WorkItem:255731 - Introduce support for WebSphere Application Server Refresh Pack 9.0.5 and Future Fix Packs

The IBM Cúram Social Program Management (SPM) application now supports WebSphere Application Server 9.0.5 and higher fix packs. Note the prerequisite minimum for this support is version 9.0.5.2.
 

WorkItem:255732 - Browser Support Update

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

Case Worker Application Browser Support

  • Google Chrome updated to 80
Universal Access Application Browser Support
  • Google Chrome updated to 80
  • Mozilla Firefox updated to 73
 

WorkItem:255733 - Introducing support for Freedom Scientific JAWS 2019 within Microsoft Internet Explorer 11

The version of Freedom Scientific JAWS used by the application has been updated to JAWS 2019. This new version has been certified against Microsoft Internet Explorer 11.
 

WorkItem:255734 - Tablet Accessibility Support

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

WorkItem:255735 - Update the Supported Prerequisites for IBM Social Program Management Reporting for 7.0.10.0


IBM Cúram Social Program Management has now certified the usage of the SPM Reporting Data Warehouse SQL scripts with the following databases:


*DB2 Advanced Enterprise Server Edition 11.1
*DB2 Enterprise Server Edition 11.1
*Oracle Database 12c Release 2
*Oracle Database 19c

WorkItem:255759 - Updates to the versions of MS Word supported for the Microsoft Word Integration feature

The following changes have been made to the Microsoft Word version support for the Microsoft Word Integration feature in SPM.

  • Support for Microsoft Word 2007 and future fix packs has been dropped. Official support for this version of MS Word has been dropped by Microsoft.
  • Support for Microsoft Word 2016 and future fix packs has been added.
This means that the Microsoft Word versions supported for SPM 7.0.10.0 are as follows:
  • 2010 and future fix packs.
  • 2013 and future fix packs.
  • 2016 and future fix packs.
 

WorkItem:256357 - 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 and 2.9.10.1 to 2.10.2. 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-annotations-2.10.2.jar - new JAR added.
  • ../CuramSDEJ/lib/jackson-core-2.10.2.jar - new JAR added.
  • ../CuramSDEJ/lib/jackson-databind-2.10.2.jar - new JAR added.
  • ../CuramSDEJ/lib/jackson-annotations-2.9.9.jar - old JAR removed.
  • ../CuramSDEJ/lib/jackson-core-2.9.9.jar - old JAR removed.
  • ../CuramSDEJ/lib/jackson-databind-2.9.10.1.jar - old JAR removed.
 
  • ../CuramCDEJ/lib/ext/jar/jackson-annotations-2.10.2.jar - new JAR added.
  • ../CuramCDEJ/lib/ext/jar/jackson-core-2.10.2.jar - new JAR added.
  • ../CuramCDEJ/lib/ext/jar/jackson-databind-2.10.2.jar - new JAR added.
  • ../CuramCDEJ/lib/ext/jar/jackson-annotations-2.9.9.jar - old JAR removed.
  • ../CuramCDEJ/lib/ext/jar/jackson-core-2.9.9.jar - old JAR removed.
  • ../CuramCDEJ/lib/ext/jar/jackson-databind-2.9.10.1.jar - old JAR removed.
 
  • ../EJBServer/components/Rest/restlib/dependencyLibsExt/jackson-annotations-2.10.2.jar - new JAR added.
  • ../EJBServer/components/Rest/restlib/dependencyLibsExt/jackson-core-2.10.2.jar - new JAR added.
  • ../EJBServer/components/Rest/restlib/dependencyLibsExt/jackson-databind-2.10.2.jar - new JAR added.
  • ../EJBServer/components/Rest/restlib/dependencyLibsExt/jackson-annotations-2.9.9.jar - old JAR removed.
  • ../EJBServer/components/Rest/restlib/dependencyLibsExt/jackson-core-2.9.9.jar - old JAR removed.
  • ../EJBServer/components/Rest/restlib/dependencyLibsExt/jackson-databind-2.9.10.1.jar - old JAR removed.
 

WorkItem:257866 - Introduce Support for IBM Cloud Kubernetes Service

Support for IBM Cloud Kubernetes Service has been introduced to the product.

IBM Cloud Kubernetes Services 1.16 is now supported as a deployment target for non-production and production environments. IBM Cúram Social Program Management supports IBM Cloud Kubernetes Services 1.16 only when containerized with IBM WebSphere Liberty.

For more information, see the What's New section in Version 7.0.10.0 of the product documentation and the Containerization of IBM Cúram Social Program Management Guide.
 

WorkItem:257869 - Introduce Support for Docker

IBM Cúram Social Program Management now supports Docker version 19.0.3.5 for packaging IBM Cúram Social Program Management into Docker Containers for development and deployment with IBM WebSphere Liberty and deployment on IBM Cloud Kubernetes Services.

For more information, see the What's New section in Version 7.0.10.0 of the product documentation and the Containerization of IBM Cúram Social Program Management Guide.
 

WorkItem:257872 - Introduce Support for WebSphere Application Server Liberty

IBM Cúram Social Program Management now supports WebSphere Application Server Liberty version 19.0.0.12 when containerized and deployed on IBM Cloud Kubernetes Services (IKS).

For more information, see the What's New section in Version 7.0.10.0 of the product documentation and the Containerization of IBM Cúram Social Program Management Guide.
 

WorkItem:257873 - Introduce Support for IBM MQ Long Term Support

IBM Cúram Social Program Management now supports IBM MQ Long Term Support (LTS) version 9.1.0.4 only when IBM Cúram Social Program Management is containerized with IBM WebSphere Liberty and deployed on IBM Cloud Kubernetes Service.

For more information, see the What's New section in Version 7.0.10.0 of the product documentation and the Containerization of IBM Cúram Social Program Management Guide.
 

WorkItem:258306 - Introduce Support for Helm

IBM Cúram Social Program Management now supports Helm version 2.16 for deploying IBM Cúram Social Program Management Docker Containers on IBM Cloud Kubernetes Services.

For more information, see the What's New section in Version 7.0.10.0 of the product documentation and the Containerization of IBM Cúram Social Program Management Guide.
 


Cúram Enterprise Framework

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

WorkItem:253863 - Update to REST infrastructure for file handling

The REST infrastructure has been enhanced to allow APIs that deal with binary data to handle additional metadata by passing the information as a JSON string in a custom header.

The Knowledge Center has been updated with full details on Cúram REST API modeling conventions:

https://www.ibm.com/support/knowledgecenter/SS8S5A_7.0.9/com.ibm.curam.content.doc/MSDK/msdk_c_rest_api_modeling_conventions.html
 

WorkItem:255703 - The Swagger spec generator in the REST Infrastructure incorrectly describes binary APIs

Issue Description:
A Swagger spec is automatically generated at runtime, which describes the details of all REST APIs in the system. There was an issue in how the description was being generated for binary APIs - some values that are sent as request or response headers were incorrectly described as body attributes.

User Interface Impact: No

Steps to Reproduce:

  1. Using a Swagger UI tool, view the Swagger spec for the REST APIs and expand the details of a binary REST API - for example, GET /v1/files/{file_id}.
  2. View the description of the response body - using the GET /v1/files/{file_id} as an example, it indicates that there are two attributes, named 'data' and 'fileName'.
  3. Issue: This is incorrect, because when the API is called, 'fileName' is not returned in the response body, the name of the file is actually returned in a Content-Disposition response header. So the description stating that 'fileName' is a body attribute is incorrect.
Resolution:
The Swagger spec generator has been updated for all binary REST APIs, so any attributes that are being sent in request or response headers are now properly described in the Swagger spec as headers, instead of body parameters.

Note that this change does not affect the API itself, only the description that is being automatically generated in the Swagger spec for the API.
 

WorkItem:257082 - Enhanced Cross-Site Request Forgery (CSRF) token based protection

IBM Cúram Social Program Management makes use of the HTTP referrer header to protect against CSRF attacks. The SPM REST infrastructure has been enhanced to support additional token-based protection for all REST operations.

This is an optional feature and for full details see the new Cross-Site Request Forgery (CSRF) Protection section in the Connecting to a Cúram REST API Guide.
 


Dynamic Evidence

Evidence Validations

Evidence Validations

WorkItem:257122 - A comparison validation with multiple clauses in a Dynamic Evidence definition gets cached repeatedly in memory at run time resulting in the heap space being exhausted

Issue Description:
If a Dynamic Evidence type definition includes a validation which has a comparison validation containing multiple clauses, duplicate copies of this configuration information will be repeatedly added to a list in memory each time the validation executes.

Each time one of the affected validations succeeds, the configuration information gets added to the list in memory once more and persists there. However, each time one of them fails, this list in memory multiplies in size. All users who encounter the affected validation will contribute to this memory issue. This leads to a rapid increase in heap usage and eventually exhausts all the heap space available resulting in the server crashing or becoming unresponsive.

User Interface Impact: No

Prerequisite(s):
This issue only affects Dynamic Evidence with comparison validations that have multiple clauses. The following example describes how to configure such a validator.

  1. Login as an administrator.
  2. Navigate to Dynamic Evidence under Rules and Evidence in the shortcuts panel.
  3. Locate an evidence type that contains an integer attribute.
  4. Select one of the Evidence Type Versions and choose New In Edit Copy specifying an effective from date.
  5. For this new version, select the Edit Metadata row-level action.
  6. On the Evidence Properties panel of the evidence editor, click on the Validations tab.
  7. Click Add to add a new Comparison validation. Specify the required fields for the validation details. Ensure Use Literal and Multiple Clauses are checked.
  8. Add two Clauses to the validation.
  9. Choose the Conjunction (Any or All) and click Save.
  10. Save the evidence type version in the editor.
  11. Activate the new Evidence Type Version from the row-level menu on the Dynamic Evidence list page.
Steps to Reproduce:
  1. Login as a caseworker.
  2. Navigate to a case for which the evidence type is configured.
  3. Add an instance of the evidence type to the case.
  4. Specify an invalid value for the attribute that has the comparison validation. Try to save the evidence.
  5. The previously configured validation message is displayed correctly.
  6. Try to save the evidence again.
  7. Issue: Multiple copies of the same validation message will be displayed on the screen, due to the multiple copies of the configuration data stored in memory on the server. The number of validation messages will increase significantly with each attempt to save the evidence. In a worst-case scenario, the heap space on the server will be exhausted, resulting in the server crashing or becoming unresponsive.
Resolution:
The configuration data for comparison validators in Dynamic Evidence is now only processed once and duplicates are no longer loaded into memory.
 


Technical Services

Business Intelligence

Business Intelligence

WorkItem:257646 - The Flex versions of Business Intelligence Charts are deprecated

The Flex versions of SPM Business Intelligence Charts are now deprecated.

They are being deprecated as all SPM provided BIRT charts that were previously rendered using Flex/Flash have been rendered in native BIRT format as PNG images since the SPM 6.0.5.8 release.

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


Integrated Case Management

Eligibility & Entitlement
Evidence Management
Investigations

PO08185, WorkItem:255177 - While printing inline view of Communications 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 Communications, the print layout incorrectly displays the placeholder text 'undefined' at the top of the page instead of the page title. A similar issue that occurred when printing Notes has been fixed in WorkItem:244924.

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 Communications.
  4. Add a new Communications using the Record Communication 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 Communications from a Person or Case, the page title now displays correctly.
 


Eligibility & Entitlement

PO07933, WorkItem:237992 - Product Delivery creation wizard requires the SERVER_DIR environment variable to be set

Issue Description:
When defining a new Product Delivery case using the wizard in the administration application, the default eligibility ruleset is not created and an error like the following is written to the server log:
java.io.FileNotFoundException: null/components/core/CREOLE_Rule_Sets/ProductWizardDefaultEligibilityEntitlementRuleSet.xml (No such file or directory).

This happens because the New Product Delivery wizard attempts to read a starter ruleset XML file from the file system of the server whose location is specified by system environment variable SERVER_DIR. In either a development or runtime environment this environment variable is not guaranteed to be set and, if it is not set, the XML file will not be found. In this instance, the starter ruleset will not be automatically created for the new product and instead must be created manually by an administrator.

User Interface Impact: No

Steps to Reproduce:

  1. Login as an administrator.
  2. Navigate to the Administration Workspace, expand Case in the shortcuts panel and click on Product Delivery Cases.
  3. Click on the New page action to open the New Product creation wizard.
  4. Enter a name for the new product, TestProduct1, for example. Enter appropriate details in all the mandatory fields for the remainder of the wizard steps.
  5. On the final page of the wizard click Finish.
  6. Expand Rules and Evidence in the shortcuts panel and click on Curam Express Rule Sets.
  7. Select the 'Eligibility and Entitlement: Determination' category and click Search.
  8. The ruleset for the newly created product is not created.
  9. Issue: The server log file contains the above error message relating to the ProductWizardDefaultEligibilityEntitlementRuleSet.xml file.
Resolution:
The starter ruleset XML file is now read from the classpath instead of the server file system and hence is no longer dependent on the SERVER_DIR environment variable. The new ruleset will now be successfully created by the New Product wizard.
 

WorkItem:254277 - Performance optimization for the ReassessOutstandingCases batch process

Issue Description:
The ReassessOutstandingCases batch process reassesses cases that have been queued for reassessment on the ScheduleReassesssment entity. More information on the batch process can be found in the knowledge center https:www.ibm.com/support/knowledgecenter/SS8S5A_7.0.10/com.ibm.curam.content.doc/Operations/c_COPSGUIDE_Processes1Reassessoutstandingcases1.html.

When ReassessOutstandingCases is used to reassess long-lived (1+ years) Provider Management product delivery cases, where provider groups have very large numbers (thousands) of providers, the batch program may take longer to execute due to the heavy use of the 'contains()' method of the Java class java.util.ArrayList within the batch program logic.

User Interface Impact: No

Steps to Reproduce:
This change relates to a performance optimization of the ReassessOutstandingCases batch program. It is highly dependent on user data and as such is not directly reproducible.

Resolution:
The dependency on the 'contains()' method of the Java class java.util.ArrayList has been removed, which improves the performance of this batch program when dealing with long-lived Provider Management product delivery cases.
 

WorkItem:257556 - The Flex Widget for Case Determination is deprecated

The Case Determination Flex Widget is now deprecated.

This Flex Widget is being deprecated as it is part of the Case Determination feature that was deprecated in Social Program Management 7.0.0.

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


Evidence Management

PO07459, WorkItem:231808 - When modifying an evidence, no validation is being performed on the effective date value of evidence types that do not contain a business start or end date

Issue Description:
A hook-point exists that allows a business start date to be derived where no business start date exists on an evidence record. This is currently not used to validate the effective date against this calculated/derived business start date. This can result in an incorrect timeline of evidence, with the effective date of a succession earlier that the business start date.

User Interface Impact: No

Prerequisite(s):

  1. Provide an implementation of the EvidencePeriodHook interface for an evidence type that has no business dates, Names, for example.
    • This implementation should return the date of birth as the business start date and date of death as the business end date.
Steps to Reproduce:
  1. Login as a caseworker.
  2. Register a new Person (Tom Smith), setting the date of birth to 1/1/1970.
  3. Modify the Names evidence, specifying the Name as Tommy Smith and the effective date as 1/1/1969.
  4. Issue: The system saves the Name details despite the fact that the effective date is earlier than the business start date.
Resolution:
The logic for performing an effective dated change on a piece of evidence now leverages the EvidencePeriodHook interface to ensure that the effective date being specified is validated against the correct evidence business dates. This ensures that the evidence timeline will remain intact and that an evidence effective date earlier than the evidence start date will never be entered.
 


Investigations

WorkItem:255384 - Printing issues with Contact Logs

Issue Description:
Attempting to print Contact Logs using the page-level print icon results in unexpected behavior after one or more Contact Logs are expanded.

User Interface Impact: No

Steps to Reproduce:

Scenario 1:

  1. Login as an investigator.
  2. Click on the Investigator workspace tab.
  3. Expand the shortcuts panel and select New Investigation under Investigations.
  4. In the New Investigation modal, choose a non-registered person.
  5. Use the Register Person wizard to register the person.
  6. In the New Investigation modal presented to the user after person registration, select any Type.
  7. Click Save.
  8. On the Investigation Case click on the Contact tab and select Contact Log.
  9. Use the New Contact page-level action to create a new Contact Log.
  10. Use the toggle to expand the newly created Contact Log on the All Contacts list page.
  11. Click on the page-level print icon.
  12. Issue: The content panel containing the Contact Logs is not printed correctly. Irregular behavior, such as printing of a blank page, refreshing of the Contacts tab, or distortion of the page layout occurs.
Scenario 2 (If you're using Child Welfare):
  1. Login as a Child Welfare caseworker.
  2. Register a new Person.
  3. Click on the Care and Protection tab and select Cases.
  4. Using the New page action, create an Ongoing Case for the person.
  5. On the Ongoing Case click on the Contact tab and select Contact Log.
  6. Use the New Contact page-level action to create a new Contact Log.
  7. Use the toggle to expand the newly created Contact Log on the All Contacts list page.
  8. Click on the page-level print icon.
  9. Issue: The content panel containing the Contact Logs is not printed correctly. Irregular behavior, such as printing of a blank page, refreshing of the Contacts tab, or distortion of the page layout occurs.
Resolution:
This issue has been resolved by ensuring the correct functionality for printing Contact Logs is invoked.
 


Administration Suite

WorkItem:249764 - Unable to close a user account if the user is the case owner of an open Participant Data Case or Assessment Case

Issue Description:
An administrator is unable to close a user account if the user is a case owner of an open Participant Data Case or an open Assessment Case. The issue is that these users may be assigned a case owner role on some cases that cannot be closed. An example of this is the Participant Data Case that is created when a new person is registered.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a caseworker.
  2. Register a new Person.
  3. Login as an administrator.
  4. Select Administration Workspace.
  5. Select User Search in the shortcuts panel.
  6. Search for the caseworker user name that registered the new Person.
  7. Click on the User Name hyperlink to open the user's home page.
  8. Select Close User from the page level actions.
  9. Add any other user for Reassign Task To and click Save.
  10. Issue: An error message is displayed, 'This user is the owner of one or more non-closed cases and cannot be closed. Please contact the user's supervisor.'
Resolution:
This issue is now resolved, a new interface has been introduced to exclude certain case types in this validation when closing the user account. Out-of-the-box, Participant Data Cases and Assessment Cases have been added as case types to exclude.

Technical:
New Interface:
  • curam.core.impl.CloseUserExcludedCases
Out-of-the-box implementations:
  • curam.core.impl.CloseUserExcludedCasesImpl - for the Participant Data Case type
  • curam.assessmentplanning.hook.impl.CloseUserExcludedCasesImpl - for the Assessment Case type
 


Intake

PO08350, WorkItem:248696 - Filing date being returned as the disposed date for the Income Support application

Issue Description:
After disposing an Income Support application, the drop-down preview of the application in the Application tab for the person incorrectly displays the filing date as the disposed date.

User Interface Impact: No

Steps to Reproduce:

  1. Login as an Income Support caseworker.
  2. Register a new Person.
  3. From the person home page, select New Application from the tab menu.
  4. Create and submit a new application with at least one program selected. Ensure that the date of the application is set to yesterday.
  5. Click on the Applications tab and click on the application reference link to open the Application tab.
  6. Click on the Programs tab and use the Withdraw row-level action to withdraw each of the programs.
  7. Navigate back to the Applications list page for the person and select the arrow drop-down beside the relevant application.
  8. Issue: The 'Disposed Date' field is populated with the filing date rather than the disposed date.
Resolution:
When an Income Support application is disposed, the disposed date is now correctly displayed when viewing the application from the person's Application tab. When an application includes multiple programs the most recent disposed date for the programs is displayed.

Technical:
The issue was caused by a front-end attribute being set to the incorrect value. The issue was resolved by setting this attribute to the correct value. Logic was also added to ensure that the most recent disposed date is shown in the case of an application with multiple programs.
 


Application Development Environment

Client Development Environment
Core Development Infrastructure
Server Development Environment

Client Development Environment
Accessibility
Widgets

PO07983 PO08726, WorkItem:239726 - When using the page level print icon in the Internet Explorer 11 browser with a minimized context panel, the context panel does not print

Issue Description:
When using the page level print button from a page with a collapsed context panel in Internet Explorer 11, the context panel does not print. Instead, in some older versions of Social Program Management only the main content area prints and in more recent versions the main content area prints twice. This issue does not occur in other supported browsers.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a caseworker using Internet Explorer 11.
  2. Register a new Person.
  3. Collapse the context panel on the newly created person home page.
  4. Click on the page level print icon.
  5. Issue on older versions of SPM: The context panel is not printed, instead, only the main content area prints.
  6. Issue on recent versions of SPM (v709 onwards): The context panel is not printed, instead, the main content area is printed twice.
Resolution:
The issue has been resolved by updating the Javascript related to printing pages to ensure that both the context panel and main content area are printed only once when using the page level print button from a page with a collapsed context panel in Internet Explorer 11.
 

PO08246, WorkItem:246520 - Completing a submit action in a modal page does not refresh the page when the action link goes through a resolver page

Issue Description:
When a user is logged in to the application and tries to edit and save data, the submit action in a modal page that invokes a resolver page redirects the user back to the page that is currently open in the tab bar, that page is not refreshed with the new values entered when the modal closes.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a Child Welfare intake worker.
  2. Create a new Intake case.
  3. Add a Participant to the Intake case.
  4. From the tab actions menu, select Open Intake to open the Intake case in a new tab.
  5. From the Intake case tab actions menu, select Edit Basics.
  6. Change the Category type and click Save.
  7. Issue: The Intake case home page is not updated with the new Category type selected.
Resolution:
The javascript surrounding resolver pages has been updated and now when a user submits a modal page where the modal's submit action invokes a resolver page that redirects the user back to the page that is currently open in the tab bar, the panel is refreshed when the modal closes.

Technical:
The javascript that handles a redirect request from a resolver page has been updated to reload the page that resolver is redirecting to if the page is currently open in the tab bar.
 

WorkItem:257169 - Hardcoded literal references to the Helvetica Neue font have been deprecated and replaced with variable references

The IBM Social Program Management (SPM) application has been updated to replace hardcoded literal references to the Helvetica Neue font with variable references. The ability to change the main SPM font has been simplified for future releases following this change.

The changes made to the SPM application are as follows:

  • The IBM application font faces that are specific to Helvetica and Helvetica Neue have been deprecated
  • Generic IBM font faces have been introduced. These font faces are defined in main-ibm-font.css and are intended to be used in place of the deprecated IBM Helvetica Neue font faces (MainLightFontforIBM, MainRegularFontforIBM, MainMediumFontforIBM, MainBoldFontforIBM)
  • Multiple style sheets throughout the application have been updated to use the font faces that are defined in main-ibm-font.css
 

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


Accessibility

PO08129, WorkItem:243579 - Mandatory indicators are not explicitly rendered visually or by screen reader on input fields used in cross field validations on the address widget

Issue Description:
When registering a person, the caseworker is not informed that at least one of the first two address fields must be filled out before submitting the form. Instead, if the caseworker does not enter at least three characters in one of the first two fields, a validation message is thrown when the caseworker submits the form.

User Interface Impact: Yes

Prerequisite(s):

Update the address configuration:

  1. Set the address format to 'US' in the curam-config.xml file.
Update the address layout:
  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 modify the value of the property 'curam.address.addressLayout' to 'US'.
  5. Click on the Publish page action to publish the changes.
Steps to Reproduce:
  1. Login as a caseworker.
  2. Launch the Register Person wizard from the shortcuts menu. Add a name that doesn't exist and click next.
  3. On the second page of the wizard, do not enter any address details.
  4. Click Save.
  5. Issue: A validation message 'Street 1 must contain at least 3 characters when Apt/Suite is empty' is thrown. This information was not conveyed to the caseworker before submitting the form.
Resolution:
This issue was resolved by adding informative text ('Please enter either Apt/Suite or Street 1') to be displayed above the address fields to inform the caseworker. For a visually impaired user, accessing the screen using the JAWS screen reader, this description is read out when the user navigates to the first two address input fields.

Technical:
The documentation has been updated to include details on how to configure the partially mandatory address fields. For more information, see https://www.ibm.com/support/knowledgecenter/en/SS8S5A_7.0.10/com.ibm.curam.content.doc/WebClientReference/r_WEBCREF_Specific1Addresses1.html
 

PO08466, WorkItem:251143 - When creating a new Child Welfare Intake, the screen reader does not read the title of the new Assistant tab created after saving the new Intake

Issue Description:
When a supported screen reader is used and a visually impaired user creates a new Child Welfare Intake, the screen reader reads the word ‘Basics’, it does not read the title of the new Assistant tab just created after saving the new Intake. This issue is not reproducible when an existing Intake is opened from the shortcuts panel Intakes to be Completed. In this scenario, the title of the Assistant tab is communicated by the screen reader.

User Interface Impact: No

Steps to Reproduce:

  1. Start a screen reader.
  2. Login as a Child Welfare intake worker.
  3. Navigate to the Intakes section in the shortcuts panel.
  4. Select New Intake.
  5. Enter the required values and click Save.
  6. Issue: The Assistance tab title of the newly created Intake is not communicated by the screen reader. Instead, the word ‘Basics’ is read by the screen reader.
Resolution:
Now when a screen reader user creates a new Intake, the focus will remain on the newly opened Assistance tab allowing the screen reader to communicate the associated aria-label and read the title of the new Assistant tab.
 

PO08563, WorkItem:253647 - When a single field is nested inside a cluster, screen reader users are not provided sufficient context for the field

Issue Description:
When a supported screen reader is used and a visually impaired user navigates to a page that contains a field attribute with no label defined and this attribute is inside a Cluster attribute with a title, the screen reader users are not provided with sufficient context on the purpose of the field.

User Interface Impact: No

Steps to Reproduce:
An example of this problem can be seen as follows:

  1. Start a screen reader and open Internet Explorer 11 browser.
  2. Login as a Child Welfare caseworker.
  3. Register a Person and create an Ongoing Case.
  4. On the Ongoing Case home page, choose Edit from the actions menu.
  5. Using the keyboard, tab to the Comments field.
  6. Issue: The screen reader reads 'edit type and text', without providing context on the purpose of the Comments field.
Resolution:
The UIM page will now be rendered so that the field will include an 'aria-label' which takes its value from the localized value of the Cluster title, providing the screen reader user with context for the field.
 

PO08574, WorkItem:254144 - In High Contrast Mode on a Windows operating system, the page size arrows do not display on searches when using Internet Explorer

Issue Description:
When High Contrast Mode is enabled on a Windows operating system, and a search is performed which returns many records, the page size arrows do not display on the Internet Explorer (IE) browser.

User Interface Impact: No

Steps to Reproduce:
The issue applies to any page size selector on a page that uses pagination to control the number of items displayed. The following scenario is an example of where this occurs.

  1. On a Windows operating system, search for the High Contrast settings.
  2. Enable High Contrast mode.
  3. Using an IE browser, login as a system administrator.
  4. Navigate to the System Configurations workspace.
  5. Click on Application Data under Property Administration in the shortcuts panel.
  6. Click on Search and scroll to the bottom of the page.
  7. Issue: The page size arrows do not display (15, 30, 45 indicators).
Resolution:
A specific IE stylesheet (CSS) attribute has been introduced to allow the background image to be displayed when High Contrast Mode is enabled on a Windows operating system.
 

PO08590, WorkItem:254490 - JAWS screen reader loses focus upon closing search modal windows when using IE11

Issue Description:
When closing or selecting a value from a search pop-up window using Internet Explorer (IE) 11, the browser focus moves away from the search icon and returns to the first editable field on the page. JAWS 2019 screen reader then reads out information of the first element on the page. This may cause a vision impaired user to perform unnecessary key navigation to navigate back to the search field.

User Interface Impact: No

Steps to Reproduce:

Example:

  1. Turn the screen reader on while using an IE11 browser.
  2. Login as a caseworker and launch the Register Person wizard.
  3. On the second page of the wizard, tab to the Preferred Office search.
  4. Execute a search and select a result from the list, or close the pop-up window.
  5. Issue: As the pop-up window closes, the focus is lost and goes back to the first editable field (Reference Number) of the modal resulting in the screen reader reading out 'Reference Number'. This causes an impaired user to perform unnecessary key navigation to navigate back to the search field.
Resolution:
This issue is now resolved across the application and the focus now remains on the search icon when a value is selected in the pop-up modal or the modal is closed.
 

PO08611, WorkItem:255274 - Field focus delay on the Microsoft Internet Explorer and Edge browsers

Issue Description:
On the Microsoft Internet Explorer (IE) and Edge browsers, there is a delay before focus is set to the first editable field on a form when a page loads. This delay is not seen when using Google Chrome. If the user does not notice this change, they will type in an incorrect field.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a caseworker.
  2. Click on the Cases and Outcomes workspace tab.
  3. Select Person under Searches in the shortcuts panel.
  4. On the Person search page, quickly begin typing in any field other than the Reference field.
  5. Issue: After a small delay the cursor will be moved back to the first row, the Reference field.
Resolution:
The issue has been resolved to prevent switching the focused field if the user has already started typing in the form.
 

PO08609, WorkItem:256480 - Participant Members list heading in the context panels fails minimum color contrast

Issue Description:
In IBM Curam Social Program Management (SPM) Child Welfare module, the column headers in the case context panels list view (Member, Relationship, Age) display in a light gray color which fails the minimum color contrast requirement. This is appearing for the Ongoing Case, Investigation Case, Adoption Case, Outcome Plan, Outcome Plan Assessment, Outcome Plan Goal, Outcome Plan Objective, and Outcome Plan Referral.

User Interface Impact: No

Related Work Items: 256479 (APAR no. PO08609)

Steps to Reproduce:

Scenario 1 - Ongoing Case:

  1. Login as a Child Welfare caseworker.
  2. Register a child.
  3. Register another child.
  4. Create a new case of type Ongoing Case.
  5. From the case’s tab action menu, select New Member.
  6. Select the name of the person not already on the case.
  7. On the context panel, select the List View rather than the Photo View.
  8. Issue: The header in the Photo View fails for color contrast.
Scenario 2 - Investigation Case:
  1. Login as a Child Welfare intake worker.
  2. Create an intake with both an alleged maltreater and an alleged victim and screen in.
  3. Submit the intake.
  4. Select Administration then Tasks.
  5. Select Make Decision and Approve. Enter comments and Save.
  6. On the task, select Intake Home.
  7. From the action menu, select Start Investigation.
  8. Select the names and Start. The Investigation context panel is open.
  9. On the context panel, select the List View rather than the Photo View.
  10. Issue: The header in the Photo View fails for color contrast.
Scenario 3 - Adoption Case:
  1. Login as a Child Welfare caseworker.
  2. Register a child.
  3. Register another child.
  4. Create a new case of type Adoption Case.
  5. From the case’s action menu, select New Member.
  6. Select the name of the person not already on the case.
  7. On the context panel, select the List View rather than the Photo View.
  8. Issue: The header in the Photo View fails for color contrast.
Scenario 4 - Outcome Plan:
  1. Login as a Child Welfare caseworker.
  2. Select the Ongoing Case you created earlier with two members.
  3. Select Outcome Plans then New.
  4. Select ‘Child Welfare Outcome Plan’ and add both members to the case.
  5. On the context panel, select the List View rather than the Photo View.
  6. Issue: The header in the Photo View fails for color contrast.
Scenario 5 - Outcome Plan Assessment:
  1. Login as a Child Welfare caseworker.
  2. Select the Outcome Plan you created earlier with two members.
  3. Select Assessments & Factors then New.
  4. Select Child Strengths and Needs.
  5. Select both members and select the Role of Child for each.
  6. Select random results in the assessment. Select Complete.
  7. Select the Assessment to see the context panel.
  8. On the context panel, select the List View rather than the Photo View.
  9. Issue: The header in the Photo View fails for color contrast.
Scenario 6 - Outcome Plan Goal:
  1. Login as a Child Welfare caseworker.
  2. Select the Outcome Plan you created earlier with two members.
  3. Select Goals then New Goal.
  4. Add a goal and Save.
  5. Select the goal to see the context panel.
  6. On the context panel, select the List View rather than the Photo View.
  7. Issue: The header in the Photo View fails for color contrast.
Scenario 7 - Outcome Plan Objective:
  1. Login as an administrator.
  2. Select Outcome Management then Outcome Plans.
  3. Select Child Welfare Outcome Plan then Objectives.
  4. Select Add and add at least one objective. Save.
  5. Login as a Child Welfare caseworker.
  6. Select the Outcome Plan you created earlier with two people on it.
  7. Select Workspace.
  8. Drag an objective into the Workspace.
  9. Enter an Expected End Date and select both clients. Save.
  10. Open the objective you entered to see the context panel.
  11. On the context panel, select the List View rather than the Photo View.
  12. Issue: The header in the Photo View fails for color contrast.
Scenario 8 - Outcome Plan Referral:
  1. Login as a Child Welfare caseworker.
  2. On the Outcome Plan you created earlier with two members, select Activities.
  3. Select New Referral.
  4. In the Service field, type a%. Click Next.
  5. Select both clients, click referred by Me, and enter a Reason. Click Next.
  6. Click Next several times until the wizard finishes.
  7. Select the Referrals tab then select a Referral to see the context panel.
  8. On the context panel, select the List View rather than the Photo View.
  9. Issue: The header in the Photo View fails for color contrast.
Resolution:
The CSS color for the headers in the Photo View has been changed to respect the color contrast ratio.

Technical:
The issue was resolved by updating the color header color to #5A5A5A in the following CSS files using the new property $infrastructure_context_panel_lists_header_font-color:
  1. OutcomePlanContextPanel.css
    • body.curam.soria .container-panel-serviceorreferral #stackCon-fourimages-outcomeplan .stack-container-list .tab-case-list th.table-header, body.curam.soria .container-panel-outcomeplan #stackCon-fourimages-outcomeplan .stack-container-list .tab-case-list th.table-header
  2. ApplicationCaseContextPanel.css
    • body.curam.soria #container_stackCon-threeimages-applicationcase .stack-container-list .tab-case-list table.list-body th.table-header
  3. cfss-IntegratedCase.css
    • classe body.curam.soria .container-panel #container_stackCon-threeimages .stack-container-list .tab-case-list th.table-header
  4. IntegratedCase.css
    • body.curam.soria .container-panel-ic #container_stackCon-fourimages .stack-container-list .tab-case-list th.table-header
  5. HCRCaseContentPanel.css
    • body.curam.HCRCASEAPP.context-panel div.pd-container-panel #container_stackCon-threeimages .stack-container-list .tab-case-list th {
  6. cgiss-cash-and-food-assistance-context-panel.css
    • body.curam.soria .container-panel-productdelivery #container_stackCon-threeimages .stack-container-list .tab-case-list th.table-header
  7. cgiss-application-case.css
    • body.curam #container_stackCon-threeimages .stack-container-list .tab-case-list th
 


Widgets

PO08213, WorkItem:245423 - My Appointments pod only shows military time

Issue Description:
My Appointments pod, also known as the BiWeekly Calendar, on the caseworker home page does not use the global setting for time. It uses its own custom properties instead. To be consistent with the rest of the application, My Appointments pod should use the global setting for time.

User Interface Impact: No

Prerequisite(s):

  1. Set the Application Configuration property timeformat=hh mm a
  2. Set the Application Configuration property timeseparator=:
Steps to Reproduce:
  1. Login as a caseworker.
  2. Navigate to the Calendar view.
  3. From the actions menu, select New Meeting.
  4. Create a new meeting for today to run from 11:15 am to 5:30 pm.
  5. Navigate back to the caseworker home page.
  6. Issue: The format of the start and end times for the meeting in the My Appointments pod is in 24-hour format.
Resolution:
The BiWeekly Calendar widget implementation has been updated to use the global time setting, as opposed to using its own custom properties for start and end time. This brings it in line and makes it consistent with other areas in the application that display time.

Technical:
As part of implementing this fix, the custom properties associated with the My Appointments pod for controlling the setting of the start time, end time and separator have been deprecated. These properties are:
  • event.time.start.format
  • event.time.end.format
  • event.time.separator
These are located inside ../webclient/components/CEFWidgets/javasource/curam/widget/render/infrastructure/i18n/BiWeeklyCalendar.properties.
 

PO08461, WorkItem:251087 - Rich Text Editor removes formatting without a warning message

Issue Description:
When pasting formatted content into the Rich Text Editor widget, the user should be informed if any styling will be lost, such as bolded, italicized or underlined words, as these may be important in the overall context of the content. Currently, no such warning is displayed.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a caseworker.
  2. Navigate to a person home page.
  3. Click on the Client Contact tab and select the Notes section.
  4. Click on the New page action to create a new Note.
  5. Populate any mandatory fields.
  6. Copy formatted content from Microsoft Word and paste it into the Rich Text Editor field of the Note.
  7. Issue: After pasting the formatted content, the font style and background style formatting are removed without any warning to the user.
Resolution:
The Rich Text Editor configuration has been updated to allow the pasting of styles from Microsoft Word. For any styles not supported, the warning 'Some content and formatting may have been removed due to filtering by the Note editor. Please review content before saving.' will be presented to the user. Note: Ensure that the browser cache is cleared in order to pick up this fix.
 

PO08510, WorkItem:252278 - Long values are truncated in the filtering drop-down widget menu after selection when using the Internet Explorer 11 browser

Issue Description:
Modals that contain drop-down menus with long item names are sometimes right justified, which means that a user cannot see the beginning of the selected drop-down text. This display issue only occurs when using the Internet Explorer 11 browser.

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 modify the value of the property 'curam.evidence.pdc.personenabled' to 'NO'.
  5. Click on the Publish page action to publish the changes.
Steps to Reproduce:
  1. Login as a caseworker using the Internet Explorer 11 browser.
  2. Click on the Cases and Outcomes tab.
  3. In the shortcuts panel under Registration, select Person and click Next.
  4. On the 'Country/Region of Birth' drop-down menu, select for example 'Macedonia, The Former Yugoslav Republic of'.
  5. Issue: The selected country name is aligned to the right and the start of the country name is not visible.
Resolution:
This issue has been resolved now and the drop-down menu widget has been updated to properly left-align all selected menu items regardless of the length.
 


Core Development Infrastructure

WorkItem:256258 - On WebSphere Liberty deployments, duplicate java classes within the jde-commons and coreinf JARs caused runtime errors

Issue Description:
Traditional WebSphere (tWAS), WebLogic (WLS) and WebSphere Liberty have different ways of handling duplicated Java classes in the same JVM.

When IBM Curam Social Program Management was deployed on a WebSphere Liberty environment, users of the application could not perform some basic application steps, like logging in to the application. In a WebSphere Liberty Deployment, the presence of duplicate Interface Java Classes in JAR files caused class cast exceptions. This is because WebSphere Liberty loads a unique instance of the class for each EAR/Application that contains it. These separate instances are incompatible, even though they are instances of the same class. The steps below are an example of how the issue manifested itself.

User Interface Impact: No

Related WorkItem(s): 256602

Steps to Reproduce:

  • Login as a caseworker.
  • Issue: The login failed. Examination of the logs highlighted the following class cast exception:
 

[err] java.lang.ClassCastException: curam.util.security.EJSLocal0SLLogin_80b12a65 incompatible with curam.util.security.AuthenticationLocal
[err] at curam.util.security.WLPCuramLoginModule.narrowStub(WLPCuramLoginModule.java:738)



Resolution:
To address this issue, a new JAR file called coreinf-ejb-interfaces.jar was created. This JAR is a consolidation of all the duplicate interface classes. In WebSphere Liberty the coreinf-ejb-interfaces JAR has been added to a shared resources directory. This means the JAR is available for each Application/EAR. In traditional deployments such as traditional WebSphere and WebLogic, each Application/EAR has been updated to include the new JAR file within their library path.

Note:
The addition of the new JAR file will require an update to the Eclipse Classpath. This will be automatically done if the build target - build createClasspaths is invoked as part of a build. For more information, refer to the Eclipse .classpath section in the IBM Curam Social Program Management Knowledge Center.

Technical:
The following list of classes have been added to the new CuramSDEJ/lib/coreinf-ejb-interfaces.jar:

  • AsyncMethod.class
  • AsyncMethodLocal.class
  • Authentication.class
  • AuthenticationBase.class
  • AuthenticationLocal.class
  • Method.class
  • MethodImpl.class
  • MethodLocal.class
  • SvrRemoteException.class
  • TimerMethod.class
  • TimerMethodBase.class
  • TimerMethodLocal.class
The following list of classes have been moved from CuramSDEJ/lib/jde-commons.jar, and added to CuramSDEJ/lib/coreinf-ejb-interfaces.jar:
  • AsyncMethod.class
  • Authentication.class
  • Method.class
The following classes have been moved from CuramSDEJ/lib/coreinf.jar, and added to CuramSDEJ/lib/coreinf-ejb-interfaces.jar:
  • Authentication.class
  • Method.class
  • TimerMethod.class
 

WorkItem:256602 - Implement EJB Local Interfaces to avoid thread pool starvation in WebSphere Liberty deployments

Issue Description:
One of the key differences between traditional WebSphere (tWAS), WebLogic (WLS) and WebSphere Liberty, is that tWAS and WLS provide the ability to create multiple thread pools within the same JVM. However, WebSphere Liberty has a single thread pool called the 'default executor' and this thread pool runs all application threads.

Currently, when an EJB Session Bean remote interface is invoked using pass-by-reference semantics in tWAS and WLS application servers, the call is made on the same thread. However, WebSphere Liberty aligns with the EJB specifications which declares that EJB Remote uses pass-by-value and EJB Local uses pass-by-reference. As a result, every EJB Session Bean remote interface invocation results in a new thread being consumed from the default executor thread pool. This difference introduced a risk of thread exhaustion in the runtime application. This issue was identified as part of reliability verification testing running sample user workflows at high volume.

User Interface Impact: No

Related WorkItem(s): 256258, 256881

Steps to Reproduce:

  • Not applicable.
Resolution:
An EJB Local Interface has been added to the following Session Beans. The existing remote interfaces have been preserved for tWAS and WLS. The list below details the updated Session Bean Interfaces:
  • EJBMethodBean
  • LoginBean
  • AsyncMethodBean
  • SLMTimerBean
  • JDETimerBean
When an EJB Local Interface is invoked, the call is made locally on the same thread, therefore reducing the risk of thread pool exhaustion. These EJB's have also been consolidated to CuramSDEJ/lib/coreinf-ejb-interfaces.jar. For more information on this move, refer to the release note for WorkItem: 256258.
 

WorkItem:256881 - Avoid thread pool starvation in WebSphere Liberty deployments

Issue Description:
Threads that are used by IBM Social Program Management carry application caches that manage application processing. One of the key differences between traditional WebSphere (tWAS), WebLogic (WLS) and WebSphere Liberty, is that tWAS and WLS provide the ability to create multiple thread pools for the same application.

In tWAS and WLS the WebContainer thread pool is set up to process HTTP Requests and the 'SIBJMSRAThreadPool' is set up to process JMS Messages. This means that the client HTTP initiated transactions and the JMS initiated transactions can be isolated. However, this is not the case with WebSphere Liberty because it has one single thread pool called the 'default executor' and this thread pool runs all application and JMS processing.

This difference introduced a risk of thread exhaustion in the runtime application. The more threads used during processing, the greater the risk of contention between HTTP initiated transactions and JMS initiated transactions.

User Interface Impact: No

Related WorkItem(s): 256602

Steps to Reproduce:

  • Not applicable.
Resolution:
To mitigate against the risk of thread exhaustion, it was decided that client HTTP initiated transactions and JMS initiated transactions will be running on different WebSphere Liberty instances, integrated through a message engine (IBM MQ).

The Application/EAR responsible for processing client HTTP initiated transactions is called the JMS Producer and has JMS message consumption through EJB MDB's disabled.

The Application/EAR responsible for processing JMS initiated transactions is called the JMS Consumer and has JMS message consumption through EJB MDB's enabled.

This resolution is part of a multi-faceted solution, with client HTTP initiated transactions and JMS initiated transactions isolated from each other, and the implementation of local interfaces which is documented in related WorkItem 256602.


 


Server Development Environment
Batch Processing

WorkItem:257874 - Introduce new SSL properties to simplify process of executing build targets against a secure DB2 database

Issue Description:
All security guidelines state that all sensitive data must be encrypted within the system when stored (at rest) and also when moving between different elements of the system (in transit).

Previously, in order to run any development ant target, for example build configtest, build database or build runbatch against a DB2 database with SSL enabled, the following complex manual manipulation of the Bootastrap.properties file and .bindings file were required:

  1. Configure Java Runtime Environment to use SSL by following the instructions in http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.apdv.java.doc/src/tpc/imjcc_t0054066.html
  2. Configure the following property to true in .bindings file:
    • jdbc/curamdb/RefAddr/ XX /Type=sslConnection
    • jdbc/curamdb/RefAddr/ XX /Content=true
  3. Set the following proeprties in the Bootstrap.properties
    • curam.db.enable.bindings.generation=false
    • curam.db.disable.bindings.generation=true
If the steps were not implemented, the ant target failed to fully execute.

In order to simplify the process two new bootstrap properties have been introduced
  1. curam.db2.ssl.truststore.location - this property specifies the SSL trust store location to be used for secure DB2 database communications.
  2. curam.db2.ssl.truststore.password - this property specifies the SSL trust store password to be used for secure DB2 database communications.
User Interface Impact: No

Steps to Reproduce:
  • Do not employ manual workaround.
  • Execute the ant target build configtest against a secure DB2 database.
  • Issue: the build fails with the following error:
 


[configtest] DATABASE CONFIGURATION
[configtest] curam.db.type : DB2.
[configtest] The .bindings File will be automatically generated using the properties in the Bootstrap.properties file.
[configtest] DATABASE CONNECTIVITY
[configtest] Cannot connect to database: [jcc][t4][2030][11211][3.64.104] A communication error occurred during operations on the connection's underlying socket, socket input stream,
[configtest] or socket output stream. Error location: Reply.fill() - insufficient data (-1). Message: Insufficient data. ERRORCODE=-4499, SQLSTATE=08001.
[configtest] Warnings found, please examine the output above and re-run when resolved




Resolution:
Setting both properties will ensure the build target successfully executed when run against a secure DB2 database.

For more information on these properties refer to the Bootstrap.properties section in the Server Development Guide.

 

WorkItem:257882 - Update the method 'getEJBContext' in the class TransactionInfo to guard against Null Pointer Exceptions

Issue Description:
When running in a production environment logging and resilience is key to helping developers debug issues and diagnose problems.

The class TransactionInfo manages the execution of the business functionality and their transactions. TransactionInfo contains a method called getEJBContext(), the purpose of the method is to return the EJB Context for the current thread. There was a risk that a null pointer exception could be thrown if a transaction is null.

User Interface Impact: No

Steps to Reproduce:

  • Not applicable.
Resolution:
In order to mitigate against the risk of a null pointer exception been thrown, the method TransactionInfo.getEJBContext() has been updated to check if the transaction is null. If the transaction is null, the method TransactionInfo.getEJBContext() explicitly returns 'null'.
 

WorkItem:257883 - Provide the ability to perform easier bulk loading of SQL files

Issue Description:
The efficient bulk loading of SQL files plays an important role in upgrading and maintaining the IBM Social Program Management system.

A new ant file called CuramSDEJ/utils/loadsql.xml has been introduced to facilitate easier bulk loading of ad-hoc SQL files. There are many times during the lifecycle of the IBM Social Program Management system where SQL will need to be bulk loaded. One example is during the upgrade process, another example is during the deployment of the containerized IBM Social Program Management application. The sample helm charts delivered in the OpenSource repository github.com/IBM/spm-containerization use the file during the deployment of the containerized IBM Social Program Management on IBM Cloud Kubernetes Services.

User Interface Impact: No

Steps to Reproduce:

  • Not Applicable.
Resolution:
If, as part of a process, you need to execute one or more SQL statements from a file, or you need to execute multiple SQL files from a directory, run the ant target
 

ant -f CuramSDEJ/utils/loadsql.xml -Dsql.resource=/full/path/to/sql_file(s)


Batch Processing

PO08382, WorkItem:249466 - Batch application incorrectly setting Host header in DBtoJMS servlet HTTP Request

Issue Description:
The HTTP header which the batch launcher sends to the online application to begin a DBtoJMS transfer comprised a host name of 'curamhost' and port of '80' instead of the host name and port of the application server. This manifested as console error RUN_ID_DBTOJMS_ERROR_NOTIFYING_SERVER when running the batch launcher with DBtoJMS enabled and when the WebSphere application server was configured to strictly enforce the Host field of the HTTP request header.

User Interface Impact: No

Steps to Reproduce:

  1. Login to the WebSphere Administration console.
  2. Navigate to Environment > Virtual Hosts > client_host > Host Aliases.
  3. Select *:9044.
  4. Edit the Hostname variable to be the hostname of the application server.
  5. Select OK and Save to Master Configuration.
  6. Restart the application server.
  7. Run the batch launcher.
  8. Issue: Console error RUN_ID_DBTOJMS_ERROR_NOTIFYING_SERVER displayed.
Resolution:
The HTTP header which the batch launcher sends to the online application now sets the Host field so that it contains the host and port of the application server.

For more information on the Host header see the RFC at https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.23 .
 


Business Services

Calendaring/Scheduling

Calendaring/Scheduling

PO08504, WorkItem:252063 - Field labels are wrapped on the Edit Recurring Activity and Modify Meeting Details modals

Issue Description:
When updating an activity using the list view option, the field labels Frequency, Number of Occurrences and Modify All Occurrences are wrapped on the Edit Recurring Activity modal. Also, when updating a meeting using the list view option, the field labels Subject and Priority are wrapped on the Modify Meeting Details modal.

User Interface Impact: No

Steps to Reproduce:

Scenario 1:

  1. Login as an administrator.
  2. Navigate to the Calendar tab.
  3. Select New Recurring Activity from the page-level action menu.
  4. Add the mandatory details and click Save.
  5. Select the List View tab to view the calendar entries in list format.
  6. For the newly created recurring activity, select the Edit row-level action.
  7. Issue: The field labels Frequency, Number of Occurrences and Modify All Occurrences are wrapped on the Edit Recurring Activity modal page.
Scenario 2:
  1. Login as an administrator.
  2. Navigate to the Calendar tab.
  3. Select New Meeting from the page-level action menu.
  4. Add the mandatory details and click Save.
  5. Select the List View tab to view the calendar entries in list format.
  6. For the newly created meeting, select the Edit row-level action.
  7. Issue: The field labels Subject and Priority are wrapped on the Modify Meeting Details modal page.
Resolution:
Both issues have been resolved by adjusting the width of the Modify Meeting Details and Edit Recurring Activity modals to prevent field label wrapping.

Technical:
The following files have been updated:
  • ../webclient/components/core/Activity/RecurringUserActivity/Activity_modifyRecurringUserActivity1.uim
  • ../webclient/components/core/Calendar/Meetings/CalendarMeeting_modifyMeetingFromUserCalendar.uim
 


Cúram Modules

Outcome Management
Social Enterprise Collaboration
Provider Management
Verification
Supervisor Workspace
Universal Access
Intelligent Evidence Gathering
Evidence Broker
Financial Management
Identity Intelligence

Outcome Management

WorkItem:185548 - The Flex Widget for Outcome Plan Workspace is deprecated

The Outcome Plan Workspace Flex Widget is now deprecated. This Flex Widget is being deprecated as there is a JavaScript alternative available by default.

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

PO08559, WorkItem:253645 - Outcome Plan Service status is updated incorrectly when service is modified

Issue Description:
When a service is created within an outcome plan and is submitted for approval, if supervisory approval is required the status of the service is set to Submitted. If a modification is made to the service before the service is approved, the status of the service is incorrectly being updated to a status such as In Progress that it would be set to once approval occurs.

User Interface Impact: No

Steps to Reproduce:

Scenario 1:

  1. Login as an administrator and configure a new Service that will require manual supervisory approval.
  2. Login as a Child Welfare caseworker.
  3. Navigate to an existing Outcome plan.
  4. Create a new Service starting today.
  5. Submit the Service for approval.
  6. The status of the service is set to Submitted.
  7. Update the Service reason.
  8. Issue: The Service status is incorrectly set to In Progress which should not occur until the service is approved.
Scenario 2:
  1. Login as an administrator and configure a new Service that will require manual supervisory approval.
  2. Login as a Child Welfare caseworker.
  3. Navigate to an existing Outcome plan.
  4. Create a new Service starting in the future.
  5. Submit the Service for approval.
  6. The status of the service is set to Submitted.
  7. Update the Service reason.
  8. Issue: The Service status is incorrectly set to Not Started which should not occur until the service is approved.
Scenario 3:
  1. Login as an administrator and configure a new Service with a Maximum Amount of 1000, Unit of Measure of Session, and that requires manual supervisory approval.
  2. Login as a Child Welfare caseworker.
  3. Register a new Person.
  4. Create an integrated case.
  5. Add an Outcome Plan.
  6. On the Outcome Plan, add an activity of type New Service.
  7. Select the Service Name added in the Prerequisite(s) and set the authorized rate to 100.
  8. Open the new activity and select Submit.
  9. The status of the service is set to Submitted.
  10. Edit the activity and change the Authorized Rate to 200.
  11. Issue: The Service status is incorrectly set to In Progress which should not occur until the service is approved.
Resolution:
This issue has been resolved and now the status of a service created within an outcome plan is on longer incorrectly updated when the service is modified before approval occurs.
 


Social Enterprise Collaboration

MDT Portal

MDT Portal

WorkItem:185552 - The Flex Discussion Widget is deprecated

The Flex Discussion Widget is now deprecated.
This Flex Widget is being deprecated as it is no longer used by any UIM pages. All instances of the Flex version of this widget were already replaced with regular UIM pages.

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

WorkItem:185553 - The Flex Widget for the Social Enterprise Collaboration (SEC) Rich Text Editor is deprecated

The Rich Text Editor in the Social Enterprise Collaboration (SEC) MDTWorkspace is now deprecated.

This Flex Widget is being deprecated as it is no longer used by any UIM pages. All instances of the Flex version of the Rich Text Editor were already replaced with the CKEditor JavaScript Rich Text Editor.

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


Provider Management

PO08492, WorkItem:251696 - Narrow modals display truncations in drop-down menu items and field labels

Issue Description:
Incorrect modal width on Edit Inbox General Settings, New Text Translation, New Training Requirement, Edit Training, and New Service modals. These screens are too narrow and are causing truncation of data in drop-down menus, field labels and date fields which makes the data only partially visible to the user.

  • Edit Inbox General Settings modal, if values exist in the drop-downs, they are only partially visible.
  • New Text Translation modal, the field label Language is wrapping and some values are only partially visible in the Language drop-down menu.
  • New Training Requirement modal, the values in the drop-down menu Completion are truncated.
  • Edit Training modal, the date fields, and drop-down menu are truncated.
  • New Service modal, the field values are partially visible.
User Interface Impact: No

Steps to Reproduce:

Scenario 1:
  1. Login as a Child Welfare caseworker.
  2. Navigate to Inbox.
  3. Navigate to Task Preferences under Tasks in the shortcuts panel.
  4. Click the Edit button on the General Settings tab.
  5. Issue: On the Edit Inbox General Settings modal if values exist in the drop-downs, they are only partially visible.
Scenario 2:
  1. Login as an administrator.
  2. Navigate to the Administration Workspace.
  3. Navigate to Services under Provider Management in the shortcuts panel.
  4. Open an existing service.
  5. Click on the translation icon for any of the localizable fields, Name, for example.
  6. On the Localizable Text modal click on Add Translation.
  7. Issue: On the New Text Translation modal, the field label Language is wrapping and some values are only partially visible in the Language drop-down menu.
Scenario 3:
  1. Login as an administrator.
  2. Navigate to the Administration Workspace.
  3. Navigate to Services under Provider Management in the shortcuts panel.
  4. Open an existing service.
  5. Click on the Training Requirements tab.
  6. Add a new training requirement.
  7. Issue: The values of the drop-down menu Completion are truncated on the New Training Requirement modal.
Scenario 4:
  1. Login as an administrator.
  2. Navigate to the Administration Workspace.
  3. Navigate to Training Courses under Provider Management in the shortcuts panel.
  4. Edit an existing Training Course.
  5. Issue: The date fields and drop-down menu are truncated on the Edit Training modal.
Scenario 5:
  1. Login as a Provider Management Resource Manager.
  2. Click on the Providers and Services workspace tab.
  3. Select My Providers under Providers in the shortcuts panel.
  4. Click on the Reference of any provider to navigate to a provider home page.
  5. Click on the Services tab.
  6. Click on the New page action to create a new service.
  7. Add the mandatory details and click Save.
  8. Click on Service Centers and select the New page action.
  9. Add a new Service Center selecting the service created in the previous step.
  10. Click Save.
  11. On the Service Center list page, select the New Service row-level action of the newly created record.
  12. Issue: The field values on the New Service modal are partially visible.
Resolution:
The issues on the above UIM pages were resolved by increasing the overall modal width. This was achieved by removing the WINDOW_OPTIONS attribute for the respective modals.

Technical:
The issues were resolved by updating the modal size in the following pages:
  • Inbox_editInboxOptionsGeneralSettings.uim
  • ProviderManagement_addDescriptionTranslationToServiceOffering.uim
  • ProviderManagement_createTrainingRequirementForServiceOffering.uim
  • ProviderManagement_modifyTrainingFrmList.uim
  • ProviderManagement_createServiceCenterProviderOfferingPopup.uim
 

WorkItem:254821 - The label Removal Reason is wrapping and the drop-down menu is truncated on the Remove Training Requirement modal

Issue Description:
When removing a Training Requirement from a Service in Provider Management, the label Removal Reason is wrapping and the drop-down menu is truncated after selecting a value.

User Interface Impact: No

Prerequisite(s):

  1. There is at least one Training Service already created.
Steps to Reproduce:
  1. Login as an administrator.
  2. Navigate to the Administration Workspace.
  3. Click on Services under Provider Management in the shortcuts panel.
  4. Open one of the services listed by clicking on the name link.
  5. Click on the Training Requirements tab.
  6. Add a New Training Requirement using the New page action.
  7. Click on the Remove row-level action of the newly added training requirement.
  8. Issue: The label Removal Reason is wrapping and drop-down value is only partially visible after selection.
Resolution:
These issues have been resolved now and the label Removal Reason and the drop-down menu text are fully visible.

Technical:
The WINDOW_OPTIONS width attribute of the following UIM page has been increased from 400 to 600:
  • ProviderManagement_removeTrainingRequirementFromServiceOffering.uim
 


Verification

PO06605, WorkItem:225258 - A new outstanding verification is incorrectly created on the edit of verified evidence when the reverification mode is 'Never Reverify'

Issue Description
A new outstanding verification is incorrectly created when performing a modify of verified evidence when the reverification mode is 'Never Reverify'.

The correct behaviour should be to clone the verified verification from the active evidence record to the in-edit evidence record.

User Interface Impact: No

Prerequisite(s):

  1. A verification with a reverification mode of 'Never Reverify' must be configured against the evidence being added to the case.
Steps to Reproduce (Generic):
  1. Register a new Person.
  2. Click on the Care and Protection tab and select Cases.
  3. Using the New page action, create an integrated case.
  4. Click on the Evidence tab on the integrated case.
  5. From the Evidence Dashboard, add an evidence record that requires verification (as configured in the prerequisite(s) section above).
  6. Navigate to the Verifications list page and satisfy the verification by adding proof.
  7. Apply changes.
  8. Edit the same evidence record again.
  9. Issue: A new outstanding verification is created.
Resolution
The issue has been corrected, the verified verification is now cloned from the active evidence record to the in-edit evidence record when the mode is 'Never Reverify'.
 

PO06779, WorkItem:227254 - Editing a field not configured as a data item or dependent data item incorrectly creates a new outstanding verification when configured with a reverification mode of 'Reverify if Changed'

Issue Description
A new outstanding verification is incorrectly created when editing evidence under the following conditions:

  1. The active evidence being edited has been verified.
  2. The verification is configured with a reverification mode of 'Reverify if Changed'.
  3. On editing the evidence, neither the data item nor any of the dependent data items configured are changed.
User Interface Impact: No

Prerequisite(s):
  1. A verification must be configured for the evidence being added to the case, with the reverification mode set to 'Reverify if Changed'.
Steps to Reproduce (Generic):
  1. Login as a caseworker.
  2. Register a new Person.
  3. Create an integrated case for the person.
  4. Click on the Evidence tab on the integrated case.
  5. From the Evidence Dashboard, add an instance of the evidence configured for verification in the prerequisite(s) section above.
  6. Click on Verifications to see the list of outstanding verifications.
  7. Use the Add Proof row-level action to add the necessary documentation to satisfy the verification.
  8. Click Save on the Add Proof modal.
  9. Apply changes.
  10. Edit the same evidence record again, changing a field that is not configured as the data item or one of the dependent data items.
  11. Issue: A new outstanding verification is created even though the field changed is not configured for verification.
Resolution
This issue is now resolved. Now the verification is cloned from the active evidence record to the in-edit evidence record as part of an update as none of the verifiable data items are being modified. Changes to a field configured as a data item or as one of the dependent data items will continue to create a new outstanding verification when the reverification mode is 'Reverify if Changed'.
 

PO07957, WorkItem:240028 - Outstanding verifications, which are configured with a conditional rule set, should be removed under specific conditions, but are instead retained

Issue Description
This issue occurs where the evidence on which the verification is configured is not being edited but is being evaluated due to a change on another evidence because the configured verification makes use of a rule set that references that other evidence.

Outstanding verifications that should be removed under the following conditions are instead retained:

  1. The verification for an evidence record is configured with a conditional rule set that uses another evidence record.
  2. The verification is processed as a result of a change to this other evidence used by the conditional rules.
  3. On evaluation, the rule set returns a false result (verification not required).
User Interface Impact: No

Prerequisite(s):
  1. A verification must be configured against evidence being added to the case with a conditional rule set with logic to return a result of true (verification required) or false (verification not required) depending on the value of another evidence record on the case.
Steps to Reproduce:
  1. Login as a caseworker.
  2. Register a new Person.
  3. Click on the Care and Protection tab and select Cases.
  4. Using the New page action, create an integrated case.
  5. Click on the Evidence tab on the integrated case.
  6. From the Evidence Dashboard, add the other evidence record that will be used by the configured verification rule set such that the rule set will return a result of true when evaluated (as configured in the prerequisite(s) section above).
  7. From the Evidence Dashboard, add the evidence record configured for verification in the prerequisite(s) section above. An outstanding verification is created.
  8. Apply changes.
  9. Edit the evidence record that the conditional rules make use of so that the verification is re-processed and the result is now false.
  10. Issue: The outstanding verification is retained.
Resolution
The issue is resolved, the outstanding verification is now removed when processed as a result of a change to the other evidence record and the conditional rules return a false result.
 

PO08522, WorkItem:252460 - A new outstanding verification is incorrectly created for an already verified evidence record under specific conditions when configured with a conditional rule set

Issue Description
A new outstanding verification is incorrectly created for an already verified evidence record under the following conditions.

  1. The verification is configured with a conditional rule set.
  2. On execution of the rules the verification result is true (verification required).
  3. The verification is processed as a result of a change to another evidence record that the configured rules make use of.
User Interface Impact: No

Prerequisite(s):
  1. A verification must be configured against evidence being added to the case with a conditional rule set with logic to return a result of true (verification required) or false (verification not required) depending on the value of another evidence record on the case.
Steps to Reproduce (Generic):
  1. Login as a caseworker.
  2. Register a new Person.
  3. Click on the Care and Protection tab and select Cases.
  4. Using the New page action, create an integrated case.
  5. Click on the Evidence tab on the integrated case.
  6. From the Evidence Dashboard, add the other evidence record that will be used by the configured verification rule set such that the rule set will return a result of true when evaluated, as configured in the prerequisite(s) section above.
  7. From the Evidence Dashboard, add the evidence record configured for verification in the prerequisite(s) section above resulting in an outstanding verification.
  8. Click on Verifications to see the list of outstanding verifications.
  9. Use the Add Proof row-level action to add the necessary documentation to satisfy the verification.
  10. Click Save on the Add Proof modal.
  11. Apply changes.
  12. Edit the other evidence record that the conditional rules make use of so that the verification is re-processed and the result is now false.
  13. Edit the same evidence record again so that the verification is re-processed and the result is now true.
  14. Issue: A new outstanding verification is created for the already verified evidence record.
Resolution
This issue is now resolved. A new outstanding verification is no longer created where the existing evidence record has already been verified.
 

PO08569, WorkItem:256070 - Outstanding verification on active evidence is not being retained on edit

Issue Description:
The following actions should occur when an active evidence record with an outstanding verification is corrected by the caseworker. The reverification mode is ‘Reverify if Changed’ and the correction made does not change the configured data items / dependent data items.

  1. On edit, the existing outstanding verification is cloned to the corrected evidence record.
  2. On apply changes, the existing outstanding verification associated with superseded evidence is removed.
Currently, only the second action is occurring which results in no outstanding verification being associated with the corrected evidence record.

User Interface Impact: No

Prerequisite(s):
  1. Login as an administrator.
  2. Configure a new Verification for any sample Income evidence type with a mode of 'reverify if changed' and data item set to the amount attribute.
  3. Apply the Verification Requirement to any integrated case the evidence type is configured against.
Steps to Reproduce (Generic):
  1. Login as a caseworker.
  2. Register a Person.
  3. Create a new integrated case of the type the referenced in step 3 above.
  4. Add new Income evidence and enter an amount - an outstanding verification is created.
  5. Apply changes.
  6. Edit the Income evidence, modifying Change Reason to Correction.
  7. Click Save.
  8. Apply changes.
  9. Issue: The outstanding verification for the Income evidence has been removed.
Resolution:
When the active evidence is edited, existing outstanding verification is cloned to the in-edit record. At step 10 there will be two outstanding verifications, one against the active evidence record and one against the in-edit evidence record. When the evidence change is applied, the outstanding verification for the superseded evidence is removed leaving the cloned outstanding verification against the active evidence.


Supervisor Workspace

PO04278, WorkItem:97703 - Assessment cases with a status of Inactive throw an unhandled server exception

Issue Description:
When assessments are created within an outcome plan, an Assessment case is created to hold the details of the assessment. In some scenarios when a user is creating an assessment and exits the assessment prior to reaching the pages on which questions are answered, the status of the Assessment case is set to 'Inactive'. These Assessment cases are currently displayed within the Supervisor Workspace and when a supervisor attempts to view an Assessment case that has a status of 'Inactive' an unhandled exception error occurs.

User Interface Impact: No

Related WorkItem(s): 249764, 123180

Prerequisite(s):

  1. An Outcome Plan is configured against an integrated case.
  2. An Assessment is associated with the Outcome Plan.
Steps to Reproduce:
  1. Login as a caseworker.
  2. Register a new Person.
  3. Create an instance of the integrated case referenced above.
  4. Create an Outcome Plan on the integrated case.
  5. Open the Assessments & Factors tab on the Outcome Plan.
  6. Create an Assessment and exit it on the role select screen.
  7. Login as a supervisor.
  8. Select User Workload and search for the caseworker.
  9. Click on the Inactive Assessment case.
  10. Click on the case reference link.
  11. Issue: An unhandled server exception occurs.
Resolution:
Assessment cases no longer display on the User Workload page for the user as per the changes made in WorkItem: 123180; the details of this fix can be found here https://www.ibm.com/support/pages/ibm-c%C3%BAram-social-program-management-6201. This related issue introduced filtering of case types to only include those relevant to a supervisor and has excluded Assessment cases out-of-the-box.
 

PO08633, WorkItem:255229 - Readmultimax parameter is not honored in Reassign Cases modal from within a user workspace when 'List all cases assigned to the user' is unchecked

Issue Description:
When reassigning cases using the Reassign Cases modal from within a user workspace with 'List all cases assigned to the user' setting unchecked, the readmultimax parameter that determines how many values can be returned in a list of records, is not honored and all the cases are displayed. In a production environment, this can result in a large number of search results returned, which in turn can lead to performance issues and in some cases an unhandled server exception.

User Interface Impact: No

Prerequisite(s):

  1. Login as a system administrator.
  2. Navigate to the System Configurations workspace tab.
  3. Select Property Administration under Application Data in the shortcuts panel.
  4. Search for the property 'curam.db.readmultimax'.
  5. Edit the property and update its value to 3.
  6. Click on the Publish page action to publish the changes.
Steps to Reproduce:
  1. Login as a caseworker.
  2. Register a new Person.
  3. Click on the Care and Protection tab and select Cases.
  4. Using the New page action, create an integrated case.
  5. Repeat step 4 to create an additional 4 integrated cases.
  6. Login as a supervisor.
  7. Navigate to My Users under Users in the shortcuts panel.
  8. Select the caseworker to open the user workspace.
  9. Click on the Cases tab.
  10. Click on the Reassign Cases page action, which will open up the Reassign Cases modal.
  11. Ensure that 'List all cases assigned to the user' is unchecked.
  12. Check the 'Open' Status and click Search.
  13. Issue: The search operation ignores the readmultimax value configured in the prerequisite(s) above and displays all the created cases.
Resolution:
When reassigning cases using the Reassign Cases modal from within a user workspace with 'List all cases assigned to the user' unchecked, the readmultimax parameter is now honored and the list shows the maximum number of records defined by the property 'curam.db.readmultimax'.
 

WorkItem:257758 - An exception is thrown when accessing the Cases tab when navigating from the Assigned Workload Pod

Issue Description:
An exception occurs on the Cases tab of the User Workspace when navigating to it from the Assigned Workload Pod.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a supervisor.
  2. On the home page, select a username on the Assigned Workload Pod to open the user workspace.
  3. Select the Cases tab in the user workspace.
  4. Issue: An application error is displayed on the page stating that 'The field 'key$key$orgObjectKey' contains a code value 'null' that is not a recognized code in the 'OrgObjectType' code-table' for the user's locale.
Resolution:
This issue has been resolved. The Assigned Workload Pod has been updated to include an additional parameter on the username hyperlink.


Universal Access

Administration

WorkItem:254459 - APIs to support the Citizen Verification Document Upload feature on an IBM Universal Access Responsive Web Application

Citizen Verification Document Upload functionality is now available that allows a citizen to upload documents for verification purposes through the IBM Universal Access Responsive Web Application.

The following APIs have been provided to support this new feature. They enable the key business functions that form part of the functionality, including the ability for a citizen to upload and view their documents, and to view the verification requirements that are related to the documents that need to be uploaded.

Note that the APIs do not cover the entire set of use cases that may be required to fully implement document uploading within the Social Program Management (SPM) application.



The following APIs are available for use:

Document Service

POST /v1/dbs/files
Uploads a file and returns the URL for the file.

GET /v1/dbs/files/{fileId}
Retrieves a specified file.


DELETE /v1/dbs/files/{fileId}
Deletes a specified file. This API is not currently used by the IBM Universal Access Responsive Web Application.


Verifications

POST /v1/ua/verifications/link_file
Links an existing file on the system to a specified verification. A link record is created to link the file and the verification.

DELETE /v1/ua/verifications/{verificationId} /file_links /{linkId}
Removes a link between a file and a verification without deleting the file.

GET /v1/ua/verifications
Returns details for all verifications for a specified person or case.

GET /v1/ua/verifications/{verificationId}
Returns details for a specified verification.



For full specification details for the new Document Service and Verification Service APIs, please see the IBM Cúram Social Program Management Swagger specification, which is available from a running IBM Cúram Social Program Management instance at http:<hostname>:<port>/Rest/api/definitions/v1.


Administration

WorkItem:246931 - The Flex Widget for the Universal Access Rich Text Editor is deprecated

The Rich Text Editor in Universal Access is now deprecated.

This Flex Widget is being deprecated as it is no longer used by any UIM pages. All instances of the Flex version of the Rich Text Editor were already replaced with the CKEditor JavaScript Rich Text Editor.

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


Intelligent Evidence Gathering

Player

PO08491, WorkItem:255571 - Modal dialog boxes stop working randomly

Issue Description:
When using Internet Explorer 11 to process an application, an issue occurs when the modal is closed. When the user is presented with the Save Application modal, chooses to Save and then clicks Next, a blank modal is displayed.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a caseworker using the Internet Explorer 11 browser.
  2. Register a Person and create a new Application.
  3. Complete half of the application and click Close.
  4. Select the first option 'Save the application and come back to work on it later.' and click Next.
  5. Issue: A blank modal is displayed.
Resolution:
This issue has been resolved by updating the JavaScript for closing modals, the Save Application modal is now correctly closed after selecting Next.
 

PO08696, WorkItem:256702 - IBM Universal Access Responsive Web Application: Changing an IEG loop control question response does not work when the user navigates back through a script

Issue Description:
Changing an IEG loop control question response does not work when the user navigates back through a script.

User Interface Impact: No

Steps to Reproduce:

  1. Update an IEG script to have multiple records added by using a loop.
  2. In the Universal Access Responsive Web Application, apply for a benefit using that IEG script.
  3. Navigate through the IEG script and add more than two loop items.
  4. Use the browser Back button to navigate back through the IEG script to the first loop item.
  5. Update the loop control question response to indicate that this is the last item in the loop.
  6. Issue: Observe that second loop item is still displayed on the next page even though the first item should the last item in the loop.
Resolution:
When a user navigates back through a script, IEG loop control questions have been modified to be read-only and an informational message is displayed to the user that explains how a user can add or delete the information that was previously entered for the loop items.
 


Player

PO08674, WorkItem:256106 - An application error is displayed on an assessment page when pressing Enter to submit a form with focus on a single text field using Internet Explorer 11

Issue Description:
When an assessment question page contains one question displayed as a text field, pressing Enter to submit the form with focus on this text field, results in an application error and the assessment page has to be restarted. If the user selects the Next button on the assessment page then this issue is not reproducible. This scenario is only displayed when using Internet Explorer 11.

User Interface Impact: No

Steps to Reproduce:

  1. Login as an administrator using the Internet Explorer 11 browser.
  2. Navigate to the shortcuts menu within the Administration Workspace.
  3. Select Scripts under Intelligent Evidence Gathering.
  4. Enter 'IEG Sample Script' in the Search Criteria and select Search.
  5. From the Search Results, Run the 'IEG Sample Script' script.
  6. Select IEGSample as the Schema Name and select Run Script.
  7. The About You page opens in a new tab.
  8. Fill out the details in the About You page and select Next.
  9. The Information About You page opens, select Next.
  10. The Household Details page opens.
  11. With focus on the 'How many other people are in your household?' field, press the Enter key.
  12. Issue: An application error is displayed on the Household Details page.
Resolution:
This issue has been resolved and now when the user presses the Enter Key with focus on a single text field in an assessment page, no application error is displayed and the user can submit the form.

Technical:
The issue was resolved by updating the underlying infrastructure javascript which is executed when an assessment form is submitted.
 


Evidence Broker

PO08655, WorkItem:210369 - Verifications do not share when sharing evidence which is logically equivalent

Issue Description:
Logically Equivalent sharing is configured between two evidence types, with verifications configured to share with the evidence. After a caseworker verifies evidence of this type, the evidence shares to the target case as expected but the verifications do not share with the evidence.

User Interface Impact: No

Prerequisite(s):

  1. A logically equivalent sharing configuration exists from Disability on an Income Support integrated case to Disability on an Insurance Affordability integrated case with the sharing rules uploaded in an appropriate XML file. Also, Trusted Source is set to Yes and Share Verifications is set to Always.
  2. Verifications are configured against both types of Disability evidence.
  3. Both verifications are satisfied with the same Verification Items.
Steps to Reproduce:
  1. Login as an Income Support caseworker.
  2. Register a person and create an Income Support integrated case.
  3. Create Disability evidence and add proof to satisfy the outstanding verification.
  4. Apply Changes.
  5. Login as an Insurance Affordability caseworker.
  6. Submit an application for the previously created person.
  7. Authorize the application.
  8. Navigate to the Verifications tab on the newly created Insurance Affordability integrated case.
  9. Issue: The Disability evidence has been shared to the case, but it has an outstanding verification against it.
Resolution:
This issue has been resolved by updating logic to correctly identify when different evidence types use the same Verification Items to satisfy outstanding verifications on them.

Technical:
The logic responsible for sharing verifications checked to see if the same Verifiable Data Item was configured against the source and target evidence. If they matched the verification would be shared. As verifications are configured separately against each evidence type, for logically equivalent sharing, the source verifiable data item and target verifiable data item would never match and the proof would never be shared.

The logic has been extended to now check if the Verification Item provided on the source evidence is configured against the target. If it is, then the proof will be shared to the target case to satisfy the outstanding verification.
 

PO08192, WorkItem:245056 - SSN Details shared to Person level and actioned there is incorrectly shared back to the source Insurance Affordability integrated case

Issue Description:
An issue exists when logically equivalent evidence sharing is set up between SSN Details on Insurance Affordability and Identifications at the Person level. The reported problem occurred on a system where the evidence was created before the new Evidence Broker was released in IBM Cúram Social Program Management (SPM) 7.0.2. In this instance, the Identifications evidence record was created during the authorization of a submitted Insurance Affordability application where the applicant applied for an SSN. The active Identifications evidence was created with a Type of Social Security Number and a blank ID Reference. Just to note, this is something that is now prevented with the new Evidence Broker via 'share when' rules in the logically equivalent XML.

After the upgrade to IBM Cúram SPM 7.0.2, with the new Evidence Broker turned on, the SSN Details on the Insurance Affordability case was updated to provide an SSN for the client. After activation on the Insurance Affordability integrated case, the SSN was brokered to Person level evidence. After performing an Update with Incoming on the Person, to update the existing Identifications evidence of type Social Security Number with the incoming record, the evidence was unexpectedly shared back to the Insurance Affordability integrated case.

User Interface Impact: No

Prerequisite(s):

  1. Login as an administrator and navigate to Evidence Sharing under Rules and Evidence in the shortcuts panel.
  2. Locate the Person to Insurance Affordability (IC) evidence sharing configuration.
  3. Use the toggle to drill down into the configurations and select the Logically Equivalent tab.
  4. Use the row-level Edit action on the Identifications to SSN Details sharing configuration to update the Trusted Source to No.
  5. Locate the Insurance Affordability (IC) to Person evidence sharing configuration.
  6. Use the toggle to drill down into the configurations and select the Logically Equivalent tab.
  7. Use the row-level Edit action on the SSN Details to Identifications sharing configuration to update the Trusted Source to No.
Steps to Reproduce:
  1. Login as an Insurance Affordability caseworker.
  2. Register a new Person.
  3. Click on the Care and Protection tab and select Applications.
  4. Use the New Application Form page action to create an Insurance Affordability application with an application date of 1/1/2020.
  5. Specify the minimum evidence in the application, including an SSN for the applicant, and submit the application.
  6. Refresh the Applications list page and click on the Reference hyperlink to open the application.
  7. Use the tab menu to authorize the application. This will create an Insurance Affordability integrated case.
To correctly replicate the reported issue, the following technical steps are required:

Run the following SQL statements to remove the SSN from the Person level evidence:
  • To find the ConcernRoleID of the applicant: "Select ConcernRoleID From ConcernRole Where PrimaryAlternateID = <PrimaryAlternateID>"
  • To find the Person CaseID: "Select CaseID From CaseHeader Where ConcernRoleID=<ConcernRoleID> And CaseTypeCode = 'CT2001'"
  • To find the RelatedIDs for Identifications evidence based on the Person CaseID, as there could be more than one: "Select RelatedID From EvidenceDescriptor Where CaseID = <CaseID> And EvidenceType = 'PDC0000259'"
  • To find the AttributeID based on the SSN entered in the application, run the following SQL. This will only return a record for one of the RelatedIDs above: "Select AttributeID From DynamicEvidenceDataAttribute Where EvidenceID=<RelatedID> And Name = 'alternateID' AND Value = <Original SSN>"
  • To delete the SSN, use the AttributeID associated with the Social Security Number: "Update DynamicEvidenceDataAttribute Set Value=NULL Where AttributeID=<AttributeID>"
  • To remove any history of evidence sharing with the new Evidence Broker: "Delete From AESMatchedEvidence"
Once these steps are complete, it's now possible to continue with the business steps.
  1. Update the SSN Details on the Insurance Affordability integrated case as follows:
    • SSN = ''
    • SSN Status = 'Applied for SSN'
  2. Click Save.
  3. Apply changes.
  4. Update the SSN Details on the Insurance Affordability integrated case again with the following details:
    • Effective Date = 02/02/2020
    • SSN = <Original Value>
    • SSN Status = ''
  5. Click Save.
  6. Apply changes.
  7. Navigate to the Person case for the applicant.
  8. Click on the Evidence tab and select Incoming Evidence.
  9. Use the arrow toggle at the top of the Existing Evidence page to select the Identifications record of type Social Security Number.
  10. Use the Update with Incoming action to update the Identifications record with the incoming evidence.
  11. Issue: The evidence is unexpectedly shared back to the Insurance Affordability integrated case.
Resolution:
This issue is now resolved and the sharing between Identifications and SSN Details evidence, and vice versa, works as expected. In the above scenario, SSN Details evidence is no longer shared back unexpectedly to the Insurance Affordability integrated case.

Technical:
A number of configuration issues were identified as part of investigating this business scenario. These are outlined here:

1. Evidence Maintenance Patterns
The evidence maintenance patterns for both PDC Identifications and SSN Details evidence, which are stored on the EvidenceTypeDef entity, are incorrect out-of-the-box. They are both set to EMP38000, which is 'Multiple Over-Time'. They should, in fact, be set as follows:
  • SSN Details (DET0026031) - Single Over-Time - the code for which is EMP38001
  • PDC Identification (PDC0000259) - Multiple - the code for which is EMP38002
2. Sharing XML
The XML containing the rules for sharing from Identifications to SSN Details contains a ShareWhen rule that checks if "PDC0000259.altIDType" is equal to "CA1". This should be done in conjunction, that is, using an AND, on a check that "PDC0000259.alternateID" is not blank. The above issues have been addressed as part of this fix and are necessary for the sharing to work correctly.

The locations of the files containing the updated configurations are as follows:
  • ../EJBServer/components/PDC/data/initial/EVIDENCETYPEDEF.dmx
  • ../EJBServer/components/HCR/data/initial/EVIDENCETYPEDEF.dmx
  • ../EJBServer/components/HCR/data/initial/clob/EVIDENCEBROKERCONFIG_5.xml
  • ../EJBServer/components/HCR/data/initial/clob/EVIDENCEBROKERCONFIG_7.xml
 

WorkItem:256535 - The sharing of Person Relationships evidence from an integrated case back to the respective Person level evidence fails

Issue Description:
The sharing of PDC Relationships evidence from an integrated case back to the respective Person level evidence fails. The server logs indicate that a null pointer exception is thrown which is preventing the process from completing successfully.

User Interface Impact: No

Prerequisite(s):

  1. Login as an administrator.
  2. Click on the Administration Workspace tab.
  3. Expand the shortcuts panel and click on Integrated Cases under Case.
  4. Click on any of the integrated cases.
  5. Click on the Evidence tab to see the evidence types configured against the integrated case.
  6. If Relationships evidence is not listed, click on the Add Evidence page action.
  7. Select Relationships in the Evidence Type drop-down and click Save.
  8. Click on Evidence Sharing under Rules and Evidence in the shortcuts panel.
  9. Select the New Sharing Configurations tab menu option.
  10. On the Select Source and Target page, select the integrated case from above as the source and Person as the target.
  11. Click Next.
  12. On the Add Identical Evidence page set Trusted Source to Yes, Share Verifications to Never, and select Relationships evidence.
  13. Click Save and Exit.
Steps to Reproduce (Generic):
  1. Login as a caseworker.
  2. Register a new Person (first person).
  3. Register another new Person (second person).
  4. Click on the Care and Protection tab for the first person and select Cases.
  5. Click on the New page action to create a new case.
  6. Select the integrated case configured for sharing in the Type drop-down and click Save.
  7. Click on the Participants tab and select Case Members.
  8. Use the New page action to add a new member.
  9. Search for the second person in the Name field of the New Member modal and click Save.
  10. On the integrated case click on the Evidence tab.
  11. On the Evidence Dashboard page select the New Evidence page action.
  12. Select All in the Category drop-down to list all evidence types configured on the integrated case. Relationships should be listed.
  13. Use the Add row-level action on the Relationships evidence type to add evidence of that type.
  14. Select the first person in the Case Participant drop-down, second person the Related Participant drop-down, and select a relationship type in the Type drop-down.
  15. Click Save.
  16. Apply changes.
  17. Issue: When examining the Person level evidences to check if the Relationships evidence has been shared, no Relationships evidence is visible. An examination of the server logs shows that a null pointer exception was thrown preventing the completion of the evidence sharing.
Resolution:
Within the Evidence Broker, there is specific logic for handling the sharing of Relationships evidence. It was found that there was an assumption in the logic that the evidence sharing configuration was logically equivalent. The system attempts to look up and process the sharing rules but, as no rules are configured on the system, a null pointer exception is thrown preventing the evidence sharing transaction from completing. The logic has been updated to handle the identical evidence sharing nature of Relationships evidence, thereby resulting in the successful sharing of Relationships evidence in the scenario outlined here.
 

WorkItem:256598 - Evidence with multiple successions brokered to an application case are inserted as separate records rather than in the same succession set

Issue Description:
When a new application case is created and evidence is pulled onto it by the Evidence Broker, evidence types with multiple successions are inserted as separate records rather than as part of the same succession set.

User Interface Impact: No

Prerequisite(s):

  1. Login as an administrator.
  2. Click on the Administration Workspace tab.
  3. Click on Evidence Sharing under Rules and Sharing in the shortcuts panel.
  4. Click on the New Sharing Configuration tab menu option.
  5. Configure evidence sharing between an application case and its associated integrated case, with Trusted Source set to Yes.
Steps to Reproduce:
  1. Login as a caseworker.
  2. Register a new Person and create an integrated case.
  3. Add evidence that was configured in the Prerequisites and apply changes.
  4. Edit the evidence record added with an effective date of change so that a new succession will be created.
  5. Apply changes.
  6. Create a new application for the same person.
  7. Fill out the minimum required details on the script without adding in the same evidence as above and submit.
  8. Issue: The evidence that was edited to create a succession above is shared from the integrated case to the application case but appears as two separate records on the application case and is not in the same succession set.
Resolution:
When a new application case is created and evidence is pulled onto it by the Evidence Broker, evidence types with multiple successions are now inserted as part of the same succession set.
 


Financial Management

PO08671, WorkItem:256000 - Unable to set-up a new Applied Deduction on a liability case where the liability has been written-off and subsequently reversed

Issue Description:
It is not possible to set-up a new Applied Deduction against a liability case where the liability has been written-off and subsequently reversed. When a write-off is reversed on a liability case, the outstanding amount increases and it should be possible to set-up a deduction against the liability to offset whatever is outstanding on the case.

User Interface Impact: No

Steps to Reproduce (Generic):

  1. Register a new Person.
  2. Create an integrated case for the Person.
  3. Add a product to the integrated case, payable weekly by check.
  4. Add the necessary evidence to make the product eligible.
  5. Submit, approve and activate the case.
  6. Click on the Financials tab and select Transactions.
  7. Issue financials using the page action.
  8. Modify and activate the evidence in order to generate an overpayment.
  9. Navigate to the overpayment case.
  10. Submit, approve and activate the case.
  11. Click on the Financial tab and select Transactions.
  12. Issue financials using the page action. This will generate the liability.
  13. Drill down into the detail of the liability using the toggle.
  14. Navigate to the Liability Items and select the Write Off row-level action.
  15. In the Create Write Off modal, specify the full liability amount in the Amount field.
  16. Click Save. A new Liability Write Off entry now appears on the Transactions page.
  17. Select the Reverse row-level action on the Liability Write Off.
  18. On the Reverse Instruction page, select any Reason and click Save.
  19. Navigate back to the product delivery case.
  20. Click on the Financials tab and select Deductions.
  21. Select the New Applied Deduction (Fixed) page-level action.
  22. On the New Applied Fixed Deduction page, select the participant in the Case Member drop-down.
  23. Click Search.
  24. Issue: No liabilities are returned in the Existing Liabilities list.
Resolution:
The deductions logic has been updated so that reversal instructions are now considered when determining the outstanding amount on a liability case when setting up a deduction on a product delivery case.
 


Identity Intelligence

WorkItem:258042 - Remove an exception from the IIWebServiceAuthentication interface that was not thrown

Issue Description:
The curam.programintegrity.impl.IIWebServiceAuthentication interface is responsible for adding extra authorization and authentication settings to the Identity Insight Web Service client used by Program Integrity.

The method signature of setIIResolverWSAuthentication() has been updated as part of a refactoring exercise.

User Interface Impact:No

Steps to Reproduce:

  • Not applicable.
Resolution:
The method signature of setIIResolverWSAuthentication() has been updated to no longer throw a javax.xml.rpc.ServiceException. This is because the exception was not thrown as part of the implementation.

Since setIIResolverWSAuthentication() no longer throws a javax.xml.rpc.ServiceException, if there is a custom implementation of this method the signature must be updated.
 


Solutions

Income Support
Child Welfare

Income Support

PO06514, WorkItem:170005 - Changing address field 'street 1' does not impact Household Composition

Issue Description:
When address field ‘street 1’ is edited for a person, who is not the primary applicant on a Streamlined Medicaid product delivery, the case does not reassess and remove the person from the financial unit/household size.

User Interface Impact: No

Steps to Reproduce:

  1. Login as an Insurance Affordability caseworker.
  2. Create an Insurance Affordability application for Mom, Child 1 and Child 2.
  3. All members are non-filers and live at the same address.
  4. Add monthly income of $850 for Mom.
  5. Submit the application.
  6. Authorize the application to create an Insurance Affordability integrated case, with all three members being eligible for Streamlined Medicaid.
  7. Financial unit/household size for each member is 3 (Mom, Child 1 and Child 2).
  8. Change address field ‘street 1’ for Child 1 and apply changes.
  9. No reassessment of the Streamlined Medicaid product delivery occurs.
  10. Issue: Reassessment of the Streamlined Medicaid product delivery is not triggered when the address field ‘street 1’ is changed for Child 1 and Child 1 is not removed from the financial unit/household size of the other two members (Mom, Child 2).
Resolution:
This issue is now resolved. A change to 'street 1' of a person’s address causes the Streamlined Medicaid product delivery to reassess and the financial unit/household size is adjusted based on the applicable rules. In the scenario reported, the child is removed from the financial unit/household size of the other two members and a separate financial unit/household size is created for the child as they are no longer living at the same address as the family.
 

PO08133, WorkItem:243673 - 'Participant' is misspelled as 'Paticipant' and 'Underemployed' is misspelled as 'Underrmployed' on the New Member Relationship modal on an Insurance Affordability integrated case

Issue Description:
When creating a new Member Relationship evidence for an Insurance Affordability integrated case, 'Participant' is misspelled as 'Paticipant' and 'Underemployed' is misspelled as 'Underrmployed' on the New Member Relationship modal. All the other labels in the New Member Relationship modal are displayed correctly.

User Interface Impact: No

Steps to Reproduce:

  1. Login as an Insurance Affordability caseworker.
  2. Select Register Person and Create Case from the Shortcuts menu.
  3. Register a new Person and create a new case of the type Insurance Affordability.
  4. Navigate to Active Evidence on the Evidence tab.
  5. Create new evidence of type Member Relationship.
  6. Issue: The 'Related Paticipant' cluster title should be spelled 'Related Participant' and 'Underrmployed Or Unemployed' under the Relationship Details cluster should be spelled 'Underemployed Or Unemployed'.
Resolution:
This issue has been resolved by correcting the spelling mistakes in the property values for Related Participant and Underemployed Or Unemployed.

Technical:
The following files have been updated as part of this work:
  • ../EJBServer/components/HCR/data/initial/blob/DynEvd_MemberRelationship_20110711.properties
  • ../EJBServer/components/HCR/data/initial/blob/DynEvd_MemberRelationship_20130801.properties
  • ../EJBServer/components/HCR/data/initial/blob/DynEvd_MemberRelationship_20140910.properties
  • ../EJBServer/components/ISProduct/data/initial/blob/DynEvd_DomesticRelationship_20120214.properties
 

WorkItem:255818 - Some attributes are displaying incorrectly for an Insurance Affordability Application PDF document

Issue Description:
When an Insurance Affordability Application PDF document is generated from within the Citizen Portal, incorrect labels are displayed for some of the fields. Also, the document includes the display of some technical attributes that should not be included.

User Interface Impact: No

Steps to Reproduce:

  1. Open the Citizen Portal.
  2. Select to apply for assistance, select to create an account to register in the Citizen Portal, and proceed to create an Insurance Affordability application.
  3. Fill out the required fields and submit the application.
  4. Navigate to the Home page in the Citizen Portal.
  5. Select to view the Health Care Application PDF document.
  6. Issue: The PDF document contains fields that have incorrect labels as well as technical attributes that should not be displayed.
Resolution:
Incorrect labels have been addressed and technical attributes have been marked as hidden attributes in the out-of-the-box properties file so that they will not be displayed in the PDF document.

Technical:
The following changes have been made to the file ../EJBServer/components/HCR/data/initial/blob/prop/HealthCarePortalDataStoreIEGPDFProps.properties:
  • Person.displaySSN.hidden=true
  • Person.isPersonCocAdded.hidden=true
  • Person.livesWithExternalParent=Lives with external parent
  • Person.anyDeductableItem=Any deductible item
  • Person.isAddedAsSecondPerson.hidden=true
  • MailingAddress.addressEvID.hidden=true
  • Pregnancy.pregnancyApproxStart=Approximate start date of pregnancy
  • IncomeItem.manuallyVerified.hidden=true
Additionally, any attribute can be hidden by following the pattern: entity.attributeName.hidden=true.
 


Child Welfare

PO04464, WorkItem:116549 - When an Intake's category is changed to Information and Referral from any other category, an application error is thrown when updating requester details

Issue Description:
An application error is thrown on the Edit Requester page when updating participant details after the category of an Intake is changed to 'Information and Referral' from any other category.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a Child Welfare intake worker.
  2. Use the New Intake quick link on the home page to create a new intake.
  3. Set the Category to Child Protection Services and click Save.
  4. Click on the Participants tab and select the New Participant page action.
  5. Provide the necessary details to register a new participant.
  6. Click on the Basics tab and select the Edit page action.
  7. On the Edit Basics page, select 'Information and Referral' as the Category and 'Information Provided Only' as the Type.
  8. Click Save.
  9. Click on the Requester tab and select the Edit Requester page action.
  10. Modify the name on the Edit Requester modal and click Save.
  11. Issue: An unhandled server exception is thrown.
Resolution:
This issue is now resolved and the functionality now facilitates updating the intake category to and from 'Informational and Referral'.

PO07243, WorkItem:199838 - Intake start date is displayed incorrectly for Intakes displayed on the Screening page for a participant

Issue Description:
The Screening page located under the Care and Protection tab for a participant displays a list of Intake cases related to the participant. For the Intake cases that are listed on this page, the date displayed for the Intake Start Date is incorrectly displayed as the current date rather than the start date entered by the Intake worker.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a Child Welfare intake worker.
  2. Create a new Child Protection Services intake and set the start date to a date in the past.
  3. Click on the Participants tab and use the New Participant page action to create a new Intake participant.
  4. Click on the newly created participant's name hyperlink and navigate to the participant home page.
  5. Click on the Care and Protection tab and select Screenings.
  6. Issue: The Screenings page displays the intake start date as the current date.
Resolution:
The Screenings page now correctly displays the start date that was entered when the user created the intake.
 

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

PO08177, WorkItem:244772 - Search Reporter by address doesn't work when the default locale is set as 'en'

Issue Description:
In Child Welfare, a reporter can be added to the intake using the Capture Reporter wizard. In the Reporter Search step of the wizard, the reporter name and address entered by the user is matched against existing Person records and the user may subsequently choose to select the Person displayed in the search results and proceed to capture Agency details, if needed.

The results displayed in the Reporter Search are incorrect for the default locale of ‘en’ because the address values are not taken into consideration. The out-of-the-box implementation only caters to the en_US and en_UK locales and it is not easy for customers to override this default behaviour as there is no compliant way for them to provide their own custom implementation.

User Interface Impact: No

Prerequisite(s):

  1. Login as an administrator.
  2. Search for a Child Welfare intake worker and open it in a new tab.
  3. Select the Edit page action on the user home page.
  4. Set the User Default Locale to English and click Save.
Steps to Reproduce:
  1. Login as a Child Welfare intake worker.
  2. Register three persons with the same name and different addresses.
  3. Select New Intake.
  4. Set the Category to Child Protection Services and click Save.
  5. Click on the Participants tab and select New Reporter from the page action menu.
  6. On the Capture Reporter wizard, on the Details page, select Type as Voluntary and Roles as Child.
  7. On the Reporter page, enter the same participant name used above, enter the address and click Next.
  8. Issue: On the Reporter Search page, all three person records registered earlier are displayed matched by name. The address aspect of the Reporter Search does not work. If it did, then only the record matching on the specified address would be returned.
Resolution:
Searching by the 'en' locale is now supported out-of-the-box and customers will now be able to override the out-of-the-box behaviour in a compliant manner.

Technical:
The Reporter Search functionality previously lived in an internal API, SearchAllParticipantRoles.searchReporter(), which meant that it wasn't possible to alter its behavior in a compliant way. As users can run in any locale and customers can create their own custom address formats, it's not possible to provide an exhaustive address search out-of-the-box.

To facilitate compliant customization of the Reporter Search functionality, a new external ReporterSearch interface has been introduced into the product. A default implementation of the interface is also provided. The default implementation works in the following manner:
  • If the user is running in the en_US locale, the address part of the search SQL is built in accordance with the US address format
  • If the user is running in the en_GB locale, the address part of the search SQL is built in accordance with the UK address format
  • If the user is running in the en_DE locale, the address part of the search SQL is built in accordance with the DE address format
This behavior provides backward compatibility to how the search previously worked. Additionally, if the user runs in any other locale, including the default locale of 'en', the value of the 'curam.address.addressLayout' environment variable is looked up. If this is one of US, UK or DE, the search SQL is built in accordance with the respective format.

If a customer's requirements are not met by the default implementation, a custom version of the interface can be implemented to override the default behavior.
 

WorkItem:249700 - New Relationship dialog lists Collateral participants with an invalid age

Issue Description:
IWhen a Collateral is created within an Intake and not matched to an existing person during the creation process, the information stored for the Collateral will not include age information. In this scenario when a new relationship is being created, the New Relationship dialog lists the Collateral participant with an invalid age value.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a Child Welfare intake worker.
  2. From the Intakes workspace tab, expand the shortcuts section and select New Intake.
  3. Set the Category to Child Protection Services and click Save.
  4. From the Participants tab select New Participant from the page action menu.
  5. Add a child participant with a Date of Birth of 1/1/2015 and a Role of Alleged Victim.
  6. Add an adult participant with Date of Birth of 1/1/1985 and a Role as Alleged Maltreater.
  7. From the Participants list page select New Collateral from the page action menu.
  8. Add a collateral participant to the intake that does not match to an existing person.
  9. From the Relationships tab select New from the page action menu.
  10. Issue: On the New Relationship page, the collateral participant is displayed with the wrong age in the 'Participant' and 'of' fields.
Resolution:
This issue is now resolved by displaying Age Not Recorded for Collateral participants with no date of birth recorded. For Collateral participants with a date of birth, their correct age is displayed in the 'Participant' and 'of' fields of the New Relationship dialog.

Technical:
The label width of the clusters within the New Relationship dialog was reduced from 30px to 28px to maximize the space available for the field containing the participant name and age details. The UIM updated is CCSIntake_addRelationships.uim.
 

PO08552, WorkItem:253411 - When a non-primary participant is removed from an Intake or Investigation the Participant Data Case of the participant is closed

Issue Description:
A participant added to an Intake or Investigation case that is not indicated as the primary participant within the Intake or Investigation case may be removed. When a user removes a participant from an Intake or Investigation case and then attempts to view evidence for the participant, the evidence tab displays the following application error message: 'No Active participant data case exists for this concern role'.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a Child Welfare intake worker.
  2. Click on the Intakes workspace tab.
  3. Select Person under Registration in the shortcuts panel and register a new Person.
  4. Select New Intake under Intakes in the shortcuts panel.
  5. Select Child Protective Services as the Category and click Save.
  6. Click on the Participants tab of the Intake Assistant.
  7. Use the New Participant page action to add a new child with a Role of Alleged Victim.
  8. Again, use the New Participant page action to add a new person with a Role of Alleged Maltreater, specifying the same First Name and Last Name as the person registered above.
  9. Click Next.
  10. Select the registered person as an Exact match on the Potential Matches page of the wizard and click Finish.
  11. Delete the Alleged Maltreater non-primary participant from the Participants list page on the Intake Assistant.
  12. Search for the person who was deleted from the Intake.
  13. Click on the Evidence tab of the Person case.
  14. Issue: The following error message is displayed: 'No Active participant data case exists for this concern role'.
Resolution:
The issue has been resolved. Now when the user accesses the evidence tab of a non-primary participant who has been removed from an Intake or Investigation case, the evidence tab is available and displays the person's evidence.
 

PO08593, WorkItem:254562 - Child Welfare Case Search does not return records when dates are used in the search

Issue Description:
The Child Welfare Case Search provides the ability to search by criteria such a primary client, date, category, and type. When values are specified for the From Date and To Date search fields on the Child Welfare Case Search page, no records are returned.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a Child Welfare caseworker.
  2. Register a new Person.
  3. Create an Ongoing Case.
  4. Navigate to the Child Welfare Case Search page and specify the following search details:
    • From Date: Today
    • To Date: Today
  5. Click Search.
  6. Issue: The search does not return any records.
Resolution:
The issue has been fixed by updating the database query. Now when values are specified for the From Date and To Date on the Child Welfare Case Search page, the search correctly returns records that match the search criteria.
 

PO08600, WorkItem:254649 - Unable to delete Contacts from a Contact Log that include case participants with active home removals

Issue Description:
In an Ongoing case, when a case participant that has an active home removal record is included as a case participant on a Contact within the Contact Log, it is no longer possible to delete the Contact from the Contact Log.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a Child Welfare caseworker. Register a new Person (age < 18).
  2. From the person home page, click on the Care and Protection tab. Select Cases and create a new Ongoing Case.
  3. Select Removals and Placements tab from the newly created case.
  4. Select New Removal from the page menu. Complete the required fields and click Save.
  5. Select the Contacts tab on the Ongoing Case. Create a New Contact Log and complete the required fields.
  6. Enter some Narrative text and click Next. Select the registered person as a case participant and click Save & Exit.
  7. From the action menu on the new Contact Log created, select Delete.
  8. Issue: An error message is displayed: 'The Participant cannot be deleted as Removal details are present.'
Resolution:
The issue has now been resolved and a Contact that includes a case participant that has an active home removal record can now be deleted.
 

PO08602, WorkItem:254717 - Unhandled server exception occurs when a supervisor returns a submitted Intake Recommendation where a participant is registered as a person after submission

Issue Description:
When an Intake that includes a participant that is not yet registered as a person is submitted for approval, it is possible to register the participant as a person before a supervisor makes an Intake Recommendation decision on the Intake. In this scenario when the supervisor attempts to return the Intake, an unhandled exception occurs.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a Child Welfare intake worker and create a new Child Protective Services Intake.
  2. From the Participants tab, using the New Participant page action, add a child as a participant with a role of Alleged Victim.
  3. Add a second participant with a role of Alleged Maltreator.
  4. Click on the Allegations tab and select the New page action.
  5. Select the Alleged Victim, Alleged Maltreater, and type as Child Abuse and click Save.
  6. Open the Intake home page by selecting Open Intake tab menu option.
  7. Click on the Recommendation tab and select the Capture page menu action.
  8. Select Screened In on the Capture Recommendation page and click Submit.
  9. Click on the Participants tab and select the Name hyperlink for the child.
  10. On the child home page, select the Register tab menu option.
  11. Register the prospect as a person ensuring to specify any missing details.
  12. Login as a Child Welfare intake supervisor. Use the Search for Participant quick link to search for the child.
  13. Click on the Intake link in the context panel to open the Intake home page.
  14. Select the Administration tab then Tasks. Select the Intake Approval Task.
  15. On the task home page, select the Make Decision primary action. Click Return.
  16. Enter Comments on the Return Recommendation modal and click Save.
  17. Issue: An un-handled server exception is displayed on the Return Recommendations modal and the recommendation can not be saved.
Resolution:
This issue has been resolved and the Intake can now be successfully returned by the supervisor.
 

PO08634, WorkItem:255243 - Validation error displayed on the Edit Discharge Date modal when there are multiple children on an ongoing case each with a removal

Issue Description:
When there are multiple children on an Ongoing Case, each with a Removal, a validation message is displayed in the Edit Discharge Date modal preventing the user from editing the Discharge Date when the removal records are for different children. It is correct that the validation message is displayed when the removal records are for the same child only.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a Child Welfare caseworker.
  2. Register a child.
  3. Register a second child.
  4. Create an Ongoing Case for the first child.
  5. Navigate to the Participants tab of the case and add the second child as a participant.
  6. Select the Removals and Placements tab and click on the New Removal page action.
  7. Add the mandatory fields and click Save.
  8. Repeat steps 6 and 7 to create a Removal for the second child.
  9. On the first removal, select the New Placement row-level action.
  10. Select Foster Care as the Type and click Next.
  11. Now search for and select a provider before clicking Finish.
  12. Repeat steps 9-11 for the second child.
  13. For each Removal, use the Discharge row-level action to create a discharge for each child.
  14. Now try to update the discharge dates for each Removal by using the Edit Discharge Date row-level action.
  15. Issue: An error message is displayed when the removal records are for multiple children: 'The Discharge Date cannot be after the next Removal Start Date.'
Resolution:
This issue has been resolved. The logic for editing the discharge date has been updated to ensure that the Removal being processed is for the correct participant.
 

PO08635, WorkItem:255281 - Placements are not displaying in the Removals and Placements tab when multiple members are placed

Issue Description:
A child's removal can be recorded using the Removals and Placements tab on an Ongoing Case. When there are multiple members on the case, and multiple children are removed and placed together with a provider, in some instances the placement details do not display correctly for all of the children.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a Child Welfare caseworker.
  2. Register three children.
  3. From one of the children's home pages, click on the Care and Protection tab.
  4. Select Cases and use the New page action to create an Ongoing Case.
  5. Click on the Participants tab on the Ongoing Case and select Case Members.
  6. Use the New page action to add the other two children as members on the case.
  7. Select Relationships.
  8. Add a relationship of type Sibling between the members.
  9. Click on the Removals and Placements tab.
  10. Click on the New Removal page action to create a removal with the following information
    • Date: Today.
    • Children: Select all of them.
    • Reasons: Neglect.
    • Type: Voluntary.
    • Sub Type: Voluntary Surrender.
    • From: Parents.
    • Prior Living Arrangement: Parents.
    • Narrative: Test.
  11. Click Save and Place.
  12. On the New Placement creation wizard, provide the following details on the Placement Details page
    • Type: Foster Care.
    • Start Date: Today.
    • Select all the children.
  13. Click Next.
  14. On the Provider Search page, enter the name of any registered provider and click Search.
  15. Select the provider using the radio button and click Finish.
  16. Use the toggle to view each of the removal records created.
  17. Click on the Placements tab for each removal.
  18. Issue: One of the children does not have a placement listed.
Resolution:
This issue has been resolved and now when there are multiple members on the case that are placed together with a provider, placement details are displayed correctly for all children.
 

PO08658, WorkItem:255718 - Unable to display the contents of the Basics tab in the Intake Assistant when repeatedly saving Intake Narrative using the Smart Panel

Issue Description:
When adding or modifying Intake Narrative text through the Smart Panel Text Editor, repeatedly saving may result in an error being displayed in the Basics tab of the Intake Assistant.

User Interface Impact: No

Steps to Reproduce:

  1. Login as a Child Welfare intake worker.
  2. Create a New Intake.
  3. Type some text into the Intake Narrative in the Smart Panel.
  4. Click Save in the Smart Panel Text Editor toolbar.
  5. Type again or delete some content.
  6. Click Save in the Smart Panel Text Editor toolbar.
  7. Issue: An error message is displayed in the Basics tab of the Intake Assistant: 'The page you have requested is not available. One possible cause for this is that you are not licensed for the necessary Cúram module. If that is the case, you can use the User Interface administration screens to remove these links.'
Resolution:
A check has been added to avoid an unwanted server call through the save button in the Intake Narrative Smart Panel Text Editor. Now, when modifying the Intake Narrative using the Smart Panel, the contents of the Basic tab are displayed successfully.

Technical:
The issue was resolved by updating the Javascript function UIMPageAdaptor.isLinkValidForTabProcessing to exclude Javascript links from tab processing.
 

PO08662, WorkItem:255821 - Intake Narrative text not saved when using the Smart Panel Text Editor

Issue Description:
When creating a new Child Welfare Intake and entering Narrative using the Smart Panel Text Editor, the Intake Narrative text followed by double spaces is not saved by the Smart Panel Text Editor. Also, when pasting text that includes different types of formatting such as bullet points, bold, or underline, the Intake Narrative text is not saved. In both scenarios, the user is not presented with a warning message informing the user that the Intake Narrative text will not be saved.

User Interface Impact: No

Steps to Reproduce:

Scenario 1:

  1. Login as a Child Welfare intake worker.
  2. Create a New Intake from the shortcuts panel.
  3. Click on the Participants tab of the Intake Assistant.
  4. Select New Participant from the page menu and enter the participant details.
  5. In the Smart Panel Text Editor type some text where double spaces have been entered in the middle of the text, for example, ‘This is to test Intake Narrative’, with an extra space between the words 'to' and 'test'.
  6. Click Save in the Smart Panel Text Editor toolbar.
  7. Select Open Intake from the Intake Assistant tab action menu.
  8. Navigate to the Intake Narrative cluster on the Intake home page.
  9. Issue: The Intake Narrative text followed by double spaces is not saved by the Smart Panel Text Editor.
Scenario 2:
  1. Login as a Child Welfare intake worker.
  2. Create a New Intake and add a new Participant.
  3. In the Smart Panel Text Editor paste multiple paragraphs of text with different types of formatting, for example, bullet points, bold, underline, etc.
  4. Click Save in the Smart Panel Text Editor toolbar.
  5. Select Open Intake from the Intake Assistant tab action menu.
  6. Navigate to the Intake Narrative cluster on the Intake home page.
  7. Issue: The Intake Narrative text is not saved by the Smart Panel Text Editor.
Resolution:
The Intake Assistant Smart Panel Text Editor functionality has been updated to now use the whitelist functionality, which will ensure a warning message is presented to the user if any text formatting is used which is not permitted by the editor. Also, the issue with double spaces has been addressed. Now, the Intake Narrative text is saved when double spaces are entered in the Text Editor.

 

WorkItem:256636 - Editing the Discharge Date on a Removal throws a validation when there are Legal Actions associated with the Removal

Issue Description:
Legal Actions created within a case may be associated with a child's removal from the home. Where legal actions are associated with a removal and the removal has been discharged, attempts to update the Discharge Date are prevented because of a validation that is incorrectly thrown due to the association of the Legal Actions.

User Interface Impact: No

Prerequisite(s):

Associate a Legal Action with an Ongoing Case

  1. Login as an administrator and click on the Administration Workspace tab.
  2. Expand the shortcuts panel and select Legal Actions under Case.
  3. Click on the Legal Categories tab and use the toggle to expand the details of the Hearing record.
  4. On the inner Legal Actions list, select the row-level action Add Integrated Cases on the Court (Other) record.
  5. Check the Ongoing Case and click Save.
Register an External Party as a Legal Authority
  1. Login as a Child Welfare caseworker.
  2. Click on the Cases and Plans workspace tab.
  3. Select External Party under Registration in the shortcuts panel.
  4. Register an External Party ensuring to select Legal Authority as the Type.
  5. Click on the Offices tab and use the New page action to add a new office.
  6. On the row-level action of the newly added office, select New Office Member.
  7. Enter the mandatory details and click Save.
Steps to Reproduce:
  1. Login as a Child Welfare caseworker.
  2. Register a child.
  3. Click on the Care and Protection tab of the person and select Cases.
  4. Use the New page action to create an Ongoing Case.
  5. On the Ongoing Case, click on the Legal tab and select Legal Actions.
  6. Use the New page action to create a new Legal action.
  7. On the New Legal Action modal select Hearing as the Legal Category and Court (Other) as the Legal Action.
  8. Click Next.
  9. On the New Hearing modal, search for and select the previously registered external party as the Court Location.
  10. In the drop-down for the Judge, select the office-member created above.
  11. Use the check-box to select the child participant and click Save.
  12. Navigate to the Ongoing Case and click on the Removals and Placements tab.
  13. Use the New Removal page action to create a new Removal.
  14. On the New Removal dialog, fill in the mandatory fields.
  15. Use the check-box to select the Court (Other) Associated Legal Action.
  16. Click Save and Place.
  17. Select Foster Care as the Type and click Next.
  18. Search for and choose a Provider.
  19. Click Finish.
  20. Discharge the Removal using the row-level action.
  21. Specify a date/time after the placement date/time and a reason.
  22. Click Save.
  23. Now use the row-level action Edit Discharge Date on the Removal to update the date/time.
  24. Issue: On clicking Save the following error message is displayed 'Legal Action should be selected when the Removal type is court.'
Resolution:
This issue is now resolved and now the Edit Discharge Date logic has been updated to correctly consider any associated Legal Actions.
 


Code Removal

WorkItem:255283 - Update the BIApp release deliverable to remove the JAR files that are duplicated from the JDE

Since version 7.0.3.0 of IBM Cúram Social Program Management, a number of open source libraries (JAR files) from the Java Development Environment (JDE) were copied in error into a directory in the BIApp component. This caused an unnecessary duplication of these libraries within both the JDE and BIApp components.

These duplicated libraries have now been removed from the BIApp component.

Below is the file location and the list of impacted files:

  • CuramBIRTViewer⁩/⁨WebContent⁩/⁨WEB-INF⁩/⁨bicontent⁩/⁨resources/scriptlib
    • antlr-3.3.jar
    • aopalliance.jar
    • appinf_internal.jar
    • appinf.jar
    • bcel-6.1.jar
    • castor-xml-0.9.5.4.jar
    • cglib-nodep-3.2.5.jar
    • commons-beanutils-1.9.4.jar
    • commons-codec-1.5.jar
    • commons-collections-3.2.2.jar
    • commons-collections4-4.1.jar
    • commons-dbcp-1.4.jar
    • commons-digester-1.5.jar
    • commons-discovery-0.5.jar
    • commons-io-2.4.jar
    • commons-lang-2.6.jar
    • commons-logging-1.2.jar
    • commons-net-3.6.jar
    • commons-pool-1.6.jar
    • commons-validator-1.6.jar
    • compass.jar
    • coreinf-ejb.jar
    • coreinf-rmi.jar
    • coreinf.jar
    • CuramMBean.jar
    • ehcache-core-1.7.2.jar
    • failureaccess-1.0.1.jar
    • fscontext-1.2b3.jar
    • gss.jar
    • guice-4.1.0.jar
    • guice-assistedinject-4.1.0.jar
    • guice-multibindings-4.1.0.jar
    • guice-throwingproviders-4.1.0.jar
    • icu4j-58.2.jar
    • jackson-annotations-2.9.9.jar
    • jackson-core-2.9.9.jar
    • jackson-databind-2.9.10.1.jar
    • java_cup-0.10k.jar
    • javax.inject.jar
    • jde-commons.jar
    • jdom-1.0.jar
    • JSON4J_Apache.jar
    • license_metric_logger_2.1.1.jar
    • log4j-1.2.17.jar
    • lucene-analyzers-3.6.1.jar
    • lucene-core-3.6.1.jar
    • providerutil-1.2b3.jar
    • Registry.jar
    • rules_debugger.jar
    • rules.jar
    • serializer-2.7.2.jar
    • slf4j-api-1.5.8.jar
    • slf4j-jdk14-1.5.8.jar
    • tools.jar
    • wlstcontrol.jar
    • wsdl4j-1.6.3.jar
    • wss4j-1.6.18.jar
    • xalan-2.7.2.jar
    • xerces-2.9.1.jar
    • xmlsec-1.5.8.jar
    • xmlservercommon.jar
    • xmlunit-core-2.6.0.jar
Any references to these JARs from the BIApp component in custom classpaths and/or build scripts should be updated to refer to the libraries with the same name in the JDE component.
 

WorkItem:256300 - Removal of the jcommon JAR file from the product

JCommon is a Java class library that was used by some legacy features which are no longer part of IBM Cúram Social Program Management. Therefore, this library has been removed.

The library was delivered in the following location:

  • CuramCDEJ\lib\ext\jar\jcommon-1.0.0.jar
Any references to this JAR in custom classpaths and/or build scripts should be removed as a result of this change.
 

WorkItem:256469 - Remove the deprecated IEG Get List Question Command from the product

In IBM Cúram Social Program Management (SPM) 6.0.4.0 and previous versions, IEG list questions were requested one by one from the IEG Engine by the IEG Player. This was replaced in IBM Cúram SPM 6.0.5.0 by a mechanism whereby IEG list questions were returned in the initial page response. This meant that IEG list questions could then be looked up in the response using the list question identifier or the list Question internal identifier (internal-id).

The old mechanism for requesting IEG list questions and its related artifacts were deprecated in IBM Cúram SPM 6.0.5.0. These deprecated artifacts are now being removed from the product. This code removal exercise has resulted in the following changes:

  • The following two deprecated structs have been removed:
    • curam.ieg.facade.struct.IEGListQuestionDetails
    • curam.ieg.facade.struct.IEGListQuestionID
  • The following function has been removed from the curam.ieg.facade.intf.IEGPageNavigator class:
    • getListQuestion()
  • The following class has been removed:
    • curam.ieg.player.IEGListQuestionMarshal
  • References to the IEGListQuestionMarshal class have been removed from the IEG domains configuration file:
    • ../webclient/components/IntelligentEvidenceGathering/Configuration/DomainsConfig.xml
 

 

Notes on Deprecation

This section describes artefacts that have been deprecated in this release and the functionality that supersedes them.

Enhancements or defect fixes may require the contract of a development artefact to be changed. In this context the contract of an artefact is its API or signature (e.g. name, parameters, return values, etc) in conjunction with its documented statement of functionality (e.g. JavaDoc).

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

You can find out whether or not your code is affected by any of the following deprecations (and precisely where) by running the deprecationreport build target. If that build produces deprecation warnings, then you are affected by one or more of the deprecated artefacts itemized below. See the 'Deprecation' chapter in the Cúram Server Developer's Guide for further information on using this build target and analyzing its output.

Cúram Enterprise Framework


Technical Services


Business Intelligence

WorkItem:257646 - The Flex versions of Business Intelligence Charts are deprecated

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies on the Flex versions of BIRT charts, particularly if you have developed custom BIRT charts.

Itemised List of Changes:

The following list of artifacts were marked as 'deprecated' as part of the deprecation of this feature.

SWF Files:

  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/BarChart.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/BarChartLegendAbove.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/BarChartLegendBelow.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/BarChartLegendLeft.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/BarChartLegendRight.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/de_font.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/en_font.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/es_font.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/fr_font.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/HBarChart.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/HBarChartLegendAbove.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/HBarChartLegendBelow.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/HBarChartLegendLeft.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/HBarChartLegendRight.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/it_font.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/ja_font.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/ja_JP_font.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/ko_font.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/kr_font.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/LineChart.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/LineChartLegendAbove.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/LineChartLegendBelow.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/LineChartLegendLeft.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/LineChartLegendRight.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/PieChartLegendAbove.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/PieChartLegendLeft.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/PieChartLegendRight.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/PieChartLegndBelow.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/PieChartNoLegend.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/pt_BR_font.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/zh_CN_font.swf
  • .../BIApp/CuramBIRTViewer/WebContent/webcontent/zh_TW_font.swf
 

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


Integrated Case Management


Eligibility & Entitlement

WorkItem:257556 - The Flex Widget for Case Determination is deprecated

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies with the Flex Widget in Case Determination.

Itemised List of Changes:

The following list of artifacts was marked as 'deprecated' as part of the deprecation of this feature.

Domain Renderer Files:

  • .../webclient/components/core/javasource/core/CaseDeterminationFlexRenderer.java
SWF Files:
  • .../webclient/components/core/WebContent/core/flex/CaseDetermination.swf
 

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


Application Development Environment


Client Development Environment

WorkItem:257169 - Hardcoded literal references to the Helvetica Neue font have been deprecated and replaced with variable references

How to Upgrade:

The following have been deprecated from the file client/CoreInf/CuramCDEJ/lib/curam/web/themes/curam/fonts/helvetica-neue-ibm.css. The font faces defined in client/CoreInf/CuramCDEJ/lib/curam/web/themes/curam/fonts/main-ibm-font.css should be used in place of the deprecated 'Helvetica Neue' font faces.

  • Use MainLightFontforIBM instead of HelvNeueLightforIBM
  • Use MainRegularFontforIBM instead of HelvNeueRomanforIBM
  • Use MainMediumFontforIBM instead of HelvNeueMediumforIBM
  • Use MainBoldFontforIBM instead of HelvNeueBoldforIBM
Text searches for the above HelvNeue*forIBM font-faces should be done to replace them with the equivalent Main*FontforIBM font.

Itemised List of Changes:

Below is a list of the artifacts that have been marked as 'deprecated' as part of the deprecation of this feature.

  • ../webclient/components/CitizenContextViewer/Context/FlexWidgets/resources/fonts/helvetica-neue-ibm.css
    • Deprecated all IBM Helvetica font faces within this file - HelvNeueLightforIBM, HelvNeueRomanforIBM, HelvNeueMediumforIBM, HelvNeueBoldforIBM
  • ../client/CoreInf/CuramCDEJ/lib/curam/web/themes/curam/fonts/helvetica-neue-ibm.css
    • Deprecated all IBM Helvetica font faces within this file - HelvNeueLightforIBM, HelvNeueRomanforIBM, HelvNeueMediumforIBM, HelvNeueBoldforIBM
 

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


Cúram Modules


Outcome Management

WorkItem:185548 - The Flex Widget for Outcome Plan Workspace is deprecated

How to Upgrade:

The JavaScript version of the Outcome Plan Workspace is configured by default through the property 'curam.outcomeplanning.flexOutcomePlanWorkspaceEnabled'. Ensure that the property value is set to false.

Itemised List of Changes:

The following list of artifacts were marked as 'deprecated' as part of the deprecation of this feature.

Domain Renderer Files:

  • ../webclient/components/AssessmentPlanning/javasource/outcomeplanning/outcomeplan/TimelineRenderer.java
SWF Files:
  • ../webclient/components/AssessmentPlanning/WebContent/flex/OutcomePlanWorkspace.swf
Facades:
  • OutcomePlan.viewWorkspace
UIMs:
  • ../webclient/components/AssessmentPlanning/Delivery/OutcomePlan/Workspace/OutcomePlan_workspace.uim
 

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


Social Enterprise Collaboration


MDT Portal

WorkItem:185552 - The Flex Discussion Widget is deprecated

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies on the Flex Discussion Widget.

Itemised List of Changes:

The following artifacts were marked as 'deprecated' as part of the deprecation of this feature.

Domain Renderer Files:

  • .../webclient/components/SECCommon/javasource/ise/renderer/discussion/FlexDiscussionRenderer.java
SWF Files:
  • .../webclient/components/SocialEnterpriseCollaboration/WebContent/flex/DiscussionWidget.swf
 

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

WorkItem:185553 - The Flex Widget for the Social Enterprise Collaboration (SEC) Rich Text Editor is deprecated

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies on the Flex Rich Text Editor in the SEC MDTWorkspace.

Itemised List of Changes:

The following list of artifacts were marked as 'deprecated' as part of the deprecation of this feature.

Domain Renderer Files:

  • .../webclient/components/SECCommon/javasource/ise/renderer/richtext/RichTextFlexRenderer.java
SWF Files:
  • .../webclient/components/MDTWorkspace/WebContent/flex/RichTextEditor.swf
  • .../webclient/components/SocialEnterpriseCollaboration/WebContent/flex/RichTextEditor.swf
 

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


Universal Access


Administration

WorkItem:246931 - The Flex Widget for the Universal Access Rich Text Editor is deprecated

How to Upgrade:

There is no upgrade path for the deprecation of this feature. You are advised to break any dependencies on the Flex Rich Text Editor in Universal Access.

Itemised List of Changes:

The following list of artifacts were marked as 'deprecated' as part of the deprecation of this feature.

Domain Renderer Files:

  • .../webclient/components/CitizenWorkspace/javasource/workspaceservices/renderer/richtext/RichTextFlexRenderer.java
SWF Files:
  • .../webclient/components/MDTWorkspace/WebContent/flex/RichTextEditor.swf
  • .../webclient/components/SocialEnterpriseCollaboration/WebContent/flex/RichTextEditor.swf
 

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


Solutions


Child Welfare

PO07243, WorkItem:199838 - Intake start date is displayed incorrectly for Intakes displayed on the Screening page for a participant

How to Upgrade:

If you have a custom page that calls the deprecated facade, it should be updated to call the new facade. Likewise, if you have any custom operation, facade or otherwise, that calls the deprecated facade, it should be updated to call the new facade.

Itemised List of Changes:

The following API has been deprecated:

  • curam.cfss.ccs.intake.facade.impl.CCSIntake.createIntakeCase
This has been replaced by:
  • curam.cfss.ccs.intake.facade.impl.CCSIntake.createIntakeCase1
 

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

 

Known Issues

Cúram Modules

Cúram Modules

Provider Management
Outcome Management

Provider Management

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

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


Outcome Management

WorkItem:114547 (was previously CC-1100) - Administration property 'curam.outcomeplanning.referralForAgreementDays' is not working as expected

Outcome Management provides the ability to create agreements where the client(s) can agree in writing to adhere to the activities (services, referrals and actions) that form part of the agreement. A system property exists to filter out referral type activities during the agreement creation process based on a number of days from when the referral was created. This property is currently not being considered when creating an agreement. To work around this issue, the user can view the start date of the referral on the create agreement wizard to determine whether the referral should form part of the agreement.

 

Notices

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

 

Copyright

Licensed Materials - Property of IBM

Copyright IBM Corporation 2020. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

 

CSV Release Notes
This CSV file summarizes the individual release notes documented above in the "Improvements, Resolved Issues, Third Party Updates and Code Removals" 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.

[{"Business Unit":{"code":"BU014","label":"Watson Health"},"Product":{"code":"SS8S5A","label":"C\u00faram Social Program Management"},"Component":"","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"7.0.10","Edition":"","Line of Business":{"code":"LOB29","label":"Watson Health Unit"}}]

Document Information

Modified date:
19 March 2020

UID

ibm15694717