Merative ™ Social Program Management 7.0.11.0 iFix3

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

Release Notes

Abstract

Merative Social Program Management 7.0.11.0 iFix3 Release Notes

Content

Introduction
System Requirements
Download
Installation
Improvements, Resolved Issues and Third Party Updates
Known Issues
Notices

Introduction

Welcome to the Merative Social Program Management 7.0.11.0 iFix3 release.

This is a cumulative release which incorporates the Improvements, Resolved Issues and Third Party Updates contained in all previous 7.0.11.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 Product documentation and PDFs.

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

Before 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 Modules

Cúram Enterprise Framework

Application Development Environment
Application Development Environment

PO09070, WorkItem:268439 - 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:

• Model an extension class, e.g. CaseAttachmentLinkExt.
• Add an nsmulti method with a custom key and return struct and add custom SQL to read from the extension class table, e.g. searchCaseAttachmentLink().
• Link the extension class with the out-of-the-box class with Extension in the class diagram, e.g. CaseAttachmentLink.
• Create a custom facade and service layer class with each having a method call, e.g. getCaseAttachmentLinkForDisplay().
• Save changes and run build server.
• Implement the custom facade so it calls service layer impl.
• 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);

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

Resolution:

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

Cúram Modules

Universal Access
Financial Management

WorkItem:268581 - External user who is member of only Provider 1 can access some details for Provider 2 by intercepting the request and modifying the concernRoleID

Issue Description:

In the Provider Management self-service application, an external user who is a member of a provider should only have access to details related to the provider of which they are a member. However, if this same external user knows the concern role identifier of another provider, they can access some information and functions of another provider by supplying that provider's concern role identifier in the URLs of some of the pages contained within the self-service external application. This should not be permitted.

User Interface Impact: No

Steps to Reproduce:

1. Login as a caseworker.
2. Register two people, Person 1 and Person 2.
3. Login as an administrator.
4. Select New External User under Users in the shortcuts panel.
5. For Person 1 from above, enter the required details. In the Application field select ExternalProviderCustomHome as the application homepage, in the Role field select ExternalUserSecureRole and enable the account.
6. Select the 'Link a Participant' action from the tab actions menu. In the External User's Relationship field select 'Is associated with'. Search for person 1 and save.
7. Repeat steps 4 - 6 for Person 2.
8. Login as a Provider Management Resource Manager.
9. Enroll and approve two providers.
10. Navigate to the Provider Members page under the Relationships tab and add Person 1 from above as a provider member to Provider 1. In the Role field select Employee.
11. Add Person 2 from above as a provider member to Provider 2.
12. Login to the CPM External Application as the newly created External User 1 from Step 4. URL: https://<server_name>:<port_number>/CPMExternalS
13. Navigate to My Details > Service Enquiries.
14. Right-click somewhere on the page (below the heading) and select View Frame Info.
15. Observe the URL under Address and write down the concernRoleID number from the concernRoleID URL parameter. This should be concernRoleID of Provider 1.
16. Login to CPM External Application as the newly created External User 2 from Step 4.
17. Navigate to My Details > Service Enquiries.
18. Right-click somewhere on the page (below the heading) and select View Frame Info.
19. Copy the URL listed under Address into a new browser window but substitute concernRoleID number with the concernRoleID from Provider 1.
20. Issue: The page is accessible, while it should give a user permissions error. This is true for the following pages: Financials > Transactions, Rosters, Facility > Reservations, Facility > Wait Lists.

Resolution:

External users can now only view the details for providers for which they are a provider member.

Technical:

This issue occurred due to the lack of a user permissions check in some of the facades used to service these pages in the Provider Management self-service application.

This issue has been resolved by adding a permissions check to the following facades:

• MaintainExternalServiceEnquiry.listWebServiceEnquiries
• ExternalProvider.readProviderSummaryDetails

A new facade, ExternalProviderFinancial.listFinancialTransactions, has been added which contains the permissions check and this is now called from the following pages:

• PME_listProviderPaymentTransactions
• PME_listProviderGroupPaymentTransactions pages

