IBM Support

IBM Cúram Social Program Management

Release notes


These are the release notes for IBM Cúram Social Program Management


Installing the Fix Pack
Supported Hardware and Software
Improvements and Resolved Issues
Known Issues


Welcome to the release.

This is a cumulative release which incorporates the Improvements and Resolved Issues contained in all previous 6.0.4 fix packs and iFixes, with the exception of iFix2 which was a restricted release for customers with entitlement to the IBM Cúram Child Welfare Structured Decision Making Add-On. Details of these Improvements and Resolved Issues are included in the release notes for each of the releases. The release notes for the previous releases and the most up to date version of these release notes are available at

Installing the Fix Pack

Fix Pack Pre-Installation Steps
Fix Pack Installation
Fix Pack Post-Installation Steps


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

Fix Pack Pre-Installation Steps

Prior to running the installer please ensure all files in the Cúram Installation directory are writable.

Pre-Installation Step for Spell Checker Component

This pre-installation step is always required before installing Cúram

Add the following entry to the installedComponents.xml file in the Cúram Installation directory:
<component version="" name="SpellChecker" packName="Spell Checker" />

Pre-Installation Step for installations where French or German is the intended locale.

This pre-installation is required before installing IBM Cúram when applying the fix pack to installations where French or German was selected as the locale.

For German installations, prior to installing IBM Cúram, ensure the locale attribute of the installation element is set appropriately in the installedComponents.xml file in the Cúram Installation directory. For example:
<installation locale="de" originalInstallerCategory="SPM">

For French installations, prior to installing IBM Cúram, please ensure the locale attribute of the installation element is set appropriately in the installedComponents.xml file in the Cúram Installation directory. For example:
<installation locale="fr" originalInstallerCategory="SPM">

Fix Pack Installation

The installation steps are as follows:

  • Extract the contents of the zip file to a local drive location.
  • Run the installer from that localtion.
  • After installation you must do a full clean build of your client and server and rebuild your EAR file/s.

Fix Pack Post-Installation Steps

POST-64 - Spend Down Medical Expense when Income Support is installed with Child Welfare and Child Care

The following post install step is required to access SpendDown Medical Expense Evidence when Income Support is installed with Child Welfare and Child Care.

Update the Product Registrar to support Evidence from Solutions when Cúram Income Support, Cúram Child Care and/or Cúram Child Welfare are installed in the same environment.

The following steps must be completed to set the Product Registrars to support Evidence Sharing.

  • Log in as sysadmin, password
  • Go to Application Data
  • Select Property Administration from the navigation bar
  • Select "Application - Case Settings" from the drop down list
  • Search
  • Edit the property file ""
  • This Property file contains a comma separated list
  • The list contains the following entries
    • curam.childcare.evidence.service.fact.ChildCareEvidenceRegistrarFactory
    • curam.evidence.service.fact.EVDEvidenceRegistrarFactory
  • Append the following classes to the list ensuring that each entry is separated by a comma.
  • The property should now have 8 entries in the list.
  • Ensure the default value is set to the same list

POST-43 - Remove the .classpath entry for BIBuildToolsTest.jar

The Project 'CuramBITools' is reporting an error, the error is that a required library is missing, namely the file BIBuildToolsTestInf.jar.

To resolve this issue remove the following stanza from the .classpath file located within the directory Reporting\components\BIBuildTools

<classpathentry kind="lib" path="jar/BIBuildToolsTestInf.jar">


<accessrule kind="discouraged" pattern="curam/util/reporting/testcases/**"/>



POST-68 - Updates required to .classpath

The following Google jar files are no longer supported by Google and have been removed. New, supported jar files are included in this release. As a result, the following changes are required to the Eclipse .classpath:

Remove the following references:

<classpathentry kind="lib" path="components/core/lib/geoGoogle-1.5.0.jar"/>

<classpathentry kind="lib" path="components/core/lib/jaxb-impl-2.1.11.jar"/>

POST-69 - The external-client target requires setting an environment variable prior to execution

The client build target external-client allows for creation of an environment and building of the components specified for an EAR entry in the deployment_packaging.xml.

In order for this build target to execute successfully the steps below should be followed:

1. Open a command prompt and navigate to webclient directory

2. Execute ..\setEnvironment.bat

3. Set the environment variable SKIP_ENV to the value TRUE on the command line i.e. SKIP_ENV=TRUE

4. Now run the external-client target

Supported Hardware and Software

The Cúram Supported Prerequisites document outlines the supported prerequisites for this release.

Improvements and Resolved Issues

Cúram Enterprise Framework
Cúram Modules

Cúram Enterprise Framework

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

SPMP-9536 - Hook point to provide additional validations for IBAN numbers

Currently, there is no validation processing done for IBAN numbers in the application. Customers may want to add validations for IBANs.

A hook point is now provided that will allow customers to add validations for IBANs as per their own criteria and specific conditions.

SPMP-9761 - Spell checking integration for fields using the rich text editor

A spell checker has been added to the Cúram rich text editor feature. The spell checker is embedded in the Cúram application and does not require an additional license. There are no additional steps required to configure the spell checker, the standard Cúram installation scripts will deploy the service. The service is provided by a separate EAR file deployed in the same application server as all other Cúram EAR files. The service is fully contained within the application server and does not communicate with any external third party service.

The spell checking functionality is presented through a standard plugin button in the rich text editor toolbar. Clicking on the button will launch the spell checker which will check the entire document for spelling errors and present the user with suggested corrections.

