Release Notes for Oracle Insurance Gateway Release 4.25.1.0.0

This document contains the release notes for Oracle Insurance Gateway Release 4.25.1.0.0.

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

ID Summary Patch

CPN-2919

Operational Reports and Data Transfer

This release introduces two new features:

  • Operational Reports: To generate reports on operational data from reporting views.

  • Data Transfer: To export data from base views, including PHI data. This feature is designed to replace the existing Extract IP, offering improved performance and memory efficiency. The existing behavior of base views remains unchanged when using BI Publisher (PHI data is excluded by default, controlled by the system property ohi.baseview.exclude.pii). The Data Transfer feature supports data extraction in the following formats:

    1. CSV (Headers are not included in this release; they will be included in the upcoming patch release)

    2. JSON

    3. XML (available only for cloud customers)

    4. PARQUET (available only for cloud customers)

Documentation Links:
Administration Guide - Gathering Metrics
Developer Guide - Report Page
Developer Guide - Operational Reporting Integration Point
Developer Guide - Data Transfer Integration Point
Installation Guide - Concepts
Installation Guide - Configuring Data Transfer
Operations Guide - Operational Reports (UI)
Operations Guide - User Access
Operations Guide - Operational Reporting Installation
Operations Guide - Overview
Operations Guide - Reporting View Metadata
Operations Guide - Data Model
Operations Guide - User Interface

CPN-3076

Move PHI Logs to OCI Object Storage

With the introduction of the PHI logging feature in operational reporting and the new data transfer IP, a significant increase in PHI log volume is expected. To optimize database storage usage and improve overall performance, PHI logs are migrated from the database to lower-cost storage options. In cloud deployments, logs are stored in OCI Object Storage, while in on-premise environments, logs are stored in the file system. This change reduces database load, ensuring better efficiency and scalability as log volumes grow.

Following this enhancement, PHI logs are retained in the database for 60 days, allowing customers to retrieve recent logs via the existing logphievents Query API. Beyond this retention period, older logs are no longer retained in the database. For cloud customers, these logs are archived in Oracle-managed OCI Object Storage, and retrieval requires submitting a request to the AMS team. In on-premise deployments, logs remain accessible in the file system according to the customer’s retention policies.

This enhancement improves database performance by significantly reducing storage overhead while maintaining access to recent logs. If you are a cloud customer and if you have relied on long-term PHI log retention, review your internal processes and work with AMS as needed to ensure continued access to historical data. No changes are required for application integrations querying logs within the 60-day window, but if you are a cloud customer, plan for an alternative retrieval approach for older logs.

Documentation Links:
Administration Guide - Logging to a Central Database - How to Check Access to PHI Data
Administration Guide - Database - Move PHI Logs to Object Storage
Security Guide - User Access - Resource Auditing

CPN-3218

Groovy 4 upgrade

This release includes an upgrade from Groovy 3.x to Groovy 4.0.24. This upgrade introduces performance enhancements, new syntax options, and improved security. The upgrade also introduces breaking changes that may impact existing dynamic logic, as some APIs and packages are removed. For detailed information, please refer to the Groovy 4.0 Release Notes.

Groovy 3 provided duplicate versions of several classes in legacy packages to ease migration. With Groovy 4, these legacy classes are removed. For detailed information, please refer to the Groovy 3.0 Release Notes. For example, classes previously available in both groovy.util and groovy.xml packages (e.g., XmlSlurper, XmlParser) are only available in groovy.xml package in Groovy 4. Therefore, if you use classes from groovy.util package in the dynamic logic, update the dynamic logic to use groovy.xml package instead before upgrading to this release. See the section "Additional Upgrade Steps" for more details.

To enable compatibility with Groovy 4, the bytecode of existing dynamic logic is reset during the upgrade. This reset causes the application start-up time to be slightly longer on the first startup after the upgrade, as the dynamic logic are recompiled at startup time. Future application restarts do not recompile this bytecode, so subsequent startups are faster.

Documentation Links:
Configuration Guide - Transform a Financial Message by Streaming
Developer Guide - External Callout
Developer Guide - Gateway Dynamic Logic Bindings
Developer Guide - Exchange Integration Point
Developer Guide - Functions
Developer Guide - Dynamic Logic - Introduction

CPN-3246

File type validation

This enhancement introduces a new validation check that ensures uploaded files (for example, via Data File Sets IP) conform to a predefined set of allowed file types. This feature prevents users from uploading files with unsupported formats, improving data integrity and system security.

Documentation Links:
Developer Guide - Data Set Operations
Developer Guide - Data File Sets
Developer Guide - Exchange Integration Point

CPN-3247

Removed database details from error messages

Certain database error responses, such as ORA-12899 ("value too large for column") expose internal database details, such as table and column names. To prevent this information from being revealed in API/IP responses, these error messages are modified to replace direct references to table and column names with corresponding entity and attribute names.

CPN-3356

Antivirus Scanning for Uploaded Files in Cloud Deployments

This enhancement introduces Antivirus scan for files uploaded to OHI (for example, through Data File Sets IP or Exchanges IP in OIG application) in cloud deployments. Only files that pass the Antivirus scan are processed, ensuring that uploaded files do not pose a security risk.

Documentation Links:
Administration Guide - Database - Purging - Purging Data from Data File Sets
Developer Guide - System Administration - Data File Sets - Antivirus Scanning
Developer Guide - Exchanges - Exchange Integration Point

CPN-3456

Channel HTTP headers

This enhancement introduces two new custom HTTP headers:

  • X-OHI-CHANNEL-TYPE

  • X-OHI-CHANNEL-SOURCE

