Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.13
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.13.
| 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-32017 |
UI: Additional Features Advanced Search With this enhancement, the following multiple capabilities are added to the advanced search:
Documentation Links: |
|
NXT-32037 |
User Interface - Additional tab features Added a “Close Other Tabs†option via a three-dot menu to close all but the active tab, auto-scroll to keep the active tab visible, and improved tab closing behavior to fall back to the previous tab when closing the last tab. |
|
NXT-32633 |
UI: Additional Features Sort With this enhancement, the sort component is updated to display null values based on the sort order, that is, for Default and Criteria:
It is now possible to specify sorting criteria for a multi-value property (list) configuration in a form and region. Documentation Links: |
|
NXT-33488 |
Remove outer join for 'And' mode quick search As part of this enhancement outer join is removed from "AND" mode based quick search and selection pop-up in LOV field. Also, outer join is removed for searches on insurable entity field in JET UI when used in quick search "OR" mode |
|
POL-18132 |
UI: Conditional display of row-level actions: edit and delete for tabs. This enhancement introduces the ability to control the display of actions (edit/delete) through initconditions. Documentation Links: |
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
38913247 |
POL-18310 |
AbstractNotificationTask logs the error only at WARN level |
|
Description: |
When the notification endpoint is invalid, the error is logged at the warning level after reaching the maximum number of retry attempts. This makes debugging challenging because the underlying cause remains unclear. |
||
Resolution: |
When the notification endpoint is invalid, the error is logged at the error level after exhausting all retry attempts, clearly indicating the cause of the issue. |
||
38953359 |
POL-18344 |
Quote IP returns no results when parameter amount format differs from premium line amount format |
|
Description: |
Calculation results were not returned if the format of the parameterAmount in the payload(decimal or non-decimal) differed from the format of the amount defined in the premium line. For example, if the premium line amount was 200 and the parameterAmount in the request was sent with 200.00, or vice versa, the system failed to recognize them as the same value. Although the numerical amounts were equal, the difference in format caused the premium line selection to fail. |
||
Resolution: |
The amount comparison logic has been improved to ensure that amounts are matched based on their numerical value rather than their formatting. With this fix, Quote IP now correctly matches the premium line and returns calculation results regardless of whether the amount is provided in decimal or non-decimal format. |
||
38819806 |
POL-18216 |
Dynamic logic fails when an output writer is created but no data is written in data file stored in object storage |
|
Description: |
Dynamic logic fails when the output writer is instantiated even though there is no data to process and no write operation is performed on the data file stored in object storage |
||
Resolution: |
The system allows the output writer to be instantiated and closed without performing any actual write operation on data file stored in object storage. |
||
38837201 |
POL-18228 |
Extended Support for ohiHttpRequest Across Additional Signatures |
|
Description: |
Previously, ohiHttpRequest was accessible only from dynamic logic of Callout Rule signature |
||
Resolution: |
ohiHttpRequest is now accessible from additional signatures, including (but not limited to) Change Event Rules, Test Units, and Policy Validation Rules |
||
38846582 |
POL-18243 |
Node crash when outbound messages are sent to external application in certain scenario |
|
Description: |
Node crash when outbound messages are sent to external application in certain scenario. |
||
Resolution: |
Added appropriate fix and checks to ensure smooth working of node. |
||
38596960 |
POL-17955 |
Can’t add new columns to flex codes definition if it has no descriptor field |
|
Description: |
While Adding a new row in the Flex Code Field Usages (Record Fields) tab for an existing Flex Code Definition without a descriptor field triggered a confirmation dialog to save the definition without a descriptor field, but the Save action on this dialog did not function as expected |
||
Resolution: |
Save action on the confirmation dialog for saving a Flex Code Definition without a descriptor field now works as expected |
||
38741307 |
POL-18148 |
If an error occurs during validate policy operation, the response is unclear and the actual error is not shown |
|
Description: |
If the dynamic logic for validation rules causes some failure, like a business rule violation or invalid dynamic logic, then the response is incorrect. It gives 500 error instead of 422 and the error message is unclear: "GEN-PROC-ERR: An error occurred in processing the request; for more information about the error search the logging for occurrences of …" (where the dots represent the original exception raised). |
||
Resolution: |
The handling of errors is improved for validate policy to show the proper response. The handling of business rule errors because of dynamic logic called in submit policy process has also been changed: activity message shows the proper business rule message and the activity ends in "Business Error" status instead of "Technical Error". |
||
38822270 |
POL-18217 |
Ensure Each Extracted Record from NDJSON in Data Transfer IP is a Valid JSON Object |
|
Description: |
NDJSON exports contain embedded newline and special characters breaking JSON parsing. |
||
Resolution: |
Fix has been provided for extraction pipeline to escape or remove illegal characters within large records with datasets containing embedded newlines and special characters there by creating valid JSON and CSV file formats. |
||
38835242 |
POL-18227 |
Several issues when logging policy enrollment events for persons |
|
Description: |
The next issues occur when policy in IP is used and pre-enrollment functionality: a) For a new policy, change detail information for person details like address is not logged b) For a new policy and a change on existing person was applied, the change detail information for person is not logged either. c) When a person is both a policyholder and an enrolled member and changes are applied, duplicate business events are created. |
||
Resolution: |
Logging of person details is added when a new policy is added and when business events are generated, duplicates are omitted. |
||
38968510 |
POL-18353 |
The business rule FIN-REGI-004 does not allow updates on registrations of type Bill (AU-only) |
|
Description: |
FIN-REGI-004: It is not allowed to update type, correlationId, amount, payDate and appliedPayDate for a registration or delete a registration. Which prevents updates on all registration, regardless of the type. This should be changes to prevent updates on registrations of type Payment only. |
||
Resolution: |
Added restriction on type Payment when checking business rule FIN-REGI-004. |
||
38477388 |
POL-17851 |
Group Accounts - Boilerplate issue on click of Add Group Account Product button |
|
Description: |
Boilerplate key is seen on click of Add Group Account Product button instead of proper translations |
||
Resolution: |
Added boilerplate for Create Group Account Product text so that translations are displayed instead of boilerplate key |
||
38975941 |
POL-18369 |
Unable to login to the application after a logout |
|
Description: |
Users are experiencing a login failure after they log out of the application. Attempting to log back in immediately does not work unless they manually clear their browser cache, cookies, and history. Once the browser data is cleared, login proceeds as expected. |
||
Resolution: |
After logging out, users are able to log in again normally without the need to clear browser cache, cookies or history. |
||
38853119 |
POL-18251 |
Delete of premium schedule (line), add-on, adjustment rule or schedule definition can be very slow |
|
Description: |
Calculation result lines have references to premium schedule (line), add-on, adjustment rule and schedule definition using foreign keys, but corresponding indexes do not exist. So when for instance a premium schedule line is deleted, a check on calculation result line references is executed causing a full table scan on the latter. |
||
Resolution: |
The foreign keys are replaced by validation rule: POL-RULE-VAL-004: <enityName> cannot be removed as it has at least one reference in calculation result lines. This is to control the query executed for the check for references better when for instance a premium schedule line is deleted. Also indexes on these reference id’s are added on calculation result lines. |
||