The spell checking dictionary will default to the locale defined by the property "Server Default Locale" (curam.environment.default.locale). This property can be inspected though the Property Administration feature in the System Administrator application view.

The available dictionaries are:

    American English (en-US,en)
    British English (en-GB)
    French (fr-FR)
    Canadian French (fr-CA,fr)
    German (de-DE,de)

If the server default locale is not mapped to one of the dictionaries shipped with Cúram, then spell checking is disabled, and the spell check button is not displayed.

The initial release of the spell checking service is only available for IBM WebSphere Application Server deployments; it is not currently available for Oracle WebLogic Application Server deployments. The spell checker also does not currently support the ability for Cúram application end-users to specify or use a different locale for the spell checking services - only use of the default system locale is currently supported.

Not supported
The initial release of the spell checking service is only available for IBM WebSphere Application Server deployments; it is not currently available for Oracle WebLogic Application Server deployments. The spell checker also does not currently support the ability for Cúram application end-users to specify or use a different locale for the spell checking services - only use of the default system locale is currently supported.

SPMP-8843 - Performance issues on pages that have large numbers of records

To improve performance and user experience in the Administration application, new search criteria have been added. Entities corresponding to these search criteria have been added with new columns to store the upper version of the named attribute value. An option has been provided for disabling the newly introduced search features. If it is search features are enabled, then data migration is required to populate the newly created columns with upper version of text.

The following tables and related entities are affected with this change: BANKBRANCH, POSITION, ORGANISATIONUNIT, LOCATION, WORKQUEUE, JOB

SPMP-9600 - Upgrade version of CKEditor

The Curam application now supports CKEditor 3.6.6_UIOne. The CKEditor is principally used as within the Notes functionality of the application.

SPMP-9761 - Spell checking integration for fields using the rich text editor

Spell checking functionality has been introduced and is available for use with text fields within the application that make use of the rich text editor.

PO01538, SPMP-10726 - Incorrect software version information displayed in the About modal page

Previously, the About modal was displaying incorrect software version information. This issue has now been resolved and the correct details are being displayed.

Integrated Case Management

Evidence Management
Participant Management
Eligibility & Entitlement
Case Audits

Evidence Management

PO00934, SPMP-6850 - Evidence Generator generates duplicate boolean variables

Previously there was an issue in the Evidence Generator where duplicate boolean variables were generated for modify<EvidenceName> methods in service layer implementations when evidence had a few different case participants of the same type.

This issue is now resolved.

PO01060, SPMP-6968 - 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.

SPMP-7109 - Provide a mechanism for viewing 'Cancelled' evidence

Previously once active evidence was deleted, it was no longer possible for a user to access and view this evidence. With this enhancement, we are now providing the ability to active evidence that has been deleted. A new application property curam.miscapp.displaydeletedevidence is required to display deleted evidence, which is configured off by default. Once the configuration is turned on, deleted evidence will be included on both the Evidence Type and Evidence Business Object list pages.

Participant Management

SPMP-9588 - Introduce validation for zip code for U.S. address format

Previously there was no validation to determine whether the zip code entered for a U.S. address was entered in a valid format. A validation has now been introduced to validate that the zip code has either been entered in a five digit (99999) or five digit - 4 digit (99999-9999) format. The validation is supported as configurable and can be disabled if necessary.

Eligibility & Entitlement

PO00986, SPMP-9051 - Pre-caching of CER data required in streamed batch jobs

To improve the performance and scalability of streamed batch jobs, pre-caching of CER data has been applied to limit the potential for performance bottlenecks.

PO01080, SPMP-9062 - 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 are calculated incorrectly leading to inaccurate statements.

This issue has now been resolved.

PO01221, SPMP-9170 - Reassessment following payment regeneration results in incorrect statement information

Previously it was possible for the reassessment of a period containing a payment that had been cancelled and re-issued to the same nominee, to produce an over/underpayment statement containing incorrect amounts. Note that the total reassessment amount was correct, only the statement amounts were incorrect.

This issue has now been resolved and reassessments following payment cancellation and re-issuance will now produce the expected results.


PO00505, CS-11098, CS-11686, SPMP-8248 - 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.

PO01038, SPMP-7769 - Contact Log issues when changing the original primary client on an intake

Previously, the concerning participants available for selection in the create new contact log wizard were not listed correctly in an intake case.

This happened only if the primary client was changed from one person to another in the intake case.

This issue is now resolved and the concerning participants list displays the participants correctly.


PO01291, SPMP-10519 - Category can now be specifed when recording a participant incident

Previously, when a Incident was created or modified for a Person, there was no option to choose the category. Now, this issue has been resolved by adding a new category dropdown.


PO00948, CEF-12322 - Narrative in Contact Log Wizard is not saved when Back button is used

Previously, when the user navigated to previous pages on the contact log wizard, the system did not capture the information that was recorded on the current page.

This has now been resolved. The user can browse backwards and forwards and the information on the current page is saved when the user returns.

PO00937, SPMP-10372 - Preview Selected Contacts link not working for Ongoing Case contact logs

Previously, the user was unable to view the contact log details for migrated ongoing cases.

This has now been fixed by cleaning up the code in ContactLog.getContactPreviewXMLData(). The user can read the note text from determineNoteText() for contact logs.

Case Audits

PO01382, SPMP-10228 - Provide ability to disable security checks for Audit Coordinator and Auditor security roles

