IBM Cúram 6.0.5.1 Release Notes

Introduction

Welcome to this IBM Cúram Social Program Management Version 6.0.5.1 release. These release notes document the improvements and resolved issues for this release.

Back to top

Installing the Application

Pre-requisites

Ensure that all installed third party software versions are consistent with those outlined in the Supported Hardware and Software section.

Application Pre-Installation Steps

If you are installing multiple Cúram offerings it is recommended that you install them in the following order: -

For the Entry Edition offerings

• Install IBM Cúram Social Program Management Platform for Universal Access Entry Edition before installing IBM Cúram Social Program Management Universal Access Entry Edition

• Install IBM Cúram Social Program Management Platform for Outcome Management Entry Edition before installing IBM Social Program Management Outcome Management Entry Edition

No additional offerings are supported on top of an Entry Edition installation. To add any additional offering you must first upgrade to a standard edition of the product.

For the standard offerings it is recommended that you install them in the order below.

1. Install IBM Cúram Social Program Management Platform. This automatically installs the following enterprise modules:

   • IBM Cúram Verification Engine
   • IBM Cúram Evidence Broker
   • IBM Cúram Life Event Management
   These enterprise modules may only be used where licensed.

2. Install any of the enterprise modules. The enterprise modules are the following: -

   • IBM Cúram Universal Access
   • IBM Cúram Outcome Management. You may then install
     • IBM Cúram Outcome Management Structured Decision Making Add-on
   • IBM Cúram Provider Management
   • IBM Cúram Social Enterprise Collaboration
   • IBM Cúram Business Intelligence and Analytics
   • IBM Cúram Appeals

3. Install any of the program-based offerings. The program-based offerings are the following: -

   • IBM Cúram Workers Compensation - Do not install any other program-based offerings with this offering.

   • Either IBM Cúram Income Support or IBM Cúram Income Support for Medical Assistance (but not both). You may then install

     1. IBM Cúram Income Support Screening followed by

     2. IBM Cúram Business Intelligence and Analytics Reports for Income Support

   • IBM Cúram Child Welfare. You may then install

     1. IBM Cúram Child Welfare Structured Decision Making Add-on followed by

     2. IBM Cúram Business Intelligence and Analytics Reports for Child Welfare

   • IBM Cúram Youth Services

   • IBM Cúram Child Care

   • Any additional assets such as demonstrations

Application Installation

To install this product please run the installer provided. See the Cúram Installation Guide

Application Post-Installation Steps

POST-50 - Additonal post install steps for WebSphere to enable the collection of JMX statistics

The following post-install step is required for WebSphere environments in order to allow the collection of application JMX statistics:

The "ALL AUTHENTICATED" special subject must be assigned the "Monitor" and "Operator" roles in order to be able to collect and download Cúram JMX statistics. From the WebSphere administrative console click on the Users and Groups menu and from the Administrative group roles add the "Monitor" and "Operator" roles to the special subject "ALL AUTHENTICATED".

POST-60 - Modify the EJBServer .classpath file for CitizenWorkspace.jar

• Open the EJBServer\.classpath file in a text or xml editor

• Find the entry for CitizenWorkspace.jar and replace with the following:-

<classpathentry kind="lib" path="components/CitizenWorkspace/lib/CitizenWorkspace.jar">
  <attributes>
    <attribute name="javadoc_location" value="jar:platform:/resource/EJBServer/components/CitizenWorkspace/doc/api.zip!/"/>
  </attributes>
  <accessrules>
    <accessrule kind="accessible" pattern="curam/citizenaccount/impl/CitizenAccountHelper"/>
    <accessrule kind="accessible" pattern="curam/citizenaccount/impl/CitizenActivities"/>
    <accessrule kind="accessible" pattern="curam/citizenaccount/impl/CitizenCaseComparator"/>
    <accessrule kind="accessible" pattern="curam/citizenaccount/impl/CitizenPayments"/>
    <accessrule kind="accessible" pattern="curam/citizenaccount/impl/MyApplications"/>
    <accessrule kind="accessible" pattern="curam/citizenaccount/impl/ReferralLetter"/>
    <accessrule kind="accessible" pattern="curam/citizenaccount/security/impl/CitizenAccountSecurity"/>
    <accessrule kind="accessible" pattern="curam/citizenmessages/impl/CitizenMessagesController"/>
    <accessrule kind="accessible" pattern="curam/citizenworkspace/applicationprocessing/impl/ConfirmationMessageComposer"/>
    <accessrule kind="accessible" pattern="curam/citizenworkspace/applicationprocessing/impl/SubmissionConfirmationMessage"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/base/CWNavigatorLink"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/base/CitizenScriptInfo"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/base/LifeEventCW"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/base/Motivation"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/base/MotivationIntakeAppLink"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/base/MotivationResult"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/base/PagePlayerState"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/fact/CWNavigatorLinkFactory"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/fact/CitizenScriptInfoFactory"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/fact/LifeEventCWFactory"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/fact/MotivationFactory"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/fact/MotivationIntakeAppLinkFactory"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/fact/MotivationResultFactory"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/fact/PagePlayerStateFactory"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/intf/CWNavigatorLink"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/intf/CitizenScriptInfo"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/intf/LifeEventCW"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/intf/Motivation"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/intf/MotivationIntakeAppLink"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/intf/MotivationResult"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/intf/PagePlayerState"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/CWNavigatorLinkDtls"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/CWNavigatorLinkDtlsList"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/CWNavigatorLinkKey"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/CitizenScriptInfoDtls"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/CitizenScriptInfoDtlsList"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/CitizenScriptInfoKey"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/LifeEventCWDtls"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/LifeEventCWKey"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/MotivationDtls"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/MotivationDtlsList"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/MotivationIntakeAppLinkDtls"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/MotivationIntakeAppLinkKey"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/MotivationKey"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/MotivationResultDtls"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/MotivationResultKey"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/PagePlayerStateDtls"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/PagePlayerStateDtlsList"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/entity/struct/PagePlayerStateKey"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/facade/base/CitizenWorkspace"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/facade/base/LocalOfficeSearch"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/facade/fact/CitizenWorkspaceFactory"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/facade/fact/LocalOfficeSearchFactory"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/facade/intf/CitizenWorkspace"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/facade/intf/LocalOfficeSearch"/>
    <accessrule kind="accessible" pattern="curam/citizenworkspace/impl/CWScreeningEvents"/>
    <accessrule kind="accessible" pattern="curam/citizenworkspace/impl/ProgramSelectionEvents"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/impl/PurgeCitizenPortalData"/>
    <accessrule kind="accessible" pattern="curam/citizenworkspace/impl/PurgeCitizenWorkspaceData"/>
    <accessrule kind="accessible" pattern="curam/citizenworkspace/impl/ResetPasswordEmailStrategy"/>
    <accessrule kind="accessible" pattern="curam/citizenworkspace/impl/StartIntakeEvents"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/motivations/impl/Motivation"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/motivations/impl/MotivationDAO"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/navigator/impl/CWNavigatorLink"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/navigator/impl/CWNavigatorLinkDAO"/>
    <accessrule kind="discouraged" pattern="curam/citizenworkspace/navigator/impl/CWNavigatorLinkValidator"/>
    <accessrule kind="accessible" pattern="curam/citizenworkspace/navigator/impl/CWProcessNavigatorEvents"/>
    <accessrule kind="accessible" pattern="curam/citizenworkspace/security/impl/SecurityStrategy"/>
    <accessrule kind="discouraged" pattern="curam/citizenaccount/entity/base/*"/>
    <accessrule kind="discouraged" pattern="curam/citizenaccount/entity/fact/*"/>
    <accessrule kind="discouraged" pattern="curam/citizenaccount/entity/intf/*"/>
    <accessrule kind="nonaccessible" pattern="curam/citizenworkspace/facade/base/*"/>
    <accessrule kind="nonaccessible" pattern="curam/citizenworkspace/facade/impl/*"/>
    <accessrule kind="nonaccessible" pattern="curam/citizenworkspace/facade/intf/*"/>
    <accessrule kind="accessible" pattern="**/struct/**"/>
    <accessrule kind="nonaccessible" pattern="**/**"/>
  </accessrules>
</classpathentry>

• Save and refresh the EJBServer project in eclipse

POST-61 - The following steps should be applied when IBM Curam Youth Services is installed without IBM Curam Social Enterprise Collaboration

The following steps should be applied when IBM Curam Youth Services is installed without IBM Curam Social Enterprise Collaboration.

From the file EJBServer\components\YouthServices\data\demo\SECURITYGROUPSID.dmx

Remove the following entry from the file

  <row>
    <attribute name="groupName">
      <value>CYSCASEWORKERGROUP</value>
    </attribute>
    <attribute name="sidName">
      <value>MDTCollaboration.isCollaborationEnabled</value>
    </attribute>
  </row>

POST-62 - Update tabbed configuration for HCR dynamic evidence

• Edit EJBServer\components\HCR\tab\DynamicEvidenceObjectDET002606820130502.tab in a text/xml editor
• Replace DynamicEvidenceObjectDET000051220130502Nav with DynamicEvidenceObjectDET002606820130502Nav (there should only be a single occurrence)
• Rebuild the database

POST-63 - Update deployment_packaging for Platform

• Edit EJBServer\project\config\deployment_packaging.xml using a text editor
• Replace the following entry -

    <ear
        name="CPMExternalNS"
        requireServer = "false"
      >
     <components>CPMExternalNonSecure</components>
     <context-root>CPMExternalNS</context-root>
    </ear>
    

  with

    <ear
        name="CPMExternalNS"
        requireServer = "false"
    >
    <components>CPMExternalNonSecure,CEFWidgets</components>
    <context-root>CPMExternalNS</context-root>
    </ear>
    

• Rebuild EARs

POST-65 - Replace CGISSEWAPPWorkspaceSection.sec if licensed for IBM Cúram Income Support for Medical Assistance

Before building the database, replace EJBServer\components\ISProduct\tab\ApplicationViews\CGISSEWAPPWorkspaceSection.sec with the replacement file provided in Readme\Additional Files.

Then, run the database and prepare.application.data build and bring up the server.

Note that this post-install step is only required for customers that are licensed for IBM Cúram Income Support for Medical Assistance.

Back to top

Supported Hardware and Software

The IBM Cúram Social Program Management Version 6 Supported Prerequisites document outlines the supported prerequisites for this release.

Back to top

Improvements and Resolved Issues

Cúram Enterprise Framework

PO00941, CEF-12324 - Discourage access warnings due to CuramBatch.setStartTime() and CuramBatch.setEndTime() not being externalized

Previously, discouraged access warnings were thrown while trying to access the CuramBatch.setStartTime() and CuramBatch.setEndTime() methods as these methods were not externalized.

Now, this has been resolved by externalizing the CurmaBatch class, CuramBatch.setStartTime () and CuramBatch.setEndTime() methods.

CEF-12349 - Review of application resolve scripts for sanitization of parameter values to avoid potential vulnerabilities

Jsp scriptlets which redirect to another page were vulnerable to attack if a malicious user tried to split the URL using carriage return or line feeds. Unlike some application servers, Weblogic does not appear to provide any protection against this problem. Parameters are now sanitized correctly prior to use in these situations.

CEF-12444 - Using Rich Text Editor causing redirect to login page within MDTWorkspace

The Curam specific configuration for the CKEditor has been amended to remove the use of the 'Curam' context from configuration paths.

Integrated Case Management

CEF-12329 - The source for curam.core.impl.MaintainCertificationAssistant should be shipped as sample

The following Java file, curam.core.impl.MaintainCertificationAssistant, is now included in the sample source shipped to customers.

Evidence Management

CEF-11057 - Apply Changes page updated to remove the Change Summary column

The "Change Summary" column has been removed from the Apply Changes dialog in the Evidence section. This was removed because it was considered low value information to users at this point in the evidence lifecyle and it was causing content to wrap in translated versions of the product leaving the page difficult to use.

CEF-12477 - Evidence with successions may not display correct summary details.

Previously there was an issue where incorrect summary details were displayed for evidence which had a few successions.

The reason for this issue was the fact that hand-crafted SQL in EvidenceDescriptor.searchAllActiveEvidenceInstances()

and EvidenceDescriptor.searchAllActiveAndModified() methods did not work correctly when there were multiple evidence

successions.This issue is now fixed.

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

PO01060, CEF-12523 - When applying evidence changes the security checks need to be targeted at the evidence being 'applied'

The server processing when applying changes to evidence on a case has been updated to improve performance.

Previously, when applying changes to evidence on a case, the evidence type security check was invoked for every evidence record on the case. This has been updated to only invoke the security check for each distinct evidence type to which changes are being applied.

Participant Management

CEF-10663 - Participant search by reference field containing non alphanumerical characters only returns all records.

