Release Notes for Oracle Insurance Gateway Patch 4.25.1.0.11
This document contains the release notes for Oracle Insurance Gateway Patch 4.25.1.0.11.
| Version compatibility: Oracle Insurance Gateway Release 4.25.1.x is only compatible with other Oracle Health Insurance applications release version 4.25.1.x unless explicitly stated otherwise. |
Enhancements
| ID | Summary | Patch |
|---|---|---|
OIG-4349 |
Incremental Data Transfer This enhancement introduces native support for incremental data transfers, enabling the system to transfer only new or updated data by default. It also allows users to define custom data transfer ranges using exchange properties, supporting recovery scenarios and providing greater flexibility. |
4.26.1.0.0 |
Additional Upgrade Steps
Post-Deploy Phase
1) OHI Agent upgrade
Upgrade OHI Agent: Refer to Downloading and Running Oracle Health Insurance Agent for steps to perform the Agent upgrade.
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
38582458 |
4-0001723099 |
OIG-4698 |
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. |
||
39811185 |
OIG-5283 |
Save integrations after navigating between activity steps not working |
|
Description: |
When users open an integration with multiple activity steps, navigate from one activity step to another, modify the second step, and save the integration, the application displays GEN-PROC-ERROR and does not save the changes |
||
Resolution: |
The Integrations page now saves the integration correctly after users navigate to another activity step and modifies it. |
||
39920336 |
OIG-5323 |
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. |
||
39839575 |
4-0003440307 |
OIG-5294 |
Indicator Expect Notification value update is not reflecting on UI on saving a subflow record with integration step configured |
Description: |
When a user creates a subflow with an activity step and updates the indicator expect notification, the change is not reflected in the UI after saving the step. |
||
Resolution: |
The indicator expect notification update is reflecting on UI when user creates subflow with an activity step |
||
39881523 |
4-0003256970 |
OIG-5307 |
0420-170000 exchange does not cancel claim if the original claim transaction exchange timed out |
Description: |
An AS2805_A Claim Transaction Reversal or AS2805_B Claim Void message triggers a 0420-170000 exchange in OIG. This exchange is responsible for cancelling the claim created earlier as part of the AS2805_A or AS2805_B Claim Transaction message. However, if the original Claim Transaction timed out in OIG while waiting for Claims, this claim cancellation does not happen because the claim cancel URL is unavailable. |
||
Resolution: |
When AS2805_A Claim Transaction Reversal or AS2805_B Claim Void message triggers a 0420-170000 exchange to cancel a Claim Transaction that timed out in OIG, the cancel URL is derived and the original claim is successfully cancelled. |
||
39522249 |
4-0002897772 |
OIG-5189 |
Exchange was marked as completed even though one of its related sub-exchanges had not finished and had timed out. |
Description: |
During recovery of timed out sequential subflows, the main exchange moved ahead to early and could be marked as completed before all sub-exchanges had actually finished |
||
Resolution: |
The recovery flow is corrected, the parent exchange waits properly on recovery of the timed-out sub-exchanges. If the sub-exchange times out again, the main exchange shows the correct status timed out. |
||
39823003 |
OIG-5286 |
Navigating from View log lines of a sub exchange using back button is not working properly |
|
Description: |
When users open View Log Lines from a Sub Exchange, clicking the Back button does not return them to the originating Sub Exchange detail page. Instead, navigation context is lost and users may be directed to the main Exchanges page. |
||
Resolution: |
The Back button now returns users to the originating Sub Exchange detail page, preserving the navigation context. |
||