Previously, it was not possible for users without a security role of AUDITCOORDINATOR or AUDITOR to perform various case audit related functions such as being able to manage an assigned case audit.

A new application property, 'curam.caseaudit.limitedsecurityroles', has now been introduced that can be used to disable the security check for the AUDITCOORDINATOR or AUDITOR roles that is used to restrict various functions, e.g. to limit the users returned when searching for a user to whom to assign a case audit to only those with these roles. When the value of this application property is set to 'YES' a security check for the AUDITCOORDINATOR or AUDITOR roles will occur.

Dynamic Evidence

PO01485, SPMP-6785 - EvidenceBroker class using wrong Keyserver keysetcode

Previously the primary key of WMInstanceData was assigned the UniqueID by using the uniqueIDObj.getNextID () API. This was causing the duplicates of the primary key.

Now the WMInstanceData is using curam.util.type.UniqueID.nextUniqueID ( curam.util.resources.KeySet.kKeySetDeferredProcessingTicket) API and duplicate of primary key issue has been resolved.

Business Services

Correspondence Management

PO01104, SPMP-10466 - Incorrect display of .doc extension when viewing Microsoft Word templates

Previously when an administrator selected to view a Microsoft Word template within the system administration application, the system displayed a .doc extension along with the name of the document even if the document did not have a .doc extension. This issue is now resolved and the appropriate extensions are shown.

Administrators were also previously able to upload files with improper file types. A validation message is now displayed if a user attempts to do this.

Application Development Environment

Core Development Infrastructure
Server Development Environment
Client Development Environment

Core Development Infrastructure

TEC-13817 - curam.util.type.CodeTable.getOneitem() method is based on user's locale

The curam.util.type.CodeTable.getOneItem(final String table, final String code) method has been updated to retrieve the code table item description based on the locale of the logged in user. If the locale of the logged in user cannot be determined, the description will be retrieved for the 'en' locale.

Please see the associated the JavaDoc for further information.

TEC-13857 - Message Fallback

Messages defined in message files that are displayed throughout the application, are displayed based on the locale of the logged in user.

If no entry is found for that users locale, then an error is displayed indicating that no message catalog can be found for that locale.

A new fall back mechanism has been introduced, whereby if no message is found for the current users locale, then a look up will be performed using the 'en' locale.

For example, given a users locale is 'fr_CA', if an entry does not exist for 'fr_CA' and no entry exists for 'fr' (i.e. the country part is stripped off), then the entry for 'en' will be displayed. If that does not exist, then the search will be determined based on the underlying message lookup mechanism provided by the JDK class java.util.ResourceBundle. If no message can be found for any of the fall back locales, the an error will be displayed indicating the message cannot be found.

An 'en' entry will be delivered for any new code table items/table names.

TEC-13858 - Codetable Fallback

Code table items and table names (within a hierarchy) defined in code table files that are displayed throughout the application, are displayed based on the locale of the logged in user.

If no entry is found for that users locale for code table items, then no description will be returned on the screen. If no entry is found for the users locale for a code table name, then the code table name identifier will be displayed on the screen.

A new fallback mechanism has been introduced, whereby if no code table entry is found for the current users locale, then a look up will be performed using the locale of 'en'. For example, given a users locale is 'fr_CA', if an entry does not exist for 'fr_CA' for either the code table item or code table name, and no entry exists for 'fr', then the entry for 'en' will be displayed.

An 'en' entry will be delivered for any new code table items/table names.

Third Party Software

PO01294, TEC-14002 - Apache Axis2 code generation defects

Corrective action has been taken for the following two Apache Axis2 code generation issues:

  • AXIS2-5518 - adb-codegen: ADBBeanTemplate.xsl generates erroneous code resulting in javac error: 'else' without 'if' - previously unreported
  • AXIS2-4771 -, String) doesn't exist - fixed in Axis2 1.6.0

See the CURAMREADME.txt file in the <CURAMSDEJ>/lib/axis2 directory for more details.

Server Development Environment

PO01074, TEC-13716 - Code that executes security cache queries is 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.

PO01057, TEC-13717 - User role changes are now updated in the security cache without needing to be published

Previously, for each security role change for a user it was necessary to publish the entire cache. This was inefficient and has now been updated.

The security cache is now updated for user role changes (without the need to publish the changes) on the subsequent login of the relevant user.

Client Development Environment

PO01179, TEC-14077 - Clicking links in quick succession in the application causes modals to open multiple times

Previously when the user clicked a link to open a modal dialog multiple times in a quick succession, the modal dialog would open multiple times.

This has been fixed and now only one modal dialog opens even when the user click on the link multiple times.

PO00711, TEC-14078 - Restoring Tabs after login or brower refresh looses additional parameters.

Previously, when restoring tabs after login or a browser refresh, any additional parameters required by a tab were lost and caused an application error.

For example, in Universal Access, if a User refreshes the page when in the middle of creating a Life Event an error was thrown due to missing parameters.

This issue has now been resolved.


PO01244, TEC-14013 - SAXParseException thrown when editing a template

Previously when template data was not passed into the FILE_EDIT widget for populating field values a dialog would appear displaying a stack trace exception. This has now been changed so that a more user friendly warning message is displayed in the dialog instead of the stack trace.


PO00877, TEC-13231 - 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.

PO00926, TEC-13406 - Add context information for tabs in tab list: Tab 1 of X