Previously, when a user searched for person or other participant type using the reference number when GSS was enabled, where the field value consisted of special characters/non-alphanumerical character(s), the system returned all the available records. No results should have been returned as the reference search is an exact match search.

This issue has been resolved by adding a validation message "Reference field must contain at least %1n alphanumerical character(s)."

This will block the user from searching by non-alphanumerical characters. Any wild card characters entered in the reference search field are now treated as normal characters.

CEF-12442 - Resolving deprecation warnings in the client build

Previously, there were few deprecation warnings in the client build for the following uims.

1. \webclient\components\core\Prospect\Citizenship\Prospect_viewCitizenship.uim
2. \webclient\components\core\Prospect\ForeignResidency\Prospect_viewForeignResidency.uim
3. \webclient\components\core\Prospect\Employment\Prospect_viewEmployment.uim

The reason was the server interfaces of the corresponding uims were deprecated. Now, these uims are deprecated as well as the entire functionality of 'Prospect' participant is obsolete.

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

Eligibility & Entitlement

CEF-9976 - Provide tooling to automate the execution of the Dependency Manager batch suite

Tooling has been provided in the form of Ant scripts to assist in the running of the Dependency Manager batch suite. Using the tooling will ensure that the batch jobs are run in the correct order, and will allow the user to set a property to manage the performance of the batch run. For further information please see the Dependency Manager section of the Curam Operations Guide.

PO00662, CS-07390, CEF-11863 - Document the CER rule set interdependencies

The CER Rule Set interdependency information is now available via the development installer. It can be found at the following location:

*<drive>\IBM\Curam\Development\Doc\IBM_Curam_Social_Program_Management\RuleSetsInterdependencies*

PO00781, CEF-12225 - Target creole.upload.rulesets triggering excessive CER recalculations

Previously, when CER rule sets were published, they were always marked as outdated via the dependency manager. This resulted in the next run of the dependency manager batch suite performing more recalculations then were necessary. In particular, using the 'build creole.upload.rulesets' command would cause all CER rule sets to be outdated in this way.

This has now been fixed and only those rule sets that have genuinely changed will be outdated via the dependency manager during the publishing process, and hence the next run of the dependency manager batch suite will only recalculate items which could be affected by the changes made.

CEF-12368 - Determinations incorrectly seen as different due to ordering of lists in display data

Previously, the determinations displayed within a case could in some cases appear to be different even when they were not different due to incorrect ordering of data lists within CER.

This issue has now been resolved.

PO01080, CEF-12492 - Over/Underpayment statements are incorrect when using "Every X weeks on a Y" delivery patterns

Previously there was an issue that could cause over/underpayment statements to be generated incorrectly when using "Every X weeks on a Y with an offset" delivery patterns, for example "Every 4 Weeks on a Thursday with a 4 day offset". Due to a problem during reassessment building up the list of payment dates, in certain scenarios where the over/underpayment spans more than one payment period the cover periods and reassessment amounts were calculated incorrectly leading to inaccurate statements. This issue has now been resolved.

PO01141, CEF-12568 - Subscreen display rule changes do not generate split decisions

Previously subscreen display rule changes were not considered in the same way that 'normal' display rule changes were considered when the system determined how and when to create split decisions. This issue has now been resolved.

Common

PO00505, CS-11098, CS-11686, CEF-9480 - Performance issues occurring during automatic translator requirement redetermination processing

Previously, when a product was configured for automatic redetermination of translator requirements for case members and a change occurred to the language skills of a caseworker that required re-determination across multiple cases, performance issues were occurring because the system was incorrectly retrieving all cases rather than just those cases owned by the caseworker. This issue has now been resolved.

In addition, a new Redetermine Translator batch process and application property have been introduced that can be used to perform redetermination in batch mode instead of online mode for changes that affect large volumes of cases. The application property, curam.cases.maxnocases.onlineautotranslatordetermination, is used to control whether automatic re-determination of translator requirements will occur in batch mode vs. online mode. If the number of open cases that require processing exceeds this value, re-determination will not occur in online mode and the batch process must instead be executed.

CEF-10359 - Receipt date is not being displayed for case attachments

A Receipt Date field has been added to the Case_viewAttachment.uim file so it will be now be available to view in the listed attachments in each of the following areas: Case attachment, Product attachment, Investigation attachment, Issue attachment.

Investigations

PO00937, CEF-12308 - Unable to preview contact log details within migrated cases

Previously, users were unable to preview the contact log details within cases that were migrated from V5.2 to V6. This issue has now been resolved by providing backward compatibility for contact logs.

Dynamic Evidence

Evidence Editor

CDP-636 - Tabbing Issue : Non of the Links in Evidence Editor are accessible using Tab+Enter Key

In the Dynamic Evidence Editor, it was not possible for the user to access any links using the Tab+Enter key. This issue has now been resolved.

Evidence Maintenance

CDP-897 - DynamicEvidenceRuleset rule definition for addressRecord not thowing an application error when ID value empty

Dynamic Evidence delivers a ruleset called DynamicEvidenceRuleset. This ruleset contains a rule definition for an attribute called addressRecord. This attribute's definition has been updated to indicate that when its rule is called then the ID value specified should not be empty. Otherwise an application error is thrown.

Previously, it was possible to call the addressRecord attribute rule specifying an empty address ID without any application error being thrown.

Any rules referencing the addressRecord attribute must ensure that the id specified is not empty.

CDP-1088 - Dependency Validation 'at least one of' not working for dates

The 'at least on of' dependency validation for a Dynamic Evidence Type checks to see that one of the attributes specified for that validation have been entered during the create operation for an evidence record of that type.

In the previous release, if a required numeric field was not populated the dependency validation was not indicating this and the create operation completed successfully. This issue has now been resolved.

CDP-1089 - Dependency Validation is not picking up for Money, Integer and Float attribute Types

In the previous release, the Dynamic Evidence Type Dependency validation definition was not detecting that a required value for an attribute of type Money, Float and Integer types during the creation of a evidence record containing that validation. The create succeeded but should have resulted in an error message indicating the dependency.

This problem has now been resolved and an error is indicated during create where the dependency validation check now fails.

CEF-11883 - Required to enter Suffix on entering new Name Evidence

Previously, the users were forced to select a suffix when adding a new Name evidence on a Participant Data Case. Now this is being resolved by adding a blank value in the suffix drop-down field.

Evidence Sharing

CEF-12497 - Evidence Broker must clear shared evidence informational manager contents

An Identical validation is executed during evidence brokering to prevent identical evidence records being shared to the target case.

In the previous release, if the broker was sharing a list of evidence records and the identical validation failed for of one of these, this caused the failure of the subsequent evidence records being shared. This problem has been fixed in this release.

CEF-12590 - Identical validation is skipped on brokering evidence on evidence modification

Evidence brokering can allow the source evidence record be brokered back onto the source case. This can happen where there are 3 or more cases configured to share that evidence type. Eg. CaseA shares to CaseB. CaseB shares to CaseC, and CaseC shares back to CaseA.

In the previous release, the identical validation checking that happens during brokering was not being invoked in the above scenario. This allowed duplicate evidence records to be recorded on a case. This problem has now been rectified and the identical check will be invoked in this scenario.

Common Intake

PO00902, CI-4188 - Application submission fails if the client submits their application outside business hours and the date submitted is set to the next business day

Previously, if a working pattern of working hours had been set and an application was submitted through Universal Access outside of the working hours defined in the working pattern, the application would fail to submit.

This has been addressed and it is now possible to submit an application outside of defined working hours through Universal Access.

PO01116, CI-4235 - Asterisk is missing on mandatory fields on the 'Add Client' wizard

Previously, the fields 'Marital Status' and 'Gender' were not mandatory on the quick registration wizard.

These fields are now marked as mandatory.

PO01102, CI-4246 - Cannot submit application if the filing date is in the past

Previously, an error existed when submitting an application that had a filing date before the submission date.

The issue was that the start date of the clients on the application was being validated against the submission date for the application as part of submission processing. A validation error occurred if the filing date (the start date of the clients on the application) was before the submission date. This validation error was incorrect, as it should be possible to have a filing date before the submission date.

This has been resolved by determining the earliest of the two dates and using this earliest date in the validation.

PO01143, CI-4252 - When application status is set to 'Ready for Determination', all the clients are set as primary members

Previously, when an application was disposed and the curam.application.disposed.menu.options environment variable value is set as 'NO', all clients in disposed applications were changed to primary members.

Clients should not be changed to primary members when the application status is updated.

This issue has been resolved.

Technical Services

Generic Search Server

TEC-9282 - GSS Extractor Multi-threading Improvement

The 'runExtractor' target of the Curam Generic Search Server has been updated to support multi-threaded operation by means of streaming.

i.e. the extraction process consists of two phases:

In phase one a single thread identifies the primary keys of the records to be extracted

In phase two these primary keys are used to extract and index the records. This phase is where the bulk of the processing is required, and multiple instances of this thread can be executed.

For more details please refer to the chapter entitled 'Deploying the Generic Search Server' in the Curam Generic Search Server guide.

TEC-13895 - Excessive locking on the GSSSYNCGAP table

An issue with the Curam Generic Search Server (GSS) has been resolved whereby setting properties 'curam.lucene.luceneOnlineSynchronizationEnabled' and 'curam.lucene.externalUpdateEventsEnabled' to False did not disable the processing which synchronized the GSS indexes with data changed by online transactions.

This resulted in unwanted overhead due to unnecessary processing.

Setting both of the above properties to False now correctly disables this processing.

CMIS Adapter

CEF-11345 - Application Reference metadata not being stored for some Common Intake application case attachments

Previously Common Intake application business flows related to verification items that could result in an Attachment getting stored on a Content Management System were not storing the Application Reference of the application as metadata associated with the file. These business flows now associate the correct set of metadata with the stored file.

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

CEF-12373 - Ability to enable/disable metadata functionality

Customers taking on 6.0.5 who wished to enable CMIS integration were forced to perform a small amount of configuration work on their Content Management System to support the use of metadata functionality.

An application property has been introduced to allow the CMIS metatdata feature to be enabled or disabled, 'curam.cms.metadata.enable' defaulting to 'false', and can be used by customers to disable the metadata feature and postpone the CMS configuration if desired.

It is strongly recommended that the metadata feature is enabled before CMIS integration is used to store any documents. Otherwise the CMS administrator will need to perform a migration effort before the metadata feature is enabled. This would consist of updating the object type of the files created to match the new types configured for Cúram.

CEF-12514 - Introduce error handling for uploading files when the Content Management System is unavailable

Error handling has been introduced for when the configured Content Management System is unavailable. This had been a potential cause of an unhandled server exception. This could only occur if the settings were incorrect or if there was a networking issue blocking access.

CEF-12547 - CMIS Error Handling improvements

Various minor improvements to the CMIS error handling have been made to make it more robust.

CEF-12548 - Introduce configuration options for CMIS timeouts

Two new application properties are now available under the Content Management settings in the system administration application. These are upper limits on the allowable networking times for transactions with the configured Content Management System.

'curam.cms.connectiontimeout' allows the administrator to set the connection timeout (in milliseconds) for the CMS. This defaults to zero which means that the JVM setting will be used instead.

'curam.cms.readtimeout' allows the administrator to set the read timeout (in milliseconds) for the CMS. This defaults to zero which means that the JVM setting will be used instead.

Security Management

CEF-3656 - Need capability to delegate authentication of external users to different implementations of PublicAccessSecurity

Previously, there can be only one External User Security implementation that can be used for all the portals at a time, as the External User Security implementation to be used in determined by the Environment property : curam.custom.externalaccess.implementation.

Now, this has been changed to provide the ability to different portals, to define their own external user security implementation specific to the application type the external user is associated with.

If there is no implementation defined for any application type, the default external user implementation will be used.

Also, to provide a custom implementation for users not present in the External User table, an implementation has to be provided for curam.core.sl.imp.ExternalUserAccessSecurity(which extends PublicAccessUser itself) and this abstract class and its implementation has to be bound explicitly in the module class.

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

TEC-13420 - Documentation: Security handbook corrections

The following topics in the Cúram Security Guide have had minor corrections and changes made:

• Analyzing the AuthorisationLog Database Table
• How to Create a New Keystore
• Alternate Login IDs
• Overview (subtopic of Cryptography in Cúram)
• Ciphering
• Cipher Encrypted Passwords
• Cipher Customization
• How to Specify a Digest Salt
• Other Security Considerations - includes a new sub-topic "Using Cúram in a Secure Environment" to provide information relating to configuring for SP800-131a and the use of TLS v1.2.

The Cúram Batch Processing Guide has been modified to add information about property curam.batchlauncher.dbtojms.notification.ssl.protocol.