These headers enable tracking of API/IP request origins by identifying the type and context of the originating channel (e.g., JET UI, portals, etc.). This structured tracking provides reliable data for improved monitoring and analytics.

When making calls to OHI APIs from external systems, such as portals, customers are encouraged to set these headers. Doing so enhances the ability to monitor request origins, supporting better operational insights and tracking.

Documentation Links:
Administration Guide - Resource Metrics
Developer Guide - Metrics

NXT-24521

Optimized data file storage using OCI Object Storage in SaaS

Prior to this release, data files were stored in the database. To optimize storage cost and improve overall performance, data files are now stored in Oracle-managed OCI Object Storage for SaaS deployments.

The interfaces for uploading and downloading data files (via Data File Sets IP and Exchanges IP in OIG application) remain unchanged.

For on-premise deployments, data files continue to be stored in the database, so existing behavior is unaffected.

NXT-25384

GET search through query API isn’t supported

The GET method for searching entities via /generic/<entityName>?queryParams is no longer supported. Instead, you can use POST requests to /generic/<entityName>/search with the query parameters included in the request body.

NXT-28899

JET 17 upgrade

This enhancement upgrades the JET (JavaScript Extension Toolkit) core library to version 17, bringing the following changes:

  1. The date and time format is automatically determined by the default language and country set for users in the application. This ensures the date and time format follows the conventions of the user’s region and language, providing a more intuitive experience.

    The value is formatted based on the user’s locale, which is defined by the displayLanguageCode(language) and the default country setting in the application.

  2. The default background colour of drawer and popup in the Redwood theme has been changed to a slightly darker shade.

Documentation Links:
Developer Guide - Single-Value Properties

NXT-29279

Allow Iframe content in OHI applications

This enhancement enables customers to integrate Oracle Health Insurance Components with Oracle Guided Learning (OGL). This is meant for customers who have purchased OGL.

Documentation Links:
Installation Guide

NXT-29355

Improve performance of operational and search pages

This enhancement removes redundant fields from the POST request payload, such as fields configured in Quick Search, Advanced Search of Search and View and Edit Object List floorplans, as well as in the Search and Popup Tail sections of LOV floorplans. It replaces the use of expand: "all" in operational pages with specific expand values for parent and child resources as defined in the floorplan, reducing the overall response payload for API requests originating from the UI.

It further reduces duplicate API calls made during application login and improves the performance of View and Edit Object – Recursive pages by deferring API calls used to construct the property model for dynamic data under the Tab Table More section until the Download action is triggered. Collectively, these changes reduce API calls and API response payload sizes for a faster UI experience.

NXT-29605

Support for deeplink is available for static/dynamic fields of string type

This enhancement supports deeplink for static/dynamic fields of string type

Documentation Links:
Developer Guide - Properties

NXT-29732

Improved performance of user interface searches

This enhancement removes all the non-operational links from the response at header level and the child lists level unless specified in the post request body. Changes are done to remove links for dynamic fields and records as well. The 'excludelinks' parameter is set to true to reduce the overall response payload for the API requests originating from the UI

Documentation Links:
Developer Guide

NXT-30624

View Technical Errors, System Event Logs, and Queue Information Page.

This enhancement improves operational efficiency and simplifies troubleshooting by giving users more control over error management. It includes an enhanced View Technical Errors page for a better user experience, a new System Event Logs page for easy access to system events, and a new View Queue Information page (for Claims only) to help users manage and monitor queue-related data more effectively.

NXT-31159

Update in LogBack Configuration

In this release, the logback-core library is upgraded. As a result, the component previously named SizeAndTimeBasedFNATP is renamed to SizeAndTimeBasedFileNamingAndTriggeringPolicy.

Please update your logback.xml configuration file to reflect this change.

OIG-3773

OIG support for Data Transfer Integration Point

The enhancement introduces a new integration step called 'Data Transfer Step'. This allows you to configure an integration step that invokes and monitors an data transfer process through the Data Transfer Integration Point of the target Oracle Health Insurance application.

Documentation Links:
Configuration Guide - Data Transfer Step
Configuration Guide - Integration Steps
Developer Guide - Examples Per Format
Operations Guide - Mapping of Integration Step and Integration Sub-Step
Operations Guide - Data Transfer Step Exchange Recovery

OIG-3852

Resource auditing for Oracle Insurance Gateway

This enhancement introduces the ability to enable resource auditing for exchanges that may process sensitive data within Oracle Insurance Gateway i.e. the system creates an audit log whenever such exchanges or linked entities are accessed using the generic endpoints. This feature can be enabled by setting indicator processes PII to 'true' for an integration.

Documentation Links:
Security Guide

OIG-3896

Upgrade OHI Agent to Java 21

This enhancement updates OHI Agent to Java 21. OHI Agent now requires a Java 21 runtime environment.

Documentation Links:
Developer Guide - Required Software for Installing and Running Oracle Health Insurance Agent
Developer Guide - Running Oracle Health Insurance Agent, Configuring Oracle Health Insurance Agent

OIG-4262

Prevent Event Consumption

This enhancement enables a user to prevent an event from being marked consumed through dynamic logic even though it was processed by an exchange.

Documentation Links:
Developer Guide

4.24.1.0.2

OIG-4300

Purge Data IP: Exclude Unhandled Events

This enhancement introduces a Purge Data Integration Point parameter to exclude unhandled events from being purged. Unhandled events are events not yet processed by an exchange.

The feature only applies to the purging of events through the Purge Data IP, not to the purging of exchanges or technical data. This feature allows a user to more frequently purge events to efficiently maintain disk storage. Currently, the purge has to be postponed because the user has no option to exclude unhandled events.

