Release Notes for Oracle Insurance Gateway Patch 4.24.1.0.4
This document contains the release notes for Oracle Insurance Gateway Patch 4.24.1.0.4.
| 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. |
Enhancements
| ID | Summary | Patch |
|---|---|---|
NXT-31617 |
Increase the length of scope attribute on OAuthClientCredentialsGrantConfiguration entity The scope attribute in the OAuthClientCredentialsGrantConfiguration entity is currently limited to 100 characters which is insufficient to store scope values. |
|
OIG-4336 |
Method to keep long running transaction alive with database During the transformation process in OIG, a data file is created and several requests are sent to the Policies system to fetch additional information. These requests can take varying amounts of time to complete, depending on the size of the data and how quickly the other system responds. While waiting for these responses, the connection to the database is not actively used. Because of this inactivity, the system may automatically close the connection after a certain period of time. When the process tries to update the data file after the responses are received, it fails with a timeout error, as the original connection to the database is no longer valid. Documentation Links: |
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 ofohi_install.cfg.templateand name itohi_install.cfg. -
Edit
ohi_install.cfgto 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:
-
Open a command window and browse to
<OHI_ROOT>/util/install. -
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
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
37995022 |
3-40662938551 |
OIG-4449 |
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. |
||
37923651 |
OIG-4413 |
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 |
||
37994294 |
OIG-4446 |
'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 |
||
38014606 |
OIG-4457 |
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 |
||
38001709 |
OIG-4452 |
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' |
||
37994213 |
OIG-4443 |
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. |
||
38282097 |
OIG-4542 |
Tracking/Tracing of requests should not be sent to external systems |
|
Description: |
Tracing headers (such as B3 headers) are being sent to external systems. This leads to a 500 error response. However, when the spanId header is removed, the request goes through successfully with a 201 response |
||
Resolution: |
B3 Tracing headers will be added when the host of the request and the application are identical. |
||