Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.2

This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.2.

Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 3.22.2.x is only compatible with other Oracle Health Insurance applications release version 3.22.2.x unless explicitly stated otherwise.
In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases.

Enhancements

ID Summary Patch

POL-9953

Ability to Update codetype and status to handle Unassigned Payments

This provides the ability to update the 'codeType' and 'status' fields of a registration and hence recognize payments that cannot be assigned to a policy.

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

  1. Perform any pre-upgrade steps.

  2. Stop all the managed nodes running the .existing version of the application.

  3. Perform any pre-undeploy steps.

  4. Undeploy the existing version of the application.

  5. Back up the database.

  6. Perform any post-undeploy steps.

  7. Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.

  8. Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.

  9. Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.

  10. Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)

  11. Run the Upgrade script:

    1. Open a command window and browse to <OHI_ROOT>/util/install.

    2. Run the upgrade by executing ./ohi-update.sh .

  12. Make the required changes to the ohi properties file

  13. Perform any post-upgrade steps

  14. Start WebLogic application server

  15. Deploy the Application

  16. Perform any post-deploy steps

Configuration Properties

This section intentionally left blank.

Web Services

Ref Action Description

POL-9953

Modified

Registration

status attribute is now updatable

POL-9953

Modified

Registration

codeType attribute is now updatable

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal BP Summary

34867206

POL-11721

BP

Long running process for policy update requests ignores time validity issues in payload.

Description:

When request with a payload with business rule violations are processed (for instance because the enrollment product is not in the same time frame as the group account attached to the policy), the error is ignored: the request is set to Processed and no error details are attached.

Resolution:

The business rule errors are now caught and logged as an error detail of the policy update request and the status of that request is set to F(ailed).

34988269

3-31692075331

POL-11997

BP

Cancelled policy is not listed under Person → Enrollment Section

Description:

After a Policy is Cancelled, the policy code is not getting listed under the Person →Enrollment section.

Resolution:

The canceled policy is listed under the Person → Enrollment section.

35042422

3-32032432881

POL-12110

BP

Group Client submit operation is not working without group clients IP access

Description:

User having access to "groupclients.submit IP" and "PO0083" is unable to perform submit operation

Resolution:

Group client IP is added to seed data which is mapped to group clients page. So, the user will be able to submit the group client without the need to give access to group clients IP for their user role.

35070292

POL-12208

BP

Error received while searching a person with Person code

Description:

In the 'Search Person' page, while trying to search with a specific person code, the page doesn’t show anything and the trace log is generated with the error:

org.springframework.dao.InvalidDataAccessApiUsageException: An instance of a null PK has been incorrectly provided for this find operation.; nested exception is java.lang.IllegalArgumentException: An instance of a null PK has been incorrectly provided for this find operation.

Resolution:

Person with person code can be searched from the 'Search Person' page.

Issues that were backported in previous Release / Patch

No backports.