Documentation Links:
Developer Guide

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:
Developer Guide - keepDbConnectionAlive

POL-14428

New OHI specific HTTP library to make HTTP calls from dynamic logic

The initCallOut and webTarget functions used in dynamic logic for making HTTP calls depend on Javax WS RS API libraries and expose third-party classes such as WebTarget, Client, InvocationBuilder, and Response within dynamic logic. This release introduces an OHI-specific HTTP library, this new library provides a more intuitive, and maintainable alternative for constructing HTTP calls, reducing reliance on external dependencies and improving compatibility with future OHI updates and enhancements.

While this release continues to support both initCallOut/webTarget and the new HTTP library, the initCallOut and webTarget functions will be removed in a future release. Customers are strongly encouraged to use the new HTTP library in the dynamic logic. The user guide provides detailed migration instructions and examples to facilitate this transition.

Documentation Links:
Developer Guide - OHI Http Library
Developer Guide - OHI Http Library - Conversion Examples

Additional Upgrade Steps

Pre-Upgrade Phase

1) Groovy 4 upgrade

Migration Details for groovy.util Classes

The following classes are removed from groovy.util package in Groovy 4. Update the dynamic logic to import the classes from groovy.xml package instead:

  • groovy.util.XmlNodePrinter

  • groovy.util.XmlParser

  • groovy.util.XmlSlurper

  • groovy.util.XmlUtil

  • groovy.util.slurpersupport.Attribute

  • groovy.util.slurpersupport.Attributes

  • groovy.util.slurpersupport.FilteredAttributes

  • groovy.util.slurpersupport.FilteredNodeChildren

  • groovy.util.slurpersupport.GPathResult

  • groovy.util.slurpersupport.NamespaceAwareHashMap

  • groovy.util.slurpersupport.NoChildren

In Groovy 3, classes from groovy.util package are automatically imported. With Groovy 4, these classes in groovy.xml package require explicit import statements.

To identify dynamic logic scripts that require modification, use the following POST request to api/generic/dynamiclogic/search:

{
    "resource": {
        "q": "logic.like('%XmlNodePrinter%').or.logic.like('%XmlParser%').or.logic.like('%XmlSlurper%').or.logic.like('%XmlUtil%').or.logic.like('%groovy.util.slurpersupport%')"
    }
}

Make these changes before upgrading to this release. The minimum required OHI version to apply these changes is 4.23.1. So, perform these changes if you are currently on version 4.23.1, 4.23.2, or 4.24.1.

Code Migration Examples
Example 1: Using XmlSlurper Without Import

Current dynamic logic: Uses XmlSlurper without an explicit import (implicitly relying on groovy.util):

def result = new XmlSlurper().parseText(response)

Updated dynamic logic: Add an explicit import for groovy.xml.XmlSlurper:

import groovy.xml.XmlSlurper

def result = new XmlSlurper().parseText(response)

Or use the fully qualified name:

def result = new groovy.xml.XmlSlurper().parseText(response)
Example 2: Explicitly Importing groovy.util.XmlSlurper

Current dynamic logic: Imports groovy.util.XmlSlurper explicitly:

import groovy.util.XmlSlurper

def result = new XmlSlurper().parseText(response)

Updated dynamic logic: Update the import to groovy.xml.XmlSlurper:

import groovy.xml.XmlSlurper

def result = new XmlSlurper().parseText(response)
Example 3: Correct Use of groovy.xml.XmlSlurper

Current dynamic logic: Already imports groovy.xml.XmlSlurper, so no changes are needed:

import groovy.xml.XmlSlurper

def result = new XmlSlurper().parseText(response)

Post-Deploy Phase

1) New OHI specific HTTP library for dynamic logic

Migration details
Identify the existing dynamic logic

To identify dynamic logic that require modification, use the following POST request to api/generic/dynamiclogic/search:

{
    "resource": {
        "q": "logic.like('%.path(%').or.logic.like('%.request(%').or.logic.like('%.invoke(%')"
    }
}

If the number of dynamic logic is large, use the (new) Data Transfer IP to query and export all the impacted dynamic logic.

Conversion of impacted dynamic logic to new format

Follow the Developer User Guide and Conversion Examples provided in the product documentation to update the identified dynamic logic.

Thoroughly review, validate, and test the dynamic logic changes before deployment.

2) OHI Agent upgrade

  1. Upgrade to Java 21 runtime environment for OHI Agent.

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

  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

Additional Upgrade Steps for Installation

The following phases are defined:

  1. pre-upgrade: Application is still running.

  2. pre-undeploy: Application is stopped, but not undeployed.

  3. post-undeploy: Application is undeployed. Database is backed up.

  4. post-upgrade: Released upgrade script run is complete.

  5. post-deploy: New application is deployed, and is up and running.

Post-Undeploy Phase

1) Create a new database user ohi_oig_rpt_user

As an admin user, create a new user ohi_oig_rpt_user, which is used to run operational report queries.

create user ohi_oig_rpt_user identified by <password>;
grant create session to ohi_oig_rpt_user;
grant create synonym to ohi_oig_rpt_user;

2) Create a data source ohi-operational-reporting-datasource

Configure a new data source named ohi-operational-reporting-datasource in the WebLogic Server to connect to ohi_oig_rpt_user. For detailed steps, refer to the Installation Guide.

3) Configure Data Transfer

  1. On-premise deployments:

    1. Follow the steps mentioned in Configure Database Directories and Properties

    2. Install DBMS_CLOUD package in on-premise deployments. Refer to My Oracle Support Doc ID 2748362.1 for details.

  2. SaaS deployments:

    1. Follow the steps mentioned in Configure Object Storage Buckets and Properties

    2. As an admin user, grant the following permission to ohi_oig_owner in SaaS deployments only.