The Cúram Web Client Reference Manual topic "User Machine Configuration" has been modified to provide information about using the Word Integration Control with the TLS v1.2 protocol.

Rules Infrastructure

Cúram Express Rules

CEF-12620 - Cúram Express Rules rule set customisation

Previously, it was not possible to customize a Cúram Express Rules rule set without renaming the rule set xml file. A validation error regarding duplicate rule sets was thrown by the server build if a rule set was not renamed when it was being customized. The Cúram Express Rules build has been updated to allow customization of a rule set file by overriding it in the EJBServer/components/custom folder. For further details of this new customization technique refer to the 'Customizing CER Rule Sets' section of the Inside Eligibility and Entitlement Using CER guide.

As a result of the updates made to the Cúram Express Rules build, where a rule set contains an {{Include}} statement with a {{RelativePath}} value that points to a location which is not within the CREOLE_Rule_Sets folder of a component, this relative path will now have changed and the {{RelativePath}} value should be updated to reflect this. The new relative path should be relative to the following EJBServer build location:

{{EJBServer\build\svr\creole.gen\SortedRuleSets}}

where previously it was relative to the {{CREOLE_Rule_Sets}} folder of the relevant component within {{EJBServer\components}}. This change only applies to include statements containing relative path values which point to locations outside of the CREOLE_Rule_Sets folder.

TEC-12374 - Text Wrapping Issue For Palette Items

Previously, in the CER Editor, labels that were longer than the width of the Tools and Templates palette were wrapped. To correct this, the Tools and Templates palette is now extendable, expanding the palette will show the full non--wrapped label.

Workflow

PO00802, TEC-13025 - Newly introduced event wait entity foreign keys failing due to decision activity DECISION MADE event

In a previous version of the product, new foreign keys were added to the EventWait, EventClass and EventType database tables. These foreign keys were added to ensure that the event classes and types specified in workflow process definitions are valid and included on the event class and event type tables.

However, for decision activities, the scenario is slightly different. The user does not specify an event to wait for in the process definition metadata as it is added automatically when a decision activity is executed by the workflow engine. This event is specified by the workflow engine to be "DECISION.MADE". Previously, no event class and event type for this event were delivered in the product. This has now been resolved and ensures that any foreign key issues related to this event class have been addressed.

Application Development Environment

Core Development Infrastructure

Localization and Internationalization

TEC-13201 - need final Fallback locale for application properties instead of serverdefault

Previously, the properties display name fallback as minor-locale (say en_US) to major-locale (say en) to ServerDefaultLocale (value of property curam.environment.default.locale) . this has been changed now to fallback as minor-locale (en_US) to major-locale (en) to root fallback locale(value of property curam.environment.fallback.default.locale).

Third Party Software

TEC-13946 - Update the Deployment guide for Websphere in relation to WAS7 and USGCB

A new section 'Using IBM Webpshere Application Server with USGCB' has been added to the following guides:

- Cúram Deployment Guide for WebSphere Application Server on z/OS

- Cúram Deployment Guide for WebSphere Application Server

TEC-14001 - Add information to WAS for z/OS deployment guide relating to prepare.application.data post-installation setup

The "Post-Installation" sub-topic of the "DB2 for z/OS" topic in the Cúram Deployment Guide for WebSphere Application Server on z/OS has been updated to indicate the possible need to modify the idle thread timeout value.

Server Development Environment

CS-11280, TEC-10450 - Log the root SQLCode of any unhandled DB exception

Previously the SQL code of an unhandled database exception was only written to the server log file when property curam.trace was set to trace_verbose or higher.

To help with problem solving, the SQL code of an unhandled exception is now always written to the server log.

PO00803, TEC-12927 - Classloading fails due to ordering issue with customized code on the environment where default file system order is descending

The building of the Curam.ear file has been updated to ensure that the jar file that contains all customized structs is always loaded first in the application server, thus removing any dependency on the classloading order.

TEC-13164 - Bootstrap property 'curam.environment.bindings.location' to be validated as optional rather than mandatory

Previously the SDEJ required property 'curam.environment.bindings.location' in Bootstrap.properties to be set to the name of a directory on disk, even though this directory is no longer required by the application.

This property is no longer treated as mandatory.

PO00820, TEC-13203 - Update Third Party Tools installation guide to indicate how to run the StartServer.java application

The Cúram Third-Party Installation Guide for Windows has been updated to correctly reflect how to launch the Server in an application development environment.

The sections updated are: Using a Server Project in Eclipse, and Running the Application in Rational Application Developer.

PO00916, TEC-13392 - Message file is not regenerated when only the file name is changed and no content.

Previously an issue existed whereby no new message files were regenerated if only the file name was changed but its contents were left unchanged.

This issue has been resolved, and renaming a message file now results in the necessary new message files being generated.

PO01074, TEC-13742 - Code that executes security cache queries needs to be synchronized and fine tuned

An issue has been resolved whereby a number of SQL queries relating to the security cache were not synchronized and could cause high concurrency wait times and lead to overall system slowness.

XML Server

CS-10630, TEC-9361 - THREAD_POOL_QUEUE_SIZE is being hard coded in XMLServer

In the Curam XML Server, configuration property 'THREAD_POOL_QUEUE_SIZE' was being ignored and a value of 200 was always used for this parameter.

This configuration property is now correctly read by the XML Server, and will default to 200 if not specified.

Document Curam XML Infrastructure Guide has been updated to explain the correct usage of this property.

CS-10790, TEC-9586 - Preview enabled without statistics, causes Nullpointer exception and xmlserver hangs

Previously when the XML Server was used to produce a preview document, and the STATISTICS_FOLDER option was not configured, an NullPointerException would occur in the XML Server and thereafter the XML Server would not respond to further requests.

This has been resolved and it is now possible to produce preview documents even if the STATISTICS_FOLDER option has not been configured for the XML Server.

Batch Processing

TEC-13499 - Allow specifying additional protocols for DBtoJMS

DBtoJMS now accepts an SSL protocol name via property curam.batchlauncher.dbtojms.notification.ssl.protocol, which defaults to SSL. The protocol name (e.g. SSL, TLS, etc.) is dependent on the support provided by your JDK and application server. See the relevant documentation for protocol names valid in your environment. For this property to be utilized the curam.batchlauncher.dbtojms.notification.ssl property must be set affirmatively (e.g. true, yes). The curam.batchlauncher.dbtojms.notification.ssl.protocol is not yet defined out-of-the-box in Application.prx; so, if you wish to use it you will need to manually specify it to the environment.

Cúram Server API

TEC-13454 - Update the curam.util.type.CodeTable.getOneitem() method to use users locale

Server method 'curam.util.type.CodeTable.getOneItem(final String table, final String code)' has been updated to retrieve the code table item description based on the locale of the logged in user.

Previously the server default locale was used.

If the locale of the logged in user cannot be determined, the description will be retrieved for the 'en' locale.

Please see the associated javadoc for further information.

Miscellaneous

CS-10133, TEC-11621 - Update Compliancy Guide re: Patching Mechanism

The Discouraged Extension Mechanisms - Other Mechanisms section within the Cúram Development Compliancy Guide has been updated to indicate that the substituting of patched files for out-of-the-box files is discouraged.

The reference to EJBServer/patch directory has been removed from the Cúram Third-Party Tools Installation Guide for Windows guide.

Client Development Environment

PO00877, TEC-13232 - iframe title attribute fallback

Previously, in the Cúram application if a UIM page did not have a PAGE_TITLE attribute set, the corresponding iframe was not titled correctly. As a workaround the PAGE_TITLE attribute was set in the affected UIM files.

This is now fixed. If a UIM doesn't have a PAGE_TITLE attribute set, the iframe title falls back to navigation tab title or the application tab based on where the affected UIM is.

TEC-13641 - Issues with page load performance

An issue with Application UI performance has been addressed. A number of modules that were previously loaded automatically in CDEJ for every page are now no longer loaded.

There is a potential impact on custom application pages that contain JavaScript and do not explicitly declare their dependencies on the required JavaScript modules. If such pages accidentally use a module that is no longer loaded by the infrastructure (for performance reasons) an update may be required to explicitly declare dependencies and avoid JavaScript errors.

How To Tell the Affected Pages

In order to determine if you are affected you need to find UIM, VIM or JSP pages, custom renderers and JavaScript code that reference code from JavaScript modules, but do not declare them as dependencies using dojo.require() or require().

Typically JavaScript code from a module is referenced by using dot notation, such as the "dijit.Dialog" in "var dialog = new dijit.Dialog();". For this to work there must generally be a corresponding dojo.require("dijit.Dialog"); call to load the required module.

Administration Suite

PO00779, CEF-12072 - Access restrictions marked incorrectly on Activity and Slot Allocation APIs

Previously, the Javadoc for the following APIs did not list them as being externally accessible.

• curam.core.facade.impl.Activity.modifyActivity
• curam.core.facade.impl.Activity.removeActivity
• curam.core.sl.impl.SlotAllocation.processSlot
• curam.core.sl.impl.SlotAllocation.modifyUnits

This has now been corrected by marking the access level as EXTERNAL.

PO01261, CEF-12424 - Performace issues when viewing all positions associated to an organization structure

Previously there was a performance issue with the page that allows a user to view the list of all positions associated with an organization structure. This issue has now been resolved.

TEC-13391 - When selecting the table name in the code table hierarchy admin screens, an application error occurs

In the Curam System Administration screens, when viewing a list of code tables in a code table hierarchy, selecting the name of the code table in the hierarchy produced an unhandled exception. This issue has been fixed.

TEC-13476 - Batch admin search sql query not working in all versions of DB2

An issue with the search facility in the Batch Processes screen has been resolved whereby searching by name or description did not work for DB2 9.5 FP6 and FP10.

Searches in this screen are now supported for all database versions supported by the Curam application.

Configuration Transport Manager

CEF-9418 - Issue with Changesets with the '&' character

Earlier, when viewing the released change set, and during importing a change set which had special characters, there was a SAX parser exception thrown, as the special characters were incorrectly being unescaped in the process flow.

This has now been corrected by using DOM APIs instead of SAX parsing, so that the special characters' escaping is preserved, and the xml is properly processed.

Finance

PO00459, CS-11618, SPMP-6039 - Creating a new bank account creates a new bank

Previously, when an administration user tried to create a new back account from New Bank Account link in the Financials shortcut, the New Bank page was incorrectly displayed. This issue has been resolved by updating the New Bank Account link to correctly direct the user to the New Bank Account page.

Cúram Modules

Service Planning

ENT-5938 - Incorrect validation message displayed on Request Milestone Waiver screen

Previously, an incorrect validation message was displayed on the Request Milestone Waiver page when a request comment was entered that was greater than 200 characters in length. The same issue also occurred on the pages used to modify, approve, and reject waivers. The correct validation message is now displayed.

Verification

ENT-6009 - Verification items are shared to target case when configurations are set such they shouldn't be shared

In 6.0.5.1 new functionality was introduced to the allow sharing of verification items with the evidence shared. This contained a configuration setting to allow the verification items to be shared only if applicable on the target case.

However, a defect existed in 6.0.5.0 which resulted in the verification items always getting shared to the target case even when this configuration setting was set. This has been fixed in 6.0.5.1 and now when the configuration setting is set to share verifications "If Applicable", the verification items are only shared to the target case when a verification requirement exists on the target case and the verification items are used by that verification requirement.

ENT-6100 - Duplicate verification items on the target case after accepting incoming evidence

Previously, when sharing verification items for shared evidence, duplicate verification items were created in some scenarios. This was because the verification items were shared based on the type of evidence being shared.

This issue has been resolved. Verification items are now shared based on the type of evidence being shared as well as the evidence attribute for which the verification has been configured.

ENT-6189 - Apply the Verifications extension mechanism to Product Delivery cases

Previously we delivered a change which allows Verification requirements to be extended beyond the support we offer OOTB. A set of technical steps were provided which outlines what must be done to extend support, as described below. We have now adapted this approach in how we provide Product Delivery support. This therefore allows customers to customized the Product Delivery functionality to better suit their own custom requirements.

The following steps outline how a customer would extend Verifications support for a new case type:

1. Create a new VerificationType code table entry to display an additional item in the 'Applies To' drop down in the Verification Requirement Usage page (that maps to the relatedItemId value in the VerificationRequirementUsage entity).

2. Create a new search page that will be displayed on selecting this new item in the dropdown, with a list of available options to select. This selection maps to the relatedItemType value in the VerificationRequirementUsage entity. This would require creating a new UI page and configuring that as a search page in the curam-config.xml

3. VerificationRelatedTypeHook has to be implemented and the implementation should be bound with the new code table item added in step 1.

