Release Notes for Oracle Health Insurance Authorizations Patch 4.26.1.0.1
This document contains the release notes for Oracle Health Insurance Authorizations Patch 4.26.1.0.1.
| Version compatibility: Oracle Health Insurance Authorizations Release 4.26.1.x is only compatible with other Oracle Health Insurance applications release version 4.26.1.x unless explicitly stated otherwise. |
| In accordance with the OHI error correction policy (Document KB347263 on My Oracle Support), error correction will be provided for: a) the current release, and b) the preceding release for a grace period of 6 months. |
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 |
|---|---|---|---|
40088823 |
4-0003751096 |
AUT-5149 |
Activity processing supports financial transaction identifiers of up to 19 digits. |
Description: |
Activity processing could fail when a financial transaction identifier exceeded the 14-digit limit used for related activity records. This could interrupt workflows such as daily billing. |
||
Resolution: |
Related activity identifiers now support up to 19 digits, allowing activity processing to continue when larger transaction identifiers are used |
||
39972539 |
4-0003656939 |
AUT-5041 |
File is not downloaded in Reference sheet lines page |
Description: |
Download option not working for Reference sheet lines. When clicking on Download option getting error and lines are not getting downloaded. |
||
Resolution: |
Able to download csv file in Reference sheet lines page. |
||
40057897 |
4-0002849021 |
AUT-5068 |
Base View Generation fails for Insurable Persons Base View |
Description: |
In certain environments, Base View Generation could fail when generating the non-PHI Base View for Insurable Persons. |
||
Resolution: |
Obsolete configuration information is removed, allowing Base View Generation to complete successfully. |
||
40088964 |
AUT-5151 |
Prevent application startup stall caused by Coherence cache initialization |
|
Description: |
During application startup, the plan manager could remain blocked while accessing a shared cache. This could prevent a node from completing startup and processing cluster communication. |
||
Resolution: |
The application now loads the plan cache only when needed, preventing startup stalls and allowing the node to process messages from other nodes and complete initialization. |
||
40089659 |
AUT-5153 |
DBMS_CLOUD CSV exports incorrectly escape JSON values causing column misalignment in excel |
|
Description: |
Operational reporting CSV exports generated through DBMS_CLOUD do not correctly quote and escape JSON-valued fields. As a result, commas within JSON are treated as CSV delimiters when opened in Excel. This splits one JSON value across multiple columns and misaligns data with its headers. The issue is observed only in cloud environments. |
||
Resolution: |
Updated OPERATIONAL_RPT_PKG to handle text containing commas, quotation marks, or line breaks correctly. This helps keep values in the right columns when the exported file is opened. |
||
40068233 |
4-0002548324 |
AUT-5075 |
Automatic recovery can fail to identify the latest errored task |
Description: |
When an earlier task has a higher identifier than a more recently created task, automatic recovery can fail to identify and recover the latest errored task. |
||
Resolution: |
Retrieval of errored tasks is optimized and based on latest creation date. |
||