grant select on v$pdbs to ohi_oig_owner;

4) Apply WLS PATCH SET UPDATE and Coherence 14.1.1 Feature Pack 22.06 Cumulative Patch

Refer Required Software for details.

Post-Upgrade Phase

1) Configure Antivirus scanning property

On-premise deployments

Set the property ohi.antivirus.scan.enabled to false in the properties file.

SaaS deployments

Set the property ohi.antivirus.scan.enabled to true in the properties file.

2) Update logback configuration file

In this release, the logback-core library is upgraded. As a result, the component previously named SizeAndTimeBasedFNATP is renamed to SizeAndTimeBasedFileNamingAndTriggeringPolicy.

Please update your logback.xml configuration file to reflect this change.

3) Configure Data Transfer

  1. On-premise deployments: Follow the steps mentioned in Configure Database Scheduler Job

  2. SaaS deployments: Follow the steps mentioned in Configure Object Storage Use Cases and Database Scheduler Job

Configuration Properties

Ref Action Description

CPN-2919

Added

ohi.phi.logs.data.transfer.target.db.directory.name

Name of the database directory where the PHI logs will be stored. Applicable only for on-premise deployments.

CPN-2919

Added

ohi.views.metrics

Timer metrics to indicate time taken to execute the query.

CPN-2919

Added

ohi.reporting.fetched.rows.count.per.view

Counter metrics which indicate the number of rows fetched per view.

CPN-2919

Added

ohi.data.transfer.target.db.directory.name

Name of the database directory where the files generated for data transfer operation will be stored. Applicable only for on-premise deployments.

CPN-3356

Added

ohi.antivirus.scan.enabled

Added a new mandatory property to enable/disable Antivirus scanning for data file uploads. Set the value of this property (in properties file, not using properties API) to true in cloud deployments and false in on-premise deployments.

NXT-24521

Added

ohi.datafile.object.storage.part.size

Size of each data file part in bytes when data file is uploaded to OCI Object Storage using multipart upload. Big data file is split in multiple parts of mentioned size. Default size is 10000000 bytes (10 MB). This property is applicable only in SaaS deployments.

NXT-24521

Added

ohi.datafile.object.storage.enabled

Enables storing data file content in OCI Object Storage. By default, data files are in the database. This property is applicable only in SaaS deployments.

NXT-24521

Added

ohi.datafile.object.storage.bucket.folder.structure

Folder structure in OCI Object Storage bucket where data files are stored. Folder structure must end with '/'. Example - CLAIMS/DATAFILES/. Default value is {appName}/DATAFILES/. This property is applicable only in SaaS deployments.

NXT-25384

Removed

ohi.service.queryapi.get.support

Removed deprecated property.

NXT-29279

Added

ohi.ui.iframe.allowlist.url

This property contains list of URLs to be allowed to load inside iFrame in OHI application.

Web Services

Ref Action Description

CPN-2919

Added

operationalreporting IP

Added a new IP to query the reporting views.

CPN-2919

Added

datatransfer IP

Added a new IP to export data from base views (including PHI data).

CPN-2919

Added

datatransferlogs API

Read-only API to query data transfer logs.

CPN-2919

Added

objectstoragecredentials API

Added a new API to configure credentials to connect to the OCI Object Storage. Applicable only for SaaS deployments.

CPN-2919

Added

objectstorageapikeyusecases API

Added a new API to configure credentials to connect to the OCI Object Storage using API keys authentication method. Use objectstoragecredentials API to configure the credentials prior to creating data using this API. Applicable only for SaaS deployments.

CPN-2919

Added

objectstorageconfigurationfileusecases API

Added a new API to configure credentials to connect to the OCI Object Storage using OCI configuration file. Applicable only for SaaS deployments.

CPN-2919

Added

reportingviews metadata IP

Added a new IP to query reporting views columns metadata.

CPN-2919

Added

viewfloorplans API

Added a new API to configure floorplan for operational reporting.

CPN-2919

Added

userviewpreferences API

Added a new API to configure search preferences for operational reporting.

CPN-2919

Added

reportingviews API

Read-only API to query reporting views metadata.

CPN-2919

Added

reportingviews IP

Added a new IP reportingviews to generate reporting views.

CPN-2919

Added

objectstorageresourceprincipalusecases API

Added a new API to configure credentials to connect to the OCI Object Storage using resource principal authentication method. Applicable only for SaaS deployments.

CPN-3076

Modified

logphievents API

PHI logs are retained in the database for 60 days, allowing customers to retrieve recent logs via the existing logphievents Query API. Beyond this retention period, older logs are no longer retained in the database. For cloud customers, these logs are archived in Oracle-managed OCI Object Storage, and retrieval requires submitting a request to the AMS team. In on-premise deployments, logs remain accessible in the file system according to the customer’s retention policies.

CPN-3076

Modified

autopurgemetadata API

The option to configure the retention period for PHI logs is removed.

CPN-3356

Modified

datafiles API

Added 2 new optional attributes status and extraInfo.

CPN-3356

Modified

datafilesets API

Added 2 new optional attributes status and extraInfo.

CPN-3356

Modified

Data File Sets IP

  • Added 2 new optional attributes status and extraInfo.

  • The operation to download data file is enabled only if the status is null or Ready or Skipped.

CPN-3456

Modified

All APIs/IPs

Two new custom optional headers are introduced: X-OHI-CHANNEL-TYPE and X-OHI-CHANNEL-SOURCE.

NXT-30624

Added

systemeventlogs API

Added a new API to view and update System Event Logs.

