Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.7
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.7.
| 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 |
|---|---|---|
CPN-3926 |
Automatic heap histogram collection for improved memory analysis A heap histogram is a lightweight memory dump that provides detailed information about objects in the heap, including their class names, sizes, and counts. It helps identify memory leaks, understand object allocation patterns, and optimize memory usage. With this enhancement, heap histograms are automatically captured in SaaS deployments when the heap memory reaches a critical state, enabling proactive and improved memory analysis. |
|
NXT-31023 |
Search Result Download in CSV Format This enhancement addresses the issue of referenced fields being downloaded in one column as JSON data in the CSV exports from UI. With this enhancement all the displayed data of a reference field will be downloaded into separate columns. |
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 |
|---|---|---|---|
38525019 |
POL-17898 |
An exception occurs when an empty messages list is returned from a Message Transformation Dynamic Logic Function |
|
Description: |
This issue arises when events are filtered in the Message Transformation dynamic logic function using aggregateEvents, and no events match the filter criteria. As a result, the messages object is returned as an empty list. Although the IntegrationTransformation task completes successfully, an ArrayIndexOutOfBoundsException is logged in the application log. |
||
Resolution: |
The system now verifies if there are no messages to process. If none are found, it skips the process gracefully, preventing any errors. |
||
38543017 |
POL-17922 |
Improve retrieval of accounting details in UI-pages |
|
Description: |
It was noticed that getting accounting details for a policy was slow. |
||
Resolution: |
Added index on subject of the accounting detail to improve retrieval of accounting details per policy/claim (a.k.a. subject). |
||
38393542 |
3-41612607721 |
POL-17728 |
Reconciliation is applied to catchUp periods |
Description: |
Reconciliation is applied to the last period of a span. When a new Policy Collection Setting is created, it is possible to configure the start date of the Collection Setting before the reference date, creating a CatchUp period between the start date and the reference date. This CatchUp is usually a period at the end of a span (the span before the first regular cycle). Therefore, the system applies the reconciliation logic to this period. But, reconciliation should not happen for this period as the span configuration of the new Collection Setting could be completely different, resulting in different daily amounts. |
||
Resolution: |
When reconciliation is about to be applied, the system checks if the calculation period at the start of the span belongs to the same span as the reconciled period. If not, reconciliation will not happen. |
||
38494170 |
3-42200427161 |
POL-17863 |
Process policy activities cannot be executed concurrently for a given policy |
Description: |
Only one process policy activity should run at a time for a policy as multiple concurrent process policy activities can lead to data inconsistency. |
||
Resolution: |
Only one process policy activity will be allowed to execute for a given policy at a time, others will be marked as complete with an attached error message. |
||
38542838 |
POL-17921 |
javax.persistence.NoResultException in CalculationPeriodRepositoryImpl |
|
Description: |
Log pollution is occurring due to inconsistent log levels, specifically using 'error' where 'warn' was appropriate. |
||
Resolution: |
Adjusted the log level from error to warn to reduce unnecessary log noise. |
||
38543054 |
POL-17923 |
Member level events for multiple policy versions (one in EDIT) status, not correctly processed |
|
Description: |
When a member is enrolled on an approved policy and enrolled on a policy in edit status: member level events are created for that policy in edit status, to ensure that those change events are included once policy is approved and premium is calculated. However, until that policy is not approved, unnecessary mutations were generated each time the generate mutations activity was executed for the already approved one. |
||
Resolution: |
Events that are created for member level events and policy edit status, will not be picked up by approved policies, so no mutations are generated. |
||
38380831 |
3-40209632171 |
POL-17712 |
Start date of Flex code is not updatable |
Description: |
After a flex code is created, the system does not allow updating its start date. Although the update request returns a 200 response, the start date remains unchanged. |
||
Resolution: |
The start date of a flex code has been made updatable. |
||
38592662 |
3-42647123201 |
POL-17952 |
Conditional value auto population and resetting using a triggering condition with property "default" is not working |
Description: |
Conditional display of a field’s value is not working when a default value is set in the floorplan |
||
Resolution: |
The field is now populating and updating its value correctly based on the triggering conditions when default is set in floorplan |
||
38543932 |
3-42462237041 |
POL-17925 |
Enrollment Names are not displayed in Run Example Calculation Dialog |
Description: |
Person formatted Name is not displayed in Run Example Calculation dialog. Enrollment member node is blank |
||
Resolution: |
Enrollment Names (formatted name) are displayed in Run Example Calculation Dialog |
||