Release Notes for Oracle Health Insurance Product Definition Patch 4.25.1.0.6
This document contains the release notes for Oracle Health Insurance Product Definition Patch 4.25.1.0.6.
| Version compatibility: Oracle Health Insurance Product Definition 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
| ID | Summary | Patch |
|---|---|---|
NXT-31594 |
JET : Save user preferences for table displays This enhancement enables saving of user preferences related to column selection and column width adjustment for select pages by clicking on "Save preference" button.
|
4.26.1.0.0 |
PRD-5376 |
Ability to retain selected criteria in Across Product Service Definitions page Filters With this enhancement, Across Product Service Definitions page will retain selected Product Filter, Service definitions, Service Options and Services in the filter, when users toggle between tabs in footer |
4.26.1.0.0 |
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.templateand name itohi_install.cfg. -
Edit
ohi_install.cfgto 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 |
|---|---|---|---|
39039593 |
PRD-5396 |
Unable to remove "Carry over period" and "Other products carry over period" value once added |
|
Description: |
In Product Limit Renewal Period, once user has entered values in "Carry Over Period" and "Other Products Carry Over Period" fields, they are unable to remove those values as blank selection is not shown even. |
||
Resolution: |
Blank selection is now available for these dropdown and user can set the value to blank |
||
39080344 |
PRD-5441 |
System throwing NullPointerException when there is no value for EXCL_PHI_LOGGING in the OHI_REPORTING_VIEWS table |
|
Description: |
When invoking the Data Transfer IP, the system verifies if any PHI information is fetched and creates PHI log entries when needed. In case the EXCL_PHI_LOGGING column in the OHI_REPORTING_VIEWS table is empty, the system throws a NullPointerException. |
||
Resolution: |
The EXCL_PHI_LOGGING column in the OHI_REPORTING_VIEWS table gets a default value 'N' |
||
38226912 |
PRD-5049 |
Tracking/Tracing of requests should not be sent to external systems |
|
Description: |
Tracing headers (such as B3 headers) are being sent to external systems. This leads to a 500 error response. However, when the spanId header is removed, the request goes through successfully with a 201 response |
||
Resolution: |
B3 Tracing headers will be added when the host of the request and the application are identical. |
||
39020599 |
PRD-5387 |
Object storage operation cause assert or Weblogic asserts at event publishing time in absence of missing class loader context in underlying thread |
|
Description: |
Object storage operation cause assert or Weblogic asserts at event publishing time in absence of missing class loader context in underlying thread. This resulted in import registration failures, failure observed at weblogic operation at time of publishing event. |
||
Resolution: |
Object storage operation cause assert or Weblogic asserts at event publishing time in absence of missing class loader context in underlying thread. Issue has been fixed by ensuring class loader context is always initialized |
||