NXT-30624

Modified

taskprocessing IP

Added a new operation to restart a list of errored task in the system.

OIG-3852

Added

integrations

Attribute processesPii has been added for the integrations API

OIG-4300

Modified

Purge Data IP

Added parameter excludeUnhandledEvents to exclude unhandled events from being purged

Data Conversion

Ref Action Description

NXT-24521

Added

DataFile Storage Type

The storage type of the existing data files is set to 'DB' in dat_data_files table.

Dynamic Logic

Ref Action Description

CPN-3218

Modified

Groovy 4 upgrade

Upgraded Groovy from 3.x to 4.0.24.

POL-14428

Added

New HTTP Library

Introduced new OHI-specific HTTP library to make HTTP calls from dynamic logic.

POL-14428

Deprecated

webTarget

webTarget method is deprecated.

POL-14428

Deprecated

initCallOut

initCallOut method is deprecated.

UI Changes

Ref Action Description

CPN-2919

Added

View Floorplans

Added page to view, add, update floorplans for reporting views.

CPN-2919

Added

Search Reports

Added page to search for reports.

CPN-2919

Added

Operational Reports

Added page to view operational reports.

NXT-29605

Added

Claims page

Deeplink added to Authorization code and Reservation code at claimline tab (applicable only to the Claims application)

NXT-29605

Added

Episodes page

Deeplink added to Claim code (applicable only to the Claims application)

NXT-30624

Added

Queue Information page (Claims)

New page added to view Queue Information

NXT-30624

Added

System Event Logs page

New page added to view System Event Logs

NXT-30624

Modified

View Technical Errors page

Page is enhanced to provide efficiency and simplifies troubleshooting

OIG-3773

Added

Export Step

A new JET UI page, "Data Transfer Step" has been added to the Integrations (configuration).

OIG-3852

Added

processesPII

processes PII indicator

Breaking Changes

Ref Action Description

CPN-3076

Modified

autopurgemetadata API

The option to configure the retention period for PHI logs is removed.

CPN-3076

Modified

logphievents API

PHI logs are retained in the database for 60 days, allowing customers to retrieve recent logs via the existing logphievents Query API. Beyond this retention period, older logs are no longer retained in the database. For cloud customers, these logs are archived in Oracle-managed OCI Object Storage, and retrieval requires submitting a request to the AMS team. In on-premise deployments, logs remain accessible in the file system according to the customer’s retention policies.

CPN-3218

Modified

Groovy 4 upgrade

Upgraded Groovy from 3.x to 4.0.24.

NXT-30624

Modified

Error Messages

The following error messages have been modified as follows,

  1. OHI-TASK-IP-001 to OHI-IP-TASK-001

  2. OHI-TASK-IP-002 to OHI-IP-TASK-002

  3. OHI-TASK-IP-003 to OHI-IP-TASK-003

Note: These message codes are used in Oracle Health Insurance Claims Adjudication.

OIG-3867

Modified

deliverByAgent step

If exchanges failed or timed out during the deliverByAgent step before the upgrade, it is not possible to recover them after the upgrade.

OIG-3896

Modified

Health check endpoint

To check whether the Agent is up and running, endpoint can be accessed through https://<host>:<port>/health

OIG-4365

Modified

Date format

The APIs/IPs accept value for date fields in ISO 8601 format (YYYY-MM-DD), for example 2025-01-01. Any other formats result in an error.

Bug Fixes

BugDB SR Internal Summary

34164754

OIG-2567

Outbound exchange attributes are not set

Description:

When trying to build a data set the attributes exactVersionMatch and disableDeleteByOmission are not getting updated. The attribute inclusionDate is not updated when passing an empty value.

Resolution:

Implemented updates for the attributes exactVersionMatch, disableDeleteByOmission, and inclusionDate.

Backports:

4.24.1.0.1

37607157

3-39759321701

OIG-4247

Deliverbyagent fails with npe when there is a raw payload created by previous step instead of a datafile

Description:

CheckAgentAvailability, DeliverByAgent, and ReceiveAgentNotification should be skipped when the previous step creates a raw payload instead of a datafile, as there are no files to deliver.

Resolution:

A conditional check has been implemented to skip the integration steps CheckAgentAvailability, DeliverByAgent, and ReceiveAgentNotification when a datafile is not available from the previous step.

Backports:

4.24.1.0.1, 4.23.2.0.2, 4.23.1.0.9

37738039

3-40043354421

OIG-4284

Improve exception handling during storage of External Process response in exchange logs

Description:

If an exception is encountered during storing external process response in exchange logs, the process is retried to make sure the response is added to exchange logs. This can lead to stuck threads in which the process keeps retrying causing duplicate responses to be added to exchange logs.

Resolution:

The handling of exception during storage of external process response is improved to prevent stuck threads and a max retry limit is introduced to make sure the process fails gracefully instead of being stuck.

Backports:

4.24.1.0.2

36870916

3-37313793651

OIG-3930

All the saved Parameters are not shown in View mode in Integrations page

Description:

Goto Integrations page, Create New Integration and Add Activity step, add more than 4 parameter values and save, on edit of parameters and save few parameters are missing.

Resolution:

All the saved Parameters are shown in View mode in Integrations page in Activity Step

Backports:

4.24.1.0.1

36684728

3-36839446281

OIG-3842

OIG OOM issue due to accumulating of in-memory logs

Description:

The issue is due to the buildup in OIG heap memory caused by already opened financial transactions in policies that push notification messages.

Resolution:

In OIG, implemented a code fix to create a transaction and commit after every 50 downloaded notification messages as a resolution to this issue.

Backports:

4.24.1.0.1, 4.23.1.0.7, 4.23.2.0.2

