Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.1.0.11

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

Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 3.22.1.x is only compatible with other Oracle Health Insurance applications release version 3.22.1.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

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

Ref Action Description

POL-11670

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-11670

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

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

34988277

3-31692075331

POL-11998

BP

Cancelled policy is not listed under Person → Enrollment Section

Description:

After a Policy is Cancelled, the policy code is not getting listed under the Person →Enrollment section.

Resolution:

The canceled policy is listed under the Person → Enrollment section.

35081515

POL-12241

BP

Group Client submit operation is not working without group clients IP access

Description:

User having access to "groupclients.submit IP" and "PO0083" is unable to perform submit operation

Resolution:

Group client IP is added to seed data which is mapped to group clients page. So, the user will be able to submit the group client without the need to give access to group clients IP for their user role.

34839326

3-29584669481

POL-11670

BP

Some events were not replicated from policies to claims by data replication

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

34977638

3-31608514081

POL-11958

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.