Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.2
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.2.
| Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.25.1.x is only compatible with other Oracle Health Insurance applications release version 4.25.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 |
|---|---|---|
POL-16056 |
Store Long Addresses The character limit for the "Additional Address" fields has been increased from 60 to 250 characters. This change applies to the following fields:
This update affects Relation Entities. |
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.templateand name itohi_install.cfg. -
Edit
ohi_install.cfgto 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
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
37809984 |
3-40316251991 |
POL-16948 |
Default value of Flex code doesn’t get saved when LOV floorplan has only descriptor |
Description: |
When a default value is added to the flexcode field and only descriptor is present in the title, it is not getting saved. If value is also added in the LOV title, then the value is getting saved. |
||
Resolution: |
Fix added to save flexcode when only descriptor is present in custom LOV floorplan. |
||
37869341 |
3-40008658091 |
POL-17059 |
Apply Registrations functionality leaves gaps when regenerating Policy Calculation Periods for over a year. |
Description: |
Policy Collection Settings are time valid entities, which means that there can be multiple consecutive Policy Collection Settings with different settings. One of those settings is the Policy Calculation Period length and another one is the Offset, indicating at what moment the Policy Calculation Periods should be generated. As these variables have no restrictions, it can happen that the offset of a later Policy Collection Setting is bigger compared to the Policy Calculation Period length of the previous Policy Collection Setting. As a result, the system generates the periods for the second Policy Collection Setting before finishing with the last periods of the first Policy Collection Setting, causing time based gaps in the Calculation Results. |
||
Resolution: |
During Policy Calculation Period generation, the system checks if all the periods are generated for a specific Policy Collection Setting. If not, the system does not continue with generating the Policy Calculation Periods for any later Policy Collection Setting, those periods are only generated once the system finishes the first Policy Collection Setting. |
||
38230186 |
3-41554949011 |
POL-17514 |
Message parameter are not getting substituted correctly for policy messages. |
Description: |
When there are multiple validation rules that adds message to the policy and any parameter is added in it, it doesn’t take the parameter and shows null in the message description. |
||
Resolution: |
Parameters are substituted now in policy messages. |
||
38230300 |
POL-17515 |
When creating adjustmentrules the valueAmount field is getting limited in the range from -99999999.9999 to 99999999.9999 |
|
Description: |
When creating adjustmentrules the user defined schedule dimension of type amount is getting limited in the range from -99999999.9999 to 99999999.9999. |
||
Resolution: |
The limit was increased to to allow amount in the range from -9999999999.9999 to 9999999999.9999 |
||
37958348 |
POL-17181 |
Unable to save Parameter Domain Values of Parameter Domains tab in Enrollment Products after an error is resolved |
|
Description: |
When an error is encountered in Parameter Domain Values, the record cannot be saved after fixing the error. |
||
Resolution: |
When an error is encountered in Parameter Domain Values, the record can be saved after fixing the error. |
||
38234053 |
3-41589053101 |
POL-17519 |
Delete rows icon in tab-table does not appear when Auto include extensibility is checked in floorplan |
Description: |
'More' link is shown and delete row is hidden when Auto include extensibility is checked in floorplan for dynamic record configured as tab-table. |
||
Resolution: |
More link will only be shown if table region is configured for dynamic record tab and Delete row button is visible. |
||
38024887 |
POL-17267 |
Prefilter is not applied to a search query for View Edit List template based pages |
|
Description: |
Prefilter is not applied to the search query for View Edit List template-based pages like Policy Enrollment Events. |
||
Resolution: |
Prefilter is now applied to the search query for View Edit List template-based pages. |
||