36662882

3-36813495181

OIG-3833

Buffer too small for CLOB to CHAR conversion during subflow recovery

Description:

In the sub-exchanges during recovery , using a VARCHAR2 data type as a placeholder to parse the Exchange Properties JSON string of data type CLOB caused issues when the string length exceeded 32700 bytes. This is a code-related issue.

Resolution:

Changed the data type of placeholder to CLOB to hold the Exchange Properties.

Backports:

4.23.1.0.7, 4.24.1.0.1, 4.23.2.0.2

36994044

OIG-3975

Action button missing on exchange pages

Description:

All Action Buttons were missing from exchanges pages

Resolution:

Action buttons are visible on the exchanges pages and are interactable.

Backports:

4.24.1.0.1, 4.23.2.0.2, 4.23.1.0.7

36668902

3-36840886581

OIG-3838

Scheduled Exchanges are triggered multiple times

Description:

If multiple Integrations with schedule are updated at a time, then all future scheduled exchanges are rescheduled. In a multi-node setup, due to an issue with scheduling mechanism, it is executed on multiple nodes at the same time. As a result, multiple instances of exchanges would be triggered.

Resolution:

The scheduling mechanism executes on one node at a time, thus avoiding creation of multiple instances of scheduled exchanges.

Backports:

4.24.1.0.1, 4.23.1.0.7, 4.23.2.0.2

36662845

3-36788604651

OIG-3830

Exchange stops processing when Fusion ERP Job status polling fails due to an Error response from Fusion

Description:

If Fusion ERP Job status polling fails due to an Error response from Fusion (eg - 502 Bad Gateway), exchange stays in Waiting on External System (W) status. No logs are added, exchange does not Fail and recovery is not possible from this scenario.

Resolution:

If an Error response is received during Fusion ERP Job status polling, exchange fails with proper error message in exchange logs. Upon recovery, Fusion ERP Job status polling is restarted for the same job.

Backports:

4.24.1.0.1, 4.23.1.0.7, 4.23.2.0.2

37583232

3-39142193471

OIG-4237

Query step fails when more than 40 fields are specified

Description:

During invocation of an exchange in OIG, the Query Step is returning a 500 error with the message 'Bad Request: Request header too large.' This issue occurs when attempting to execute the query for more than 40 fields. While providing the same number of fields in Postman, we are getting the correct output. However, it is not working with the Query Steps in OIG exchange steps.

Resolution:

In order to tackle the header issue we are now passing the fields of the query in body of the request instead of passing in the header.

Backports:

4.24.1.0.1

36733265

3-37002072411

OIG-3867

Exchange incorrectly marked completed during recovery without file delivery to agent

Description:

When an exchange containing a 'deliverByAgent' step fails and is subsequently recovered after resolving the underlying issue, the exchange is incorrectly marked as completed without actually delivering the file via the Agent. This behavior is also observed in sub-exchanges.

Resolution:

  • Delivery by Agent step is now split in three sub steps i.e. check agent availability, delivery by agent and receive notification.

  • Exchange status will now be 'waitingForExternalSystem' instead of 'waitingForAgentToSignoff' during the delivery by agent process.

  • Agent now uses notification endpoint to send the response back to Oracle Insurance Gateway instead of using the sign off and failure integration points.

  • It is now possible to configure 'timeAllowed' type config for the delivery step (using agent) within an integration.

  • For the integrations responsible for delivering large file using an Agent, it is recommended to set a higher allowed time for the delivery step to prevent time outs (default wait time is 5 minutes).

  • If exchanges failed or timed out during the deliverByAgent step before the upgrade, it is not possible to recover them after the upgrade.

Backports:

4.24.1.0.1, 4.23.1.0.8, 4.23.2.0.2

37343570

OIG-4153

Combination of quick search and advanced search isn’t working

Description:

When user does a search with some criteria in quick search & then add another criteria in advanced search, the quick search criteria is ignored and only advanced search criteria is considered but the advance search criteria should be in concatenation with quick search

Resolution:

When search is triggered with criteria in both quick search & advanced search, advance search criteria is concatenated with quick search.

37007918

OIG-3981

Failure on the postProcess step is marked incorrectly in previous exchange step

Description:

If the postProcess dynamic logic fails it should be marked in postProcess step itself. Its being marked in previous exchange step.

Resolution:

Adding a code change in the error handling part of the process fixed the problem and resolved the issue.

Backports:

4.24.1.0.1

37223310

OHISD-3966

OIG-4105

Invoke exchanges tiles are shown with only retrieve access to exchanges.

Description:

Invoke exchanges tiles are shown with only retrieve access to exchanges.

Resolution:

Invoke exchanges tiles are not shown when only retrieve access is present on exchanges.

Backports:

4.24.1.0.1, 4.23.1.0.8, 4.23.2.0.2

36029226

3-34889024331

OIG-3484

NullPointerException upon exchange recovery

Description:

When an activity step fails to return an appropriate response, the exchange can come into a state where recovery is impossible due to a NullPointerException occurring.

Resolution:

If upon recovery the activity notification does not exist, it is fetched with the location header

Backports:

4.24.1.0.1, 4.23.1.0.8, 4.23.2.0.2

37379336

3-38942079481

OIG-4160

Sequence of Exchange steps does not follow the sequence defined for Integration steps

Description:

The sequence of Exchange steps does not follow the sequence defined for Integration steps when Integration step IDs are out of order compared to the steps sequence. Eg: For two integration steps defined in following sequence - Step 1 with a higher step ID and Step 2 with a lower step ID, when exchange is invoked, Step 2 is executed first, followed by Step 1.

