Release Notes for Oracle Insurance Gateway Patch 4.25.1.0.7
This document contains the release notes for Oracle Insurance Gateway Patch 4.25.1.0.7.
| 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. |
| 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-32037 |
User Interface - Additional tab features Added a 'Close Other Tabs' option via a three-dot menu to close all but the active tab, auto-scroll to keep the active tab visible, and improved tab closing behavior to fall back to the previous tab when closing the last tab. |
4.26.1.0.0 |
NXT-33396 |
Search page - Filter Component This enhancement adds support for trailing wild card selective search in filter component used in Exchanges page. 'likeic' operator checks the system property if trailing % should be included or not. |
4.26.1.0.0 |
NXT-33488 |
Remove outer join for 'And' mode quick search As part of this enhancement outer join is removed from "AND" mode based quick search and selection pop-up in LOV field. Also, outer join is removed for searches on insurable entity field in JET UI when used in quick search "OR" mode |
4.26.1.0.0 |
OIG-4478 |
OIG Stash This enhancement introduces a persistent stash store in OIG to support reliable multi-step processing. With the stash, integrations can resume from the point of failure instead of restarting from the beginning. It helps teams track progress across large workloads, rerun only the remaining or failed items during retries, and reduce the risk of duplicate work or inconsistent outcomes when failures occur. Stash data is removed when an exchange is purged. Documentation Links: |
4.26.1.0.0 |
Additional Upgrade Steps
Post-Deploy Phase
1) OHI Agent upgrade
Upgrade OHI Agent: Refer to Downloading and Running Oracle Health Insurance Agent for steps to perform the Agent upgrade.
If the OHI Agent was running with the below coherence properties as workaround, it can be reverted, and the previous agent startup scripts can be used to run multiple agents as before.
-
Dcoherence.ttl=0
-
Dcoherence.cluster=<Unique cluster name>
-
Dcoherence.distributed.localstorage=true
-
Dcoherence.wka=127.0.0.1
Configuration Properties
| Ref | Action | Description |
|---|---|---|
OIG-4944 |
Added |
ohi.httpapi.query.dynamicdata.fetchexplicit.disable Property to disable query api behavior where dynamic fields and records are returned only for the lists explicitly specified in the fields parameter. |
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
38856821 |
4-0001793793 |
OIG-4882 |
Missing secrets for OAuth clients while ohistore is used as keystore |
Description: |
Sometime OAuth clients shows clientSecretRegistered as false even through secret is already set in the database. |
||
Resolution: |
OAuth client credential keys are now correctly fetched. |
||
38974578 |
4-0001791688 |
OIG-4944 |
Control dynamic Data retrieval in Generic API using a flag |
Description: |
Dynamic fields and records were returned only for the lists explicitly specified in the fields parameter. |
||
Resolution: |
This introduces a property ohi.httpapi.query.dynamicdata.fetchexplicit.disable to disable query api behavior where dynamic fields and records are returned only for the lists explicitly specified in the fields parameter. Note : This property will be taken out in a future 4.25.1.x patch version. |
||
39086977 |
4-0002256434 |
OIG-4991 |
Dates not populated when using JET on virtual box |
Description: |
Translations, Date Time fields are not populated and throwing console error when application is configured in virtual box set up |
||
Resolution: |
Date Time fields are loaded and UI pages work fine |
||
39114088 |
OIG-5017 |
Oauth restclientbuilder lookup fails due to duplicate enum keys across authentication feature enums |
|
Description: |
A key mismatch occured due to duplicate OAuth enum values defined in different authentication feature enums, resulting in a lookup failure and the error 'No RestClientBuilder specified for OAuth' |
||
Resolution: |
The application now correctly resolves the restclientbuilder specified for OAuth |
||
38892045 |
4-0001624549 |
OIG-4891 |
Upload to UCM is not successful when Object Storage is enabled |
Description: |
When Object Storage is enabled, the upload request sent to UCM server as part of the Upload to UCM step is missing the file contents. As a result, the file is not uploaded to the UCM server and the subsequent fusion load job triggered fails. This leads to the exchange failing during Load Job processing, and further recovery is not possible. However when Object Storage is disabled, the file is uploaded to UCM server and fusion load job is successful. |
||
Resolution: |
Upload to UCM step now works as expected even when Object Storage is enabled. The file is successfully uploaded to the UCM server and the subsequent fusion load job triggered is also successful. |
||
38904292 |
OIG-4904 |
System throwing NullPointerException when there is no value for EXCL_PHI_LOGGING in the OHI_REPORTING_VIEWS table |
|
Description: |
When invoking the Data Transfer IP, the system verifies if any PHI information is fetched and creates PHI log entries when needed. In case the EXCL_PHI_LOGGING column in the OHI_REPORTING_VIEWS table is empty, the system throws a NullPointerException. |
||
Resolution: |
The EXCL_PHI_LOGGING column in the OHI_REPORTING_VIEWS table gets a default value 'N' |
||
38848677 |
4-0001730662 |
OIG-4880 |
OHI agents fail to start in a Coherence cluster |
Description: |
When running multiple OHI agents in a Coherence cluster, the agents fail to initialize successfully, resulting in startup failures and service unavailability. |
||
Resolution: |
OHI agents now deploy successfully in the Coherence cluster. Note: this fix requires an agent upgrade. See 'Additional Upgrade Steps' section. |
||