Additional hidden tab index information has been added to the each tab navigation label in the application. This tab index information informs a screen reader user of the tab index and tab list length for each tab in a given tab list. Example: "Tab 1 of 4". This additional information provides location context information for screen reader user when navigating through the Cúram application.

PO00906, TEC-14043 - Adding refresh prompt to high contrast mode label in user preference

The high contrast label in the user preference dialog has been modified. The label now contains a prompt telling the user that when high contrast mode is enabled the page needs to be refreshed to activate the high contrast mode correctly.

PO00978, CS-11126, TEC-14044 - Cluster title and toggle alternative text is propagated down to form fields incorrectly.

Previously labels of form fields within clusters were incorrectly appended with the word "toggle" in JAWS' form field dialog box. This issue has been resolved. JAWS' form field dialog box now only displays the correct form label. The without "toggle" reference has been removed.

PO01477, TEC-14203 - UIM Lists renderered without headers do not add role of presentation onto table

Previously it was possible to generate a layout table using a UIM LIST element that contained unlabelled fields. Although these fields were purposefully not labelled the generated header-less table resulted in an accessibility defect as the relationship between each table cell could not be programmatically determined.

This issue has been resolved by adding a aria role of presentation when fields are not labelled in a LIST. This allows developers to use LIST tables for layout purposes in an accessible manner.


PO01254, TEC-14033 - Labels are not displayed in Screen Previews

Screen Previews have been fixed so that property text is now displayed.

Administration Suite


PO01224, SPMP-8733 - Unable to edit an announcement once it has been created

Previously, while modifying an organization announcement, an error message stating 'Start Date/Time must be in the future' was displayed. Now, this issue is resolved and the user can modify an organization announcement.

PO01396, SPMP-10600 - User Search showing positions for 'non' active Org Structures

Previously, when a user was assigned a position in a non-active organization structure but not associated to any position in the active organization structure, the user search would still display position and organization details.

This issue is now resolved and the user search would display empty position and organization results when he/she is not associated to an active organization structure.


CI-4267 - End date being populated as current date in CaseParticipantRole when adding new client to application

End date was populating as current date when the second client was added to integrated case.

This issue is now resolved. Now, end date for second client is "Null".

Cúram Modules

Financial Management
Evidence Broker
Intelligent Evidence Gathering
Provider Management
Universal Access
Outcome Management

Financial Management

PO01088, SPMP-6078 - Component name "Manual Payment OverPayment" not displayed for Manual Payment Instruction Line Items(ILIs)

Previously,the component name column was not present on the view Manual Payment ILIs and manual underpayment case status was "Payment".

Now this has been fixed by adding the component column in manual payment view ILIs.For underpayment manual payment,the case status changed from 'Payment' to 'Manual Payment'.

SPMP-10100 - Provide hook point to allow underpayment to be automatically paid to the nominee currently assigned the underpaid component

Previously when a payment to rectify an underpayment was generated within the original benefit case, it was not possible to issue the underpayment to any nominee other than the nominee who received the original payment amount.

A new extension point has now been introduced that can be used by organizations to implement custom processing that can redirect the underpayment to the nominee currently assigned the component rather than to the original underpaid nominee, and under what specific circumstances this should occur.

PO01065, SPMP-6253 - Create overpayment case when manual payment issued is more than client's eligible amount

Previously, when a manual payment was issued to a client for an ineligible amount, an overpayment case was not created against the manual payment. Now, this has been resolved by creating an overpayment case against the manual payment when the amount has been issued for an ineligible amount.

SPMP-6295 - Ability to capture the cover period as part of creating a manual payment

Previously, when a manual payment was created the cover period for the payment was defaulted based upon the payment date specified and there was no ability for the user to manually specify a cover period.

This functionality has now been enhanced to allow the user to specify the cover period and supports the ability to capture manual payments for past periods so that if payments have already been paid by the system for a past period they can be accurately reflected as overpaid.

SPMP-7386 - Bank account number missing from View Financial Transactions page

Previously, the View Financial Transactions page did not display the bank account number information for the account when the delivery method was EFT.

This issue has now been resolved.

Evidence Broker

SPMP-6712 - The ‘sharedInstanceID’ is not populated correctly by the Cúram Evidence Broker in some scenarios

The sharedInstanceID field on the EvidenceDescriptor table is used by Evidence Broker functionality to indicate an instance or evidence object. The objective of this identifier is to prevent the same evidence object being shared multiple times to the same case. To safeguard this sharing objective, the value in the sharedInstanceID is checked prior to the first sharing of a piece of evidence and if its not already set, it is now given a value.

Previously, this check was not performed. This resulted in duplicate evidence being shared to a particular case in a multi-case sharing configuration. This issue has now been resolved.

Intelligent Evidence Gathering


TEC-9967 - Inconsistent placement of the "Exit" and "Save and Exit" buttons.

In IEG when displaying a question page that has an "Exit" button the button is displayed on the left side of the page. If displaying a question page that has a "Save and Exit" button the button is displayed on the right side of the page beside the "Next" and/or "Back" buttons.

IEG has been updated so that both the "Exit" and "Save and Exit" buttons are not displayed on the right side of the page.

TEC-13880 - High contrast mode required in IEG2

The IEG Player now supports a high contrast mode. To avail of the this functionality, the high contrast user preference must be switched on.

To support this feature, a number of new configuration properties have been introduced which allow various aspects of the high contrast look and feel to be configured. These are listed below and must be added into any custom IEG script configuration property files that are currently being used if a high contrast mode is required in the IEG Player.




























