Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.9
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.9.
| Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.23.2.x is only compatible with other Oracle Health Insurance applications release version 4.23.2.x unless explicitly stated otherwise. |
| As per the Service Description, you are obligated to request a service upgrade within 90 days of this release being generally available (GA). In line with the Oracle Cloud Services Pillar document, Section 4.2.2 End of Life, this release will be EOL in 12 months. |
Enhancements
| ID | Summary | Patch |
|---|---|---|
POL-15792 |
Optimize loading of SVNTV fields into the memory during extracts Currently, the system loads all the Single Value Non-Time Valid(SVNTV) dynamic fields associated with resources into the memory which causes OOM. Only the required SVNTV dynamic fields should be loaded into memory while processing the extracts. |
4.23.1.0.8, 4.24.1.0.1 |
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
36925407 |
3-37554577351 |
POL-15663 |
Evaluate Conditions not working in Edit Mode |
Description: |
Evaluate condition in floorplan not working for the first time in edit mode. Its working fine in create mode. initconditions are not used in floorplan, as evaluateconditions are not working as intended when used with initconditions |
||
Resolution: |
Evaluate conditions are working in edit mode as well as expected |
||
37091028 |
POL-15943 |
Include stand alone catchUp periods when running APPLY_REGISTRATIONS activity |
|
Description: |
During the APPLY_REGISTRATIONS activity, periods are (re)generated and used to apply registrations. CatchUp periods are defined as periods that start before the reference input date. When the system generates periods, the catchUp periods are only generated in combination with the first regular cycle, which is the period starting on the reference date. If the first regular cycle is not generated, neither are the catchUp periods, causing gaps when the first regular cycle is never generated (for example when the reference date is after the end date of the collection setting). |
||
Resolution: |
The Apply Registrations activity does not make a distinction between catchUp periods and regular periods so registrations can be applied to catchUp periods only. |
||
37157979 |
POL-16046 |
Reconciliation is not applied when enrollment period ends in the mid of calculation period |
|
Description: |
When the enrollment period ends in the middle of a calculation period, meaning the calculation period segment’s end date does not match the span end date, reconciliation is not applied. Instead, the amount is calculated as the product of the daily rate and the total days enrolled within the segment. This leads to discrepancies between the expected and actual outcomes. |
||
Resolution: |
Reconciliation is now applied to the calculation period segment where the enrollment ends, treating it as the last period segment. This has resolved the discrepancy between the expected and actual outcomes. |
||
37093053 |
POL-15947 |
Parameter Amount Value is saved With Default Value instead of zero |
|
Description: |
Parameter Amount Value is saved With Default Value when value zero is sent. |
||
Resolution: |
Parameter Amount Value is saved with value zero instead of default value |
||