Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.21

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

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

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.

Breaking Changes

This section intentionally left blank.

Access Restrictions

This section intentionally left blank.

Bug Fixes

BugDB SR Internal Summary

39569000

4-0002996907

POL-18815

Business events does not return the correct policy enrollment in the change objects when updating flex code in policy

Description:

When business events were generated for updates to dynamic fields on a policy enrollment product, the change object could reference the previous policy enrollment instead of the current/latest policy enrollment. This could cause notification dynamic logic or integrations consuming the business event payload to evaluate the wrong policy enrollment for the changed object.

Resolution:

The policy version change detection logic now enriches the object changes using the working policy version. This ensures that dynamic field changes on policy enrollment products are associated with the current policy enrollment.

39829297

4-0003422821

POL-18994

Cleared dynamic fields could still return the previous value during the same processing flow.

Description:

When a dynamic field was cleared by assigning null, the value was removed, but a cached copy could still be used for later reads in the same flow. As a result, the dynamic field could appear to still contain its old value immediately after being cleared. This could affect dynamic fields, including flex-code dynamic fields, across single-value time valid, multi-value non-time-valid & time-valid, configurations.

Resolution:

The cache is now invalidated when a dynamic field is cleared. After assigning null, later reads correctly and returns no value instead of the previously cached value.

39840318

POL-19005

Quote IP in no-flush mode fails with NullPointerException when deleteDynamicRecord method is invoked from dynamic logic

Description:

Quote IP in no-flush mode fails with NullPointerException when deleteDynamicRecord method is invoked from dynamic logic. The issue occurs when the dynamic record is included in the request payload and had not yet been saved.

Resolution:

Quote processing now handles these new dynamic records correctly when deleteDynamicRecord is invoked.

39768904

4-0003293807

POL-18934

Maxcolwidth and Mincolwidth property does not affect Start Date and End Date column widths

Description:

When using "percentage" or "rem" in maxColWidth or minColWidth for date fields, it is not rendering the width based on configuration.

Resolution:

maxColWidth and minColWidth width are rendered based on configuration and if not configured default width is assigned

Issues that were backported in previous Release / Patch

No backports.