TEC-13889 - No next button when running IEG scripts in readonly mode

IEG allows script executions to be resumed in read-only mode. This allows a user to see the data that was entered in a script execution without being able to change any of the data. The user may navigate around the script using the section panel and the navigation buttons. However, the user may not proceed further in the script than the last page that was previously reached. For this reason there is no next button displayed on the last reachable page of the script execution.

An error existed in IEG where sometimes the next button was incorrectly displayed on the last reachable page. This inconsistency was due to differences in processing between the user pressing the "Exit" and "Save and Exit" buttons. This issue has now been resolved.

TEC-13987 - Containers in read-only clusters

IEG allows read-only expressions to be defined for clusters. Clusters can contain containers which in turn can contain questions. Previously in IEG if a cluster had a static read-only expression the fields in any containers would not be displayed as read-only.

This issue has been addressed and now the fields in containers in clusters with static read-only expressions are correctly displayed as read-only.

TEC-13992 - Provide a mechanism to include a logout button in the IEG banner

IEG now supports displaying a configurable button/link in the page banner. By default the button is not displayed but it may be added by adding a and configuration properties. For Example:

The url property may be any url required, either absolute or relative. The property above is only an example.

An optional configuration property is which can be used to specify a tooltip for the button. For example: here to logout

If the button is present it will be displayed to the right of the print button.

PO01272, TEC-14038 - Blank IEG Screen due to issue in JavaScript code that sets the focus on the validation panel

in, some JavaScript was introduced to set the focus on the validation panel when validation messages were displayed.

However, on slow machines, when a slow rendering of the page occurs, a blank page is being displayed as the JavaScript is being executed before the actual element to set the focus on has been rendered.

This issue has now been addressed and a blank page is no longer being displayed

TEC-14220 - Multi-select values not retained after client-side validation error

Previously, when multi-select questions were rendered as a series of checkboxes in a one-column scrolling listbox, selected values were not retained when the page was reloaded upon paging backward to the page with this kind of question, or upon submitting the page with a client-side validation error. This has been fixed.

TEC-14248 - Security update

For more information about this security update, see the release notes on the product media.

TEC-14299 - Navigation issue on Final Summary page

When editing answers from a final summary page, different behaviours could be seen depending on the answer that was changed:

If the answer was used in an expression in a subsequent section, the user was returned to the final summary and all the sections between the one where the answer was changed and the final summary were disabled.

This was incorrect and has been addressed as the user is not returned to the final summary but to the next page within the normal flow and all subsequent sections are disabled.

If the answer was used in an expression in the current section, the user was not returned to the final summary but all the subsequent sections were enabled.

This was incorrect and has been addressed as the user is still brought to the next page within the normal flow but all subsequent sections are now disabled.

Provider Management

Contract Management
Place Management

Contract Management

PO01026, CPM-1754 - Payments for Provider Flat Rate Contract with Weekly frequency are not being made correctly

Previously, when a flat rate contract was activated for a provider whose frequency was set on weekly/bi-weekly with a regular payment amount, the payment generated for the contract weeks was un-even.

This was an issue when the application was accessed in a different time zone i.e., (UTC-05:00) Eastern Time (US and Canada) timezone. This was because the date conversion from the curam.util API to java.util was done using the asLong() API i.e., getDateRange().start().asLong() which was returning a date one day behind the actual date. The converted date was the feeder to Calendar class to return the day of week.

Now, this issue is resolved by changing the implementation of date conversion by directly referring to the calendar API to get correct the date.

Place Management

PO01304, CPM-1849 - Unable to edit the physical capacity of a re-opened provider

Previously, when a user attempted to modify the physical capacity information for a provider that was re-opened after being closed, an error message was incorrectly displayed preventing the user from doing so.

This issue was occurring for providers that had a designated capacity of 0 at the time of closure due to the fact that all places were end-dated.

This issue has been resolved, and a user can now update the provider's physical capacity when re-opening the provider in this situation.

PO01364, CPM-2059 - Unable to discharge a child from a placement when a place was marked out of use and back in use on the same day

Previously, the system was incorrectly preventing a user from discharging a child from a Placement within an Ongoing case within the IBM Curam Child Welfare module, where the place in which the child was placed had been designated as out of use and then back in use again on the same day.

This issue has now been resolved.


PO01032, CPM-1702 - Received Application Error when attempted to Record Attendance through Secure Provider Portal

Previously, when a user attempted to open the daily attendance widget viacuram provider management external secure portal, there was an application error displayed.

This occurred on a deployed application when hours enabled was set to true for the service offering.

This was because the daily attendance renderer which was supposed to retrieve the properties of the widget from DomainPlugInsConfig.xml file which were missing. These properties are required to display the widget without any error.

This issue has been resolved by adding the required properties in the DomainPlugInsConfig.xml file.

PO01156, CPM-1605 - Error message displayed when creating a new incident injury incorrectly contains technical information

Previously, when a user entered more than 200 characters into the 'Actions Taken' field of the New Injury modal for a provider incident, the error message displayed incorrectly contained technical information. This issue has now been resolved and the error message is displayed as expected.


PO00961, APL-779 - Legal Status must not be created for end dated case members.

Previously, the application allowed users to create legal status for case members who are end dated or having status as either cancelled or deleted . This is incorrect.

Now, this has been resolved and the application doesn't allow the user to create legal status for case members who are end dated or having a status as either cancelled or deleted .