Resolution:

The Exchange steps sequence follows the sequence defined for Integration steps irrespective of step IDs.

Backports:

4.24.1.0.1

37506977

OIG-4198

Exchange Invocation Headers should be treated as case sensitive

Description:

When an exchange is invoked with exchange specific headers like ohi-exchange-description but with uppercase letters like Ohi-Exchange-Description, it is ignored because it is not in lowercase. According to HTTP RFC standard, headers should be treated as case insensitive and so OIG should accept the headers irrespective of case.

Resolution:

In order to make exchange specific headers case insensitive we are explicitly converting them to lowercase and then try to get the value of that header.

Backports:

4.24.1.0.1, 4.23.1.0.9, 4.23.2.0.2

37654292

OIG-4260

Conflicting keyboard shortcuts

Description:

Users can set up set a custom shortcuts using an existing key combination. This creates a conflict when the key combination is used.

Resolution:

A new business rule is introduced to ensure that all custom shortcuts have unique key combinations.

37248628

OIG-4110

Error when attempting to upload files to OIG

Description:

User experiences 406 (Not Acceptable) Error when attempting to upload files to OIG

Resolution:

It is possible to upload files in OIG without any error.

Backports:

4.23.1.0.8, 4.24.1.0.1, 4.23.2.0.2

37093031

3-37860226571

OIG-4058

NPE in Eclipse Integrations

Description:

NPEs are raised for some eclipse integrations when the token is not retrieved successfully

Resolution:

There was a delay in the synchronization process between the keystore and the cache, which could lead to both being out of sync temporarily. The synchronization process has changed to make them consistent.

Backports:

4.24.1.0.1, 4.23.1.0.8, 4.23.2.0.2

37832221

3-40337961631

OIG-4357

OHI Agent startup fails due to security protocol version mismatch

Description:

OHI Agent fails to connect to OIG due to security protocol version mismatch, and as a result Agent fails to launch successfully.

Resolution:

OHI Agent is able to connect to OIG and Agent startup is successful. Upgrade of OHI Agent is required as part of bug resolution.

37837905

OIG-4365

Number and Date incorrectly converted based on locale in API/IP requests

Description:

Dates are incorrectly converted based on the locale value in API/IP requests.

Resolution:

The date conversion no longer considers the locale value.

Issues that were backported in previous Release / Patch

BugDB Internal Summary Backport BugDB SR

34164754

OIG-2567

Outbound exchange attributes are not set

4.24.1.0.1

37303062

36029226

OIG-3484

NullPointerException upon exchange recovery

4.24.1.0.1

37438084

3-34889024331

36029226

OIG-3484

NullPointerException upon exchange recovery

4.23.1.0.8

37438058

3-34889024331

36029226

OIG-3484

NullPointerException upon exchange recovery

4.23.2.0.2

37438064

3-34889024331

36662845

OIG-3830

Exchange stops processing when Fusion ERP Job status polling fails due to an Error response from Fusion

4.24.1.0.1

37063701

3-36788604651

36662845

OIG-3830

Exchange stops processing when Fusion ERP Job status polling fails due to an Error response from Fusion

4.23.1.0.7

36662861

3-36788604651

36662845

OIG-3830

Exchange stops processing when Fusion ERP Job status polling fails due to an Error response from Fusion

4.23.2.0.2

36662857

3-36788604651

36662882

OIG-3833

Buffer too small for CLOB to CHAR conversion during subflow recovery

4.23.1.0.7

36662895

3-36813495181

36662882

OIG-3833

Buffer too small for CLOB to CHAR conversion during subflow recovery

4.24.1.0.1

36662904

3-36813495181

36662882

OIG-3833

Buffer too small for CLOB to CHAR conversion during subflow recovery

4.23.2.0.2

36662889

3-36813495181

36668902

OIG-3838

Scheduled Exchanges are triggered multiple times

4.24.1.0.1

37095255

3-36840886581

36668902

OIG-3838

Scheduled Exchanges are triggered multiple times

4.23.1.0.7

36668982

3-36840886581

36668902

OIG-3838

Scheduled Exchanges are triggered multiple times

4.23.2.0.2

36668969

3-36840886581

36684728

OIG-3842

OIG OOM issue due to accumulating of in-memory logs

4.24.1.0.1

37073869

3-36839446281

36684728

OIG-3842

OIG OOM issue due to accumulating of in-memory logs

4.23.1.0.7

37073859

3-36839446281

36684728

OIG-3842

OIG OOM issue due to accumulating of in-memory logs

4.23.2.0.2

36684743

3-36839446281

36733265

OIG-3867

Exchange incorrectly marked completed during recovery without file delivery to agent

4.24.1.0.1

36748428

3-37002072411

36733265

OIG-3867

Exchange incorrectly marked completed during recovery without file delivery to agent

4.23.1.0.8

36733331

3-37002072411

36733265

OIG-3867

Exchange incorrectly marked completed during recovery without file delivery to agent

4.23.2.0.2

36733311

3-37002072411

36870916

OIG-3930

All the saved Parameters are not shown in View mode in Integrations page

4.24.1.0.1

36946546

3-37313793651

36994044

OIG-3975

Action button missing on exchange pages

4.24.1.0.1

36994055

36994044

OIG-3975

Action button missing on exchange pages

4.23.2.0.2

37056631

36994044

OIG-3975

Action button missing on exchange pages

4.23.1.0.7

37153117

37007918

OIG-3981

Failure on the postProcess step is marked incorrectly in previous exchange step

4.24.1.0.1

37073790

37093031

OIG-4058

NPE in Eclipse Integrations

4.24.1.0.1

37093034

3-37860226571