4. At runtime, the customer must be able to determine the relatedItemType attribute(mentioned in step 2), given the caseID of the case created in the application. This logic must be implemented by the customer in the implementation of another hook, VerificationRelatedItemHook and this should be bound with the CaseTypeCode for the MedicalAssistance Product.

Therefore the changes delivered was to implement ProductDelivery case type as per steps above, which allows customers to overwrite this to provide their own custom implementation, if required.

ENT-6197 - Mandatory verification error occurs when activating a PD but the verification configuration does not apply to PD type in question

Previously, when activating a product delivery (PD) case of a particular Integrated Case, in which the PD does not have any verification requirement applied to it, the system was throwing a validation message if an outstanding mandatory verification exists for another Product Delivery case linked to the Integrated Case.

Now this is resolved, and the application will allow the user to activate the product delivery if there are no outstanding verifications that are configured for the same.

ENT-6334 - VERIFICATIONITEMUTILIZATION workflow fails for Participant evidence

Previously, the expiry and warning dates were applied for the participant evidence and PDC evidence which was causing error while processing workflow. Now this issue has been resolved by removing the workflow call for participant or PDC evidence.

ENT-6344 - Unhandled server exception on View Verifications for Incoming Evidence

Previously, an unhandled server exception occurred on selecting to View Verifications from the Incoming Evidence page. This has been resolved. Verifications can now be viewed on the Incoming Evidence list page.

Supervisor Workspace

PO00828, ENT-6195 - Performance issue to list All User Cases in Supervisor Workspace

Previously, within Supervisor Workspace to list cases for all user reporting to the supervisor was experiencing performance problem. This was due to a read operation being called within a for loop resulting in the same sql being performed repeatedly for the same case type. This issue has been resolved by moving all the case details before the loop and populating the case list.

PO01014, ENT-6144 - Page is taking more time to load when when the number of cases are around 8000.

Previously, the modal pages in case reassignment and forward tasks screens in Supervisor Workspace were taking lot of time to load.

Now, a search filter has been introduced in Reassign Cases and Forward Tasks modals. The supervisor should be able to view the refined list of cases and tasks based on the search criteria.

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

CR00379440, ENT-6362 - Cases/Tasks are still listed for bulk reassignment/forwarding after initial selection for offline reassignment

Previously, on selecting cases/tasks for later reassignment/forwarding, these cases/tasks continued to be presented in these bulk case reassignment or bulk task forwarding list pages. This allowed the possibility for multiple successive case reassignment/task forwarding for a particular case/task. This has been fixed and now, the case/task records are filtered from the bulk case reassignment or bulk task forwarding list pages when the cases/tasks are queued for later reassignment/forwarding.

Financial Management

PO00945, CEF-12258 - Access to PaymentInstrument.modifyReconcilStatusCode()

As the entity APIs are internal, the customer was not able to access PaymentInstrument.modifyReconcilStatusCode API and update their newly added

reconcilestatus code. Now a new external facade API is introduced which will call a service layer API which will call the entity API and update the custom

codetable value.

CEF-12262 - 'Bank account reference' has been renamed as 'Bank account'

The bank account view modal displayed when selecting the sort code link from the financial transaction list has been updated as follows:

• Bank Account Reference field has been renamed 'Bank Account'
• The bank/branch status has been removed from this display as it is information more relevant to an administrator

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

CS-11200, ENT-6232 - Provide ability to apply a deduction to a reissued payment

A few feature has been introduced where in a user can reissue a cancelled payment by creating a deduction against the payment to reduce the net amount issued to the client. This feature will be particularly useful in scenarios where a reduced payment needs to be reissued to a client after the period in question has already been reassessed and invalidate payment cannot be used.

Payment can be reissued by either creating an applied deduction or an un-applied deduction. Reissue with Applied Deduction can be used when the deduction amount needs to be deducted from the reissued payment and applied towards an outstanding liability owed to the organization.

Reissue with Un-applied deduction can be used when the deduction amount is not applied towards any specific liability. The deduction amount can be used to make a general refund to the organization.

CS-12218, ENT-6233 - Provide extension point for changing the payment date on payment instrument

Previously, the effective date for a payment instrument was calculated by the system and there was no mechanism to overwrite this in a custom solution.

A new interface - curam.core.impl.FinancialManagerHooks and a default implementation class - curam.core.impl.FinancialManagerHooksImpl

have been introduced in OOTB. The effective date on a payment instrument which is set inside curam.core.impl.CreatePayments.createPmtInstrument(PmtInstrumentDetails) has now been moved to the new implementation class.

Customers who want override the payment date have to

1. create a new class that implements FinancialManagerHooks interface
2. provide implementation to support the desired payment date
3. bind the new implementation class in their Module class using Guice binding

For example, in their own Module class,

bind(FinancialManagerHooks.class).toInstance(new MockFinancialMangerHooksImpl());

To load their new Module class, customers should add a row to MODULECLASSNAME table in the database using a custom DMX file. More details can be found in chapter 5 of Persistence Cookbook guide.

By default, OOTB implementation will be called. After the new implementation class is bounded, it will then be called.

Evidence Broker

CEF-12032 - Brokering of non-identical evidence not occuring when identical evidence exists specifying 'All' Evidence Types

Previously, the sharing of non identical evidence did not happen as expected when the following configuration was in place:

i) evidence sharing was configured for specific evidence types for both identical and non-identical evidence

ii) evidence sharing was configured using the "All" evidence types option, for identical evidence

The issue was that the "All" evidence types configuration for the sharing of identical evidences took priority and any further configurations were ignored.

This has been fixed now.

CEF-12565 - Allow custom processing override the filtering of closed cases during evidence brokering

When evidence is broadcast via the Evidence Broker, a filtering mechanism is applied to remove closed cases from the list of cases considered during the brokering process. When evidence is being 'pushed out', as in the activation of evidence on a case, closed cases are removed from the list of target cases. When evidence is being 'pulled in', as will be the case for new participants being added to an integrated case for example, closed source cases are removed from the list. The closed case check has been enhanced to also include the result of a call to a custom hook, EvidenceBrokerHooks.canClosedCaseBeIncluded, to see if certain closed cases should be included. This is done specifically for the situation where evidence is being pulled in from source cases for case participants being added to a case as some scenarios exist in Intake processing where evidence must be shared from a closed Application. The default implementation of EvidenceBrokerHooks.canClosedCaseBeIncluded returns false.

Intelligent Evidence Gathering

TEC-13110 - Progress Bar rollover text not localized

IEG provides an optional progress bar which allow a user to see how far through a script they have progressed. The text which appeared when the user moved the mouse over the progress bar was not localizable. This text now uses the localizable property "progress.bar.text", this property was already used for the text displayed on the progress bar.

TEC-13304 - Contextual Page Titles

Previously when an IEG script was executed in Universal Access, the Page Title displayed in the banner at the top of the page was not updated as the script progressed. and hence did not provide context for the user. This behavior did not meet accessibility requirements as the window/browser tab title should be contextual. IEG can now be configured to update the the title of the window/browser tab where IEG is running with the current Page Title of the IEG script. To support this the following configuration property has been introduced:

set.window.title.to.page.title

By default, this is set to false. When set to true, the current page title is used as the window/browser tab title.

TEC-13305 - Person Tab images do not provide alt text.

Previously, the images in the IEG persons tab did not have alt text associated with them. This caused an accessibility issue. These icons now have configurable alt text which resolves this issue.

To facilitate this, the following translatable properties and their default values have been added to ieg-config.properties:

persontabs.adult.male.alt=Adult male

persontabs.adult.female.alt=Adult female

persontabs.child.male.alt=Male child

persontabs.child.female.alt=Female child

persontabs.unknown.person.alt=Unknown household member

persontabs.current.person.alt=Current household member

TEC-13306 - Validation messages not read by screen readers

IEG supports validations for the fields on a page. If a page is submitted and these validations fail, a validations panel is displayed to provide the details of the validation issues. Previously focus was not given to validation panel, rather the first field with a validation issue was given focus. This caused an issue when using a screen reader as the validation messages were not read to the user. Focus is now given to the validations panel and the validation messages are read by the screen reader.

Player

TEC-12576 - Filtered select for codetable drop-downs.

In the previous version of IBM Cúram Social Program Management, drop-down selects in IEG Scripts in Universal Access did not allow a user to select an entry by typing the first letter of the value they required. This presented a usability issue in cases where a large number of choices were provided. In this version of Cúram, IEG scripts in Universal Access use a filtering select. A filtering select allows users to type in text, this text is used to filter the contents of the dropdown.

PO00999, TEC-13387 - IEG Page Titles images do not require alt text

In IEG an image can be displayed alongside the Page Title. Previously this image provided alt text. As this image is purely decorative, this alt text is not required and has been removed.

Provider Management

Contract Management

PO01026, ENT-6245 - Payments for provider flat rate contracts with weekly payment frequency not being made correctly

Previously, when a flat rate contract with a weekly or bi-weekly frequency and a regular payment amount was activated for a provider, the payment generated for the contract week was incorrect. This issue occurred due to time zone issues that were causing the system to retrieve an incorrect date for use in processing, and has now been resolved.

Attendance Tracking

PO00757, ENT-6042 - Roster generation not correctly using the current attendance tracking configuration

Previously, when multiple attendance tracking configurations with different roster generation frequencies were created for a service offering, the system was not sorting the configurations correctly and was using a superseded configuration during roster generation. The roster now gets generated correctly using the active attendance tracking configuration.

Miscellaneous

ENT-6081 - Fields missing on Transfer to Provider screen

Previously, the following fields that are displayed on the Enroll Provider screen were missing on the Transfer to Provider screen:

1. Accept Citizen Referral
2. Reservation Grace Period
3. Areas Served
4. Client Information
5. Service Enquiry Method

These fields have now been added to make the Transfer to Provider screen consistent with the Enroll Provider screen.

PO00864, ENT-6124 - Application error displayed when viewing provider member created by registering a provider as a person

Previously, when a user created a provider member by registering a provider as a person on the Provider Home page an application error was displayed when the user then attempted to view the provider member. This issue has now been resolved.

PO01058, ENT-6265 - Addition of new provider category results in the opening of a duplicate tab

Previously, adding a new category for a provider resulted in a duplicate provider tab being opened due to an unnecessary link that was present on the new category page. This issue has now been resolved.

ENT-6342 - IBAN and BIC fields missing from Transfer to Provider screen

Previously, the Transfer to Provider screen was missing the IBAN and BIC fields that were introduced to support payment to foreign bank accounts.

The screen has now been updated to include these two fields.

Provider Self Service

ENT-6106 - Issues with e-mail notifications for providers and provider groups

Previously, an error was occurring when the system attempted to send e-mail notifications to providers or provider groups that signed up for self service or forgot their password. This was an issue on WAS v8 onwards due to a space being incorrectly passed into the bcc and cc fields, and has now been resolved.

using Curam Provider Management External Portal an email notification containing password information should be sent, instead an error message 'an error occurred when sending an email' was displayed. This was because a 'space' getting passed in bcc and cc fields. This was an issue on WAS v8 onwards.

Now this issue is resolved by passing empty values to the bcc and cc fields.

PO00939, ENT-6186 - Interface defining the email address used to send an email to a new external user should be marked as external

Previously, the interface curam.externaluseraccess.impl.ExternalUserEmailAddressStrategy that defined the email address used to send an email to a new external user was marked as INTERNAL. To allow customization of the default email address set, the interface and the method that defines the email address has now been marked as EXTERNAL.

ENT-6202 - Prevent account lock out on provider self service application for non-secure external users

In the provider self service application, log-in functionality has been enhanced to prevent an account from getting locked out for non-secure external users, if the number of log-in attempts with an incorrect password exceed the allowed threshold.

This will ensure that external public user accounts will never be locked out.

ENT-6251 - Address formats missing from CPMExternalSecure application

Previously, address formats for a number of locales were missing from the CPM External Secure application resulting in application failures.

Missing address formats and domain plugins have now been added to resolve this issue.

PO01032, ENT-6255 - Error occurring when attempting to record attendance using the external provider self service application

Previously, when a user attempted to view daily attendance information using the external provider self service application, an application error occurred in the situation in which the entry of hours was enabled for the associated service offering. It is now possible to view the daily attendance information without error.

PO01123, ENT-6299 - Unhandled server exception when viewing roster line item history via provider self service application

Previously, when a user tried to view the roster line item history details page using the provider self service application, an unhandled server exception occurred. This issue has now been resolved and the history details can now be viewed.

Business Intelligence and Analytics

PO00622, CS-10878, ENT-4929 - Provide a configuration option to turn on/off BIRT connect test

Previously, the BI configuration test performed a connect test to ensure any BIRT KPI's could connect to the Data mart schema. This test is now configurable, and can be turned off by setting the 'environment.birt.testconnections' property within the BIApplication.properties file (also refer to BIApplication.propertiessampleora).

