Merative ™ Social Program Management 126.96.36.199
Merative Social Program Management 188.8.131.52 Release Notes
Welcome to the Merative Social Program Management 184.108.40.206 release.
Full product documentation can be found in the documentation.
For the latest version of the release notes, see https://curam-spm-devops.github.io/wh-support-docs/spm/release-notes.
This 220.127.116.11 release incorporates content from previous 7.0.0 releases, which is documented separately in the following sets of online release notes:
- [Merative Social Program Management 18.104.22.168](/support/spm/release-notes/7-0-0-2)
For information about the supported software and hardware for this release, see the Merative Social Program Management Prerequisites.
See the download instructions for this release at /support/spm.
Prior to running the installer please ensure all files in your Cúram installation are writable.
The installation steps are as follows:
- Extract the contents of the zip file to a local drive location.
- Run the Cúram installer, which can be found in the INSTALLER folder at that location.
- After installing, the appropriate build targets must be run as necessary for your installation.
Additional installation instructions can be found in the Development Environment Installation Guide.
If you are upgrading from a previous version, the Merative Social Program Management Helper contains documentation and tooling to help you to upgrade your Cúram application codebase and database to work with your new version of Cúram. The Merative Social Program Management describes a recommended process for performing application and database upgrades. The Upgrade Helper contains tools to assist you with implementing the upgrade, including tooling to produce a schedule of required migrations for your upgrade, tooling to provide information about database schema changes and tooling to generate initial SQL scripts for applying changes to your database.
To download the appropriate version of the Merative Social Program Management Upgrade Helper, see the download instructions at /support/spm.
Post Installation Steps
Delete the folders listed below which were incorrectly included in the release. These folders and their contents are not supported. They may lead to build errors in Eclipse.
Improvements, Resolved Issues ad Third Party Updates
Third Party Updates
WorkItem:198556 - Standard.jar and jstl.jar delivered in the Client Development Environment (CDEJ) have been renamed and updated to the latest version
The standard.jar and jstl.jar that were delivered as part of the Client Development Environment (CDEJ) in the "CuramCDEJ\lib\ext\jar" directory have been updated. This has resulted in both the JARs being renamed and the versions of the JARs being increased to the latest versions as follows:
- jstl.jar has been removed and replaced by the taglibs-standard-spec-1.2.5.jar
- standard.jar has been removed and replaced by the taglibs-standard-impl-1.2.5.jar
Any custom classpath references, build scripts and/or build dependencies should be updated to point to the new JAR files as listed above.
WorkItem:199958 - Upgrade the version of Apache Commons BeanUtils to 1.9.3 and Apache Commons Logging to 1.2
The Apache Commons BeanUtils API released under the Apache License enables dynamic access to Java object properties within Java EE web applications. The version of Apache Commons BeanUtils used in the Social Program Management (SPM) product has been upgraded from version 1.6 to 1.9.3. Additionally the Apache Commons Logging API has been upgraded from version 1.1.1 to 1.2 due to the dependency between Commons BeanUtils and Commons Logging.
WorkItem:199965 - Upgrade the version of Apache Commons FileUpload to 1.3.2
The Apache Commons FileUpload API released under the Apache License enables file upload capabilities in Java EE web applications. The version of Apache Commons FileUpload used in the Social Program Management (SPM) product has been upgraded from version 1.3.1 to 1.3.2.
WorkItem:199971 - Upgrade the version of Apache Struts 1 to 1.2.9 SP3
Apache Struts 1 is an open-source web application framework released under the Apache License and is used for developing Java EE web applications. The version of Apache Struts used in the Social Program Management (SPM) product has been upgraded from version 1.2.4 to 1.2.9 SP3.
WorkItem:204099 - Upgrade the version of Apache Derby to 10.12.1.1
The Apache Derby API released under the Apache License is a pure Java relational database engine using standard SQL and JDBC as its APIs. The version of Apache Derby used in the Social Program Management (SPM) product has been upgraded from version 10.3 to 10.12.1.1.
WorkItem:204500 - Upgrade the version of Apache FOP to 2.2 and Apache XML Graphics Commons to 2.2
Apache FOP (Formatting Objects Processor) is an open-source web application framework released under the Apache License and is used for reading a formatting object (FO) tree and rendering the resulting pages to a specified output in Java EE web applications. The version of Apache FOP used in the Social Program Management (SPM) product has been upgraded from version 2.0 to 2.2. Additionally, Apache XML Graphics Commons has been upgraded from version 2.0 to 2.2 due to the dependency between Apache FOP and XML Graphics Commons.
WorkItem:204501 - Upgrade the version of Apache Batik to 1.9
Apache Batik is an open-source web application framework released under the Apache License and is used for developing Java EE web applications or applets that want to use images in the Scalable Vector Graphics (SVG) format. The version of Apache Batik used in the Social Program Management (SPM) product has been upgraded from version 1.8 to 1.9.
Cúram Enterprise Framework
PO07150, WorkItem:196131 - Relationship Evidence - Select and Clear participant icons disappear after error displayed
Previously, the Search and Clear icons for Participant field were disappearing after validation error was displayed. This issue has now been resolved.
WorkItem:195119 - Documentation for evidence period calculation algorithm
If a multiple participant update is configured, the modify page now uses the same evidence period calculation algorithm as all other application areas.
For information about the evidence period calculation algorithm, see the documentation at: https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation
WorkItem:105581 - Updates to Developing Business Intelligence Reports troubleshooting documentation
The Developing Business Intelligence Reports troubleshooting section has been reformatted. See https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation.
PO05956, WorkItem:147816 - CMS password encryption documentation update
The following topics have been updated to indicate that the CMS password is encrypted by Cúram encryption algorithms during the creation of the target system service. The plain text password is not stored on the system.
Integrated Case Management
PO07253, WorkItem:200485 - 'PROSPECT DUPLICATE' water mark is displayed in v6 fashion on v7
Previously, the 'PROSPECT DUPLICATE' water mark was displayed in V6 fashion on the person details page. This has been corrected to align with the V7 style.
WorkItem:194998 - End Dating Enhancement - Incorrect Label on the Edit Evidence Modal for Configuring the End Dating Enhancement
Previously, in the administrator application, the labels on the Edit Evidence modals for non-dynamic and dynamic evidence, as well as the associated help text, used incorrect terms when referring to the "End Dating when Creating evidence" enhancement.
The wording has now been updated to use the correct terms, removing confusion.
PO07133, WorkItem:195712 - Evidence Action item list is partly obscured
Previously the action item drop down list for Evidence was partly obscured, now this has been fixed and the action item drop down list for Evidence displays without any obstruction.
WorkItem:206995 - Provide environment property to toggle display of evidence period column for same start and end date
For an evidence record, the "Period" column shows the Start Date and End Date during which time a piece of evidence is valid.
Previously, if the evidence was valid for one day, meaning the Start Date and End Date were the same date, only the "Start Date" displayed in the 'Period' column.
In other scenarios, where the duration of the evidence spans longer than one day or where the evidence is still active, '-' is used, for example: "Start Date - End Date" or "Start Date - "
Now, there is a configurable property: "Display evidence period as point in time" which controls how the evidence period is displayed. The default value for this property is true. When set to false, and where the duration spans one day only, the same Start Date and End Date are displayed separated by '-'.
PO07262, WorkItem:201191 - Criteria Surrounding of check box group is missing
In Cúram V6.x, there was a border on the "Assigned To" checkbox list on the New Task Query modal. When the new UI was added in V7, the border was removed. This made it difficult to see which items belonged to the checkbox list.
This has been resolved by restoring the border around the "Assigned To" checkbox list on the New Task Query modal.
Application Development Environment
PO07174, WorkItem:206996 - Static evidence metadata field relatedEvidenceParticipantID undefined will fail modify
Previously, an error occurred stating "Failed to modify evidence" when attempting to modify a static child evidence, where the metadata field relatedEvidenceParticipantID was set as undefined. Now this has been fixed and the modify action completes successfully.
CLIENT DEVELOPMENT ENVIRONMENT
PO07089, WorkItem:192337 - CLIPBOARD element is not working when there is the property value as parameter
Previously, the system did not allow the user to copy the value from the property file. Now, this issue has been resolved.
PO07236, WorkItem:199947 - Search field border loses top line when tabbing through fields in Internet Explorer
Previously, the top border of the search field was being cut off when the user was tabbing through the search or clear button that are part of the search widget. Now, this issue has been resolved by showing the field border when the search or clear button has the focus.
Intelligent Evidence Gathering
PO07074, WorkItem:206998 - Unable to add validation custom function in pages with a dynamically populated list question
Previously, when the datastore was populated outside of Intelligent Evidence Gathering (for instance from a callout), a page that referenced these newly added entities and that both contained a list-question and a validation would throw a NullPointerException upon submission. This has been addressed as the exception is no longer encountered and the validation is performed successfully.
WorkItem:191684 - Removal of incorrect references from the cash assistance section of the Income Support documentation
The Cash Assistance display rules topic in the Income Support documentation includes the following changes:
- Removed references to ABAWD from the 'Household' tab, as it no longer applies
- Removed references to Concurrent Benefits from the 'Household' tab, as it no longer applies
- Added details of the Federal Time Limit and of ineligible categories to the 'Household' tab
- Expanded the details of the 'Dependent Child' tab
- Revised the order of the tab sections to reflect the current interface layout
The changes apply to the following page: https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation
Cúram Enterprise Framework
Integrated Case Management
WorkItem:123357 (was previously SPMP-15534) - Evidence shared from Person to case, is accepted but not activated on the case, modifying this evidence prior to activation will not share this modification back to Person
An issue exists at present with evidence that is shared from Person level to case(s). If the evidence shared from Person evidence to a case is not activated on the case, and that shared evidence is modified within that case prior to activation, the updated evidence is not shared back to Person evidence.
For example; if address evidence is configured for sharing from Person to an Integrated Case with auto-activate disabled and auto-accept enabled. On capturing a new address for a client at Person level, the address is shared to the Integrated Case and automatically accepted onto the In-Edit evidence list on that case. If a case worker modified the In-Edit address within the Integrated Case and activates this change, this address update is not shared back to Person evidence.
To work around this issue, customers have two options.
- Case workers should activate incoming evidence that has been accepted on to the case from Person evidence
- Customers can configure the evidence sharing between the Person evidence to other cases with both auto-activate and auto-accept enabled
Application Development Environment
WorkItem:37987 (was previously TEC-18014) - CDA Assessment Decision Matrix application timeout error
When an administrator is configuring a CDA assessment in Outcome Management, the Decision Matrix displays a wizard to assist the user for creating the matrix. The wizard throws a timeout error, which prevents it from being used. The workaround available is to click OK when the application timeout error appears, select the Cancel button on the wizard and then use the Questions, Outcome and Options button to create the matrix.
WorkItem:103350 (was previously CPM-2415) - Incorrect underpayment amount created when multiple service invoice line items reassessed due to change in service rate
When there are multiple service invoice line items created and paid for a provider using a fixed amount service rate and payment option of 'pay fixed amount', if the service rate that was used to determine the payment amount is retrospectively modified, e.g. to a higher rate, underpayments are not being generated for all of the affected service invoice line items.
WorkItem:114547 (was previously CC-1100) - Administration property 'curam.outcomeplanning.referralForAgreementDays' is not working as expected
Outcome Management provides the ability to create agreements where the client(s) can agree in writing to adhere to the activities (services, referrals and actions) that form part of the agreement. A system property exists to filter out referral type activities during the agreement creation process based on a number of days from when the referral was created. This property is currently not being considered when creating an agreement. To work around this issue, the user can view the start date of the referral on the create agreement wizard to determine whether the referral should form part of the agreement.
WorkItem:115188 (was previously CC-930) - Incorrect Activity Responsibility setting when a plan is automatically created by the system.
In certain scenarios, an activity will have an incorrect responsibility setting, in that the responsibility will be set to ‘system’ instead of the appropriate user. The issue occurs for a specific set-up where:
- ‘Enable Automatic Population of Outcome Plans’ system property is set to true; and
- Outcome Plan is created automatically from referral processing; and
- An action which is configured to be automatically added, has been configured so that the responsibility is assigned to a user.
To work around this issue, the responsibility for the actions that are automatically added should be set to 'Any User', so that the planner user can edit the responsibility field when the action is added to the plan and change the responsibility from 'System' to the appropriate user.
WorkItem:148405 - Outcome Plan Activity Workspace does not refresh and display the newly created Action
When a new action is created from outcome plan activity workspace, the created action is not displayed on the workspace as the workspace does not get refreshed automatically. The workaround available is to refresh the workspace manually to see the action.
Before using this information and the product it supports, read the information in "Notices".