Release Notes for Oracle Health Insurance Authorizations Patch 3.20.2.0.1

This document contains the release notes for Oracle Health Insurance Authorizations Patch 3.20.2.0.1.

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

AUT-1914

Modified

Activity Integration Point

The property ohi.processing.headroom.{0} has been 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

31963745

AUT-1866

Imposisble to access a keystore that is created via the application

Description:

When attempting to request a new token via the new token IP an internal server error is received.

Resolution:

It is possible to access a keystore that was created via the application to add a key.

32113646

3-24068646251

AUT-1907

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 as the expected error. Message 'The server is unable to respond' does not show anymore when saving in the application.

32150237

3-24500949741

AUT-1910

BP

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

Description:

When the user selects a value from the LOV for a multivalued flex code column, null pointer exception was thrown and error page was displayed.

Resolution:

A value can now be selected from the LOV for a multivalued flex code column.

32165312

AUT-1914

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

Description:

The property ohi.processing.headroom.{0} has been 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.

32973629

3-25870554621

AUT-2136

Impossible to set up the OAuth2 assertion grant typw (with JWT as assertion)

Description:

It is not possible to set up the OAuth2 Assertion grant type (with JWT as assertion) in OHI Authorizations 3.20.2.0.0.

Resolution:

The OAuth2 module in OHI Authorizations is upgraded to the last 4.0.x release of that in order to resolve the issue.

Issues that were backported in previous Release / Patch

No backports.