Release Notes for Oracle Health Insurance Authorizations Patch 3.22.1.0.1

This document contains the release notes for Oracle Health Insurance Authorizations Patch 3.22.1.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

This section intentionally left blank.

Bug Fixes

BugDB SR Internal BP Summary

34916582

3-29584669481

AUT-2768

BP

OptimisticLockingException when updating lastlogintimestamp of the user

Description:

Updating lastLoginTimestamp is controlled by a system property ohi.ws.last.login.update.threshold i.e the lastLoginTimestamp is not updated if the user logs-in multiple times with in the same hour.But if there are concurrent requests next second after this hour, both the API/IP requests try to update the same user record, system throws 500 error in this case.

This causes problem in updating the LASTLOGINTIMESTAMP

Resolution:

Error thrown by the system is ignored in case there are concurrent requests to update the same user record. The LASTLOGINTIMESTAMP will be set according to the first request that updates the user record amongst all the incoming concurrent requests.

35168108

3-32286060571

AUT-2936

BP

Currency field on Authorization page resets to default currency

Description:

Currency field on Authorization page resets to default currency when creating a new version of an existing Authorization

Resolution:

When a new version of an existing authorization is created, then the Authorized amount’s currency is set to the currency of the existing authorization and is not set to default currency.

Issues that were backported in previous Release / Patch

No backports.