Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.1.0.6
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.1.0.6.
Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.23.1.x is only compatible with other Oracle Health Insurance applications release version 4.23.1.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-24066 |
WebLogic authentication implemented compliant with the Java Authorization and Authentication Service (JAAS) specification This enhancement introduces support for the SAML 2.0 authentication mechanism in the Oracle Health Insurance. Additionally, a new JAR file named "CustomIdentityAsserter" has been created to accommodate the Basic Auth configuration. Refer installation guide for further detail.
Documentation Links: |
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
Breaking Changes
Ref | Action | Description |
---|---|---|
NXT-24066 |
Modified |
Installation Configuration Customers using the Basic Authentication mechanism must follow the installation guide to install the newly built JAR file, "CustomIdentityAsserter.jar," and configure the WebLogic security provider accordingly. |
Bug Fixes
BugDB | SR | Internal | Summary |
---|---|---|---|
36809666 |
3-36452370811 |
POL-15457 |
Advanced search lov’s for dynamic fields are not loading in referencesheetlines |
Description: |
Not able to search using the LOV’s in the reference sheet lines page. When clicking in the LOV field an error occurs on the api/generic/flexcodes/search. |
||
Resolution: |
Proper results are displayed in the LOV for flexcodes based on diagnosis, procedures and providers, displays. |
||
36552245 |
3-36171988661 |
POL-15074 |
Date Paid To is not reset when enrollment ended and future dated payments exist |
Description: |
When policy enrolllment products are all (retroactively) ended while applied registrations exist after the end date, the date paid to is not reset to the end date of the policy enrollment products when apply registrations is executed. |
||
Resolution: |
If there are no new calculation results, but only reversed calculation results (which means that the (unzipped) registrations are no longer applicable for that period that is reversed): the date paid to is set to the start date of the first reversed calculation result minus one day. |
||
36482266 |
3-36178158771 |
POL-14986 |
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. |
||
36601400 |
POL-15154 |
Policies page : Group Account sorting not applied |
|
Description: |
Create a policy with multiple Group Accounts. All the Group Accounts added to the policy should be sorted but latest is not shown first |
||
Resolution: |
Group Accounts added to the policy are sorted and displayed in UI |
||
36659297 |
3-36463843611 |
POL-15218 |
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. |