Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.3

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

Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 3.22.2.x is only compatible with other Oracle Health Insurance applications release version 3.22.2.x unless explicitly stated otherwise.
In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases.

Enhancements

ID Summary Patch

POL-9591

Throttle number of global level activities that can run in parallel

Feature to limit the number of parent activities that can run in parallel at any given point in time.

Documentation Links:
Developer Guide - Throttling Concurrent Parent-Level Activities

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

Ref Action Description

POL-11645

Added

ohi.datareplication.event.retrieval.include.current.timestamp

Property when set to true fetches events created before current time, when false this restriction doesn’t apply

POL-11645

Added

ohi.datareplication.event.retrieval.diff.current.timestamp

System property to fetch events created before given number of seconds. The default value is 30s which means events which were created upto 30s before current time will be replicated in target system

POL-9591

Added

ohi.processing.max.concurrentparentactivities.size

Optional system property that controls the number of parent level activities that can run in parallel. Default value is 2.

POL-9591

Added

ohi.processing.concurrentparentactivities.throttle

Optional system property that controls whether the parent level activities should be throttled or not. Default value is true

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

34831406

3-29584669481

POL-11645

BP

Some of the persons were not replicated in claims by data replication events

Description:

Some of the events (persons/relations) were missed by the data replication process and were not replicated in claims.

Resolution:

Introduced 2 properties that fetch events that were created before a given number of seconds from the current time, when the flag is turned on

34870693

POL-11737

BP

Additional Fields: Cancel button is saving the data.

Description:

Create a new claim and click on additional fields. Save few additional fields. Now edit the additional fields and click on cancel. New changes are getting saved

Resolution:

On click of cancel, the values in the additional fields drawer move back to prior state if there are any changes made.

35087256

3-31977844691

POL-12248

BP

HTTP api metadata caches url from the first api request to get the metadata of a resource

Description:

When metadata of any entity is accessed first time using generic API, it’s generated with absolute URLs and gets cached. Subsequent requests to the same metadata is served from the cache. In multi-node system, accessing metadata from different nodes will return already cached metadata and base URL (hostname and port) mentioned there won’t match with current requests' base URL.

Resolution:

Instead of caching generic API metadata request response with absolute URLs, it gets cached by replacing base URL by placeholder. While returning response for each generic API metadata, cached metadata is processed and placeholder gets replaced by base URL of current request.

34977639

3-31608514081

POL-11959

BP

Policy holder changes are not saved correctly in the policy details page

Description:

When adding an endDate to an existing policyholder with has a flexcode value and creating a new policyholder with a new flexcode value on a policy in one go, this removes the flexcode value of the existing policyholder.

Resolution:

Creating and updating multiple policy holders in one go does not remove dynamic fields on existing policy holders.

Issues that were backported in previous Release / Patch

No backports.