Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.15
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.15.
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. |
Enhancements
ID | Summary | Patch |
---|---|---|
NXT-25239 |
Non-Unique Relation Identifiers This enhancement introduces a new configuration setting that controls whether a relation identifier is unique across relations. Documentation Links: |
4.23.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.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
Web Services
Ref | Action | Description |
---|---|---|
NXT-25239 |
Modified |
identifiertypes API An identifier type cannot be set to unique when identifiers exist |
NXT-25239 |
Modified |
relationidentifiers API Identifier must be unique when identifier type is set to be unique |
NXT-25239 |
Modified |
Relations IP If more than 1 relation is matched to an identifier, then an error message is thrown |
Data Conversion
Ref | Action | Description |
---|---|---|
NXT-25239 |
Added |
Identifier types New column IND_UNIQUE added to REL_IDENTIFIER_TYPES_B with default value set to 'Y' in all the applications except for Policies. |
NXT-25239 |
Removed |
Relation Identifiers Unique constraint on identifier and identifier type is dropped in all the applications except for policies as in policies it was already dropped earlier. |
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
35530671 |
3-32053398351 |
POL-13029 |
BP |
Wait time too long after setting group client to changed |
Description: |
When a group client is set to changed status, the page refreshes. This results in the user having to press submit twice since after the first time screen is still refreshing. |
|||
Resolution: |
Loading icon is shown indicating the page is being refreshed after the group client operations (like submit/set to changed) are performed. Note: Slowness while loading group client with large number of group accounts will be picked up in the enhancement POL-12478. |