37093031

OIG-4058

NPE in Eclipse Integrations

4.23.1.0.8

37093041

3-37860226571

37093031

OIG-4058

NPE in Eclipse Integrations

4.23.2.0.2

37093039

3-37860226571

37223310

OIG-4105

Invoke exchanges tiles are shown with only retrieve access to exchanges.

4.24.1.0.1

37223321

OHISD-3966

37223310

OIG-4105

Invoke exchanges tiles are shown with only retrieve access to exchanges.

4.23.1.0.8

37161035

37223310

OIG-4105

Invoke exchanges tiles are shown with only retrieve access to exchanges.

4.23.2.0.2

37223332

OHISD-3966

37248628

OIG-4110

Error when attempting to upload files to OIG

4.23.1.0.8

37248665

37248628

OIG-4110

Error when attempting to upload files to OIG

4.24.1.0.1

37248640

37248628

OIG-4110

Error when attempting to upload files to OIG

4.23.2.0.2

37248654

37379336

OIG-4160

Sequence of Exchange steps does not follow the sequence defined for Integration steps

4.24.1.0.1

37522651

3-34889024331

37506977

OIG-4198

Exchange Invocation Headers should be treated as case sensitive

4.24.1.0.1

37506998

37506977

OIG-4198

Exchange Invocation Headers should be treated as case sensitive

4.23.1.0.9

37507000

37506977

OIG-4198

Exchange Invocation Headers should be treated as case sensitive

4.23.2.0.2

37506999

37583232

OIG-4237

Query step fails when more than 40 fields are specified

4.24.1.0.1

37583287

3-39142193471

37607157

OIG-4247

Deliverbyagent fails with npe when there is a raw payload created by previous step instead of a datafile

4.24.1.0.1

37607167

3-39759321701

37607157

OIG-4247

Deliverbyagent fails with npe when there is a raw payload created by previous step instead of a datafile

4.23.2.0.2

37607201

37607157

OIG-4247

Deliverbyagent fails with npe when there is a raw payload created by previous step instead of a datafile

4.23.1.0.9

37607211

3-39759321701

37738039

OIG-4284

Improve exception handling during storage of External Process response in exchange logs

4.24.1.0.2

37738045

3-40043354421

Known Issues

BugDB SR Internal Summary

33767440

3-28173135801

OIG-2387

File upload fail with java heap size error

Description:

When a large file is uploaded to the exchange, exchange fails with the error OIG-GATE-019: citing Java heap space as error

36413617

OIG-2902

Displaying back button on exchange home screen

Description:

Displaying back button on exchange home screen

35686796

OIG-3322

Dynamic logic unit test statistics are incorrect

Description:

When the user queries something in the testunit dynamic logic and then tests another dynamic logic in the same testunit dynamic logic, the value/count for all query parameters displays incorrect

35777257

OIG-3389

Boilerplate seen in JET dynamiclogic page

Description:

Boilerplate seen in JET dynamiclogic search page for labels

35942075

3-33802793381

OIG-3456

OptimisticLockException in log instead of exchange log timeout in blocking exchanges

Description:

Blocking exchanges which time out during transformation step with HTTP 504 Gateway timeout, result in an OptimisticLockException in the log file.

36423323

OIG-3548

credentials page - page navigation is displayed rather than load more on scroll

Description:

credentials page - page navigation is displayed rather than load more on scroll

36240867

OIG-3648

Activity invocation response in exchange logs has status IP instead of QD

Description:

When an activity triggered in end application is in 'QD' (Queued) status, the log line added to the exchange has 'IP' (In Process) as status.

36325016

3-35757295771

OIG-3690

Unable to add parameters to integration steps

Description:

unable to add parameters to integration steps

36367680

3-35755073101

OIG-3703

The outboundintegrationpoints IP is not always showing the correct value for authenticationFeature when OAuth is used

Description:

The outboundintegrationpoints IP is not always showing the correct value for authenticationFeature when OAuth is used

36970162

3-37743857111

OIG-3967

Incorrect use of ohi.ws.client.readtimeout propperty to set the entire request/response timeout

Description:

The system property ohi.ws.client.readtimeout is intended to control the time (in milliseconds) that the client will wait for a response from the server after sending a request. However, it is currently being incorrectly applied to set the timeout for the entire request/response conversation, rather than just the response wait time.

36972779

3-37582942001

OIG-3969

Large chronicle queue files of size 180GB were created by applicationDBAppender while capturing application log events

Description:

The applicationDBAppender that captures the application log events in DB generated a large chronicle queue files of size 180GB due to an exception that got re-queued in an end-less while loop

37818443

OIG-4274

There is no error message displayed in UI on a unsupported file format upload

Description:

When Invoke is done in Invoke Exchange With File upload page by uploading a unsupported file format, there is no error shown or message given to user

37782138

3-39282478411

OIG-4319

Search exchanges is slow when access restrictions are defined for Integration

Description:

When access restrictions are defined for Integration, Search on exchanges is very slow

37882217

OIG-4399

Zip and Unzip operations in Data File Sets IP return HTTP 405 in SaaS

Description:

The Zip and Unzip operations in Data File Sets IP return HTTP 405 (Method Not Allowed) in SaaS.

Deprecated Items

These features will be removed in a future release. Customers are advised to review the documentation and take timely action.

JIRA Key Announced Release Announced Summary

NXT-25000

3.22.2.0.0

The use of parameters that influence the resource representation in the 'Accept' header of an HTTP request is deprecated.

Reference Document

POL-14428

4.25.1.0.0

The webTarget and initCallOut functions, which are used to make HTTP calls from dynamic logic, have been deprecated.

Reference Document