Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.22
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.22.
| 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. |
| 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. |
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
39747746 |
4-0003279914 |
POL-18926 |
Amount Parameter Value Floorplan Uses paramterAlias Title Property |
Description: |
The delivered Amount Parameter Value floorplan uses the title property paramterAlias instead of parameterAlias. Although the property name appears to be a typographical error, changing it to parameterAlias is causing existing parameter amount values to display incorrectly in Edit mode. |
||
Resolution: |
Fixed the display of Parameter Value properties and corrected the property name typo in the Number of Units, Percentage, Service Days, and Amount Parameter Value floorplans. Custom floorplans for these pages should also be updated to use the correct property name, "parameterAlias". |
||
39875612 |
POL-19051 |
Not Authorized error in persons Page |
|
Description: |
A user with the Persons Access Grant receives an authorization error when opening the Persons page. The page requests specialty data that the grant does not permit the user to access. |
||
Resolution: |
The Persons Access Grant now permits access to the specialty data that the Persons page requires. A user with this grant can open the Persons page without an authorization error. |
||
39768966 |
4-0003326305 |
POL-18936 |
Reference sheet lines remain unavailable after creating flex codes removed through CMT |
Description: |
Reference sheet lines are not returned when they reference a flex code that was missing during an earlier lookup and is subsequently created. The missing lookup result remains cached, so the reference sheet lines remain unavailable until the affected application nodes are restarted. |
||
Resolution: |
When a previously missing flex code is created, its flex-code lookup is refreshed. Associated reference sheet lines are returned without restarting application nodes. |
||
39959076 |
4-0003638382 |
POL-19139 |
Policy enrollment time valid multi value flex code values are not displayed against their respective start date and end date after collapse and re-expand in edit mode when sort is configured |
Description: |
When sort criteria is configured for a multi-value dynamic field, collapsing and re-expanding the policy enrollment in edit mode may cause the field columns to display out of the configured sort order |
||
Resolution: |
All columns of multi-value dynamic fields are correctly sorted based on the configured sort criteria after collapsing and re-expanding the member in edit mode. |
||
39902776 |
POL-19076 |
Dynamic logic security checks fail for unresolved Groovy receiver types |
|
Description: |
Dynamic logic execution could fail with a NullPointerException when the receiver type of a Groovy method call could not be resolved during security rule evaluation. |
||
Resolution: |
Dynamic logic security predicates now safely handle unresolved receiver types, allowing valid dynamic logic execution to continue without a NullPointerException. |
||
39953738 |
4-0003656939 |
POL-19132 |
File is not downloaded in Reference sheet lines page |
Description: |
Download option not working for Reference sheet lines. When clicking on Download option getting error and lines are not getting downloaded. |
||
Resolution: |
Able to download csv file in Reference sheet lines page. |
||
39856272 |
4-0003233561 |
POL-19030 |
Bulk Update activity remains stuck when a queued policy is reverted before processing |
Description: |
During a Bulk Update, one policy was reverted while the Bulk Update was already running but before that policy’s queued child activity had started processing. When the child activity was later picked up, the policy was no longer available. The system did not handle this situation correctly, so the child activity remained stuck instead of moving to a terminal error status. All other activities in the Bulk Update completed successfully. |
||
Resolution: |
For all policy activities, not only Bulk Update activities, if a policy is reverted or deleted before its queued activity is processed, the system detects that the policy is no longer available and handles the activity gracefully. For each policy activity where the policy is no longer available, informative message POL-IP-POLI-044 is added and the activity is set to status Completed. |
||
38576490 |
4-0002317078 |
POL-17937 |
Writing incident data files in Object Storage fails intermittently |
Description: |
Writing an incident data file in Object Storage fails intermittently with NoSuchElementException |
||
Resolution: |
The intermittent issue that prevented incident data files from being written to Object Storage has been resolved. The fix improves the reliability of file creation and storage operations. |
||
39889259 |
3-39952004651 |
POL-19057 |
Create invoice process should select reversal transaction detail only if there is no non-reversal transaction |
Description: |
Currently system selects the financial transaction detail having maximum detail ID while creating financial message chunks for a bulking group. This process doesn’t distinguish between reversal and non-reversal details and wrongly assumes non-reversal entries always have the highest ID. Since detail ID order depends on non-deterministic caching and processing behavior, this approach is unreliable and fails in edge cases. |
||
Resolution: |
The transaction detail selection logic has been updated. Within a bulking group, non-reversal details are now prioritized over reversal transactions. The detail with the maximum ID among non-reversal entries is selected and a reversal detail is chosen only if no non-reversal details exist. |
||