Release Notes for Oracle Insurance Gateway Patch 4.25.1.0.2
This document contains the release notes for Oracle Insurance Gateway Patch 4.25.1.0.2.
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. |
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-31011 |
Access Restriction on Download Feature This enhancement links the ability to download data from the JET user interface to a user role. Only users with access to the Download Data restriction grant can download data from JET UI using the download action. |
|
OIG-2876 |
Display Enabled Integrations Only In Exchange Invocation LOV This enhancement filters the list of values for integrations during exchange invocation through the user interface. When invoking an exchange through the user interface, the applicable integration has to be selected. This enhancement implements the feature that only enabled integrations are displayed in the list of values. This is particularly relevant when an integration has multiple versions. Typically, only one of the versions is enabled and should show up in the list of values when invoking an exchange. |
|
POL-17575 |
Reset a value using floorplan conditions With this enhancement, a new optional floorplan property Documentation Links: |
Additional Upgrade Steps
This section describes the steps that a functional application manager will take during the upgrade. These steps are to be performed by an application user who is authorized to access the IPs.
Post-Deploy Phase
-
Upgrade OHI Agent
Refer to Downloading and Running Oracle Health Insurance Agent for steps to perform the Agent upgrade.
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.template
and name itohi_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:
-
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
Data Conversion
Ref | Action | Description |
---|---|---|
NXT-31011 |
Added |
OHI_ACCESS_RESTRICTION_GRANTS The new access restriction will be provided to all non system active roles (with retrieve flag as Y), having at least a system function access grant with retrieve flag as Y |
UI Changes
Ref | Action | Description |
---|---|---|
OIG-2876 |
Modified |
IG0001 Exchanges Page Integration version is added |
OIG-2876 |
Modified |
Integration LOV Integration LOV system floorplan is updated to show property selector |
OIG-2876 |
Modified |
Invoke Exchange Pages Only 'enabled' integrations are shown in integrations LOV |
Breaking Changes
Ref | Action | Description |
---|---|---|
NXT-31011 |
Added |
OHI_ACCESS_RESTRICTION_GRANTS JET (UI) will implement a new access restriction called "Download 'Data'" to manage the visibility of the Download button. Users who are not granted this access restriction will no longer see the download action, making this a breaking change. |
Access Restrictions
Ref | Action | Description |
---|---|---|
NXT-31011 |
Added |
OHI_ACCESS_RESTRICTIONS_B A new access restriction of type DWDATA and code as UI_DATA_DOWNLOAD has been added. The same has been assigned to ALL_FUNCTIONS_ACCESS_ROLE |
Bug Fixes
BugDB | SR | Internal | Summary |
---|---|---|---|
38471133 |
OIG-4657 |
In Activity pages, for Column 'created By', values are not displayed on scroll |
|
Description: |
Activities page: user log (created By) values are not displayed when user tries to load records with scroll bar. |
||
Resolution: |
createdByJET and lastUpdatedByJET properties are now displayed in Search pages when user scrolls to load more records |
||
38429684 |
3-42116427601 |
OIG-4626 |
Function Access mapping missing in IG0003 for Data Transfer step |
Description: |
Data Transfer step API Function Access mapping missing in seed data for page IG0003. Error: Not authorized for this operation in this resource is displayed |
||
Resolution: |
Data Transfer step API Function Access mapping is added for page IG0003 and no error is displayed in UI when Exchanges page is loaded. |
||
38179132 |
OIG-4493 |
Enhance OHI Agent logging for keystore and token retrieval failures |
|
Description: |
In OHI Agent, logs related to keystore and token retrieval failures are not stored in the log files. |
||
Resolution: |
When keystore and token retrieval failures are encountered in OHI Agent, the proper logs are stored in log files. |
||
38445972 |
OIG-4635 |
Exchange invocation fails with Internal Server Error (500 response code) if payload contains a null value |
|
Description: |
When Exchange is invoked with payload containing a parameter with null value, the request fails with an Internal Server Error (500 Response code) response. The null value causes an Null Pointer Exception which is not handled properly and causes the Internal Server Error. |
||
Resolution: |
Proper validation is added for Exchange request payload parameters. If null value is provided in Exchange request payload, a Bad Request (400 Response code) response is returned with a meaningful error response. |
||
38234379 |
3-41237424921 |
OIG-4525 |
Duplicate entries in OHI_TABLE_COLUMNS |
Description: |
The table OHI_TABLE_COLUMNS keeps track of database columns which are marked as PII, but also if a column is subject to diacritics search options. Currently there are duplicate entries. As a result, when generating base views the system could throw a Null Pointer Exception. |
||
Resolution: |
The duplicate entries as merged into a single entry. |
||
38210085 |
3-41510962871 |
OIG-4510 |
Delivery by OHI Agent is unsuccessful when there are more than 50 files to deliver |
Description: |
In an exchange during OHI Agent delivery step, if there are more than 50 files to be delivered, only the first 50 files are successfully delivered and remaining files are ignored. The exchange also completes successfully despite this incomplete Agent delivery. This happens due to a bug in handling pagination in OHI Agent. |
||
Resolution: |
The issue with handling pagination is fixed in OHI Agent. While delivering more than 50 files during OHI Agent delivery, all files are successfully delivered and the exchange is completed. |
||
38309334 |
OIG-4570 |
Add error handling for duplicate columns in base view generation |
|
Description: |
Throw a clear and descriptive error message when duplicate columns are detected in views during base view generation. Currently, if a table has duplicate columns in its view, the base view generation fails silently without any error message, causing confusion and making it difficult to identify the root cause. |
||
Resolution: |
Added a duplicate columns check in base view generation process and throwing descriptive error message to user. |
||
38350833 |
OIG-4594 |
eventDate attribute in logapplicationevents and logdynamiclogicevents resources ignores time component |
|
Description: |
The eventDate attribute in both logapplicationevents and logdynamiclogicevents resources ignores time component in Query API. So, the query criteria including a time component (e.g., 2025-06-15T14:30:00 are not honored. The system defaults to 00:00:00 as the time, effectively filtering by date only. Also, the response payload includes only the date portion, omitting time entirely. |
||
Resolution: |
The eventDate attribute is updated to honor the time component in Query API criteria. The response now also includes the time component (hours, minutes, and seconds). Fractional seconds (e.g., milliseconds) are not included in the response. |
||
38226942 |
3-40724895331 |
OIG-4522 |
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. |
||
38412676 |
3-42058901561 |
OIG-4619 |
Exchange status filters are still applied after deselecting the filter records |
Description: |
Filters for exchange status are still applied after all filters are deselected and the page is reloaded. |
||
Resolution: |
Only selected exchange status filters are applied after page reload. |
||
38416418 |
OIG-4622 |
Exchanges with Data Transfer stop processing after invoking the Data Transfer |
|
Description: |
After invoking Data Transfer, occasionally the exchange stops processing and is stuck in 'Waiting on External System' status and cannot be recovered. This happens due to a bug in handling the polling process after the Data Transfer starts. |
||
Resolution: |
The issue with improper handling of the Data Transfer polling process is fixed. After a successful Data Transfer invocation, the exchange should continue processing as usual with the Data Transfer polling process. |
||
38380299 |
OIG-4611 |
The field 'Processes Pii?' is missing in Integrations page |
|
Description: |
The field 'Processes Pii?' is not shown in Integrations page |
||
Resolution: |
'Processes Pii?' is added to system floorplan and visible in UI |