Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.20.2.0.6
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.20.2.0.6.
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 | Subject | Description |
---|---|---|---|
POL-6760 |
Modified |
Activity Integration Point |
The property This change can cause performance issues as the default value may not be optimal for every situation. |
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
32113631 |
3-24068646251 |
POL-6636 |
BP |
Business validation error not handled correctly in UI leading to unexpected exception |
Description: |
When business validation added to the corresponding UI data row, exception throws and it was not handled in UI. So it navigates to the standard error page. |
|||
Resolution: |
Handled the error where save logic is written. Now it will be shown in the corresponding page as the expected error. Message 'The server is unable to respond' does not show anymore when saving in the application. |
|||
32142904 |
3-24377974061 |
POL-6723 |
BP |
Group Account "CALCULATE_PRODUCE_INVOICE" activity , should contain links to Data file in the activity notification. |
Description: |
Group Account "CALCULATE_PRODUCE_INVOICE" activity , do not have the links for data file in activity notification. |
|||
Resolution: |
Data file links are now available in "Run Calculation and Produce Invoice for a Group Account" activity notification when the activity is completed. |
|||
32150222 |
3-24500949741 |
POL-6742 |
BP |
Exception occurred when user selects value to the column level multivalue flex code. |
Description: |
When the user selects a value from the LOV for a multivalued flex code column, null pointer exception was thrown and error page was displayed. |
|||
Resolution: |
A value can now be selected from the LOV for a multivalued flex code column. |
|||
32164979 |
3-24491372481 |
POL-6768 |
BP |
CALCULATE_PRODUCE_INVOICE activity completes successfully, but the notification received on premium/commission end point has status as "Failure" |
Description: |
Even though the "Run Calculation and Produce Invoice for a Group Account" activity completes successfully, the notification received on premium/commission end point has "Failure" status. |
|||
Resolution: |
In the following use cases, the status in the data file notification now correctly reflects the status of the activity:
With this bug fix, the order of the links in the data file notification has changed. |
|||
32170146 |
3-24498375181 |
POL-6773 |
BP |
THE CHILD ACTIVITY GENERATE_FIN_MSG_XML OF "RUN CALCULATION AND PRODUCE INVOICE FOR A GROUP ACCOUNT" ACTIVITY SHOWS BOTH PREMIUM AND COMMISSION DATA FILE SET CODES IN UI. |
Description: |
In "Run Calculation and Produce Invoice for a Group Account" activity, two different financial transaction sets are created (one for premium and one for commission). So, two different child activities GENERATE_FIN_MSG_XML are created. The child activity for premium adds an activity message (ACT-FL-DAFI-001) with the code the data file set containing financial messages of premium and the child activity for commission adds an activity message (ACT-FL-DAFI-001) with the code the data file set containing financial messages of commission. However, in the ADF UI, both the child activities (GENERATE_FIN_MSG_XML) show both the messages. |
|||
Resolution: |
now the generate financial message activity (premium) will show message related to data file for premium and generate financial message activity (commission) will show message related to data file for commission. |
|||
32119912 |
3-24415907141 |
POL-6646 |
BP |
ALL THE RECORDS ARE NOT VISIBLE IN THE SCHEDULE DEFINITIONS AND ADJUSTMENT RULES |
Description: |
All the records are not visible in the Schedule Definitions and Adjustment Rules pages as the next set button is not available. Scenario: Next set button is currently unavailable in the above mentioned pages. So all the records are not seen. Expected: Next set button should be available. |
|||
Resolution: |
Next button is now available for pages on schedule definitions and adjustment rules. |
|||
32160383 |
POL-6760 |
Breaking property name change: |
||
Description: |
The property This change can cause performance issues as the default value may not be optimal for every situation. |
|||
Resolution: |
If a property matching |