Setting the property to true raises an informational message if the connection properties are not sufficient.

PO00289, CS-11687, ENT-5782 - Issues executing the case ETL against large data sets

Previously there were performance issues encountered with the DW_CASE_TRANSFORM_ETL ETL when executed against large data sets. These issues have now been resolved.

PO00620, ENT-5951 - Ensure case owner data is extracted incrementally

Previously the staging ETL process was not using an available "last written" column to extract case owner data incrementally and therefore all case owner data was extracted every night, resulting in more data being reprocessed than necessary and causing the ETL batch run to take longer to complete.

The following ETL's have now been updated to include the new column so that the case owner data is now extracted incrementally:

- S_ORGOBJECTLINK_ETL

- S_CASEUSERROLE_ETL

ENT-5997 - Ensure removal reasons are logically deleted rather than physically deleted

The Oracle data warehouse has been changed to logically delete removal reasons, rather than physically deleting them, as physical deletes are not permitted.

The data warehouse also now stores old removal reasons that have been deleted from the application.

The following two columns have been added to the CCS Oracle and DB2 Models, DDL, and OWB Meta Data:

- DWRECORDSTATUSKEY has been added to the Table DW_CCSREMOVALREASON

- RECORDSTATUSDESC has been added to the Table DIMCCSREMOVALREASON

The following OWB ETL's have been modified to populate the new columns:

- DW_CCSREMOVALREASON_DELETE_ETL

- DW_CCSREMOVALREASON_ETL

- DM_DIMCCSREMOVALREASON_ETL

PO00963, ENT-6150 - Ensure changed data capture dates are always updated

Only changed data should be extracted during daily/nightly batch runs of the Business Intelligence ETL processes. In Oracle Warehouse Builder there exists a "Max Warnings" threshold (this is set to 50) within an ETL process. Previously if the number of warnings was less than the "Max Warnings" threshold the ETL were marked as completed successfully but the Changed Data Capture dates were not updated. This was an error. This is now resolved and to ensure that all ETL processes are correctly flagged as either successful or failed, a new standard has been introduced and a zero tolerance to errors and warnings has been enforced. The BI build process now sets the "Max Warnings" property to zero for all ETL processes. This is set during the import process.

Please review any of your custom ETL processes which may now fail.

Two new build commands have been introduced to assist with this:

1. build owb.etl.runtime.check - This command reports an error if the max warnings threshold is zero. The base value can be overridden at build time using –Denvironment.owbconfig.maxnumberoferrors=0

2. build owb.etl.runtime.set - This command sets the value of the max warnings threshold to zero, the base value can be overridden at build time using –Denvironment.owbconfig.maxnumberoferrors=0

ENT-6155 - Errors returned when importing tables into OWB

DW_CFSSPLACEMENTS is a CCS Table, which was incorrectly included in the Core central.mdo file.

It has now been removed.

ENT-6259 - Incorrect target table loading properties specified in DM_UPDATE_FACTCP_MASTER_ETL

Previously the target table loading properties in DM_UPDATE_FACTCP_MASTER_ETL were incorrect and were loading all data. This has now been resolved.

The PERSONHISTORYKEY column in DM_FACTCASEPARTICIPANT has been changed to 'Match Column when Updating Row' only.

PO01134, ENT-6339 - Incorrect Join condition on DM_DIMRECURRENCE_ET

The Join condition in the following datamart ETL (DM_DIMRECURRENCE_ETL) has been updated to this:

DM_ETLCONTROL.TARGETTABLENAME = 'DM_DIMRECURRENCE' AND

DM_DIMRECURRENCE.LASTWRITTEN >= DM_ETLCONTROL.LAST_ETL_DATE

The Loading Properties on the Target Table Columns in the ETL have also been modified to match on Code when updating.

Appeals

ENT-6231 - Appeals analysis of resolve scripts for problems related to "HTTP Response Splitting"

Jsp scriptlets which redirect to another page were vulnerable to attack if a malicious user tried to split the URL using carriage return or line feeds. Unlike some application servers, Weblogic does not appear to provide any protection against this problem. Parameters are now sanitized correctly prior to use in these situations.

Universal Access

GUM-3487 - Inefficient storage of the motivation result causes poor performance

There has been a change to the way Motivation results are stored and retrieved. This change leads to much improved performance in this area. This improvement necessitated a change to the way Motivation Results are stored. As a result of this change, existing Motivation Results records created using previous versions of Universal Access can no longer be displayed. Please seek assistance from IBM technical support if this is an issue.

GUM-3510 - Text for Username and Password missing from Universal Access Home page

Previously, Username and Password text was not displayed on the Log into your Account panel. To make it easier to identify the Username and Password fields, this text has now been added.

GUM-3746 - Version of Google Maps API used with the Citizen Workspace to be retired on 19 May 2013

Previously, the Google maps displayed within the Citizen Account were loaded using the Google Maps v2 JavaScript API. This API is deprecated and on 19 November 2013, all applications requesting v2 will be served a wrapped version of the v3 API instead.

To avoid any potential issues that the wrapped v3 API may introduce, all Citizen Account pages that display a Google map have been updated to load using the Google Maps v3 JavaScript API.

GUM-3763 - Program Status of the application is displaying as blank for submitted application

Previously, the Program Status of an application submitted in Universal Access was displaying blank. The status is now correctly displayed on the My Applications page.

To recreate:

1. Create an account in the Citizen Portal and submit an application.
2. Without logging out, navigate to the Universal Access Home page.
3. From the Home page, click the Apply for Benefits button.

The My Applications page is displayed. The Program Status field is no longer blank.

GUM-3793 - Implement infrastructure to allow customer to add language picker to custom landing page

A new renderer has been added to CitizenWorkspace to facilitate customers adding a language picker to a custom landing page, citizenworkspace.renderer.landingpage.LanguageSelectRenderer.

The render() operation programatically creates a HTML SELECT element in javascript and adds it to the DocumentFragment object passed to the operation.

Customers wishing you use this functionality need to do 2 things:

1. Ensure that the render() operation is called as part of their custom renderer.
2. Add a "div" element to their landing page with the id of "selectLang" e.g. <div id="selectLang"/>. The DOJO infrastructure will populate this div with the language dropdown data. It is up to customers to position and/or style the SELECT element to meet their requirements.

One thing to note is that the new renderer expects that the Field object passed to it will contain an XML document that contains the following XML structure:

<languages>

<language display-value="English" value="en"/>

<language display-value="Italiano" value="it"/>

...

</languages>

If the renderer cannot find this structure, then it will simply return and the HTML select element will not be created.

Administration

GUM-3772 - Update renders to correctly load Google Maps API

The Google Maps API used within the Cúram application has been updated from v2 to v3 as the v2 API is to be retired on the 19th November 2013.

Google Maps Key

Previously, to use the v2 Google Maps API it was required to obtain a key from Google. The following keys types are available: public, premier. These were stored in the system properties, ENV_CW_GOOGLE_MAP_LICENSE_KEY, and ENV_CW_GOOGLE_CLIENT_ID.

With the v3 update, a key is still required. The following types are provided: public and business. The business key replaces the premier key.

Within the application, the properties used to store the v2 key values (ENV_CW_GOOGLE_MAP_LICENSE_KEY, and ENV_CW_GOOGLE_CLIENT_ID) have been reused and now store the v3 key values as entered by customers.

Note that a customer must at least supply a public key for the use of Google Maps. As a result, the properties are expected to hold the following values:

ENV_CW_GOOGLE_MAP_LICENSE_KEY

The v2 key (pre 6.0.5.1) is public

The v3 key (6.0.5.1) is public

ENV_CW_GOOGLE_CLIENT_ID

The v2 key (pre 6.0.5.1) was premier

The v3 key (6.0.5.1) is business

Additionally, the property 'ENV_CW_ENABLE_HTTPS_GOOGLE_MAP' is no longer required. It was used to switch the loading of the Google Maps API to use a SSL connection (a premier key was required for this). v3 of Google Maps permits the loading of Google Maps API through SSL as a standard option. As a result, this property is no longer required and is no longer part of the default flow of the application when loading the Google Maps API.

Solutions

Income Support

CGISS-6161 - Future program authorization should be supported at the integrated case level

Program authorization is now supported at the integrated case level without the requirement for an application being present. The user may initiate eligibility checks from the integrated case and authorize the result, creating a new product delivery if the family unit is not already in receipt of the program being authorized.

The future authorization of a result from the integrated case is now supported. The environment variable "curam.isproduct.checkeligibility.futureauthorizationmonths" controls the number of months from the application date that the result can be authorized in the future. By default the value is 2, so the results which are eligible in the current month and next month will be available for the user to select to "Authorize" or "Apply Update".

PO01298, CGISS-6233 - Participant name incorrectly displayed in the 'Placed By' and 'Application Filed By' fields

Previously the 'Placed By' and 'Application Filed By' fields incorrectly displayed the name of the participant in the medical institution. If 'other' is selected and details are entered for 'Placed by' or 'Application Filed By', when the record is viewed, the field 'Placed By' should display the name of the participant recorded as placing the participant in the medical institution. The field 'Application Filed By' should display the name of the participant recorded as filing the application.

This issue has been resolved and both fields now display the correct name.

CGISS-6259 - An exception occurs when an application is submitted with a postal code in the incorrect format

Previously, applications failed to submit and an application exception error occurred if the postal code was entered in an incorrect format. Postal codes must be entered in either of the following: a five digit format, e.g., 'xxxxx', or a nine digit format, e.g., 'xxxxx-xxxx'.

A validation is now displayed to inform the user that this format is required. Submission of an application with postal codes using an incorrect format is prevented.

Cash Assistance

PO00322, CS-11608, CS-11382, CGISS-3887 - Cash Assistance Federal Time Limit

The federal time limit processing has been implemented for Cash Assistance. The Federal Time limit rules impose a lifetime limit of 60 months on a family's receipt of federally funded Cash Assistance. The time limit applies to adult household members, including a minor parent who is a head of household. Children are exempt from the federal time limit regulations. A household in which any adult member, including a minor parent who is the head of household, has received federally funded Cash Assistance for 60 countable months is ineligible for benefits unless an exemption or extension has been granted.

A countable month is one in which an adult household member or a minor parent head of household is either an eligible or excluded household member and does not have an exemption for the month. Partial months are considered countable months unless the initial payment is less than $10 in which case the assistance unit is eligible but no payments are made and the partial month is not countable. An exemption is a circumstance under which a month of assistance does not count in determining whether a family has reached the time limit. An extension is a circumstance under which assistance may be continued even though the family has reached its time limit. The total number of months for which Cash Assistance is received for an adult household member or a minor parent head of household is a cumulative total of the countable months of Cash Assistance received in the current state and other states.

Federal Time Limit Tracking Out of State Months

The Countable Assistance Period entity records the months for which Cash Assistance has been received in other states. This evidence is now implemented as a new dynamic evidence entity on the Income Support Integrated Case. The Countable Assistance Period evidence can also be recorded at the Person Level. All Income Support rules have been updated to use the new Income Support Countable Assistance Period entity.

Countable Assistance Period evidence is shared between the person and the integrated case using the Evidence Broker functionality. Where a household member is on multiple integrated cases, the Countable Assistance Period is shared across all the integrated cases. For more information on Evidence Broker see the Curam Evidence Guide.

By default, Countable Assistance Period evidence is configured to be automatically accepted from the integrated case to person and is non-automatic from the person to integrated case. This allows the caseworker to decide whether or not the evidence on the integrated case is updated.

Countable Assistance Period Entity

The Countable Assistance Period entity attributes are defined the same as the previous Countable Assistance History entity.

countableAssistancePeriod

evidenceID

caseParticipantRoleID

numberOfMonths

state

programType

startDate

endDate

comments

The previous Countable Assistance History entity will no longer be displayed to the user on the evidence dashboard within the Income Support integrated case. If the old entity is required, it can be configured back onto the required case. This can be achieved through the Cúram Administrator Application. Select 'Case', then select the case type to configure. Then select 'Evidence Types' and the action 'Add Evidence'. For example select a case type of integrated case 'Income Support' to configure evidence types on that case. Select to add Countable Assistance History. The new version of the entity, Countable Assistance Period should be removed if not required from the list of evidence types on the case.

Federal Time Limit Tracking Current State Months

The system automatically determines when a month of Cash Assistance received in the current state is counted towards the federal time limit. Where a household member is on multiple integrated cases, the months received in the current state are shared across all the integrated cases. Countable months in the current state are recorded using a new entity called Receipt Period. The entity attributes are defined as follows:

uniqueID

caseID

personID

program

startDate

endDate

