Release Notes for Oracle Insurance Gateway Patch 4.23.1.0.2

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

Version compatibility: Oracle Insurance Gateway Release 4.23.1.x is only compatible with other Oracle Health Insurance applications release version 4.23.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.
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-28569

Migration of credentials from OPSS to ohistore

4.23.2 Release does not support opss anymore hence two new endpoints have been developed to export existing keystore/credentials. This functionality can be used while upgrading to 4.23.2 and moving away from opss/vault to ohistore.

Configuration Properties

This section intentionally left blank.

Web Services

Ref Action Description

NXT-28569

Added

Export Keystores

Export existing keystores

NXT-28569

Added

Export Credentials

Export existing credentials

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.

Bug Fixes

BugDB SR Internal Summary

35775565

OIG-3384

Exchanges with autoRecovery which fail generate stacktraces with NullPointerException

Description:

When a process invoked by an integration with autoRecovery true results in failure, the exchange fails as expected. In this case, it is also generating stacktraces with NullPointerException.

Resolution:

The NullPointerException no longer occurs in this case.

36156181

3-35334218641

OIG-3565

Agent fails to start up with logging enabled

Description:

When trying to start the agent with property "agent.rest.client.logging" enabled, a ClassNotFoundException is thrown.

Resolution:

The agent succesfully starts up with the logging property enabled.

Issues that were backported in previous Release / Patch

No backports.