APL-842 - Allow the creation of an appeal when an open or active appeal exists

Enabled the creation of multiple active Appeals cases. Previously it was not possible to have more than one active appeals case. This can be enabled by turning off the following configurable validations:



PO01100, APL-721 - Screen Title is blank for New Hearing screen

Previously, the title of the New Hearing Case page was missing.

This has now been fixed.

Universal Access

PO00537, CS-11862, GUM-2806 - The submission script is not displayed when a user navigates from Full Summary page after using the back browser button.

Previously it was possible for a user to get the system into a state where the submission script was skipped by the system. A user could do this by using the browser back button from the submission script until they were viewing the intake script. Using the next functionality from here meant that the submission script was not offered to the user.

Processing has been changed to ensure that the submission script is always offered to the user even when they have used the back button.

GUM-3356 - Provide a hook for customers to add an additional information to the Citizen Account Contact Details page.

Added a new interface curam.citizenaccount.impl.CitizenContactHelper which allows the addition of extra case worker details and case worker contact details to the Contact Information screen in the Citizen Account.

PO01108, GUM-3704 - Deferred Processing required for Remote Life Events

A new workflow has been added to WorkspaceServices, SendLifeEventToTargetSystem.

This workflow is invoked when a Life Event that is configured to be sent to an external system is submitted.

The workflow was added to allow failed sending to be resent. A system administrator can now see and resend failed Life Events (for example if the remote system was unavailable at the time of submission).

PO01316, GUM-3760 - User contact information not displayed

In the Citizen Account contact information screen, the user's contact details (Address, Phone and Email addresses) were not displayed after setting the related environment variable ( to true.

Now, these details are displayed after setting the environment variable to true.

GUM-3801 - Version of Google Maps API used with citizen workspace to be retired 19 November 2013

Universal Access has been updated to use Google Maps JavaScript API Version 3 in preparation for the deprecation of The Google Maps JavaScript API Version 2 on November 19 2013. Customers will not be impacted by this change.

PO01229, GUM-3803 - Support change of ownership of session data from an anonymous user to a logged in user

Provides support to Universal Access users transitioning from an "anonymous" process such as Screening to a process where a logged in standard account is required as a minimum. The logged in user will be able to securely access the information that was previously entered in the same session as part of the "anonymous" process, for example information entered anonymously in Screening is carried through into Intake for the logged in user.

GUM-3900 - Geocoding Bias Area admin Map page uses a public key