Note that the page MyDetails > Requests, and the actions New Service Invoice Request, Request Member Login Credentials, and Change Password do not show the error message. This is correct behavior as the data is always displayed for the logged-in user due to these facades not requiring a concernRoleID as a parameter and are thus not affected by this issue. As a result, if Provider 1 is logged into the CPM self-service application, but an attempt is made to pass in the concernRoleID of Provider 2 for these specific pages and actions, the data specific to Provider 1 will still be displayed.

Universal Access

PO09199, WorkItem:268191 - Universal Access Responsive Web Application: Error while editing a page from the Summary page

Issue Description:

When a user clicks Edit on the Summary page of their application to go back to a previous section but makes no changes, when they try to go to the next page by clicking Continue, the system shows a ‘Something went wrong. Try again later’ message. The issue doesn't occur if they change a value and click Continue, they proceed to the next page as expected.

User Interface Impact: No

Prerequisite(s):

Create a script with the following structure:

1. Page 1 - An initial page that contains a question that is evaluated to display Page 2a or Page 2b, based on Criteria1.
2. Page 2a - A conditional page that is displayed only when Criteria1 is true.
3. Page 2b - A conditional page that is displayed only when Criteria1 is false.
4. Page 3 - A Summary page that is displayed only when Criteria1 is false and the previous page is Page2b.

Steps to Reproduce:

1. Go to the Universal Access Responsive Web Application.
2. Click Apply for Benefits.
3. Click the new program (might not have a label if not yet configured - this is okay).
4. Start the application.
5. Page 1: Leave all default values, select No to alternative flow question, click Continue.
6. Page 2b: Leave default values, click Continue.
7. Summary: Click Edit on a cluster.
8. Page 1: Don't change an answer, click Continue.
9. Issue: An Error Page is displayed.

Resolution:

This issue has been resolved. Now, when a user clicks Edit on the Summary page of their application but makes no changes and clicks Continue, the next page is displayed correctly.

WorkItem:268945 - Universal Access Responsive Web Application: Enhanced support for privacy by obscuring confidential information in forms

Description:

Where users need to type confidential information, such as a Social Security Number (SSN), you can now obscure the input values as they type to ensure privacy. Users can show or hide the text as they type. This configuration is done in the data store schema by setting a new data type and cannot be used in conjunction with masks. Instead of using a mask, you can also implement any extra constraints, such as the number of characters, in the data store schema by creating a custom domain. For more information about obscuring inputs, see https://curam-spm-devops.github.io/wh-support-docs/spm/pdf-documentation

Financial Management

PO09073, WorkItem:268273 - Overpayment generated instead of an underpayment on a case where a canceled payment was regenerated using a new delivery pattern

Issue Description:

Performing a change of circumstance on a case where a payment has been canceled and regenerated using a new delivery pattern sometimes results in a benefit overpayment being created instead of a benefit underpayment.

**User Interface Impact: **No

Steps to Reproduce (Generic):

1. Login as a caseworker.
2. Register a new Person.
3. Create an integrated case for the person.
4. Add the necessary evidence to make the client eligible.
5. Apply changes.
6. Add an associated product delivery with delivery pattern 'Weekly By Check In Advance on a Monday', for example.
7. Add certification from today for a number of weeks.
8. Submit, approve, and activate the case.
9. Click on the Financials tab of the product delivery.
10. Use the Issue Payment action on the Transactions page to generate the payment.
    • A payment should be generated for the first week.
11. On the generated payment, use the row-level Cancel Payment action to cancel the payment.
12. On the Cancel Payment modal, select a Reason in the drop-down and click Save.
13. Select Delivery Patterns on the left-hand navigation menu.
14. Click on the New page action to launch the New Delivery Pattern modal.
15. Select a different delivery pattern in the Name drop-down, 'Weekly By Voucher In Advance on a Monday', for example.
16. Check the From Case Start Date checkbox.
17. Click Save.
18. Navigate back to the Transactions page.
19. On the canceled payment, use the row-level Reissue action to reissue the payment.
20. On the Reissue Payment modal, select the newly created delivery pattern in the Reissue To Another Nominee drop-down.
21. Click Reissue.
22. Perform a change of circumstance, an evidence change, for example, that should result in a benefit underpayment being created.
23. Apply changes.
24. Issue: Sometimes a benefit overpayment is created instead of a benefit underpayment.

Resolution:

This issue has been resolved and now a benefit underpayment is created consistently in the above scenario.

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"