Release Notes for Oracle Insurance Gateway Patch 4.24.1.0.1

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

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

In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases.

In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases.

Enhancements

No enhancements.

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

Perform any pre-upgrade steps.
Stop all the managed nodes running the existing version of the application.
Perform any pre-undeploy steps.
Undeploy the existing version of the application.
Back up the database.
Perform any post-undeploy steps.
Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.
Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.
Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.
Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)
Run the Upgrade script:
1. Open a command window and browse to <OHI_ROOT>/util/install.
2. Run the upgrade by executing ./ohi-update.sh .
Make the required changes to the ohi properties file
Perform any post-upgrade steps
Start WebLogic application server
Deploy the Application
Perform any post-deploy steps

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

Ref

Action

Description

OIG-3871

Modified

deliverByAgent step

If exchanges failed or timed out during the deliverByAgent step before the upgrade, it is not possible to recover them after the upgrade.

Bug Fixes

BugDB

SR

Internal

Summary

36946546

3-37313793651

OIG-3961

All the saved Parameters are not shown in View mode in Integrations page

Description:

Goto Integrations page, Create New Integration and Add Activity step, add more than 4 parameter values and save, on edit of parameters and save few parameters are missing.

Resolution:

All the saved Parameters are shown in View mode in Integrations page in Activity Step

37073869

3-36839446281

OIG-4042

OIG OOM issue due to accumulating of in-memory logs

Description:

The issue is due to the buildup in OIG heap memory caused by already opened financial transactions in policies that push notification messages.

Resolution:

In OIG, implemented a code fix to create a transaction and commit after every 50 downloaded notification messages as a resolution to this issue.

36662904

3-36813495181

OIG-3836

Buffer too small for CLOB to CHAR conversion during subflow recovery

Description:

In the sub-exchanges during recovery , using a VARCHAR2 data type as a placeholder to parse the Exchange Properties JSON string of data type CLOB caused issues when the string length exceeded 32700 bytes. This is a code-related issue.

Resolution:

Changed the data type of placeholder to CLOB to hold the Exchange Properties.

36994055

OIG-3976

Action button missing on exchange pages

Description:

All Action Buttons were missing from exchanges pages

Resolution:

Action buttons are visible on the exchanges pages and are interactable.

37303062

OIG-4142

Outbound exchange attributes are not set

Description:

When trying to build a data set the attributes exactVersionMatch and disableDeleteByOmission are not getting updated. The attribute inclusionDate is not updated when passing an empty value.

Resolution:

Implemented updates for the attributes exactVersionMatch, disableDeleteByOmission, and inclusionDate.

37095255

3-36840886581

OIG-4062

Scheduled Exchanges are triggered multiple times

Description:

If multiple Integrations with schedule are updated at a time, then all future scheduled exchanges are rescheduled. In a multi-node setup, due to an issue with scheduling mechanism, it is executed on multiple nodes at the same time. As a result, multiple instances of exchanges would be triggered.

Resolution:

The scheduling mechanism executes on one node at a time, thus avoiding creation of multiple instances of scheduled exchanges.

37063701

3-36788604651

OIG-4033

Exchange stops processing when Fusion ERP Job status polling fails due to an Error response from Fusion

Description:

If Fusion ERP Job status polling fails due to an Error response from Fusion (eg - 502 Bad Gateway), exchange stays in Waiting on External System (W) status. No logs are added, exchange does not Fail and recovery is not possible from this scenario.

Resolution:

If an Error response is received during Fusion ERP Job status polling, exchange fails with proper error message in exchange logs. Upon recovery, Fusion ERP Job status polling is restarted for the same job.

37607167

3-39759321701

OIG-4248

Deliverbyagent fails with npe when there is a raw payload created by previous step instead of a datafile

Description:

CheckAgentAvailability, DeliverByAgent, and ReceiveAgentNotification should be skipped when the previous step creates a raw payload instead of a datafile, as there are no files to deliver.

Resolution:

A conditional check has been implemented to skip the integration steps CheckAgentAvailability, DeliverByAgent, and ReceiveAgentNotification when a datafile is not available from the previous step.