The Universal Access administration section contains a 'Geocoding Bias Area' administration page that accesses a google maps api using a public key. Were this page to be accessed in the application out of the box without modification it could lead to a breach of the Google Maps API ( licensing agreement. As the page is not freely accessible by the public it should not be using a public license key.

with this release the Geocoding Bias page now utilizes a business key to load via the Google Maps api. You must provide this business key in order for the page to function. Out of the box the page will not function until that business key is provided.

In this release we have stopped shipping our public key and updated the software to read the Business Key that you will provide and populate in the 'ENV_CW_GOOGLE_CLIENT_ID' system property. The page will operate only when a valid business key is supplied.

You will have received a welcome letter from Google upon purchasing your Google Maps API for Business license. This letter contains your unique client ID. This ID, prefixed with the characters gme-, is the key which will be passed as part of each request to the Google Maps API. To configure the system to use this key, set the system property ENV_CW_GOOGLE_CLIENT_ID to the value of your client ID, omitting the prefix gme-.

Outcome Management

PO01081, HOBO-1142 - Long activity names on the workspace overlap

A new environment variable (Minimum Distance Between Activities In The Workspace (In Days)) has been added which dictates the minimum distance (in days) between activities in the day view of the workspace.

The infrastructure drawing the activities on the workspace will take this value into account when laying out the items on the workspace in the day view and will logically treat every activity as if it spans at least as many days as this value. The layout of the week view and the month view is also based on this property, the actual minimum distance between activities in these views is inferred from this value.

Note the wrapping of text can still occur if the value is set too low, if for example the value is set to 30 (the default) and a label spans more than 30 days and another activity starts on a date that means the minimum distance between activities does allow the next activity to be drawn on the same line, the wrapping of labels will still occur. Customers are expected to set the minimum distance value with respect to the longest label possible (if they want to be certain no wrapping will occur) or the longest label likely (if they are willing to accept wrapping in a small number of edge cases).

PO01280, HOBO-2063 - "Not Assessed" incorrectly displayed in some assessment answers

Previously, answers given in an assessment were being displayed as "Not Assessed" when the answers were viewed in the application.

This was due to the answers being in a different locale than the current user (en, and not en_US). The issue has now been resolved.

HOBO-2069 - Display rejection information when an assessment is rejected and provide a 'Rejected' closure reason for an assessment

Previously, comments entered by the supervisor when rejecting an assessment were not subsequently displayed on the assessment. It was not possible for the user to specify that an assessment was rejected when closing it.

Users can now to select a reason of 'Rejected' when closing an assessment. In addition, any rejection comments entered by the supervisor are now displayed in the Approval Requests list on an assessment.


Income Support
Child Services
Child Welfare SDM

Income Support

Internal Benefit Application

CGISS-6166 - Addresses not mapped for non primary clients on an internal benefit application

Previously, When a user submitted an application for two clients and provided an address for the primary client, and checked the option to 'Use the Primary Client address', the following validation was thrown: "Rules Expression 'validateUSAddress(ResidentialAddress.Zipcode)' could not be parsed."

This has now been fixed.

Child Services

PO01023, CFSS-5768 - Location Type not displayed in View Allegation page

Previously, the location type was not getting displayed in the view allegation page. This issue has been fixed by adding a new field called 'Location Type' to the view allegation page.

PO01245, CFSS-5821 - Unhandled Server Exception on loading the Ongoing case context panel

Previously, an unhandled server exception was displayed on the context panel of an ongoing case when there were a large number of ongoing cases (approximately 5000 cases and above) in the application. This has been resolved by revisiting the logic that reads the context panel data.

PO01208, CFSS-5822 - Editing address of victim or maltreater results in user not being able to dispose allegation

Previously, an allegation disposition would result in an incorrect validation if the address of the allegation participant had been changed to an address that was different from the participants address at the time the allegation was created. This issue has been addressed by removing the code snippet that was returning the incorrect validation.

PO01239, CFSS-5827 - System shows blank service against the placement type while editing the placement mapping in "Placement Type Mapping" option within Family Services configuration.

Previously, updating a placement type mapping in administration would not present the selected service associated with the placement type. The issue has been resolved by modifying the retrieving logic such that the services name is correctly read and presented (instead of presenting as blank).

PO01253, CFSS-5829 - Canceling a Provider Offering then reading the service results in the Open places on CCS side not listing correctly

Previously, the number of available places for a provider was not getting updated by the deletion of a provider's service offering. This has been corrected now, to accurately reflect the number of available places based on the updates to a provider's active service offerings.

PO01279, CFSS-5832 - Create Investigation Link Missing from Approved Intake

Previously, the Start Investigation tab action menu item was missing from the Intake home page.

This has been resolved by adding the Start Investigation action to the intake tab action menu, allowing the user to create an investigation from the approved intake's homepage.

PO01444, CFSS-5833 - Task search - Disable CCS values of business object type search parameter

Previously, solution specific business object types were incorrectly included as search parameters for Task Search. This has been fixed whereby the solution specific business object types are removed from Task Search.

PO01334, CFSS-5835 - Error message is NOT displayed when Narrative text length exceeds certain limit.

Previously, a validation message would not display when an Intake Narrative's text length exceeded the allowable limit (98,000 characters). This has been fixed whereby a validation message is displayed when Intake Narrative text length exceeds the allowable limit.

PO01340, CFSS-5847 - Wrong page parameter passed to Modify Relationship page from Intake Assistant tab

Previously, the page parameter referenced on the edit relationship action from the CCS Intake Assistant did not allow for implementation customization. This has been updated to to refer to the CaseID instead of the IntakeID to more readily allow for implementation customizations.

PO01389, CFSS-5851 - Prospect Person gets created when a registered person has multiple addresses and is added to an Intake Case

Previously, attempting to add a person to the application that was already registered with multiple addresses resulted in the creation of a new prospect person record. This issue has been resolved by allowing the user to select the existing person with multiple addresses and adding that person via the intake participant wizard.

PO01364, CFSS-5852 - Not able to discharge the child when a place is marked as 'Out of Use' and 'Back in Use' on the same day

Previously, the system was incorrectly preventing a user from discharging a child from a Placement, where the place in which the child was placed had been designated as out of use and then back in use again on the same day. This issue has now been resolved.

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

Previously, there was a delay in displaying Contact Logs page in an Ongoing Case or Investigation because of an inefficient SQL query used to load the contact log details when accessing the page. This issue has been addressed by simplifying the SQL query used to load the contact log details when accessing the page

CFSS-5865 - Data store error while running Screening Assessment after creating a new version of the Questionnaire and releasing it.

Previously, creating a new version of an existing assessment script or questionnaire matrix resulted in an Unhandled Server Exception. This issue has been resolved by moving the custom domain definition into a separate file and including the newly created file in the Data store entity schema.

Child Welfare SDM

PO01282, CFSS-5834 - Print functionality of the Screening Assessment and Response Priority Assessment

Previously, the application did not provide the ability to view a report of an SDM Screening or Response Priority Assessment. This has been addressed by providing access to the standard assessment report functionality provided by the application's assessment framework via the "View Report" row level action, which is enabled upon the completion of an assessment.

Known Issues

Known Issues Cúram Enterprise Framework
Cúram Modules

Cúram Enterprise Framework

Technical Services
Application Development Environment
Administration Suite

SPMP-9727 (was previously CEF-12852) - Check Spelling modal is not closed when spell checking is complete

Currently when a user has completed spell checking a text field, the Check Spelling modal is not automatically dismissed and the user must manually close the modal.

This issue will be resolved in a future release.

Technical Services

TEC-8459 (was previously LUC-174) - Generic Search Server RAM directory search service may return deleted records in search results

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.

TEC-8428 (was previously LUC-189) - Generic Search Server DoSearch function identifier has been disabled

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.

TEC-10881 - Generic Search Server startup command fails sporadically on Websphere Application Server

The GSS startupSearchServer command may fail sporadically with the following error on WebSphere Application Server: " 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.

TEC-11895 - Generic Search Server (GSS) runPersist target fails if file index location not set for all index type.

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

TEC-1847 - Issue with non-standard entity operation key struct

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.

TEC-1857 - Issue with smart quotes in Java files and when using the IBM JDK with UTF-8 encoding set for Eclipse based IDEs.

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.

CS-06592, TEC-1864 - Usage of core VIM file in customized UIM page for online help

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.

TEC-4880 (was previously UDI-524) - In page navigation inclusion of conditional links

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.

CS-08488, TEC-3483 - The default value functionality of the Rational Rose model cannot be used for Boolean domains

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.

TEC-3485 - Use of fully qualified property name for PROPERTY attribute

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).

