Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.24.1.0.9
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.24.1.0.9.
| 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. |
Enhancements
| ID | Summary | Patch |
|---|---|---|
POL-16651 |
Memory optimization in premium calculation activity Optimized memory footprint of schedule dimension value configuration data during premium calculation. |
4.25.1.0.0 |
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 |
|---|---|---|---|
37812755 |
POL-16957 |
Single-value, non time-valid dynamic records cannot be deleted |
|
Description: |
In the case of non time-valid record, 'Remove' button does not appear. So once data is entered for the record, the record itself cannot be deleted. Assuming fields are optional, clearing the values for a record does not work. After saving the cleared fields, data appears again. |
||
Resolution: |
'Clear All' action is made available on Single value non-time valid dynamic records to clear all the values in record |
||
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 policy cannot be nullified by passing in empty tags |
||
Resolution: |
Fields of a dynamic record for a policy can now be nullified by passing in empty tags in the PATCH payload. |
||
37898382 |
3-40602279631 |
POL-17089 |
Explicit datatype conversion on record definition fields instead of implicit for char types. |
Description: |
Earlier Referencesheetline query api returned incorrect results when any comparative query like >, <, etc was done on number type fields. Some refactoring was done to fix this behavior where the datatype of the query was determined from the datatype defined on the record definitions and for char type the datatype was implicitly inferred in the database query. This caused some datatype mismatch when some records was defined as such where the definition was char but the values were of number type like 1, 2, etc. |
||
Resolution: |
Some more refactoring was done to handle this given situation where in the database query datatype explicitly defaults to varchar2 unless inferred otherwise from the record definition. This gracefully handles situations where the datatype char is used for numeric data like "1", "2", etc. |
||
37905797 |
3-40174643941 |
POL-17094 |
User information is not available as a parameter in deepLink (external URL) |
Description: |
An external link created with param to display logged in user information doesn’t gets replaced by user’s displayName |
||
Resolution: |
Logged in user information can be used as param in external Links in JET UI |
||
37919579 |
3-38855434721 |
POL-17126 |
Global activities do not display messages |
Description: |
Global activities do not display messages when GET is returned in response |
||
Resolution: |
Added a fix to load messages when GET is returned in response |
||
37812081 |
3-39640248381 |
POL-16950 |
Policies with enrollment end date after date paid to are not picked up for Apply Registrations |
Description: |
When Apply Registrations is invoked, policy selection is based on the Look Back Date of the Policy. For Australian Localization the Look Back Date is not an input parameter, but that date is calculated based on the availability of either new registrations or the effective date of a mutation. When a Policy is end dated retroactively, we need the last period(s) to be recalculated to consider the changed end date. If end dating a policy enrollment results in a mutation with effective date after the end date, the policy is not picked up for recalculation. Reasoning behind this is that a policy is only picked up for recalculation if: - The policy has an active enrollment on the look back date; - The policy has a non-reversed calculation result that starts after the look back date. |
||
Resolution: |
Policy selection for Apply Registrations is changed to the following two conditions: - The policy has an active enrollment on the look back date; - The policy has a non-reversed calculation result that ends after the look back date. |
||