37583287

3-39142193471

OIG-4238

Query step fails when more than 40 fields are specified

Description:

During invocation of an exchange in OIG, the Query Step is returning a 500 error with the message 'Bad Request: Request header too large.' This issue occurs when attempting to execute the query for more than 40 fields. While providing the same number of fields in Postman, we are getting the correct output. However, it is not working with the Query Steps in OIG exchange steps.

Resolution:

In order to tackle the header issue we are now passing the fields of the query in body of the request instead of passing in the header.

36748428

3-37002072411

OIG-3871

Exchange incorrectly marked completed during recovery without file delivery to agent

Description:

When an exchange containing a 'deliverByAgent' step fails and is subsequently recovered after resolving the underlying issue, the exchange is incorrectly marked as completed without actually delivering the file via the Agent. This behavior is also observed in sub-exchanges.

Resolution:

Delivery by Agent step is now split in three sub steps i.e. check agent availability, delivery by agent and receive notification.
Exchange status will now be 'waitingForExternalSystem' instead of 'waitingForAgentToSignoff' during the delivery by agent process.
Agent now uses notification endpoint to send the response back to Oracle Insurance Gateway instead of using the sign off and failure integration points.
It is now possible to configure 'timeAllowed' type config for the delivery step (using agent) within an integration.
For the integrations responsible for delivering large file using an Agent, it is recommended to set a higher allowed time for the delivery step to prevent time outs (default wait time is 5 minutes).
If exchanges failed or timed out during the deliverByAgent step before the upgrade, it is not possible to recover them after the upgrade.

37073790

OIG-4040

Failure on the postProcess step is marked incorrectly in previous exchange step

Description:

If the postProcess dynamic logic fails it should be marked in postProcess step itself. Its being marked in previous exchange step.

Resolution:

Adding a code change in the error handling part of the process fixed the problem and resolved the issue.

37223321

OHISD-3966

OIG-4106

Invoke exchanges tiles are shown with only retrieve access to exchanges.

Description:

Invoke exchanges tiles are shown with only retrieve access to exchanges.

Resolution:

Invoke exchanges tiles are not shown when only retrieve access is present on exchanges.

37438084

3-34889024331

OIG-4176

NullPointerException upon exchange recovery

Description:

When an activity step fails to return an appropriate response, the exchange can come into a state where recovery is impossible due to a NullPointerException occurring.

Resolution:

If upon recovery the activity notification does not exist, it is fetched with the location header

37522651

3-34889024331

OIG-4209

Sequence of Exchange steps does not follow the sequence defined for Integration steps

Description:

The sequence of Exchange steps does not follow the sequence defined for Integration steps when Integration step IDs are out of order compared to the steps sequence. Eg: For two integration steps defined in following sequence - Step 1 with a higher step ID and Step 2 with a lower step ID, when exchange is invoked, Step 2 is executed first, followed by Step 1.

Resolution:

The Exchange steps sequence follows the sequence defined for Integration steps irrespective of step IDs.

37506998

OIG-4200

Exchange Invocation Headers should be treated as case sensitive

Description:

When an exchange is invoked with exchange specific headers like ohi-exchange-description but with uppercase letters like Ohi-Exchange-Description, it is ignored because it is not in lowercase. According to HTTP RFC standard, headers should be treated as case insensitive and so OIG should accept the headers irrespective of case.

Resolution:

In order to make exchange specific headers case insensitive we are explicitly converting them to lowercase and then try to get the value of that header.

37248640

OIG-4111

Error when attempting to upload files to OIG

Description:

User experiences 406 (Not Acceptable) Error when attempting to upload files to OIG

Resolution:

It is possible to upload files in OIG without any error.

37093034

3-37860226571

OIG-4059

NPE in Eclipse Integrations

Description:

NPEs are raised for some eclipse integrations when the token is not retrieved successfully

Resolution:

There was a delay in the synchronization process between the keystore and the cache, which could lead to both being out of sync temporarily. The synchronization process has changed to make them consistent.

Issues that were backported in previous Release / Patch

No backports.