Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.20.2.0.8

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

Enhancements

No enhancements.

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

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

32343080

3-24690688341

POL-7076

BP

Calculate premium activity fails to select valid collection setting when multiple collection settings with collection method exist

Description:

When input date to calculate premium activity is 4th Dec, the system only looks at the first collection setting. However second collection setting with start date 5th Dec should be looked at for further period generation as there is collection method with calculation date offset of -1 associated with this collection setting.

Resolution:

Calculate premium activity now selects a valid collection setting when multiple collection settings with collection method exist.

32344254

3-24455989661

POL-7081

BP

Sample invoice API is not setting the pay date of the PCPs generated as part of its process to system date.

Description:

The pay date of all PCPs generated by sample invoice API must be set to system date automatically.

Resolution:

The pay date is now correctly set for all PCPs generated by sample invoice API.

32353927

3-24806255191

POL-7094

BP

Percentage based adjustment is not applied to a base premium of zero

Description:

When the base premium is configured as zero and if two adjustments are configured - the first adjustment (with sequence 1) with amount and the second adjustment (with sequence 2) with percentage, then the second adjustment is not applied (on base premium + amount from the first adjustment).

Resolution:

Percentage based adjustment is now correctly applied to a base premium of zero.

Issues that were backported in previous Release / Patch

No backports.