Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.24.1.0.3
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.24.1.0.3.
Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.24.1.x is only compatible with other Oracle Health Insurance applications release version 4.24.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. |
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-30781 |
Increase number of financial message attributes on invoice and invoice lines This enhancement extends the number of available attributes on invoice and invoice lines in the financial message by additional sixty bringing the total number of available attributes to ninety. |
|
POL-16031 |
This enhancement introduces the ability to invoke an insurance gateway exchange, using a list of payment registrations as its payload. The exchange is invoked either by API or through a new set of controls in the user interface. This enhancement introduces ability to select records from payments registrations (search page) and invoke an OHI exchange using macros functionality. 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
Web Services
Ref | Action | Description |
---|---|---|
POL-16031 |
Modified |
Generic API for Macro definition Value REGI ("Registration" ) and list indicator are added. |
POL-16031 |
Modified |
Generic API for Macro history Subject ID is made optional |
POL-16031 |
Modified |
Macro IP Attribute requestContextList is added |
Data Conversion
Ref | Action | Description |
---|---|---|
POL-16031 |
Added |
List indicator New indicator list on Macro definition is set to false |
Bug Fixes
BugDB | SR | Internal | Summary |
---|---|---|---|
37323686 |
POL-16309 |
Policy update requests : reque status action missing |
|
Description: |
Policy Update Requests : Reque status action missing |
||
Resolution: |
Requeue action is shown in policy update requests |
||
37379873 |
POL-16383 |
The Boolean option for the Datatype field is absent in Macro Parameters. |
|
Description: |
In Macro Parameters, the Datatype field support for Boolean option was missing. |
||
Resolution: |
Boolean option for the Datatype field is added for Macro Parameters. |
||
37248268 |
POL-16207 |
Referencesheet query api works erroneously in some cases |
|
Description: |
Referencesheet query api did not return correct result set when a comparison operation like gte or lte was used because the passed value was being interpreted as a string instead of a number |
||
Resolution: |
Referenesheet query api now returns correct result set when a search operation is done using gte or lte comparison operators |
||
37031736 |
3-37528423931 |
POL-15786 |
Additional Field values when filled are not retained after save |
Description: |
Additional field values of a dynamic record for a claim cannot be nullified by passing in empty tags |
||
Resolution: |
Additional field values of a dynamic record for a claim can now be nullified by passing in empty tags in the PATCH payload |
||
37309930 |
POL-16294 |
POL - Individual Provider Page - Rendering Addresses tab - Service Address LOV field is not loading the values |
|
Description: |
Service Address LOV field in Rendering Addresses tab in the Individual Provider Page is not loading the values |
||
Resolution: |
Service Address LOV field in Rendering Addresses tab in the Individual Provider Page is loading the values |
||
37286430 |
POL-16263 |
Business Event Rules - "Unsaved changes" pop up on search page |
|
Description: |
"Unsaved changes" popup appears on the Business Event Rules page after performing a '%' search, even though no changes have been made. |
||
Resolution: |
The "Unsaved changes" popup doesn’t appear after performing a search without any modifications to data. |
||
37204943 |
3-38073502601 |
POL-16138 |
Anomaly in generic patch operation for Time Valid dynamic records |
Description: |
When performing generic patch operation for a time valid dynamic record to update the endDate, the operation fails, getting a time valid error thrown. In some instances, when updating both startDate and endDate, other dynamic records are getting affected. |
||
Resolution: |
Generic patch operation on all resources is isolated from policies in IP patch operation. Apart from this a time validity check is added per dynamic records per resource which resolves the issue. |
||
37351082 |
POL-16346 |
Registration: Code is set as mandatory field, it should be autopopulated |
|
Description: |
In payment registration page, code is set as a mandatory field. It should be mandatory false and the value should be auto populated. |
||
Resolution: |
Registration code is autopopulated when left empty |