Federal Time Limit Views

It is possible to view the time limit details for Cash Assistance on the person, integrated case and product delivery.

• Person

At the person level, the user can view the total months received, the total months remaining and whether a current exemption or extension exists. The total months received is a total of out of state months (this could be across multiple integrated cases) plus total months received in the current state (this could be across multiple integrated cases). The total months remaining is 60 minus the total months received. A further breakdown of the total months received shows the total months received in the current state and total months received in other states. The total months received in the current state provides a link to the integrated case home page.

• Integrated Case

At the integrated case, the user can view the summary details including total months received, total months remaining and whether a current exemption or extension exists for all household members who are on the integrated case and are subject to the federal time limit requirements. It is possible to drill down from the summary view to see the expansion of the person's details, which include total months received in the current state and total months received in other states. The total months received in the current state provides a link to the integrated case home page.

• Cash Assistance Product Delivery

At the Cash Assistance product delivery, the total months received for each individual is displayed on the home tab. The total months received is the total of out of state months (could be across multiple integrated cases) plus total months received in the current state (could be across multiple integrated cases). The time limit progress bar indicates how many months a person has received and the number is displayed in text beside the progress bar. If time limits do not apply to a member such as a child the progress bar is not displayed and the text 'Federal Time limit does not apply' is shown.

Evidence Change Triggering Automatic Check Eligibility

When a household is in receipt of Cash Assistance, any change made to the Countable Assistance Period, Exemption or Extension details will trigger automatic check eligibility as a change to any of these evidence types could cause the assistance unit to be ineligible. For example, a change to the Countable Assistance Period could result in an increase to the total months received and could cause ineligibility if, as a result of the change, the total months received exceed the time limit of 60 months. Similarly, if exemption details are updated by editing existing Exemption details or removing Exemption details, the total months received will increase which could cause ineligibility.

Medical Assistance

HCR-1329 - Pregnant Woman Post-partum logic

All information entered by an applicant for the Insurance Affordability programs related to a pregnancy is now being mapped appropriately to evidence on the application (and ultimately the integrated) case. As a result, Medicaid rules around eligibility as a pregnant woman during the post-partum period should now be working as expected.

HCR-2124 - 3 residential address verifications appearing for one person

Previously, where multiple people on an Insurance Affordability application lived at the same address as the primary applicant, and that the residency could not be verified electronically, multiple outstanding verifications were showing up on the application case. This has been corrected so that only one outstanding verification is shown for each separate address.

HCR-2128 - Internal Insurance Affordability Application

An internal application has been configured in the system to allow case workers to initiate applications through the standard case worker application view. To use this feature, the worker must first register either a person or a prospect person in the system and will then have an option on the actions menu for that person called 'New Application Form'. This will run a modified version of the Insurance Affordability application script and result in an Insurance Affordability application case created upon completion of the script.

HCR-2195 - Optional Verifications on the Insurance Affordability application case

As initial support for the federal rules around inconsistency periods, the conditional verification requirements for evidence on the Insurance Affordability application case type have all been made optional. This allows case workers to authorize an application case which has outstanding verifications, thereby allowing an integrated case and the appropriate product delivery cases to be created. In addition, waivers have been added to the appropriate verifications on the integrated case so that product deliveries can be activated with outstanding verifications while the waiver applies.

It is our intention to further enhance this area in a future release though the use of milestones to initiate activities on or before the end of the inconsistency period.

HCR-2196 - Exceptions to lawfully residing aliens on who the 5 year bar to enroll in medicaid applies

As part of the Insurance Affordability rules, the 5 year bar from enrolling in Medicaid was previously applied to all lawful aliens who have resided for less than 5 years in the country. In this release, the rules have been updated to cater for exceptions to that rule included in the latest federal guidance. These exceptions include veterans, pregnant women and individuals under age 21 who would be exempt from this 5 year bar for enrollment in Medicaid.

In order to support this, changes have been made to the application script so that people who are indicated to be lawfully present are asked questions about whether they are a veteran or the spouse/dependent of a veteran.

HCR-2203 - Separate Application Types for each type of Insurance Affordability application

Applications for exemptions, for employer-sponsored coverage and for using the exchange without assistance have been separated out from the insurance affordability application case onto their own application case types. These case types are configured with the specific evidence types and verifications required by those applications. All these new application types still map onto the one Insurance Affordability integrated case.

HCR-2219 - Implement 2013 FPL limits

The Insurance Affordability rules have been updated to use the 2013 Federal Poverty Levels (FPL) instead of the 2012 levels. The new values are as follows:

Household Size = 100% FPL

1 = $11,490

2 = $15,510

3 = $19,530

4 = $23,550

5 = $27,570

6 = $31,590

7 = $35,610

8 = $39,630

>8 = Add $4,020 for each additional person

HCR-2249 - Mapping of Address information from Insurance Affordability applications to Person Evidence

Address information provided by an applicant as part of an application for the Insurance Affordability programs is now mapped to person evidence for that applicant and all other people included on the application, as well as being mapped to the address evidence on the application case itself. Previously, a default 'address unavailable' record was created as evidence for each person.

HCR-2291 - ESignaturePage updates

The pages displayed when a client clicks the 'Submit Application' button in Universal Access for an Insurance Affordability application have been updated to capture e-signature consent and renewal details before submitting the application and displaying a reference number to the client.

HCR-2351 - Handling of tax exempt income

Income calculations performed as part of the Insurance Affordability rules and script have been updated to better capture tax-exempt portions of income. This is important as it gives us an accurate representation of gross income and how it is built up to Adjusted Gross Income (AGI) before the tax-exempt portions are added back in to give a MAGI income total for an individual - the program display rules highlight this on the Income tab. Tax-exempt portions of income are captured for Interest, Social Security Benefits and Foreign Earnings. However, there are varying types of Interest, some of which are entirely exempt from tax, such as municipal bonds, and some of which are taxable. As a result we have separated the Interest income type into -taxable Interest and tax-exempt interest. Both are counted in the MAGI determination, but only the taxable interest type is counted initially in the GI. The implementation for Social Security benefits and Foreign Earnings hasn't changed - when either income type is entered, we identify how much of that amount is tax-exempt - again the tax exempt amount is excluded from the GI total but included in the MAGI total for an individual. We don't list these as distinct income types (as we do for Interest) as their tax-exempt portions are identified above a certain threshold for the same income type.

HCR-2360 - Non applicant not being included in financial unit

Previously, income earned by non-applicant members of the household who are tax filers was not being included properly in the household income for applicants. This has been resolved in this release.

HCR-2368 - Provide Check Eligibility option on Application Case

The Insurance Affordability application case type has been configured to include an option for a case worker to run an eligibility check using the evidence currently in edit on the case. Each time an eligibility check is performed a new row is added to the 'Eligibility Checks' page which can be expanded to show which members of the household are eligible for each program.

HCR-2370 - Income above 400% FPL - add in the tobacco usage question

Previously, if an applicant for the Insurance Affordability programs was had household income of greater than 400% of the Federal Poverty Level (FPL) they would not be asked any program-specific questions as part of the application script and therefore the system would assume that they are not a tobacco user. This has been corrected by ensuring that the tobacco usage question is asked for anyone who is eligible to use the exchange but not eligible for MAGI Medicaid or CHIP.

HCR-2382 - Case Relationship records not being created between IC and PD

Case Relationship records will now be created between Integrated Case and Product Deliveries that are created by HCR.

HCR-2403 - Residency - Handling Temporary Absence from the state

In order to support the requirement that individuals who are temporarily absent from the state with an intention to return back should be considered state residents for the purposes of Insurance Affordability determinations, an extra conditional question has been added to the Insurance Affordability application script. If the address or state residency details provided for an applicant indicate they are not living in the current state/exchange service area, they will be asked whether they are living outside the state temporarily and have intentions to return.

The Residency rules now have an additional condition to handle temporarily absent individuals and will consider such individuals as state residents to deem them eligible for the Insurance Affordability programs.

HCR-2409 - Add implementation to pass attribute values for county, state, zip and tobaccoUser to exchange isShopMember.

Added implementation to pass attribute values for zipcode, county, city, tobaccoUser to exchange for EmployerSponsorCoverage isShopMember.

HCR-2438 - EmployerDetails and Subscriber IDs added to EligibilityAndDemographicsDetails Web Service

The 'EligibilityAndDemographicDetails' Web Service has been updated with the addition of 'EmployerDetails' containing attributes 'employerID' and 'coverageStartDate'. The 'EmployerDetails' are retrieved from the related motivation result selected via the result page action of EmployerSponsoredCoverage

The attribute subscriberID has been added to Person. The subscriberID is the the personID of the primary member for all persons.

Two functions have been deprecated from HCR-VOB\EJBServer\components\HCROnline\source\curam\healthcare\impl\Statics.java 'isShopMember' and 'isShopMemberNoPlanManagerAvailable'.

HCR-2491 - Employer attribute employerID type updated from primary key to IEG_INT64 in HealthCarePortalDatastoreIEG.xsd

On insert of the Employer entity record to the HealthCarePortalDatastoreIEG the employerID value is updated to the employerID returned from an external system. This value was overwritten on the insert as the primary key of the Employer entity is auto generated. The employerID was changed to IEG_INT64 and is no longer a primary key on the Employer entity. As a result of this change the employerID assigned to this field is no longer overwritten.

HCR-2493 - Support for different plan selection actions within employee flow

Support for 'Save and Exit', 'Cancel', 'Resume' and 'Finish' operations related to plan selections has been added to the flow for employees seeking to use their employer-sponsored coverage.

HCR-2494 - TaxFilerRelationshipList and TaxFilerRelationship attributes added to EligibilityAndDemographicDetails Web Service

The 'EligibilityAndDemographicDetails' web service has been updated to include tax relationship details of a Person. A 'TaxFilerRelationshipList' has been added to 'Person' where its 'TaxFilerRelationship' has attributes 'relatedPersonID' and 'taxFilerRelationshipType'.

The current implementation does not contain the logic required to populate these values - it is our intention to provide this in a future release.

Child Services

CFSS-5471 - Deleted provider specialities still being presented on the provider's details page when accessed from Child Welfare placements

Previously, if a provider's specialty record was deleted, it would still be presented as a valid specialization for the identified provider. This has been addressed by filtering out deleted (or canceled) specialties for a provider.

PO00880, CFSS-5754 - The investigation due date is defaulted to +60 days on the Investigation context panel

Previously, the Investigation Due Date displayed on the context panel of Investigation was always calculated as 60 days from the Approval Date of the Investigation irrespective of the due date offset (number of days) set at the application property "curam.ccs.investigation.recommendation.duedate". This has been corrected whereby the Investigation Due Date is calculated based on the application property.

PO01037, CFSS-5785 - The intake graph on the supervisor's dashboard is not populating correctly

Three issues have been resolved with regards to the Intake Screening Rates graph:

1. Previously, the Intake Screening Rates graph only listed approved intakes. It has been updated to include both approved and submitted intakes.
2. Previously, the Intake Screening Rates graph would include all Intake Types irrespective of the intake type selected by the user in the search criteria. The graph has been corrected and now displays results based on the intake type selected.
3. Previously, there was no link to the Intake Details list page from the Intake Performance graph. The graph has been corrected to allow the user to access the corresponding list page via a hyperlink in the graph.

PO01054, CFSS-5788 - Contact Logs page takes too long to load

Previously, accessing the Contact Logs page in an Ongoing Case or Investigation would result in performance issues because of an inefficient SQL query. This issue has been addressed by simplifying the SQL query used to load the Contact Log details when accessing the page.

CFSS-5816 - Not able to create an allegation on a z/OS environment

Previously, the database connection failed when the user attempted to create allegations from an intake or investigation on a z/OS environment. This issue has been resolved and the user is now able to create an allegation from the intake or the investigation.

CFSS-5819 - The Intake Screening Rate graph displays incorrect information

Previously, the intake screening rates graph did not display any data in locales other than English. This was because the system processing for the graph presentation of intakes searched for a month name that matched the English spelling for that month.

This issue has been resolved by ensuring that the system displays the intakes for a particular time frame irrespective of whether the abbreviations for the month names match the English spelling or not.

Back to top

Known Issues

Cúram Enterprise Framework

Integrated Case Management

It will be possible to create an identification evidence (for person/prospect person evidence) of the same type and ID for another participant because there is no validation to check for duplicate identification records outside of a case. However, if the identification evidence is configured at the case level, this validation will be applied to participants within the case.

In order to check for any possible duplicates, the person search page allows for search on an identification ID (of any type). If more than one person is returned in the search, they may have the same ID as another person/prospect person in the system. This would be the work around until this issue is resolved.

