Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.24.1.0.14

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

Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.24.1.x is only compatible with other Oracle Health Insurance applications release version 4.24.1.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-15555

Accept enriched enrollment requests

This enhancement introduces the ability to access user-defined attributes included in the enrollment request payload, within the context of the enrollment response definition groovy function. By enabling the option to put in additional parameters and use them while building a response payload, the response can become more concise to the specific situation of the claim.

Documentation Links:
Developer Guide - Integration Points - Enrollment Status Response Integration Point
Developer Guide - Dynamic Logic - References - Functions

4.25.1.0.3

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-15555

Modified

Enrollment Status Response Integration Point

Add additional (user configurable) parameters to the request

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Access Restrictions

This section intentionally left blank.

Bug Fixes

BugDB SR Internal Summary

38719329

3-42831655789

POL-18115

Connector configuration page: does not reflect updates to an existing changelist

Description:

Change list Values not getting updated properly, old changelist details are retained

Resolution:

Entity and Action are now correctly updated in change list on connector configuration page

38652963

POL-18049

Group Client page is not loaded when it is in In-Process Status

Description:

Trying to open Group Clients page when it is in In-Process status doesn’t open the page. Expected behaviour is to view In-Process group client only in view mode

Resolution:

Able to open In-Process group client in view mode

38587045

3-42470374891

POL-17951

Can’t add new columns to flex codes definition if it has no descriptor field

Description:

While Adding a new row in the Flex Code Field Usages (Record Fields) tab for an existing Flex Code Definition without a descriptor field triggered a confirmation dialog to save the definition without a descriptor field, but the Save action on this dialog did not function as expected

Resolution:

Save action on the confirmation dialog for saving a Flex Code Definition without a descriptor field now works as expected

38660078

3-42702599701, 3-42695355031

POL-18056

The activity thread pool size does not revert to its original value of 8 after memory usage returns to normal

Description:

During periods of high memory usage, the system automatically reduces the number of activity threads it can handle to 1, to prevent further strain. However, after memory usage returns to normal, the system does not increase this capacity back to its usual level i.e. 8. As a result, the affected node can only process one activity at a time, which causes slow performance and delays.

Resolution:

Once memory usage returns to normal, the system automatically restores it the thread-pool capacity back to the usual level of 8 threads on the impacted node. This ensures that performance returns to normal and multiple tasks can be processed at the same time, preventing delays.

38380857

3-40209632171

POL-17713

Start date of Flex code is not updatable

Description:

After a flex code is created, the system does not allow updating its start date. Although the update request returns a 200 response, the start date remains unchanged.

Resolution:

The start date of a flex code has been made updatable.

Issues that were backported in previous Release / Patch

No backports.