TEC-3490 - Parameter merging with duplicate target connections in UIM

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">
    <TARGET PROPERTY="pageParameter" NAME="PAGE" />
    <TARGET PROPERTY="pageParameter" NAME="PAGE" />
TEC-3491 - UIM List FIELD element and list structure

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.

TEC-3508 - Rules Decision Dynamic Tree and newline characters

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.

TEC-3601 - Configuring the start day of the week in a calendar

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.

TEC-3602 - Actions when messages missing from catalog

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.

PO00293, CS-07650, TEC-3609 - Time zone validation in user preferences

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.

TEC-3622 - Changing tabs while current tab loading causes sporadic issues

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.

TEC-3807 - Modal window not opened when deleting multiple notifications or adding multiple tasks to the My Tasks list

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.

TEC-5629 (was previously UDI-1505) - Modal dialog and SVG tree widget issue

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

CS-08409, TEC-5798 - not working with IBM WebSphere Application Server

The 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.

TEC-5827 - JavaScript support in main content area

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.

PO00287, CS-09020, TEC-6069 - Error reporting for file downloads

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.

TEC-6263 - TARGET connection restrictions on multiple visible UIM FIELD elements on insert or edit pages

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.

TEC-6410 - Agenda Player issues

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
TEC-6573 - Use of new line characters in UIM properties

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.

TEC-6623 - LobManager SQL syntax exception with a BLOB field and no primary key

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

TEC-6624 - Pipe character ("|") not allowed as an argument for exception text placeholder

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}}}.

TEC-7021 - Display issues with Rules Tree

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.
CS-09848, TEC-7850 - Type Search dialog not returning matched elements in closed models

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).

TEC-8364 - Issue with updating numeric values in the frequency pattern editor

Users cannot edit numeric values with the delete keys in the frequency pattern editor. To update an incorrect entry, the user must select the value and overwrite with the new value.

TEC-8609 - 'Preferences' link is disabled after opening and closing a modal

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.

TEC-8622 - Naming convention for pages being linked together using an explicit link in ACTION_CONTROL

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.

TEC-8704 - Checksql target may throw 'Connection is closed. ERRORCODE=-4470 error' when using IBM DB2 for z/OS

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:

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).
TEC-8751 - Dialog behaviour issues when Flex editor page is loaded in the main content panel

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.

TEC-8920 - Unhandled server exception uploading a new dynamic UIM Page with top level comments

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.

TEC-8973 - reloadextracteddata requires LOB fields to allow null

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.

TEC-8974 - Update to datamanager_config.xml file required for the reloadextracteddata build target to run

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"/>
  <compositetarget name="insertextracteddata">
   <subtarget name="tables"/>
   <subtarget name="extracteddata"/>
   <subtarget name="constraints"/>
   <subtarget name="indices"/>
TEC-10121 - Multi-byte characters cannot be used when editing the Cúram input metamodel

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.

TEC-12659 - Filedownloads with DBCS characters will corrupt the filename in IE7

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.

TEC-14048 - Windows 7 user related issue opening Word document with FILE_EDIT

On some Windows 7 machines, a user with standard access permissions can get the "java.lang.IllegalStateException: Dispatch not hooked to windows memory" error when trying to open a Microsoft Word document from within Cúram. This only occurs when using Internet Explorer 9 in a mode supported by Cúram. Please review the Third Party Supported Prerequisites for more information. The workaround is to create a new user account in Windows 7 and access Cúram from this new account.

Administration Suite

SPMP-10809 - UHSE message encountered in work queue search while searching without entering any data in the search fields

Currently, the system will throw an exception when no search criteria is specified in the work queue search fields. Because, there is no validation defined for this condition.

Cúram Modules

Intelligent Evidence Gathering

TEC-11352 (was previously GLS-566) - WAS7: Page submit after session has timed out causes error messages and field labels are displayed in English

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.


Child Welfare
Child Welfare SDM

Child Welfare

CFSS-5866 - Investigation Summary not displaying

HTML coding of foreign language characters result in text not displaying in the summary reports for Child Protective Services Intakes and Investigations.

Child Welfare SDM

CFSS-5868 - SDM Assessment Override Validation Missing

SDM assessments that provides the ability to override a recommendation (i.e. Screening, Risk, RUA and RRA) and any SDM process that provides the ability to override a recommended decision (i.e. intake recommendation, investigation recommendation) are missing the following validation:

The recommendation selected via an override cannot be the same as the recommendation identified via the assessment.

CFSS-5699 - SDM Application allows the user to override a recommendation with the same value as the determined recommendation

The SDM Child Welfare solution provides recommendations at key decision points in the child welfare process. Many of these recommendations can be overridden by the user if deemed necessary by the end user due to policy or discretionary reasons. The current system allows the user to complete an override, but also allows the user to select, as the new decision, the same value that was determined by the original assessment.



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


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


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.


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.



IBM, the IBM logo, and 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

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.

Document information

More support for: Cúram Social Program Management

Software version: 6.0.4

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows, z/OS

Reference #: 7039105

Modified date: 31 October 2013

Translate this page: