Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.4
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.4.
Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.23.2.x is only compatible with other Oracle Health Insurance applications release version 4.23.2.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 |
---|---|---|---|
36593604 |
POL-15136 |
Remove the usage of utl_tcp DBMS package in extract functionality |
|
Description: |
Using utl_tcp DBMS package requires explicit grant in SaaS environments. This has operational challenges as the grants that are explicitly granted are periodically revoked by DBA as part of a scheduled process |
||
Resolution: |
Removed the usage of utl_tcp DBMS package in extract functionality and replaced it with a standard DB function |
||
36482265 |
3-36178158771,3-36983961191 |
POL-14985 |
PII data is not correctly populated when setting corresponding property |
Description: |
PII data is filled in as NULL when setting property "ohi.baseview.exclude.pii" to false, even though they are not null. This is only the case for entities where certain attributes are only PII if the entity is of a certain subtype. E.g. for Relation of subtype 'PERS', the code columns is seen as PII. When the "ohi.baseview.exclude.pii" property is set to false, this data should be seen. |
||
Resolution: |
PII data is now correctly populated when setting property "ohi.baseview.exclude.pii" to false. |
||
36591308 |
POL-15134 |
Table component: When we select any LOV value from lookup field, and come out of the row, the value selected disappears |
|
Description: |
Table component: When we select any LOV value with popup tail configured, and come out of the row, the value selected disappears |
||
Resolution: |
When we select any LOV value with popup tail configured, and come out of the row, the value selected is retained. |
||
36704153 |
3-36998302541 |
POL-15273 |
Example Calculation is not showing the correct Calculation period startdate/ enddate |
Description: |
Example Calculation is not showing the correct Calculation period startdate/ enddate. The startDate and endDate in Run Calculation Example and Show Premium are not getting converted correctly according to the user’s timezone |
||
Resolution: |
The startDate and endDate in Run Calculation Example and Show Premium are getting converted according to the user’s timezone and displayed correctly in UI |
||
36672312 |
POL-15245 |
QD status activities are not set to TE during system startup |
|
Description: |
Activities that were not processed and in 'QD' status before system down, are not setting up to status 'TE' |
||
Resolution: |
During system startup, activities which are in status 'QD' will be set to status 'TE' |
||
36659365 |
3-36463843611 |
POL-15217 |
Generate mutations activity takes disproportionate amount of time to complete in a specific scenario. |
Description: |
Generate mutations activity takes very long to complete in a scenario where although there are no group client level events, there are a large number of existing events (of other event levels) and group account products. |
||
Resolution: |
Generate mutations activity is optimized for this scenario and hence completes in reasonable amount of time. |