Note subject and text incorrectly displays additional text on the timezone and user along with other unrelated data. This displays on the note page for a person where the note is created as a result of merging the note from a duplicate client during the Client Merge process.

Dynamic Evidence

If an evidence type designed with a related case participant attribute set to 'allow modification', has an empty value and property set to 'multiple', an issue occurs in the following scenario:

When a user is editing an evidence with this type of attribute, they are able to select a participant from a drop-down which will also include a blank value. If the user selects a participant, saves the evidence and then attempts to modify the evidence by selecting the blank value, upon save, the participant attribute is not updated - the original participant displays.

Technical Services

Currently for some business flows when an attachment is created without initially selecting a file, the system does not store a file in the Content Management System as expected. However, when the Attachment record is subsequently modified and a file is then associated to the attachment, the metadata is not being stored correctly.

Online validation and publication of a CER ruleset can fail with an out of memory exception when a large number of rulesets are present on the system. The issue occurs because all available rulesets have to be included in the validation processing due to a limitation in the way ruleset inter-dependencies are currently identified. For customers who experience this issue, increasing the java heap size and/or switching to a machine running a 64bit OS may allow the validation/publication to complete successfully.

The tooltip feature for flex charts has been turned off as the text value is not displaying correctly for all supported languages.

The use of the RAM directory may return deleted records in search results. This can be resolved in a development or testing configuration by restarting the Search Server process. Please note, the RAM directory is not recommended as a deployment configuration.

The Generic Search Server DoSearch function identifier has been disabled. Access to search data may still be controlled via access to the application operations that invoke GSS searches.

In the CER Editor, when a rule set is validated, the CER infrastructure validates it against all the other rule sets in database on which the rule set is dependent on or has the references in them, and returns the errors and warning messages for all rule sets. These messages are not filtered.

The GSS startupSearchServer command may fail sporadically with the following error on WebSphere Application Server: "com.ibm.ws.naming.util.InvalidObjectException: Some object reference in the name "searchejb/EJBMethodHome" relative to the context is invalid".

To avoid this issue, please restart WebSphere Application Server following GSS deployment, before starting GSS using the startupSearchServer command.

The GSS "runPersist" target currently fails, if the file index location is not set for all supported index types.

Before persisting the index on to the database, the "runPersist" target internally persists the index into a temporary file system using FILE index type. So, if the file index location is not set by setting the property "curam.searchserver.file.index.location", then the runPersist target will fail.

To work around this issue, set the property "curam.searchserver.file.index.location" to a temporary file location before running the "runPersist" target for all supported index types.

Application Development Environment

An issue exists in the modeling environment whereby if a non-standard operation's SQL statement needs to include the same attribute of the struct in the SQL statement's INTO and WHERE clauses, then the same struct cannot be specified as the operation's return type and argument type. To avoid this issue, the SQL statement must use two copies of the same struct with different names for the operation's return type and argument type.

