Release Notes for Oracle Health Insurance Product Definition Patch 3.20.2.0.2

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

Ref Action Subject Description

PRD-2435

Modified

Activity Integration Point

The property ohi.processing.headroom.{0} should be changed to ohi.max.headroom.{0} to create consistency with the property ohi.max.headroom.
This change can cause performance issues as the default value may not be optimal for every situation.

Bug Fixes

BugDB SR Internal BP Summary

32113614

3-24068646251

PRD-2425

BP

BUSINESS VALIDATION ERROR NOT HANDLED CORRECTLY IN UI LEADING TO UNEXPECTED EXCEPTION

Description:

When business validation added to the corresponding UI data row, exception throws and it was not handled in UI. So it navigates to the standard error page.

Resolution:

Handled the error where save logic is written. Now it will be shown in the corresponding page like standard error.

32150167

3-24500949741

PRD-2430

BP

Exception occurred when user selects value to the column level multivalue flex code.

Description:

When user selects the value to the column level LOV multivalue flex code, null pointer exception is logged and error page is getting navigated. First it is observed in parameters section from enrollment product screen.

Resolution:

Code change implemented which initializes to empty string instead of null.Now value can be selected to the column level LOV multivalue flex code.

32165302

PRD-2435

Breaking property name change: ohi.processing.headroom.{0} is changed to ohi.max.headroom.{0}

Description:

The property ohi.processing.headroom.{0} should be changed to ohi.max.headroom.{0} to create consistency with the property ohi.max.headroom.
This change can cause performance issues as the default value may not be optimal for every situation.

Resolution:

If a property matching ohi.processing.headroom.{0} is set through api or property file, use ohi.max.headroom.{0} instead.

Issues that were backported in previous Release / Patch

No backports.