Release Notes for Oracle Insurance Gateway Patch 4.25.1.0.6
This document contains the release notes for Oracle Insurance Gateway Patch 4.25.1.0.6.
| 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. |
| 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: |
4.26.1.0.0 |
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: |
4.26.1.0.0 |
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: |
4.25.1.0.4, 4.26.1.0.0 |
Additional Upgrade Steps
Pre-Upgrade 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 |
|---|---|---|---|
38876947 |
4-0001800026 |
OIG-4888 |
Exchange should continue processing if the datatransfer query doesn’t return any results. |
Description: |
When the query does not return any results(datatransfer location header gives a 204 response code), the data transfer exchange fails at the CheckDataTransferStatus step with the OIG-GATE-029 error. In the sub-exchange, the CheckDataTransferStatus fails with a NullPointerException under the same condition. In both cases, the exchange should continue processing and skip the CollectDataTransferData step. |
||
Resolution: |
Enhanced data transfer handling by skipping the CollectDataTransferData step when a 204 (No Content) response is received from CheckDataTransferStatus. This improvement applies to both the main flow and subflows. |
||
38819818 |
4-0001674695 |
OIG-4862 |
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. |
||
38832618 |
4-0001730662 |
OIG-4866 |
HICAPS/healthpoint requests are not being processed by the agent |
Description: |
The OHI Agent is unable to log on to HICAPS/HealthPoint devices and is failing to process requests. |
||
Resolution: |
OHI Agent is now able to log on to HICAPS/HealthPoint devices and processing requests successfully. |
||
38769154 |
4-0001366319 |
OIG-4833 |
Extract failures are now handled at the receivenotification step to ensure proper and efficient recovery flow |
Description: |
Recovering a failed extracts exchange doesn’t restart the collectData step making the recovery inefficient. To improve recovery handling, extract failures should be marked in the InvokeExtract step rather than in notificationCollectMessages step. On recovering the exchange after manual recovery of extracts, steps from InvokeExtract should be restarted. |
||
Resolution: |
For Extract use case, auto-recovery is always enabled. So code changes implemented in such a way when an Extract fails with Notification status marked as FAILED, the check recovery step fails all steps up to InvokeExtract. During manual recovery, the Extract recovery is initiated using the recovery link from InvokeExtract, ensuring proper restart of the recovery flow. |
||
38474169 |
3-42065414021 |
OIG-4664 |
Exchange endpoint returns Unsupported Media Type for certain XML files. |
Description: |
Certain XML files are misidentified as HTML files because of a bug in Apache Tika, the third-party dependency used for file type validation. As HTML files are not allowed as an input to exchange endpoint, Unsupported Media Type exception is returned as response. |
||
Resolution: |
While the bug in Tika is being resolved by Apache, we are allowing HTML files in exchange endpoint as a temporary fix. We will disallow HTML files again once the bug fix is delivered by Apache. |
||