Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.19
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.19.
| Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 3.22.2.x is only compatible with other Oracle Health Insurance applications release version 3.22.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.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 | BP | Summary |
|---|---|---|---|---|
35421016 |
3-33092865931 |
POL-12836 |
BP |
Group account not reflected correctly |
Description: |
When searching Policies by Person in ADF the Group Account does not always get reflected correctly. |
|||
Resolution: |
The Group Account is reflected correctly in the View Person page now. |
|||
35865481 |
3-34391377541 |
POL-13784 |
BP |
Registration is re-applied when using the /applyregistrations IP |
Description: |
When a registration is in "Applied" status, but it has a pay date later than the look back date, the registration will be reapplied. The system tends to keep the policy calculation periods that were created during the application of the initial registration . As a result, when the registration is reapplied, the registration is applied on a new period instead of the same period is was applied to initially. |
|||
Resolution: |
The system will remove the policy calculation periods that have the same pay date as the registration to make sure that the registration can be re-applied on the same period it was applied on initially. |
|||
35811139 |
3-34053143361 |
POL-13710 |
BP |
Person level policy event with a reference to non-existing policy id is not removed after mutations are created |
Description: |
The orphan policy events (having a reference to a non-existing policy) were not removed after generating mutation, leading to the creation of unwanted financial transactions. |
|||
Resolution: |
Added deletion logic to delete orphan policy events after the mutations are generated. |
|||
35958820 |
POL-13884 |
BP |
Policy In IP matches on identifier, but updates the policy code |
|
Description: |
The Policy In IP sometimes updates the code of an existing policy. Steps to reproduce: 1. Send in a policy request with identifier as code (like a SSN-no) with identifier type so that this identifier is added to the new policy. 2. Approve the policy (or submit in step 1) 3. Send in the same payload and a new version is created, but code is now updated to the value of the identifier (like the SSN-no). |
|||
Resolution: |
When identifier is used to retrieve an existing policy in the Policy In IP, the code of that existing policy will not be updated. |
|||