Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.6
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.6.
| 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. |
Enhancements
| ID | Summary | Patch |
|---|---|---|
NXT-31592 |
Conditionally disable actions for the claims and policies page This enhancement introduces the ability to disable the following buttons conditionally:
Documentation Links: |
|
POL-16632 |
Set policy enrollment event text parameters This enhancement introduces the ability to set custom text parameters in business event messages (Business Policy Enrollment events) through the business event dynamic logic condition. Furthermore, this enhancement enriches the functionality of the business event dynamic logic condition for evaluation of the Business Event Rules:
Documentation Links: |
Web Services
| Ref | Action | Description |
|---|---|---|
POL-16632 |
Modified |
Compare policy versions Every single change that matches a business event rule leads to the creation of a policy enrollment event |
Dynamic Logic
| Ref | Action | Description |
|---|---|---|
POL-16632 |
Added |
getActivePolicy Predefined method that retrieves the active version of the policy |
POL-16632 |
Modified |
businessEvent This dynamic logic condition has the new or updated object as input parameter and offers the possibility to set custom text parameters |
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
38508710 |
POL-17884 |
Premium calculation for last period is incorrect for evenly distributed yearly contracted policy when the calendar month split is disabled |
|
Description: |
The calculated premium amount for the last period of an evenly distributed yearly period contracted policy does not match the expected value when the calendar month split setting is disabled. This issue occurs when the policy contract begins on February 28th of a non-leap year. |
||
Resolution: |
A discrepancy existed between the contract periods and the generated policy calculation periods. The logic for generating contract periods has been corrected to align with the generated PCPs for yearly periods in leap years. |
||
38388214 |
3-41612607721 |
POL-17721 |
Reversed Calculation Results included during reconciliation calculation |
Description: |
When reconciliation is applied to the last period of a period span, the system will look for the latest version of the calculation results that have a start date between the start of the span and the start of the last period. In fact, the system will look for all the start dates of the calculation results within that period, and afterwards takes the latest Calculation Result version per start date. This means that if the latest Calculation Result is reversed, it is also included in the search. At the end, all the amounts of those Calculation Results are added up and subtracted from the amount that should be paid for the entire span. |
||
Resolution: |
Reversed Calculation Results are not included in the search during reconciliation. |
||
38412153 |
3-42051417011 |
POL-17747 |
"Domain Values" is not showing in Parameter Domain Values Tab in Enrollment Products |
Description: |
Not able to view Domain Values in Parameter Domain Values Tab of Enrollment Products page after a new Domain Value is created and saved. Page has to be reloaded to view Domain Values. |
||
Resolution: |
After new domain value is created in Parameter Domain Values tab of Enrollment Products page, it is shown immediately, without having to reload the page |
||
38393117 |
3-41972506271 |
POL-17726 |
Notation To Be Shown After Parameter Values |
Description: |
Notation to be shown after the parameter vales like units, days, % or $ accordingly in policies and member page |
||
Resolution: |
Added notations for unit, days, percentage in policies and members page for parameter values |
||
38414587 |
3-42030672651 |
POL-17753 |
500 Internal server error occurs when populating the province field in the group account address under the extensibility tab |
Description: |
A 500 Internal Server Error occurs when populating the province field in a group account address under the Extensibility tab, where the province field is configured under record definition to use CountryRegion as a picklist |
||
Resolution: |
Query is created as expected and the list of values is loading successfully without any errors |
||
37859797 |
3-40389292391 |
POL-17055 |
Enhanced diagnosability and error handling for transactions marked as Rollback |
Description: |
Some activities took longer than expected time to complete because the transaction that updates the status of activities was silently rolled back due to an exception being suppressed within dynamic logic. |
||
Resolution: |
Added the exception in no rollback attribute to prevent silent rollbacks. |
||
38476501 |
3-42101202791 |
POL-17849 |
Unable to Select a Product when Group Account Product Availability is in the Future |
Description: |
When a Group Account or Insurable Class is setup with future effective dates, when trying to enroll a member in policies, the Product drop down is not displaying any available products to select |
||
Resolution: |
Applicable products are displayed in dropdown when Group Account Product Availability is in the future. |
||
38462492 |
POL-17812 |
Enrollment product: adjustment override : copy button not working |
|
Description: |
Copy button is shown in adjustment override for Enrollment products though the page doesn’t have create access |
||
Resolution: |
The copy action is removed in adjustment override for Enrollment products. |
||
38497092 |
3-42214428861 |
POL-17865 |
Policies widget is not available when a policy is opened |
Description: |
On navigating to Policies details page from widget and back to search page, widgets and tiles are not visible |
||
Resolution: |
Widgets and tiles are visible when we navigate to search page from details and there is no search criteria |
||
38406116 |
3-42061494681 |
POL-17741 |
Person’s formatted name is not shown in Policies page |
Description: |
Person’s formatted name is not shown in policy detail page and search page. |
||
Resolution: |
The person’s formatted name now displays consistently on the Policy Detail Page, Policy Search Page based on configuration |
||
38498939 |
3-42254617011 |
POL-17870 |
Policy Premium: Policy reversal calculation results are dispalyed |
Description: |
Policy Reversal field is excluded from the fields being queried. As a result reversal calculation was not happening properly. |
||
Resolution: |
Policy Reversal Calculations are displayed properly. UI filters out the reversed transactions. |
||
38494159 |
3-42204313821 |
POL-17862 |
Not all calculation results are reversed when collection setting start date is moved to a date after a date from a previous version of a policy. |
Description: |
When a collection setting with generate policy calculation periods set to true and policy is approved and premium calculated, and a next version has a collection setting with a start date after the previous one: not all calculation results are reverted. For example: Create a policy with a collection setting startDate 2025-09-01, approve and calculate premium. Then, create a new version with a collection setting start date of 2025-09-05, approve and calculate premium. Calculation result starting on 2025-09-01 is not reversed. |
||
Resolution: |
The cause is that when looking at calculation results to be reverted, the new start date of the earliest generated policy calculation period is used. Thus skipping the ones that started on the previous earliest generated policy calculation periods. This is solved by including calculation results that are starting after or on the earliest effective date of mutations of type Recalculation. |
||