Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.1.0.9

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

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

ID Summary Patch

POL-16476

Remove restrictions from registrations entity

This enhancements removes the additional restrictions from the registration entity that were introduced as part of POL-15396 i.e.

  • Payment registration with code type 'CARRYOVER', 'CARRYOVER_OFFSET' and 'REFUND_OFFSET' can neither be created, updated nor deleted

  • Payment registrations with status 'Applied' cannot be created or deleted and update is not allowed on the fields 'type', 'status', and 'codeType' fields for such registrations

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.

Bug Fixes

BugDB SR Internal Summary

37231508

3-38581095771, 3-38556860431, 3-38933128751

POL-16188

Parent activity terminates or is marked as terminated (TE) prematurely, while its child activities are still under execution

Description:

While initializing one of the groups of activities, the parent activity is marked as 'TE' while the other groups (children) are still running.

Resolution:

If a group of activities fail to initialize, the system will automatically retry the initialization process up to a configurable maximum number of attempts. If all retries fail, the group of activities will be marked as Terminated (TE). This approach ensures that the parent activity remains active until all its child groups have been successfully processed, preventing premature termination

36915932

3-36983961191

POL-15655

No base views are generated for Insurable entity and Insurable person tables

Description:

Base view generation for OHI_INSURABLE_ENTITIES and OHI_INSURABLE_PERSONS tables was disabled.

Resolution:

Base view generation for OHI_INSURABLE_ENTITIES and OHI_INSURABLE_PERSONS tables has been enabled.

36930375

3-37575580501

POL-15671

Field values are intermittently not being set when using the JET UI in version

Description:

Create dynamic fields, set a value for this field and save it. The updated value is not being saved properly.

Resolution:

Dynamic field values are updated properly using additional fields dialog

37396750

3-35224413241

POL-16392

Issue with change event rule (function) showing same new/old object for group client - display name

Description:

When updating a translatable entity as per the change event rule dynamic logic, oldEntity binding comes up same as newEntity. Group Client translations shows same new and old values in the change event based on the dynamic logic. Like same old and new display name. It should show the old display name and new display name correctly as per the change.

Resolution:

When updating a translatable entity as per the change event rule dynamic logic, it will now show the old entity bindings and new entity bindings correctly as per the change.

37200394

3-38363602931

POL-16130

Policies parameter values sequence incorrect when not using the toggle

Description:

Policies parameter values sequence incorrect when not using the toggle to expand view format

Resolution:

Policies parameter values are being sorted on display sequence and code in expanded and old view

37215144

3-38065813361

POL-16161

Calculation result lines are not displayed under each calculation period

Description:

Calculation result lines are not displayed under each calculation period. Calculation result (including all the calculation result lines under it) per calculation period is visible under the row displaying the member name (used for looking up products to be used for premium calculation)

Resolution:

Calculation result lines are getting displayed under each calculation period

37367128

3-38933143561

POL-16364

Query API returns partial JSON response when large volume of data is queried

Description:

When querying the policies API and fetching one or more dynamic fields/records of attached policy data, if the volume of dynamic records on attached policy data is high, the Query API may return a partial JSON response. This occurs when the memory consumption is high, leading to a TooManyRequestsException error on the server side, which interrupts the response generation.

Resolution:

The memory footprint when fetching attached policy data dynamic records is optimized.

Issues that were backported in previous Release / Patch

No backports.