The UTF-8 encoding set with Eclipse based IDEs (including Rational Application Developer) causes problems where smart quotes (i.e. curly quotation marks as opposed to straight quotes ") exist in Java files and when using the IBM JDK. When a Java file containing the smart quote is opened there will be prompted to change the encoding of the project. A work around for the issue is to remove the smart quote from the offending Java file or alternatively change the project encoding to CP-1252.

When a core VIM file is included in a customized UIM page, the Online Help application will output duplicate links in the Related Help section of the UIM page's help content. There is currently no workaround for this defect as the VIM files are core files.

When in page navigation contains conditional links, if none of the conditional links are displayed an empty tab container will be drawn on the screen. Visually this looks like an empty rectangle with a blue border.

For boolean domains definitions, the "default" domain definition option in the Cúram application model in Rational Software Architect cannot be used. For example, it is not possible to set the default value to "true" so that an on-screen checkbox is checked by default. The default is "false" and cannot be changed through Rational Software Architect.

The PROPERTY attribute of the IS_TRUE and IS_FALSE elements, used as children of the CONDITION element, requires the fully qualified property name instead of using the "short-hand" version of the name. For example, use "dtls$booleanField" rather than "booleanField". The fully qualified property names can be viewed using the generated Server Interface HTML documentation (<client-dir>\build\bean-doc\index.html).

Duplicate target connections specified on a UIM LINK element will cause a parameter merging error at runtime when the link is used. For example, the parameter "pageParameter" is duplicated below. There is currently no build time validation in place to prevent this.

<LINK PAGE_ID="SomePage">
  <CONNECT>
    <SOURCE PROPERTY="someValue" NAME="DISPLAY" />
    <TARGET PROPERTY="pageParameter" NAME="PAGE" />
  </CONNECT>
  <CONNECT>
    <SOURCE PROPERTY="someValue2" NAME="DISPLAY" />
    <TARGET PROPERTY="pageParameter" NAME="PAGE" />
  </CONNECT>
</LINK>

Within a UIM LIST, all list properties referenced by a FIELD element's source connection must belong to the same list structure. While this is documented, it is not validated by the client build process and manifests as an ArrayIndexOutOfBounds error when the page is accessed at runtime.

The Rules Decision Tree (SVG) widget does not support new line characters in the text displayed on nodes in the tree and for input data. However, instead of ignoring those characters, a JavaScript error can occur, which results in the widget not being displayed. To avoid this please ensure newline characters are not used with this widget.

Cúram provides support for configuring the start day of the week in a calendar. However, if the start day of the week is set to a day other than Sunday or Monday (e.g. Saturday for Arabic locales), the start day will always default to Sunday.

When the application attempts to report a message from a server message catalog, and that message does not exist in the catalog, the correct error is displayed which tells the developer which message could not be found. However, the error is displayed in the application server's default error page instead of the Cúram error page.

Time zone validation in the user preference editor is limited in the set of supported time zone identifiers. Previously it was possible to specify time zones in the format GMT+X or GMT-X, where X is the offset in hours, e.g. GMT+4. To specify a time zone in this format will now require pre-pending the identifier with "Etc/", e.g. Etc/GMT+. In use of time zones, Cúram recommends the use of geographical time zones, e.g. Europe/Dublin or US/Eastern, as these are daylight savings aware.

In Internet Explorer 7 and 8 if the user switches between sections, while content in the section is still loading, this can result in the presence of duplicate tabs or the display of a validation message on an incorrect tab. For example, where a validation error message is to be displayed on a tab in the originally selection section; it may display incorrectly on a tab in the newly selected section. Functionality is not impaired and refreshing the browser resolves any issues.

The Inbox provides functionality to delete multiple notifications and add multiple tasks to the My Tasks list. The confirmation dialogs that are displayed to a user performing these actions should open in a modal window. This is not currently the case due to a limitation in the multi-select widget used for these actions.

A modal dialog containing an SVG tree widget will not display any page level action sets. The workaround is to define the action set within a cluster

The file upload widget browse button will be displayed according to the browser and operating system language. As a result, the browse button text may not match the Cúram locale being used.

The curam.trace.oracle.cachehits property, used in Oracle to produce trace output describing whether the statement was obtained from a cache, is not supported with IBM Websphere Application Server.

The "javascript:" URL protocol is not supported for links in the main content area of a tab. Other standard ways of invoking JavaScript functions can still be used in custom pages, but anchor tags with the "javascript:" URL protocol should be avoided.

A file download initiated through a tab level action menu, which subsequently fails, does not report an error. To troubleshoot a file download failure, enable client logging and search the Eclipse console for errors. Alternatively, use a HTTP monitor (e.g. Firebug NET Panel) and search for failed requests to "servlet/FileDownload". Examine the response for more error information.

The PRE_CLASSPATH environment variable which is used to add JAR files to the build and deployment classpaths/packaging is also used by Oracle WebLogic Server. Entries found on this environment variable will be added to startup of the application server. This has the effect of loading classes from the System classloader which can cause issues if referring to deployed content (Application classloader).

The infrastructure build scripts unsets this environment variable when starting WebLogic Server, and it would be advised to follow this same approach during the server launch if using custom build scripts if this environment variable is not set intentionally for WebLogic Server.

On insert or edit pages, multiple visible UIM FIELD elements cannot have a TARGET connection referencing the same server interface property simultaneously. If FIELDs are contained in mutually exclusive conditional CLUSTERs, they are allowed to reference the same property because only one will be visible.

A page with this issue will display correctly. However, when it is submitted, it will result in an internal server error (HTTP code 500) being displayed.

A number of issues exist in the Agenda Player:

• Modal Dialogs have the capability to automatically adjust their height based on the contents of the dialog. However, this is not the case when running the Agenda Player in a modal dialog. In this scenario, the dialog must be given a fixed size by specifying it on the UIM LINK element which initially launched the dialog. Please refer to Chapter 5 in the Cúram Web Client Reference manual for more information.
• If any text (e.g. section label, item label) in the Agenda Player XML data contains an apostrophe, the Agenda Player will currently fail to load, and the browser screen will be left empty without any error. The workaround is to ensure that any apostrophes in the Agenda Player XML are correctly escaped.
• In the Agenda Player, the optional validation feature which allows you to skip the completion of mandatory fields is not currently available. Please design your page flow with this knowledge

UIM properties files do not support using new line escape sequences (\n) to alter the layout of screen content such as page descriptions or field labels. Attempting this may lead a runtime exception: "String literal is not properly close by a double quote". The new line escape sequence must be removed from the properties file.

The LobManager throws an SQL syntax exception when updating a table with a BLOB or CLOB field and no primary key defined.

A pipe character ("|") is not allowed as part of the value which is passed as an argument for an exception text placeholder when constructing an {{{AppException}}}.

A number of display issues exist with dynamic and static rules trees:

• Dynamic rules trees can encounter sizing issues which will result in scrollbars appearing despite the available space being sufficient to display the widget in full.
• The dynamic rules tree widget flickers when a tooltip is being displayed.
• In certain scenarios the text of the static rules tree widget can be hidden when the tree is displayed in a modal dialog. A workaround is to force a browser redraw of the tree by collapsing and expanding the cluster containing the tree.

The Type Search dialog used when creating or managing Cúram UML type-based elements will only return searched elements found in the set of currently opened models/fragments. The workaround is to open the model/fragment containing the type or find the type through the Browse tab of the dialog. This issue has been raised with Rational (PMR 61187).

The Preferences link in the application banner will be disabled in following scenario. If a search page is used within a modal dialog and the search results are displayed in that modal dialog and the dialog is then closed without loading another page. The link enables itself again on a subsequent page load.

When linking pages together using an explicit link in ACTION_CONTROL, ensure the pages have distinct page-ids, such that one page id is not a substring of the other. Not naming pages in this way can result in an incorrect look and feel appearing in linked modal dialogs.

When running the checksql target against IBM DB2 for z/OS Version 9 on z/OS you may encounter this error:

'Invalid operation: Connection is closed. ERRORCODE=-4470, SQLSTATE=08003'

This is due to an IBM DB2 for z/OS error as described here: https://www-304.ibm.com/support/docview.wss?uid=swg1PM36770

To resolve this you can perform any of the following three actions:

1. Run the runstats utility against the database; or
2. Run the checksql target remotely; e.g., from Windows pointing to the DB2 for z/OS database; or
3. Install IBM DB2 for z/OS PTF UK69340 (RSU1112).

In the administrator workspace, when the user opens a modal dialog using the shortcut panel and the current tab in focus is a CER, Dynamic Evidence or IEG editor, the dialog will not close as expected. The dialog will display blank or incorrect content.

The work around here is to close the dialog and navigate to the target of the action manually. To prevent the issue, the user should avoid having the CER, Dynamic Evidence or IEG editor open when performing any actions from shortcut panel.

An unhandled server exception occurs when a UIM file that contains a copyright outside of the PAGE element, is uploaded to the resource store as a new dynamic UIM page.

A limitation exists for the reloadextracteddata build target where it is unable reload LOB xml data to a column where the column value is not allowed to be null.

The following should be added to the datamanager_config.xml file to allow the reloadextracteddata to run:

  <target name="extracteddata">
    <entry base="basedir" name="build/dataextractor/" type="dmx"/>
  </target>

  <compositetarget name="insertextracteddata">
   <subtarget name="tables"/>
   <subtarget name="extracteddata"/>
   <subtarget name="constraints"/>
   <subtarget name="indices"/>
  </compositetarget>

Multi-byte characters can not be used when editing the Cúram input metamodel using IBM Rational Software Architect. This applies to all text fields including comments, property values and object names.

When using the FILE_EDIT widget sporadically the Word document will not open leaving a small popup window opened and the application window greyed-out. To work around the problem close the small popup window and refresh the main browser.

If a user selects a day of the month in the date pop-up widget and subsequently updates the year value, the day selection is lost and must be reselected.

Under some circumstances in wizard dialogs dropdown box contents may appear in a wrong location on the page after clicking the dropdown button. This doesn't prevent the dropdown from working.

Failing HTTP requests will appear in browser console if a tab in the application is configured with no dynamic menu or navigation items.

In Internet Explorer 7, a file download link, where the file contains double byte characters, will corrupt the name of the file when selected. The file will still correctly download and the name can be manually modified.

In Windows 7, Word integration fails in Internet Explorer if the user is logged into Windows as Administrator or if Internet Explorer is started in administration mode. In these cases, the JVM crashes when trying to access Word.

When using Internet Explorer 7 browser, an initially collapsed shortcuts panel will not display its title text. The text will be displayed once the panel is expanded and collapsed. This issue only affects the full Internet Explorer 7 browser.

While the Rules Tree SVG widget is fully functional in IE9, there are SVG errors thrown in the background when hovering the widget elements. These errors are displayed when the IE9 console is opened.

These errors are expected and related to the native implementation of SVG in IE9. However these erros do not affect this functionality.

The truncated labels on the Workflow widget blocks display in full and not wrapped when hovered in Internet Explorer 9 and above. This is related to the native SVG implementation in the latest IE versions. It does not affect the widget functionality though.

Cúram Modules

Verification

At present there is a known issue with the re-verification of conditional verifications. Every time evidence on the cases changes the dependency manager is initiated to evaluate if any conditional verifications on the case are impacted and this evaluation is stored as a new set of verifications on the case. On the verification list pages, this looks to the user that a verification is duplicated over time.

Note that the user will only ever have to process one of these, capture verification documentation once, and all verifications will change together. Likewise if expiry occurs on all verifications at the same time. So the user will not have confusion over which records is correct as they will all be the same but they will see a single verification duplicated potentially many times depending on the number of evidence modifications on the case.

Evidence Broker

Where the same Person/Prospect Person evidence is recorded on two (or more) existing cases, when a new case is created and the evidence broker is configured to share these Person/Prospect Person evidence evidence type(s) from more than one existing case, duplicate evidence records may be seen on the new case.

When configuring brokering of evidence and Person or Prospect Person is the target, setting the 'auto accept' and 'auto activate' options to 'on' may cause activation of evidence or application case authorization to fail. On a person/prospect person record, evidence is automatically accepted and activated so this setting is not required. Setting these indicators is causing the system to attempt activation after it has already been activated resulting in application authorization to fail.

Until this issue is resolved, the following work around should be in place:

The 'Auto Activate' and 'Auto Accept' indicators should NOT be set when a Person or Prospect Person is the 'target' for evidence brokering.

An issue exists in Evidence Broker when the configuration of evidence sharing for a particular evidence type is across multiple cases (>2). The same evidence should only ever be shared once to a target case but in some scenarios, duplicates of the same evidence exist. This arises where the evidence is on the Incoming evidence list on the target case and the same evidence is being shared again from a different source case.

For example if evidence sharing configured from Case A -> Case B -> Case C and also a direct evidence configuration from Case A -> Case C.

On creation of evidence on Case A, the evidence is shared to Case B. At this point the evidence is on the Incoming evidence list for Case B. Creating Case C will result in the evidence being shared from Case A to Case C. Accepting and activating the evidence on Case B, it is again shared from Case B to Case C even though this same evidence already exists on the Incoming evidence list for Case C.

This issue only applies to sharing for dynamic evidence and as a workaround, the user can reject one of these duplicates.

An issue exists in Evidence Broker when the configuration of evidence sharing for a particular evidence type is set to share across multiple cases (>2). The modification or deletion of evidence is not operating in line with the sharing configuration and not shared in the same way as evidence creation.

For example if evidence sharing configured from Case A -> Case B -> Case C.

On creation of evidence, if evidence created on Case A, it is shared to Case B. On accepting and activating on Case B, it is shared to Case C.

If the evidence is later modified/deleted on Case A, on activation this change is shared to Case B. Accepting the change on Case B does not share this the change onto Case C.

This issue only applies to static evidence and is working as expected for dynamic evidence.

When evidence sharing is configured for auto-accept and auto-activate, if any failures occur during the automation steps, the expected error handling is as follows. A notification is generated to the case owner to inform them of the problem and the evidence is shared to the target case but reverts back to the previous successful state. For example, if the auto-activate fails, the evidence revert back to in-edit, and if the auto-accept fails the evidence reverts back to incoming evidence.

As issue exists currently with the error handling and there is a scenario where a failure notification is not sent to the case owner and the evidence is not shared to the target case. This arises when evidence is configured for auto-accept and auto-activate, evidence is shared to the target case but that piece of evidence was previously shared to the target case and is also currently in-edit on the target case. In this scenario the evidence is not created on the incoming evidence list on the target case and a notification is not sent to the case owner.

Intelligent Evidence Gathering

Whenever a session timeout occurs on the "Run Script" page in IEG, an error message stating that the session has expired is displayed instead of redirecting to the logon page. The error message and the page might not be in the same language that was displayed before the timeout. This depends on the server configuration.

Business Intelligence and Analytics

The Data Warehouse ETL - DW_EDUCATION_ETL is failing to transfer any data from the staging to central education tables and is returning an invalid number error.

Cúram supports case ownership by user, organizational unit (OU), position or work queue (WQ). The current reporting model only supports reporting on cases owned by a user or OU only.

The Data Warehouse ETL - DW_CASEPARTICIPANTROLE_ETL is not extracting all the records from S_CASEPARTICIPANTROLE. This is related to the DW_CASE_ETL not fully extracting records from S_CASEHEADER and loading them into DW_CASE.

The Data Warehouse ETL - DW_CONCERNROLERELATIONSHIP_ETL is not transferring updated data correctly to the central concernrolerelationship table. For example if the relationship type is updated in the application, this information is not getting updated in the data warehouse.

The Data Warehouse ETLs DW_UPDATE_ALGCOUNTBACK_ETL and DW_UPDATE_ALGCOUNT_ETL, which both update the warehouse allegation table, are failing when run. This is after the warehouse allegation table has been successfully populated.

The Data Warehouse ETL DW_UPDATE_INV_OUTCOME_ETL which applies updates to the investigation table doesn't successfully populate the investigation table with updated data.

The Data Mart ETL DM_DIMSERVICEOFFERING_ETL is not extracting Service Offering data to the Datamart. Child Welfare placements and removals records will not contain any service offering data as a result.

The case aggregate monthly snapshot table is not being populated with monthly case load data. The Infosphere data flow "DM_AGGCASEMONTH" which populates this table is failing with an exception.

The Data Warehouse ETLs DW_CASESUPER_ETL and DW_STATE_ETL may give errors when run against a Curam Child Services (CCS) source database, depending on the type of data in the source tables.

The Data Warehouse ETL DW_CASEEVENT_ETL fails when there are 2 Reviews created on a Case, for the same day, in the source application.

When running the DM_FACTCASEHISTORY ETL it throws an integrity constraint parent key not found error.

The following IWE ETLs will raise an exception if they are run twice in succession: DW_MILESTONEDURATION,DW_CASESTATUS, DM_DIMPERSONTYPE, DM_DIMINVSUBTYPE, and DM_DIMINVRECOMMENDATION.

The staging table (S_CASEDEDUCTIONHISTORY) has an incorrect mapping into the INSTRUCTIONLINEITEM column, and is currently putting the CASEDEDUCTIONITEMID value instead of the INSTRUCTIONLINEITEM value into this column.

This also affects the DW_UPDATE_DEDUCTIONS ETL.

When running the OWB ETL's the following warnings are displayed multiple times for DM_DIMSTATUS and DW_CASESTATUSDETAIL:

ORA-00001: unique constraint (CURAMDM.AK_IDENTIFIER_2_D2) violated for DM_DIMSTATUS

ORA-00001: unique constraint (CURAMDW.AK_ID2_DW_CASESTATUS) violated

The following ETL's fail to populate their target tables with data.

Staging ETL's:

S_CODETABLEDISPLAYNAME

S_INTAKEPROGRAMAPPLICATION

Central ETL's:

DW_EDUCATION_ETL

DW_FUNDRELATION_ETL

Datamart ETL's:

DM_AGGCASEDAY_ETL

DM_AGGCASEMONTH_ETL

DM_DIMNUMOFPARENTS_ETL

DM_FACTPAYMENTS_ETL

The following issues exist in relation to errors with Java Transforms:

The DW_OUTCOME ETL is failing to run. There is a Java exception thrown for a unique constraint from CaseStatusHistoryTransformImpl.

DW_ORGUNIT_TRANSFORM_ETL fails to run throwing the following Java exception: java.lang.IllegalArgumentException: key cannot be empty'.

When running the command 'build run.datamarts.operational.aggregates' the DM_AGGCASEDAY ETL is failing due to an uncaught Java exception in CaseFactProcessTransformImpl.

The following two ETL's fail trying to insert null values:

DM_FACTPAYMENTS_ETL

ORA-01400: cannot insert NULL into("CURAMDM"."DM_FACTPAYMENTS"."ORGUNITKEY")

DW_UPDATE_DEDUCTIONS_ETL

ORA-01400: cannot insert NULL into ("CURAMDW"."DW_PAYMENT"."DWPAYMENTID")

Universal Access

Clicking the Back button after selecting a link from the default out of the box or Health Care Reform landing page within the Universal Access application displays another application banner upon returning to that landing page.

On the Results page for Health Care Reform, when the user selects the 'Submit Application' action a second time, the error message "Error.The application that you are trying to submit has already been submitted" is displayed. This error message while correctly associated with the submit application action is not cleared when the user attempts to execute another action from this page.

The error message is incorrectly persisted if, for example, a user selects the category action 'Enroll in Plan' to proceed to the 'Select Household Members' page.

The Person menu within Universal Access does not appear when a citizen logs in as part of a motivation flow. For example, as part the 'Find Assistance' process within the Health Care Reform application. Motivation functionality needs to be updated to do this. The Person menu does automatically update when a citizen logs in as part of a Screening or Intake flow within Universal Access.

The Screening BOM provided by Universal Access is currently not working. This is due to the relationship between ScreeningType and CreoleRuleSet being lost during the transport.

The ruleset needs to be inserted and activated before the Screening BOM can be used. This insertion generates a new creolerulesetid so the transported data is out of sync.

To resolve the issue the ScreeningRulesLink table will need to be extended to store the ruleset name and not just the creoleruleset identifier.

Solutions

Child Care

The Child Care solution implemented an Approve link on the Service Plan Action menu. This resulted in an additional Approve link in the action menu. Please see the post installation steps for details on how to remove the additional link.

Currently, when the IBM Cúram Child Care solution is installed, the default value for the "curam.case.owner.system.user.reference" property is set to 'ccscaseworker'. On completion of the application process, the task generated by the system is assigned to the Child Care Case Worker. When the IBM Cúram Income Support or IBM Cúram Income Support for Medical Assistance solution is installed, the default value for the "curam.case.owner.system.user.reference" property is set to 'intakeworker'. This means that on submission of an application, the case owner for integrated and product delivery cases is Intake Worker.

When IBM Cúram Child Care and IBM Cúram Income Support or IBM Cúram Income Support for Medical Assistance are installed together, related tasks and cases have an incorrect owner. For example, the case owner of integrated and product delivery cases created for the IBM Cúram Income Support solution is Child Care Case Worker. This is because the default value for the "curam.case.owner.system.user.reference" property is set to 'ccscaseworker' as the Child Care component takes higher precedence.

Customers are recommended to consider an appropriate strategy for case owner allocation.

Previously, a placement request could be canceled after being accepted. In the current release, the Cancel link for a placement request is in a disabled state irrespective of the status of the placement request. This means that a placement request cannot be canceled.

The following issue occurs when a Child Care case is created from a screening. When the Care Plan for the case is submitted, the status of the Care Plan and its associated Plan Item changes to 'Submitted'. On approving the Care Plan, the Care Plan is approved but the Plan Item is not approved.

Child Care CER rule works with Case Determination type of 'Manual Eligibility Check'. Reassessment has not been converted to CER yet.

An application error occurs while accessing the evidence for a person under person home page. This error is applicable only for demo data.

Back to top

Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law.

IBM Japan Ltd.

19-21, Nihonbashi-Hakozakicho, Chuo-ku

Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation

Dept F6, Bldg 1

294 Route 100

Somers NY 10589-3216

U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources.

IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:

your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs.

Copyright IBM Corp. _enter the year or years_. All rights reserved.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Back to top

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at http://www.ibm.com/legal/us/en/copytrade.shtml.

Adobe, the Adobe logo, and Portable Document Format (PDF), are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both.

Microsoft and Word are trademarks of Microsoft Corporation in the United States, other countries, or both.

Other names may be trademarks of their respective owners. Other company, product, and service names may be trademarks or service marks of others.

Back to top