Merative ™ Social Program Management 7.0.10.0 iFix4

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

Release Notes

Abstract

Merative Social Program Management 7.0.10.0 iFix4 Release Notes

Content

Introduction
System Requirements<u>Download</u>Installation
Improvements, Resolved Issues, Third Party Updates
Known Issues
Notices

Introduction

Welcome to the Merative Social Program Management 7.0.10.0 iFix4 release.

This is a cumulative release which incorporates the Improvements, Resolved Issues and Third Party Updates contained in all previous 7.0.10.0 iFix releases. Details of these Improvements, Resolved Issues and Third Party Updates are included separately in the release notes for each of the previous iFix releases.

For the latest version of the release notes, see https://curam-spm-devops.github.io/wh-support-docs/spm/release-notes.

Full product documentation can be found in the documentation.

System Requirements

For information about the supported software and hardware for this release, see the Merative Social Program Management Prerequisites.

Download

See the download instructions for this release at /support/spm.

Installation

Prior to running the installer please ensure all files in your Merative Social Program Management installation are writable.

The installation steps are as follows:

• Extract the contents of the .zip file to a local drive location.
• Run the Merative Social Program Management installer, which can be found in the INSTALLER folder at that location.
• After installing, the appropriate build targets must be run as necessary for your installation.

Additional installation instructions can be found in the Development Environment Installation Guide.

Upgrading

If you are upgrading from a previous version, the Merative Social Program Management Upgrade Helper contains documentation and tooling to help you to upgrade your Merative Social Program Management application codebase and database to work with your new version of Merative Social Program Management. The Merative Social Program Management Upgrade Guide describes a recommended process for performing application and database upgrades. The Upgrade Helper contains tools to assist you with implementing the upgrade, including tooling to produce a schedule of required migrations for your upgrade, tooling to provide information about database schema changes and tooling to generate initial SQL scripts for applying changes to your database.

To download the appropriate version of the Merative Social Program Management Upgrade Helper, see the download instructions at /support/spm.

Improvements, Resolved Issues and Third Party Updates

Cúram Enterprise Framework

Cúram Enterprise Framework

Application Development Environment

Application Development Environment

Client Development Environment

PO09070, WorkItem:266240 - The implementation JAR missing from class loader in coreinf-ejb EJB Module on WebLogic 12.2

Issue Description:

In Merative Social Program Management deployed on WebLogic 12.2, classes in the implementation.jar can no longer be sourced from the coreinf-ejb.jar EJB Module. This means that classes extended by customers that require the implementation.jar in the coreinf-ejb.jar EJB Module are returning errors when attempting to invoke custom methods that reference methods in out of the box classes.

Customers may experience a java.lang.AbstractMethodError at runtime when invoking custom methods in extended classes.

User Interface Impact: No

Steps to Reproduce:

1. Model an extension class, e.g. CaseAttachmentLinkExt.
2. Add an nsmulti method with custom key and return struct and add custom SQL to read from the extension class table, e.g. searchCaseAttachmentLink().
3. Link the extension class with the out of the box class with Extension in class diagram, e.g. CaseAttachmentLink.
4. Create a custom facade and service layer class with each having a method call, e.g. getCaseAttachmentLinkForDisplay().
5. Save changes and run build server.
6. Implement the custom facade so it calls service layer impl.
7. Implement the service layer impl and create an object of the out of the box class that invokes the created nsmulti method, e.g. code snippet:

curam.core.intf.CaseAttachmentLink link = curam.core.fact.CaseAttachmentLinkFactory.newInstance();
CustomSearchClientAndPartnerDocumentsKey searchDocumentsKey = new CustomSearchClientAndPartnerDocumentsKey();
searchDocumentsKey.primaryConcernRoleID = key.concernRoleID;
CustomDocumentDetailsList publishedScannedDocumentsList = link.searchCaseAttachmentLink(searchDocumentsKey);

1. Create a UIM to call the created custom facade method.
2. Build and deploy the application on a WebLogic 12.2 server.
3. Access the custom UIM from the application.
4. Issue: An un-handled server exception appears in the application and an AbstractMethodError appears in application server logs.

Resolutio n

This issue was resolved and it is now possible to invoke custom methods on an extended class of an out of the box entity without a java.lang.AbstractMethodError occurring.

Technical

WebLogic 12.2 implemented a fix which ensured the application server followed the class loading policies of the J2EE specification correctly. This fix caused conflicts with EJBs in the SPM implementation.jar during deployment of SPM applications on WebLogic 12.2 and the initial resolution was to remove the SPM implementation.jar from offending EJB Module classpaths which introduced this issue.

A Bundled Library has been added to EAR files during the EAR building process and this library is populated with the SPM implementation.jar. This library allows EJB Modules on these EAR files to reference classes within JARs located in the library and as the EJB Modules can now reference the SPM implementation.jar, this resolves the java.lang.AbstractMethodError appearing when invoking a custom nsmulti search method.

CLIENT DEVELOPMENT ENVIRONMENT

PO08832, WorkItem:261505 - The Close all tabs button does not always close all the application tabs that are opened

Issue Description:

In the Internet Explorer 11 browser, the Close all tabs button, which is supposed to close all application tabs that are open in the caseworker application, does not always work as intended. If there is more than one application tab open or if the Close all tabs button is selected from a tab whose content is not currently displayed, some of the tabs may remain open.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker using the Internet Explorer 11 browser.
2. Open three application tabs.
3. Right click on a tab whose content is not currently displayed.
4. Select Close all tabs.
5. Issue: Only the application tab that was clicked is closed.

Resolution:

This issue was resolved by updating the JavaScript executed when Close all tabs is selected.

Technical:

The following file has been changed:

TI/client/dojo-overrides/jscript/src/dijitl/ayout/ScrollingTabController.js

Known Issues

See the Known Issues section in the 7.0.10.0 release notes.

Notices

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