Release Notes for Oracle Insurance Gateway Patch 4.26.1.0.1

This document contains the release notes for Oracle Insurance Gateway Patch 4.26.1.0.1.

Version compatibility: Oracle Insurance Gateway Release 4.26.1.x is only compatible with other Oracle Health Insurance applications release version 4.26.1.x unless explicitly stated otherwise.

Enhancements

No enhancements.

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.

Configuration Properties

This section intentionally left blank.

Web Services

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Access Restrictions

This section intentionally left blank.

Bug Fixes

BugDB SR Internal Summary

40085860

4-0003904832

OIG-5465

Incorrect default for agent.gateway.websocketuri in Tomcat

Description:

The Agent WebSocket URI explicit configuration is mandatory when connecting to a Gateway application running on Tomcat server, whereas it is optional for a WebLogic server. This represents a breaking change to customers introduced in 4.26.1.0.0.

As a workaround: configure the Agent property "agent.gateway.websocketuri" and the value should match "agent.gateway.uri", excluding the /api suffix.

Example:

URI specifies the OIG Gateway exchange endpoint.
agent.gateway.uri=https://ABC.com/uat/oig/api
URI specifies the OIG Gateway websocket URI.
agent.gateway.websocketuri=https://ABC.com/uat/oig

Resolution:

The Agent now connects to the Tomcat-compatible websocket URI by default.

39941132

OIG-5345

Improved stash item retrieval performance.

Description:

Retrieving items by unique key could become increasingly slow for large stashes.

Resolution:

Database access was optimized to improve unique-key lookup performance for large stashes.

39895791

4-0003389512

OIG-5311

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

39891049

OIG-5309

Fusion Financials Deliveries Can Use the Wrong Transformation Output

Description:

When an integration generates several files before delivery, a Fusion Financials delivery can use data from the most recently completed transformation instead of its selected source transformation. This can send the wrong file to Fusion Financials and cause the delivery to fail.

Resolution:

Fusion Financials deliveries now use data from their selected source transformation. Existing integrations can generate all files before starting their corresponding deliveries. No configuration changes are required.

39881521

4-0003256970

OIG-5306

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.

40089656

OIG-5467

DBMS_CLOUD CSV exports incorrectly escape JSON values causing column misalignment in excel

Description:

Operational reporting CSV exports generated through DBMS_CLOUD do not correctly quote and escape JSON-valued fields. As a result, commas within JSON are treated as CSV delimiters when opened in Excel. This splits one JSON value across multiple columns and misaligns data with its headers. The issue is observed only in cloud environments.

Resolution:

Updated OPERATIONAL_RPT_PKG to handle text containing commas, quotation marks, or line breaks correctly. This helps keep values in the right columns when the exported file is opened.

Issues that were backported in previous Release / Patch

No backports.