Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.21.3.0.5
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.21.3.0.5.
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
Additional Upgrade Steps for Installation
The following phases are defined:
|
Stage: pre-upgrade
Action: execute the following query to find future duplicates
select usrs.login_name
, dupes.alias
from ohi_users usrs
, ohi_user_preferences uspr
, (select uspr_id
, alias
from ohi_bookmarks
group by uspr_id
, alias
having count(*) > 1
) dupes
where uspr.id = dupes.uspr_id
and usrs.id = uspr.usrs_id
This query lists bookmark aliases per user that have more than one occurrence and will violate the new unique contraint. Update the alias of the violations such that there are no more duplicates
Web Services
Ref | Action | Subject | Description |
---|---|---|---|
POL-9539 |
Modified |
AttachedPolicyData API |
Customers are allowed to set property 'manual' during creation. |
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
33568543 |
3-27562427001 |
POL-9540 |
BP |
UI : Creating a policy from JET does not update the field 'manual' in attached data. |
Description: |
When creating a policy from the JET UI, the field 'manual' should be checked as yes. However, the field that is used to distinguish between manual and integration is set to false, indicating the policy was created through the integration. |
|||
Resolution: |
The property 'manual' on attached policy data can now be set during creation. |
|||
33641635 |
3-27463122071 |
POL-9664 |
BP |
Removing column URI from OHI_BOOKMARK_UK1 |
Description: |
In 3.21.3.0.0 unique constraint OHI_BOOKMARK_UK1 was created on the combination of user preferences, alias and URI of the bookmark. The URI column should be removed from the constraint. |
|||
Resolution: |
The attribute URI is removed from the Unique Key on Bookmarks |
|||
33657901 |
3-27944936671 |
POL-9678 |
BP |
Updating an approved policy through 'POLICY IN DATA FILE SET IMPORT' fails when the policyholder person is matched on relation identifier instead of code |
Description: |
GEN-TMVL-011 is raised during policy import: The Policyholder with start date 10/01/2021 overlaps in time with a Policyholder that has start date 10/01/2021). This happens when: 1) policyholder is matched by relation identifier in the incoming payload. 2) policy loaded using file based policy import. 3) existing policy in system is APPROVED and the file contains new version of the policy. |
|||
Resolution: |
The scenario described will no longer lead to the mentioned business rule failure. |