Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.21.2.0.2

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

Enhancements

ID Summary Description Included in Patch

POL-8031

Support for third column in the region component

With this enhancement, it will be possible to add a third column within the regions component by configuring set3. This support is added to view and edit - recursive template and in the overflow area within the table component

POL-8250

Groovy Method to End Enrollment

New method to end policy enrollment products (as well as remove future dated policy enrollment products) that can be called in a bulk update function

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 Subject Description

POL-8229

Modified

premiumschedulelines API

The metadata of schedule dimension of type Amount (both for single value and for range of values) is updated

POL-8229

Modified

Group Account Product Adjustment Rules Operation

The metadata of schedule dimension of type Amount (both for single value and for range of values) is updated

POL-8229

Modified

Enrollment Product Adjustment Rules Operation

The metadata of schedule dimension of type Amount (both for single value and for range of values) is updated

POL-8229

Modified

adjustmentrule API

The metadata of schedule dimension of type Amount (both for single value and for range of values) is updated

POL-8486

Modified

Calculate Premium activity

Calculate Premium activity now supports a list of group account codes (semicolon separated) in groupAccount parameter

Data Conversion

This section intentionally left blank.

Dynamic Logic

Ref Action Subject Description

POL-8250

Added

endPolicy

Added a new pre-defined method endPolicy which is available on Policy entity

POL-8250

Added

endEnrollment

Added a new pre-defined method endEnrollment which is available on PolicyEnrollment entity

UI Changes

Ref Action Subject Description

POL-8169

Modified

All JET pages

Client side validation implemented for mandatory columns in multivalue fields

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

32945037

POL-8269

BP

Client Side Validation Not Working For Multivalue Fields

Description:

Client side validation not working for multivalue fields. Some fields are not reflecting as mandatory fields, hence client validation doesn’t work.

Resolution:

Now all the required fields are showing as mandatory and client side validation also works for multivalue fields

32945098

POL-8270

BP

Schedule dimension of datatype 'amount' cannot be added, edited or rendered

Description:

For Premium Schedule, Adjustment Rule, Enrollment Product Adjustment Rules, and Group Account Product Adjustment Rules page, the user is not able to add, edit and render the added amount for Schedule Lines having Schedule dimension of datatype 'amount'.

Resolution:

A fix was made in the metadata and on the JET page so that CRUD actions on the Schedule dimension of datatype 'amount' can be performed by a user.

33025373

3-25974201831

POL-8487

BP

OutOfMemoryError occurs when running concurrent Global level Calculate Premium activity

Description:

OutOfMemoryError occurs when running concurrent Global level Calculate Premium activity each with a different groupAccount code

Resolution:

Instead of submitting concurrent/multiple Calculate Premium activity each with a different group account code, it is now possible to submit one Calculate Premium activity with a list of group account codes (separated by semicolon).

33030714

POL-8504

BP

Some of the locked Person Covered Services are being replaced by the predefined method in case of transfer certificate scenario

Description:

Person Covered Services that were locked and were considered as Transfer Certificate were deleted and replaced after the predefined method was executed. This only occurred when multiple locked Person Covered Services were available with the same start date.

Resolution:

All locked Person Covered Services are now preserved

33030741

POL-8505

BP

Time validity of Product Covered Services is not considered while generating Person Covered Services

Description:

During the Person Covered Service generation Product Covered Services were considered that were invalid because the ended already passed

Resolution:

Only Product Covered Services are considered during Person Covered Service generation that are time valid

33030727

POL-8506

BP

The Wait Start Date is calculated incorrectly when the enrollment product ends before the reference date but the product is covered in previous enrollment.

Description:

Enrollment products that ended before the reference input date are not considered during Person Covered Service generation. But, for products that exist in such an enrollment and are then carried over to a new enrollment, the Wait Start Date must be taken into account.

Resolution:

The Wait Start Date is taken into account when the enrollment product ended before the reference date but the product is covered in previous enrollment.

Issues that were backported in previous Release / Patch

No backports.