Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.24.1.0.11

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

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

NXT-31617

Increase the length of scope attribute on OAuthClientCredentialsGrantConfiguration entity

The scope attribute in the OAuthClientCredentialsGrantConfiguration entity is currently limited to 100 characters. This is not sufficient to store scope values provided by OIC.

POL-16202

Policy level activity page

This enhancement introduces a new page to view failed policy-level activities. Users will now have the ability to view related messages, restart activities, and easily navigate to the "View and Edit Policy" page for further action.

4.25.1.0.0

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

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

Ref Action Description

POL-16202

Added

View Policy Actvities page

A new page has been added to view Policy level activities

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal Summary

37841866

3-40216895161

POL-17041

Group Account Adjustments are not shown for a group account with no end date in time period

Description:

When a group account has a time period without end date, in Group Account Adjustment Overrides page, no rows are displayed for that time period. So the user cannot add overrides for the Group Account Adjustments

Resolution:

Group Account Adjustment Overrides are shown in UI for a group account which has a time period without end date

37625687

3-39664837951,3-39711991321

POL-16670

Plan Objects Not Cleaned Up When OutOfMemoryProtector Triggers During Calculate Premium Activity

Description:

Necessary configurations for Calculate Premium activity are fetched once and stored in plan objects within the distributed Coherence cache. When OutOfMemoryProtector triggers, activity remains stuck in IP status and plan cache does not get cleared, overtime this degrades JVM performance.

Resolution:

Clearing plan cache when system reaches CRITICAL state reduces GC overhead, improving JVM performance. It also allows stuck activities to reach final state.

37888243

POL-17076

Generateaccountingmessage IP populates reversal as false for null reversal accounting details

Description:

Reversal has been made optional for POL-16484 since an option is added to not group accounting details on reversals, but the generate account message operation was not adjusted to reflect that the reversal indicator could be empty.

Resolution:

In case reversal is null, it is not displayed in payload (as all null values do) and accounting details will be grouped based on either reversal being true or false or null.

37867863

3-40372816341

POL-17062

Conditional loading of value does not work in List Of Values dropdown once the value is selected

Description:

Filter is not applied correctly to the dependent List Of Values dropdown whenever a conditional trigger is used to update the filter.

Resolution:

The filter is applied consistently, displaying the correct value in the LOV.

37832870

POL-16934

Attributes, Segments, More Section retain previous search result values in Accounting details page

Description:

In policy accounting details page, when a new search is done without closing Attributes, Segments and more section from previous search, these sections are not refreshed. It retains previous data.

Resolution:

Attributes, Segments, More Section don’t retain previous search result values in Accounting details

38010593

3-40795406971

POL-17245

'UserJET' property should expose userid, login name, display name, last login timestamp, defaultCountry information

Description:

userJET property is exposing only displayName and id fields and not rest of the information in UserInformation IP

Resolution:

userJET property gives access to user id, login name, display name, last login timestamp, defaultCountry information about the logged-in user

37947800

3-40947650401

POL-17165

Bill Receiver is missing in More section for Premium Bill Allocation tab on Policies Page

Description:

Bill Receiver is missing in More section for Premium Bill Allocation tab on Policies Page

Resolution:

Bill Receiver has been added as a region in Billing allocations tab

37966333

POL-17187

Contract Periods should be multivalue field

Description:

In policies page, Contract Periods should allow user to add more than one value

Resolution:

Contract Periods is displayed as multivalue field and user will be able to add more than one period

Issues that were backported in previous Release / Patch

No backports.