Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.24.1.0.4
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.24.1.0.4.
Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.24.1.x is only compatible with other Oracle Health Insurance applications release version 4.24.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. |
Upgrade Steps for Installation
To perform the upgrade, perform the following steps:
-
Perform any pre-upgrade steps.
-
Stop all the managed nodes running the existing version of the application.
-
Perform any pre-undeploy steps.
-
Undeploy the existing version of the application.
-
Back up the database.
-
Perform any post-undeploy steps.
-
Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.
-
Change Installation Configuration: In
<OHI_ROOT>/util/install
, make a copy ofohi_install.cfg.template
and name itohi_install.cfg
. -
Edit
ohi_install.cfg
to contain your specific database connection data and other configuration settings. The settings are explained in the file itself. -
Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)
-
Run the Upgrade script:
-
Open a command window and browse to
<OHI_ROOT>/util/install
. -
Run the upgrade by executing
./ohi-update.sh .
-
-
Make the required changes to the ohi properties file
-
Perform any post-upgrade steps
-
Start WebLogic application server
-
Deploy the Application
-
Perform any post-deploy steps
Bug Fixes
BugDB | SR | Internal | Summary |
---|---|---|---|
37424969 |
POL-16411 |
Unable to change macro definition while starting the macro |
|
Description: |
When navigating to the Payment Registrations page and starting a macro, the system retains the previously selected macro definition even after canceling and selecting a new macro definition. |
||
Resolution: |
The "Start Macro" dialog displays details of the newly selected macro definition. |
||
37072824 |
3-36700304951 |
POL-15895 |
Processing of activities stuck with NPE on AggregateResumableActivityTask during node initialization |
Description: |
The Coherence service started processing activities too early, before the node was fully initialized, causing the ServiceLocator to initialize prematurely and resulting in a NullPointerException (NPE), which destabilized the entire application. |
||
Resolution: |
Delayed Coherence session creation until system initialization is complete, ensuring a stable environment for subsequent operations. |
||
37447187 |
3-39027664311 |
POL-16437 |
Value in flexcode field vanishes after saving on defaulting and with readonly as true |
Description: |
On any detail floorplan, if we default a flex Code and also used readOnly as true, but after saving the page record, the value of the flexCode is disappearing. So, the combination of readOnly and default properties is not working on flex code fields. |
||
Resolution: |
Value in flexcode field retains as is after saving on defaulting and with readonly as true |
||
37326684 |
3-38820404001 |
POL-16323 |
Add-on error message not displayed when deleted |
Description: |
When user tries to delete an add-on which cannot be deleted because it’s being used, the screen is not presenting any message |
||
Resolution: |
Error message is displayed in UI when a row is deleted and there is a business rule error. |
||
37367140 |
3-38933143561 |
POL-16366 |
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. |
||
37350509 |
3-38913319921 |
POL-16344 |
GEN-PROC-ERR is raised occasionally when accessing parameter values API |
Description: |
A GEN-PROC-ERR error intermittently occurs when accessing certain APIs. Once this error occurs, all subsequent API calls to the same resource fail with the same error. The only workaround is to restart the specific node/JVM. |
||
Resolution: |
To prevent the error when accessing certain APIs, the necessary initialization is now performed during startup instead of waiting for the first API call. |
||
37359374 |
POL-16361 |
Percentage is shown twice in Parameter Domain values tab |
|
Description: |
Percentage is shown twice in Parameter Domain values tab |
||
Resolution: |
Percentage and Condition is shown properly in Parameter Domain values tab |