Release Notes for Oracle Insurance Gateway Patch 4.25.1.0.1

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

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.
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:

  1. Perform any pre-upgrade steps.

  2. Stop all the managed nodes running the existing version of the application.

  3. Perform any pre-undeploy steps.

  4. Undeploy the existing version of the application.

  5. Back up the database.

  6. Perform any post-undeploy steps.

  7. Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.

  8. Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.

  9. Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.

  10. Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)

  11. 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 .

  12. Make the required changes to the ohi properties file

  13. Perform any post-upgrade steps

  14. Start WebLogic application server

  15. Deploy the Application

  16. 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

This section intentionally left blank.

Bug Fixes

BugDB SR Internal Summary

37995019

3-40662938551

OIG-4448

User information is not available in floorplans using userJET property

Description:

The userJET property in the floorplan does not support setting default values or filtering data based on the current user.

Resolution:

Id and displayName fields of userJET property can be used in the floorplan for setting default values or filtering data based on the current user.

37923644

OIG-4412

When a field of type Number is configured as LOV in Search, it is returning 'undefined'

Description:

Configure Advance Search in Exchange Search custom floorplan with property as 'createdBy' with reftype as 'users'. Select a Value in Advance Search for LOV field 'createdBy'. There is an error - "GEN-PROC-002: Value "undefined" provided is not of type Number"

Resolution:

'createdBy' with reftype as 'users' configuration works fine in advance search

37994275

OIG-4445

'UserJET' property should expose userid, login name, display name, last login timestamp, defaultCountry information

Description:

userJET property is exposing only displayName and id fields and not rest of the information in UserInformation IP

Resolution:

userJET property gives access to user id, login name, display name, last login timestamp, defaultCountry information about the logged-in user

38014602

OIG-4456

Permissions error thrown in exchange search page

Description:

Setup access role has inconsistency between OIG, NXT, POL applications. Widgets API entry is missing in OIG, hence permissions error thrown in exchange search page

Resolution:

Widgets API permission error is not shown in OIG Exchanges page

38004405

OIG-4454

Implement retry mechanism and content length verification during data file download in OIG

Description:

If an exception is encountered during data file download in OIG due to java.io.EOFException, the data download process fails and has to be recovered manually. A retry mechanism can be introduced that retries the download with some time gap so that the failure can be avoided altogether. Also, if an incomplete data file is received in OIG due to connection closed by external system, the partial data file is saved and step is marked as Done, leading to potential issues in later steps. A content length verification method can be introduced that verifies that the content-length returned in response header is same as size of downloaded data file so that the step can be marked Failed if data file is downloaded partially.

Resolution:

To address issues of incomplete or failed data file downloads in Oracle Insurance Gateway (OIG), a content length validation has been implemented. This mechanism is triggered when OIG detects partial data by comparing the actual content length with the expected value provided in a custom response header X-Content-Length. This header is now included in the POL/NXT data file response to facilitate accurate validation. If a mismatch is found, indicating a partial download, the system will automatically log and retry the download to ensure the complete file is retrieved.

Note : The content length validation will only happen if X-Content-Length header is available in the response of the Data File IP. Please check if the fix is implemented in the applicable OHI Component by checking the release notes for a bug fix with summary containing 'custom content-Length header'

37994183

OIG-4441

Performance degradation during OIG purge operations

Description:

The auto-purge job has been scheduled successfully. While the majority of purging tasks and batch data processing completed within a few hours, the OIG_EXCHANGE_LOG purge has been running for an extended period without completion.

Resolution:

The OIG purge operation is now completing within the expected duration after optimizing the purging logic by implementing a commit-size based design.

38179115

OIG-4498

The datatype of the type_config column in the oig_integration_steps table should be modified to CLOB to accommodate larger typeconfig objects.

Description:

The datatype of the type_config column in the oig_integration_steps table should be modified to CLOB from varchar2(4000) to accommodate larger typeconfig objects.

Resolution:

The datatype of the typeConfig column in the oig_integration_steps table is changed to CLOB.

38210135

OIG-4513

All the servers experience decline in performance after invoking dynamiclogic/invalidateall

Description:

The dynamiclogic/invalidateall integration point triggers a recompilation of all the dynamic logics across all the application servers. Since dynamic logic compilation is a resource-intensive process, this operation causes performance decline on all the servers.

Resolution:

Dynamic logic is compiled on a single server, allowing other servers to reuse the compiled output. The performance of the other servers isnot impacted.

38186900

OIG-4500

collectDataTransfer step is failing with unique constraint error while downloading more than 1 file

Description:

While downloading more than one file in the collectDataTransfer step, exchange is failing with the following unique constraint error. ORA-00001: unique constraint (OHI_OIG_OWNER.DAT_DATA_FILE_UK1) violated. This is happening in on-prem deployment.

Resolution:

collectDataTransfer step now can download more than one file in on-prem deployment. The collectDataTransfer step’s processing logic has been updated to precisely parse and extract unique filenames from the data transfer IP’s response.

Issues that were backported in previous Release / Patch

No backports.