Release Notes for Oracle Insurance Gateway Release 4.26.1.0.0

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

Version compatibility: Oracle Insurance Gateway Release 4.26.1.x is only compatible with other Oracle Health Insurance applications release version 4.26.1.x unless explicitly stated otherwise.

18 months after the release date this release will be End of Life. After this date Oracle is not responsible for performance or security issues.

Enhancements

ID	Summary	Patch
CPN-3641	Enhanced PHI logs access using base views In SaaS deployments, PHI access logs are stored in the database for 60 days in the PHI_LOG_EVENTS table. Logs older than 60 days are moved to OCI Object Storage by a daily database scheduler job. Prior to this release, customers could query recent logs (≤ 60 days) using the logphievents generic API, but accessing older logs required raising an SR with the AMS team to retrieve files from OCI Object Storage. This enhancement improves the customer experience by enabling PHI access logs to be extracted directly through base view generation. The PHI_LOG_EVENTS table is now included in base view generation, allowing customers to schedule a daily extract of the PHI_LOG_EVENTS_BV base view and load the extracted data into their own data warehouse for analysis and reporting. An access restriction is created for PHI_LOG_EVENTS_BV, but it is not automatically granted to the ALL_VIEW_ACCESS_ROLE. Documentation Links: Administration Guide - Accessing PHI Logs in Oracle Health Insurance Cloud Services (OHI CS) Developer Guide - Base Views Access Restrictions	4.25.1.0.4
CPN-3676	Upgrade to Java 21, Jakarta EE 9.1 and WebLogic 15.1.1 This enhancement upgrades Java to version 21, Java EE to Jakarta EE 9.1 and WebLogic to version 15.1.1. See "Additional Upgrade Steps for Installation" below and the installation guide for more details. Documentation Links: Installation Guide - Installation Guide Installation Guide - Upgrade Steps for Java and Oracle WebLogic Server Installation
CPN-3775	Allow purging of data with a 7-day retention period in non-production environments The data purge process previously required a minimum retention period of 30 days. This enhancement allows to configure a lower retention period (e.g: 7 days) specifically in non-production environments, while production environments maintain the 30-day policy. This change will help optimize disk space in non-production environments. Documentation Links: Administration Guide - Database - Purging - Auto Purge Installation Guide - Release Installation - Install Database Objects	4.25.1.0.9
CPN-3799	Operational Reports and Data Transfer The following changes are made in Operational Reports and Data Transfer: In the previous release, the CSV files generated by the Data Transfer IP did not include a header row. In this release, CSV files include the header. In the previous release, when a query returned no records, the Data Transfer IP responded with HTTP 200 with an empty response body. This behavior is changed to return HTTP 204 (No Content). Two new error messages are introduced in the Operational Reporting IP. The IP returns an HTTP 422 response with one of the following error messages: OHI-IP-ORV-008: View {0} does not exist OHI-IP-ORV-009: Access restriction grant is missing to query the view {0} Default PAR (Pre-Authenticated Request) URL expiry time has been changed from 30 minutes to 1 minute. The following issues specific to On-Prem deployments are fixed: Incomplete or truncated responses when querying very large data. Documentation Links: Developer Guide - Data Transfer Integration Point - CSV Developer Guide - Data Transfer Integration Point - Response Developer Guide - Data Transfer Integration Point - Response Developer Guide - Data Transfer Integration Point - Response File Format Developer Guide - Operational Reporting Integration Point - Error Messages	4.25.1.0.4
CPN-3862	Optimized evaluation of logging parameters in dynamic logic When debug or trace logging is turned off, certain log statements may still trigger additional data retrieval or calculations in the background. This can slow down execution or cause errors, for example when trying to log a null value. With this enhancement, such log statements are automatically guarded. When debug or trace logging is disabled, the associated expressions are skipped, avoiding unnecessary work and improving overall efficiency. Example: log.debug("Claim ID: {0}", claim.getId()) In earlier versions, claim.getId() was executed even if debug logging was disabled. If claim was null, this resulted in a NullPointerException, even though debug logging was turned off. With this enhancement, the expression is executed only when debug logging is enabled. This enhancement applies only to new or recompiled dynamic logic. Documentation Links: Developer Guide - Dynamic Logic - Logging
CPN-3869	Expose Foreign Keys and Unique Keys on Base Views The Data Transfer functionality requires some understanding of the data model and the keys between different Base Views. A Base View does not have a key on its own, but the underlying tables do. This enhancement introduced two new tables: BVG_FOREIGN_KEYS, representing the foreign key relations between two Base Views BVG_KEYS, representing the unique and primary keys on a single Base View The data from each table can be accessed by a Base View itself.
CPN-3926	Automatic heap histogram collection for improved memory analysis A heap histogram is a lightweight memory dump that provides detailed information about objects in the heap, including their class names, sizes, and counts. It helps identify memory leaks, understand object allocation patterns, and optimize memory usage. With this enhancement, heap histograms are automatically captured in SaaS deployments when the heap memory reaches a critical state, enabling proactive and improved memory analysis.	4.25.1.0.3
CPN-3973	Groovy 5 upgrade This release includes an upgrade from Groovy 4.x to Groovy 5.0.7. This upgrade introduces performance enhancements and new syntax options. For detailed information, please refer to the Groovy 5.0 Release Notes. Some of the key breaking changes in Groovy 5 include: Stricter handling of duplicate imports: In earlier versions of Groovy, the compiler was lenient when finding duplicate imports or an import and a similarly-named class definition. While having duplicates was considered poor style, the compiler followed the lenient behavior of letting the last definition "win". From Groovy 5, the compiler now follows Java behavior and gives an error in such cases. New default imports from java.time: The java.time packages are an additional default import in Groovy 5. If you have classes in the default (no) package with the same names as classes in the java.time package, you will need to rename those classes, or place them in a package, or use an import alias, to avoid conflicts. The most common classes that might conflict are Year, Month, and Duration. For additional details, see the Breaking changes section in the Groovy 5.0 release notes. Not all internal compiler or runtime changes are fully described in the Groovy 5.0 release notes. Customers are therefore strongly advised to perform comprehensive unit and regression testing of the dynamic logic to ensure compatibility with Groovy 5. To enable compatibility with Groovy 5, 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: Developer Guide - Dynamic Logic - Introduction
CPN-4025	Security logs retrieval via API and data transfer Prior to this release, security logs were written only to the file system and were not accessible through any API. With this enhancement, SaaS customers can now retrieve security logs using a dedicated API as well as through the data transfer feature. A new API, logsecurityevents, is introduced, backed by the new table LOG_SECURITY_EVENTS. A corresponding base view, PHI_LOG_SECURITY_EVENTS_BV, is now available to support extraction of security logs via the data transfer feature. This allows customers to schedule regular extracts (e.g., daily) and load the data into their own analytics or SIEM systems. Access to security logs is controlled: The access restriction for PHI_LOG_SECURITY_EVENTS_BV is created but not granted automatically to ALL_VIEW_ACCESS_ROLE. A dedicated access role must be explicitly granted to users who are allowed to extract security logs. The table LOG_SECURITY_EVENTS is included in auto-purge with a default retention period of 7 days. Documentation Links: Administration Guide - Auto Purge Administration Guide - Fetch Security Logs through API	4.25.1.0.4
CPN-4206	Introduced additional attributes in security logs for enhancing log auditing and parsing capabilities Introduced the following new attributes in security logs: eventCategory: All security events are categorized into distinct categories. This attribute holds the category assigned to the security event being logged. eventType: Brief summary of the security event being logged. eventOutcome: Outcome of the event. Possible values: Success or Failure. eventSeverity: Describes the severity of the event. Possible values: INFO, WARN or ERROR. httpStatusCode: HTTP response code of the request for which the event is being logged. This will be null whenever the code is not deterministic at the time of event. failureReason: Briefly describes the reason of failure. This attribute will be non-null only where relevant. apiEndpoint: Holds the API endpoint to which the request was sent. sessionId: Identifies the session provided by the caller. Applicable to SaaS and UI requests. accessTokenId: Identifies the access token associated with the request. Applicable to SaaS and non-UI requests Documentation Links: Administration Guide - Fetch Security Logs through API Administration Guide - Application - Security Logs Generated in Oracle Health Insurance	4.25.1.0.9
CPN-4207	Enhanced PHI access logs to include access scope, session ID and access token ID Enhanced PHI access logs to include three new attributes: accessScope: Indicates whether a single record or multiple records are accessed within a transaction. sessionId: Identifies the session provided by the caller. Applicable to SaaS and UI requests. accessTokenId: Identifies the access token associated with the request. Applicable to SaaS and non-UI requests. Documentation Links: Security Guide - User Access - Resource Auditing	4.25.1.0.9
CPN-4302	Configurable PHI Event Logging for Data Transfer IP PHI event logging for Data Transfer IP is now configurable using the system property ohi.datatransfer.logging.phi.events.enabled. By default, this property is set to true, so existing behavior remains unchanged and PHI access events continue to be written to LOG_PHI_EVENTS when PHI data is accessed during Data Transfer IP operations. When this property is set to false, PHI access event records during Data Transfer IP operations are not written to LOG_PHI_EVENTS. Before disabling PHI event logging, customers should review their audit, compliance, and security requirements. Documentation Links: Administration Guide - Database - Move PHI Logs to Object Storage Developer Guide - Integration - IP - Operational Reporting - Data Transfer Integration Installation Guide - Introduction - Configuring Data Transfer and PHI Logs Export
NXT-26542	Exposed generic API for deployment metadata and extended User Preferences to support switching between customer and browser timezones A generic deployment metadata API is now available to retrieve the customer time zone. The User Preferences API includes a new browserTimeZone flag, which defaults to false. When set to true, timestamps are displayed in the end user’s browser time zone. When set to false, timestamps are displayed in the configured customer time zone.	4.25.1.0.9
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. Documentation Links: Security Guide - User Access - Data Access Restriction Types - Download Data Restriction	4.25.1.0.2
NXT-31023	Search Result Download in CSV Format This enhancement addresses the issue of referenced fields being downloaded in one column as JSON data in the CSV exports from UI. With this enhancement all the displayed data of a reference field will be downloaded into separate columns. Documentation Links: Developer Guide - JET User Interface - References - Properties - Common Custom Jet Properties	4.25.1.0.3
NXT-31178	Upgrade to JET version 19.0.0 This enhancement upgrades the JET (JavaScript Extension Toolkit) core library to version 19 from 17. This uptake includes the required dependency, tooling, and compatibility updates to align the UI with the OJET 19, enabling continued support for the latest Oracle JET components, framework fixes, and runtime improvements.
NXT-31594	JET: Save user preferences for table displays This enhancement enables you to save your table column selections and column widths on supported pages. After you adjust a table, select Save Preferences to save your settings for that page. Where it applies System- or floorplan-driven pages that use following templates when the flexColumn property is true (Note: Default setting is true): View/Edit List Search Object Table Supported pages and tables Product Definition Product Service Definition table in products and across products page Claims Draft provider pricing clause table within worksheet and across worksheet page Fee Schedule lines Provider Pricing Clause Claim lines table within claims page Common Reference Sheets Documentation Links: Security Guide - User Access - Functional Access Restriction (JET)	4.25.1.0.8
NXT-31617	Increase the length of scope attribute on OAuthClientCredentialsGrantConfiguration entity The scope attribute was limited to 100 characters, which was insufficient to store full scope values provided by Oracle Integration Cloud. Its length is increased to 200 characters.	4.24.1.0.4
NXT-32017	UI: Additional Features Advanced Search With this enhancement, the following multiple capabilities are added to the advanced search: Ability to select query operators for different search criteria. Ability to specify selected criteria as mandatory in advanced search. Multiple adjustments to reference sheet lines, page searches, and sort, including the ability to search on nulls, the ability to sort on start and end dates, view last updated by, and time details. Documentation Links: Developer Guide - JET UI - References - Components - Advanced Search	4.25.1.0.6
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.25.1.0.7
NXT-32471	Improve handling of HTTP error: 401 UnAuthorized in JET UI With this enhancement, OHI uses system property OHI_DEPLOYMENT_TYPE to handle HTTP 401 error. When this property value is set to "CLOUD", this will force a "401" response to re-direct the OHI JET login page when the IDCS OpenID session cookie is missing/expired.	4.25.1.0.9
NXT-32524	Table component improvements - Usability with editable row Introduced check (Apply) icon as a table row-level action in edit mode. Clicking the check icon returns the row from edit mode to view mode. Actions in other rows will be disabled until the user clicks on the check icon of the current row being edited. Editable row remains in edit mode and persists the data when the user clicks outside the table or switches to another browser tab. Documentation Links: Developer Guide - JET User Interface - References - Components - Table Developer Guide - JET User Interface - Floor Plan Templates - View and Edit Object - List	4.25.1.0.4
NXT-32617	UI: Ability to exclude trailing wildcard with like search This enhancement allows excluding the automatic inclusion of the trailing wildcard for like search in quick search, advanced search, and lookups by setting the application property ohi.ui.likesearch.wildcard.enabled to false. The system also auto-truncates the leading and trailing white space for searches. Documentation Links: Installation Guide - Application Properties	4.25.1.0.4
NXT-32621	UI: Additional Features Quick Search With this enhancement, the quick search component is extended, and it will be possible: To include all types of fields in the quick search. To have query operators like between, less than, greater than, etc, configurable in quick search. To set specific search criteria flagged as mandatory. Documentation Links: Developer Guide - JET User Interface - References - Components - Quick Search	4.25.1.0.4
NXT-32629	UI: Expandable "more" section in tables With this enhancement, the overflow region for the table ("More" link) is now expandable to a two-column layout, allowing more information to be viewed at once. Documentation Links: Developer Guide - JET User Interface - References - Components - Table	4.25.1.0.4
NXT-32633	UI: Additional Features Sort With this enhancement, the sort component is updated to display null values based on the sort order, that is, for Default and Criteria: If the sort order is descending, nulls last is applied. If the sort order is ascending, nulls first is applied. It is now possible to specify sorting criteria for a multi-value property (list) configuration in a form and region. Documentation Links: Developer Guide - JET UI - References - Components - Sort Component	4.25.1.0.6
NXT-33004	Copy Action for Duplicating Records on HRR Pages The Copy Action is available when the metadata indicates that cloning is supported for a resource. It allows users to quickly duplicate an existing record by providing a new functional key. The system pre-fills the remaining values from the original record (excluding system-generated fields), allowing users to modify and save the new record while keeping the original record unchanged. During cloning, the following child entities are not copied: User Roles for Access Roles, Relation Identifiers for Persons, and Provider Limit Rules for Provider Limit Categories. Modifying individual child records during the clone operation is currently not supported for Access Restriction Grants under Access Roles, Partial Provider Pricing Clauses under Pricing Options, and Diminishing Rate Blocks, along with nested block amount and size lists, under Diminishing Rates.
NXT-33070	Improved Multi-Select Behavior for Row Selection in Tables The record-selection behaviour has now been updated to follow an additive selection model, ensuring that selecting a record no longer clears existing selections. All previously selected records will remain selected and will not be unintentionally deselected. Prior to this implementation, when user selects multiple records using checkboxes, clicking anywhere on a another row (outside the checkbox) would deselect all selected records except the one that was clicked.
NXT-33394	UI: Search Object - Table template to support edits This enhancement introduces the ability to inline-edit table data on the search page, built on the 'Search Object - Table' template. Documentation Links: Developer Guide - JET UI - References - Floor Plan Templates - Search Object - Table View
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.25.1.0.7
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.25.1.0.7
NXT-33659	Disable user location based time conversion JET UI no longer relies only on the user’s browser timezone for datetime display. This helps prevent incorrect time conversion for customers operating across different geographic locations. The customerTimeZone, configured in the deployment metadata table during application installation, is used by default by JET UI. Users can override this through the "Use Browser Timezone?" option in the Preferences dialog, after which the UI will use the browser timezone. If customerTimeZone is not configured or is invalid/unsupported by JET, the UI falls back to the browser timezone. Documentation Links: Developer Guide - JET UI - References - Properties - Properties Security Guide - User Access - Function Access Restriction (JET)	4.25.1.0.9
NXT-33697	UI: European date/number formatting for English Language With this enhancement, support is added to keep the UI in English language while using European date and number formats (e.g., dd/MM/yyyy and 1.234.567,00), when user sets 'en‑EU' in the existing ohi.ui.default.locale system property. If the property is not set, date and number formats continue to follow the user’s selected locale (language + region), with no change in behaviour.	4.25.1.0.8
NXT-33718	Extended user preference - Reorder and Auto-commit With this enhancement it is now possible to reorder table columns as per user’s preference. Also, the save button to store preference is replaced by auto commit feature. This feature is available for all pages based on the following floor plan template: View and Edit List Table List View - Table This feature is also available for selected pages which are not floorplan based: Common Pages like Reference sheets. Claims page claim line tab. In Policies application, pages like Premium schedule lines, Adjustment lines, and Fee schedule lines. Documentation Links: Developer Guide - JET UI - References - Components - Table	4.25.1.0.9
NXT-33750	Enhance UI download functionality to include all search results based on query criteria. This enhancement expands the UI download functionality, allowing users to export the complete set of search results that match the active query across all download-enabled use cases in the application. Documentation Links: Developer Guide - Integration - HTTP API - Download API
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.	4.25.1.0.2
OIG-3267	New exchange step status 'In Progress' This enhancement introduces a new exchange step status 'In Progress' to improve the visibility into the current stage of an exchange. This status is selective, and is shown only for long-running exchange steps. Note: This new status might affect customer queries that select, filter, or group by exchange step status. Documentation Links: Operations Guide - Exchange Step Status
OIG-3899	User interface improvements for exchanges and sub-exchanges search and view page. This enhancement improves exchange and sub-exchange page user experiences with respect to searching capabilities, navigation, refresh action, and additional fields added.
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	4.23.1.0.10, 4.24.1.0.4, 4.25.1.0.0
OIG-4349	Incremental Data Transfer This enhancement introduces native support for incremental data transfers, enabling the system to transfer only new or updated data by default. It also allows users to define custom data transfer ranges using exchange properties, supporting recovery scenarios and providing greater flexibility. Documentation Links: Configuration Guide - Incremental or Full Data Transfer Developer Guide - Exchange Integration Point - Header-Based Watermark Injection
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: Administration Guide - Package OIG_PURGE_PKG.PURGE_EXCHANGE_DATA Developer Guide - Purge Exchanges Developer Guide - OIG Stash Developer Guide - Exchange Stash Methods Developer Guide - Stash Integration Point Operations Guide - Stash Fields Operations Guide - Stash Error Handling and Recovery Operations Guide - Stash Processing Security Guide - Stash Restriction Security Guide - Stash Security Guide - Exchange	4.25.1.0.7
OIG-4573	Update File Upload Results This enhancement introduces a new IP and page that lets users manually mark an agent delivery as successful to prevent the same file from being sent again during recovery. Manual updates are allowed only when the step is Delivery, the type is AGENT, and the related processing attempt failed either because the main delivery attempt failed or because the related notification attempt failed. The change is limited to marking the result as successful, and once it is marked successful it cannot later be undone. Documentation Links: Developer Guide Operations Guide - File Upload Results Operations Guide - Agent (delivery step) times out
OIG-4977	Tracing Support for OHI Agent Delegation Flows This enhancement improves trace continuity and observability reliability within delegation patterns, enabling Application Performance Monitoring (APM) tools such as Dynatrace to accurately capture and monitor outbound spans from the OHI Agent.	4.25.1.0.9
POL-16598	Detecting & resolving duplicate message transformation task. If a more recent transformation task exists, the older task is stopped to avoid duplicate tasks. This applies only to the Policies application. Only tasks with an Errored status can be restarted.
POL-17575	Reset a value using floorplan conditions With this enhancement, a new optional floorplan property resetValue is introduced, which can be used within the condition block to reset the value for a field. Documentation Links: Developer Guide - JET User Interface - References - Components - Condition	4.25.1.0.2
POL-17946	Generic Auditing Framework This enhancement introduces a Generic Audit Framework in OHI to provide standardized tracking of record-level and field-level changes across supported entities. It captures create, update, and delete actions along with details of what changed, who performed the action, and when it occurred. A new API allows users to retrieve audit history with filtering and pagination, while built-in access controls ensure audit visibility aligns with entity, record, and field-level permissions. Audit tracking applies only to user-driven or directly modified fields and does not include technical or system-generated (calculated) fields. Audit API resources use separate access restrictions instead of inheriting those of their parent resources. Therefore, users with access to a resource, such as Policies, may still require an additional Audit API-specific grant. The need to grant separate Audit API access will be removed in the next patch. Users with access to the main resource will automatically be able to access its Audit API. Documentation Links: Administration Guide - Package OHI_AUTO_PURGE_PKG Administration Guide - Generic Audit Administration Guide - Administration Guide - Generic Audit Developer Guide - Audit Search Generic API Security Guide - Audit API
POL-18132	UI: Conditional display of row-level actions: edit and delete for tabs. This enhancement introduces the ability to control the display of actions (edit/delete) through initconditions. Documentation Links: Developer Guide - JET UI - References - Components - Conditions	4.25.1.0.4, 4.25.1.0.6

Additional Upgrade Steps

Post-Deploy phase

1. Groovy 5 is more restrictive and doesn’t support direct use of .size or .value on collections (lists)

   Example: Replace .size with size() and list*.value.sum() with list.sum()

   checkPOEP = defaultPoliciesSql.getPolicyEnrollmentProducts(testCode + '_POLI_001', 2, 'PERSON', testCode + '_RELA_001')
   // def poepSize = checkPOEP.size //INVALID,throws error
   def poepSize = checkPOEP.size() //VALID

   def customerList = getCustomerList(inputList)
   // Integer b = customerList*.value.sum(); //INVALID,throws error
   Integer b = customerList.sum(); //VALID

   The impacted dynamic logic to be identified and updated as stated below

   Identify the impacted dynamic logic using GUI based search or API as mentioned below

   API: POST generic/dynamiclogic/search

   {
   "resource": {"q":"logic.like('%*.value.sum()%').or.logic.like('%.size%')"}
   }

2. Java 21 and Groovy 5 enforce stricter rules and no longer allow direct use of private variables and methods

   Example: Parsing the below JSON as a String and then calling .value on it results in an error, since .value is a private field of the String class and is not accessible

   "communicationPreference":[{"communicationMode": "EMAIL"}]

   person.communicationPreference.get(0).communicationMode.value //INVALID, throws error
   person.communicationPreference.get(0).communicationMode //VALID

   Identify the impacted dynamic logic using GUI based search or API as mentioned below and update it

   API: POST generic/dynamiclogic/search

   {
   "resource": {"q":"logic.like('%.value').or.logic.like('%.value.toString%')"}
   }

3. With the Java 21 upgrade, Java EE-related package names have changed from javax to jakarta (for example, javax.ws is now jakarta.ws) as part of the adoption of Jakarta EE standards. Please update any use of javax.ws. in dynamic logic to jakarta.ws. to ensure compatibility.

   Identify the impacted dynamic logic using GUI based search or API as mentioned below and update it

   API: POST generic/dynamiclogic/search

   {
   "resource": {"q":"logic.like('%javax.ws.%')"}
   }

4. OHI Agent upgrade

Upgrade OHI Agent: Refer to Downloading and Running Oracle Health Insurance Agent for steps to perform the Agent upgrade.

Configuration Properties

Ref	Action	Description
CPN-4302	Added	ohi.datatransfer.logging.phi.events.enabled Introduced a new optional property
NXT-32617	Added	ohi.ui.likesearch.wildcard.enabled This property enables or disables the trailing '%' sign from quick, advanced search, and lookup (LOV) with the query operators like and likeic.
NXT-33750	Added	ohi.api.download.max.rows The ohi.api.download.max.rows system property, which allows users to configure the maximum number of rows that can be downloaded through the Download API. By default, this property is set to 2,000 rows. The maximum supported value is capped at 10,000 rows.
OIG-4859	Added	ohi.object.storage.read.timeout.millis Time to wait between reads of data bytes from OCI object storage service
OIG-4859	Added	ohi.object.storage.connect.timeout.millis Timeout in milliseconds to establish connection with OCI object storage service.

Web Services

Ref	Action	Description
CPN-3799	Modified	Operational Reporting IP Two new error messages are introduced in the Operational Reporting IP. The IP returns an HTTP 422 response with one of the following error messages: OHI-IP-ORV-008: View {0} does not exist OHI-IP-ORV-009: Access restriction grant is missing to query the view {0}
CPN-3799	Modified	Data Transfer IP CSV files generated by the Data Transfer IP includes the header. When the query returned no records, the Data Transfer IP responds with HTTP 204 (No Content).
CPN-4206	Modified	logsecurityevents Added 9 new attributes: eventCategory, eventType, eventOutcome, eventSeverity, httpStatusCode, failureReason, apiEndpoint, sessionId, accessTokenId.
CPN-4207	Modified	logphievents Added three new attributes: accessScope, sessionId, and accessTokenId.
NXT-26542	Added	deploymentmetadata API New read-only generic API is added.
NXT-26542	Modified	userpreferences API Added a new attribute browserTimeZone to the user preferences API.
NXT-33750	Added	Download API New HTTP API integration Point -Download API is added
OIG-3267	Modified	exchangesteps API Added a new exchange step status 'In Progress'
OIG-4185	Modified	integrations api attribute subflowProcessInSequence' changed to 'processSubflowInSequence' in integrationsteps of type subflow
OIG-4573	Added	fileuploadresults IP To update the uploadSuccess field for a specific file upload result
POL-17946	Added	Audit Search Generic API Enable Generic POST operations. Retrieves Generic Audit records for a selected auditable entity, including its create, update, and delete history.

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

Dynamic Logic

Ref	Action	Description
CPN-3973	Modified	Groovy 5 upgrade Upgraded Groovy from 4.x to 5.0.7.

UI Changes

Ref	Action	Description
NXT-33659	Modified	Preferences Dialog A new checkbox, "Use Browser Timezone?" has been introduced in Preferences dialog which can be used to override the user’s configured timezone.
NXT-33750	Modified	All floorplan based pages (and Reference Sheet Lines) API based download is enabled in UI pages. However, there is an exclusion list application wise: UI based download is retained in Extensibility tabs and tabs of some Detail pages: Claims - Transaction Sources (Transaction Source Usages), Banks (Addresses, Bank Account Number Relations), Draft Provider pricing clause → deep link to Diminishing Rates Override drawer → Rate Blocks table, Search Adjudication Limit Counters, Diminishing Rates tab (Diminishing Rate Blocks), Organizations tabs (Addresses, Bank Account Number Relations, Relation Identifiers, Relation Links), Coverage Regimes Tabs (Cover Withhold Rules, Count Towards Limit), Draft Provider Pricing Clauses Deeplinks (Pricing Worksheet(Draft Provider Pricing Clauses Tab), Restrict To Method Drawer Link), Adjustment Rules Tabs (Adjustment Rule Percentages, Reimbursement Method Types), Combination Adjustment Rules Tabs (Adjustment Rule Percentages, Reimbursement Method Types), Dynamic Field Rules Tabs (Reimbursement Method Types tab), Encounter Rules Tabs (Reimbursement Method Types), Inclusion Rules Tabs( Reimbursement Method Types), Lower Of Rules Tab (Reimbursement Method Types), Messages Rules Tabs (Reimbursement Method Types), Pricing External Intervention Rules Tabs (Reimbursement Method Types), Provider Limit Categories → Provider Limit Rules Tabs (Provider Limit Heights, Reimbursement Method Types tabs) Proddef - Product Service Definition (Products and Across) Boilerplate text value is updated for all the Regime fields to indicate the type of regime Policies- Group Account adjustment overrides, Enrollment Product Adjustment overrides, Organization Providers Tabs (Provider Specialties, Provider Group Affiliations, Service Addresses, Provider Identifiers), Policy Process Flows Tabs ( Policy Process Steps, Policy Rule Steps), Group Process Flows Tabs (Group Process Steps, Group Rule Steps) Authorizations - Organization Providers Tabs (Provider Specialties, Service Addresses, Provider Identifiers) Capitation - Banks tabs (Addresses, Bank Account Number Relations), Organizations tabs (Addresses, Bank Account Numbers, Relation Identifiers, Relation Links), Persons tabs, Organization Providers tabs (Provider Specialties, Service Addresses, Provider Identifiers), Contract Adjustment lines
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
OIG-3267	Modified	Exchange step and subExchange step table in Exchange Page (IG0001) Added label 'blue' for new exchangeStepStatus 'InProgress'
OIG-3899	Modified	Exchange Search Page (IG0001), Exchange View Page (IG0001) Exchange Search Page: Quick search, advanced search added. Exchange ID column added. Row More Section field added - Properties, IntegrationType, Transaction Identifier 1, Transaction Identifier 2 Exchange View Page: Fields added - Exchange Id, Transaction Identifier 1, Transaction Identifier 2 Action added - Manual Refresh Button, Fail Exchange Button Label updated from 'Back to exchanges' to 'Exchanges'
OIG-3899	Modified	Sub-exchange search page (IG0001), Sub-exchange view page (IG0001) Sub-exchange search page: Quick search, advanced search added. Exchange ID column added. Sub-exchange view page: Fields added - Exchange Id, Transaction Identifier 1, Transaction Identifier 2
OIG-4185	Modified	Integrations Field name is changed from 'subflowProcessInSequence' to 'processSubflowInSequence' in subflowsteps floorplan
OIG-4573	Added	IG0032 File Upload Results New page "File Upload Results" for viewing and modifying the file upload status

Breaking Changes

Ref	Action	Description
CPN-3973	Modified	Groovy 5 upgrade Upgraded Groovy from 4.x to 5.0.7.
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.
NXT-33750	Modified	Below breaking change will be observed for UI download enhancement. Date / date time fields are not formatted. For system enumerations ( example status field on claim) key will be download. For composite columns - example when two different fields were shown in one column in UI, download will have columns per value. Example instead of one column for formatted name, download will have separate columns for first name, middle name , last name and so on. Another example is maximum value / current value in counters, and setup pages, in download separate columns will be present for maximum/current days, units and amount. Product service definition - download will show separate columns for each regime. In UI if a custom list of value is added on a native field / string field using floorplan based configuration, only native data will be part of download - example - partial provider pricing clauses only method code will be download
OIG-4942	Removed	Data File Sets IP Removed the GET operation on the datafilesets IP endpoint.

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
NXT-31594	Modified	CO0019 Added Create, Retrieve, Update, Delete access to User View Preference API as part of CO0019
NXT-33659	Modified	CO0019 The 'deploymentmetadata API' access restriction has been added to function code CO0019.
NXT-33750	Added	Download API access A user who has been granted GET access to a resource’s HTTP API can download that resource’s data using this endpoint.
OIG-4573	Added	IG0032 Access Restriction for File Upload Results UI page
OIG-4617	Modified	CO0019 keyboardshortcuts API and floorplans.enhance IP added to CO0019 function code

Bug Fixes

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
Resolution:		When a large file is uploaded to the exchange the exchange will complete
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.
Resolution:
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
Resolution:
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
Resolution:
37882217	4-0001407551	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. Also, UploadToUCM step fails with database error ORA-06512 in SaaS.
Resolution:		Zip and Unzip operations are now supported in the Data File Sets IP in SaaS. Also, UploadToUCM step now runs successfully and no longer fails with database error in SaaS.
Backports:		4.25.1.0.4
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
Resolution:		Fix added to show proper error message in UI
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.
Resolution:		Blocking exchanges that time out while a transformation is still running are now handled without logging an OptimisticLockException, and a system log is added to the exchange step that timed out.
37832181	3-40337961631	OIG-4353	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.
Backports:		4.25.1.0.0, 4.24.1.0.3
37782138	3-39282478411	OIG-4319	Search on exchanges is very slow when access restriction is defined
Description:		Search on exchanges is very slow when an access restriction is defined for an integration. This is because of suboptimal query generated as a result of redundant joins.
Resolution:		Search on exchanges now works efficiently, when an access restriction is defined for an integration.
Backports:		4.25.1.0.3
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
Resolution:		The reset method in the QueryStatisticsService is called for each dynamic logic because of which the statistics are cleared by the second dynamic logic. We need to ensure the reset method is called only once for every test unit call
39436234		OIG-5160	Stash items are now read in a deterministic order
Description:		Stash items inserted in the same batch could have the same creation timestamp. Because unprocessed stash item reads were ordered only by creation date, items with the same timestamp could be returned in an intermittent order. If dynamic logic stopped processing after an error, this could leave expected earlier items unprocessed and cause intermittent status update failures.
Resolution:		Stash item reads now use the stash item ID to order by. This makes cursor-style reads, including readUnprocessed() and getFirstUnprocessed(), return stash items in a deterministic order.
Backports:		4.25.1.0.10
38634091	4-0001407551	OIG-4748	Integration invocation with ZIP file fails
Description:		When an integration is invoked with a ZIP file, it fails with an error code GEN-PROC-ERR and exchange is not triggered.
Resolution:		Integration can be successfully invoked with a ZIP file. When exchange starts processing the Trigger step, the file is unzipped to data files and can be used in further processing.
Backports:		4.25.1.0.10
37528074		OIG-4213	Creating an integration code with spaces is allowed, but then results in errors
Description:		Users can create integration codes containing spaces, which causes errors after saving and when opening the integration from the search page.
Resolution:		Fix added to prevent error when integration code contains spaces.
38856814	4-0001793793	OIG-4881	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.
Backports:		4.25.1.0.7
37924983		OIG-4415	DAT-IP-DAFI-013, DAT-IP-DAFI-014 is not showing message in response
Description:		DAT-IP-DAFI-013, DAT-IP-DAFI-014 is not showing message in response. in the response. The expected behavior is that the error messages corresponding to these error codes should be returned in the response, providing more context and information about the error
Resolution:		Now user can see the response of the error message DAT-IP-DAFI-013 & DAT-IP-DAFI-014 working properly.
38876933	4-0001800026	OIG-4887	Exchange should continue processing if the datatransfer query doesn’t return any results.
Description:		When the query does not return any results(datatransfer location header gives a 204 response code), the data transfer exchange fails at the CheckDataTransferStatus step with the OIG-GATE-029 error. In the sub-exchange, the CheckDataTransferStatus fails with a NullPointerException under the same condition. In both cases, the exchange should continue processing and skip the CollectDataTransferData step.
Resolution:		Enhanced data transfer handling by skipping the CollectDataTransferData step when a 204 (No Content) response is received from CheckDataTransferStatus. This improvement applies to both the main flow and subflows.
Backports:		4.25.1.0.6
38171208		OIG-4494	Data transfer export to Oracle directory has issues with CSV and JSON formats
Description:		Data transfer export has issues: CSV output is invalid when string columns with commas are not escaped, JSON export returns empty values for CLOB columns exceeding 20MB, and JSON exports show only one file even when more records exist in the database.
Resolution:		Data transfer export now generates valid CSV output with escaped special characters, supports CLOB data in JSON format, and correctly reports the number of exported files. For SaaS customers, exporting columns of type CLOB in CSV or JSON format is currently not supported due to a known issue in the DBMS_CLOUD package. This limitation is tracked under Oracle Bug 38183169.
Backports:		4.25.1.0.4
39267154	4-0002125064	OIG-4952	Resources cannot be searched when code starts with %255%
Description:		POST search API requests were failing with an IntrusionDetectionException when the query contained specific special patterns. These legitimate input param were incorrectly identified as potential intrusion attempts, resulting in search failures.
Resolution:		Enhanced the intrusion detection mechanism to correctly handle search query parameters, preventing legitimate requests from being incorrectly flagged
Backports:		4.25.1.0.8
39079821		OIG-4982	Flex Code Base Views are both removed and updated at the same time
Description:		During Base View Generation, the generation of Flex Code Base View is unstable: (1) Concurrent update/remove operations occasionally targeted the same view, raising the Oracle error “table or view does not exist”. This happened intermittently. (2) The generator skipped creating some Flex Code Base Views whenever the Flex Code System code contained lowercase characters.
Resolution:		The update/removal operations are serialized to prevent errors like “table or view does not exist”. Flex Code Base Views are generated for Flex Code Systems with a code containing lowercase characters.
Backports:		4.25.1.0.8
38774302	4-0001329840	OIG-4837	Exchange recovery fails for Fusion job timeouts
Description:		While processing fusion steps in an exchange, If Load job ends with TIMEDOUT status in fusion portal, the exchange fails and recovery is not possible. If Load job is still in RUNNING status at the end of polling timeout (configured in the fusion destination), the exchange fails and recovery is not possible.
Resolution:		While processing fusion steps in an exchange, If fusion job ends with TIMEDOUT status in fusion portal, For Import job or Submit job, the exchange continues processing without any failure, similar to other error scenarios. For Load job, the exchange is marked Failed. The Load job has to be manually recovered by customer in fusion portal. Then, the exchange can be recovered to start polling the status of the Load job again and continue processing as usual. If fusion job is still in RUNNING status at the end of polling timeout (configured in the fusion destination), For all fusion jobs (Load job, Import job and Submit job), the exchange is marked Timed Out. Then, the exchange can be recovered to start polling the status of the fusion job again and continue processing as usual.
Backports:		4.25.1.0.10
39122626	4-0002100715	OIG-5021	Old handled events are re-processed when processing unhandled events
Description:		Old handled events outside the retention period of auto-purge can come up again when 'readUnhandledEvent' method is called in dynamic logic. This causes these handled events to get re-processed by the exchange.
Resolution:		The order of purge operations in auto-purge operation is modified so that events are purged first, followed by exchanges. This prevents old handled events from being re-processed.
38616008	3-42597605671	OIG-4722	All the files stored in the object storage are returned as data transfer response when no files are generated for the data transfer request.
Description:		All the files stored in the object storage are returned as data transfer response when no files are generated for the data transfer request.
Resolution:		HTTP 204 no content is returned as response when no files are generated for the data transfer request.
38892819	3-41728688211	OIG-4796	Increase in heap memory usage following the Groovy 4 upgrade
Description:		Post Groovy 4 upgrade, noticed higher memory usage, which can slow down the system. Groovy stores the reference of large Groovy-meta-class objects using soft references, meaning these objects are only removed when garbage collection runs and memory is low. Before this happens, the system can approach critical memory levels, triggering safety measures that reduce processing capacity on affected nodes and cause visible performance issues.
Resolution:		We have disabled the use of Groovy meta classes to address the memory issue. The necessary functionality will now be provided using non meta class references and methods instead.
39086926	4-0002256434	OIG-4989	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
Backports:		4.24.1.0.5, 4.25.1.0.7
38974021		OIG-4960	Exchange is failing while trying to create with xml fileupload or payload
Description:		When creating an Exchange of Payload type XML, the XML content is present for the POST call sent, which causes the exchange to fail with the error: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.
Resolution:		Fix has been implemented to ensure that XML content is correctly included in the payload for Exchange.
Backports:		4.25.1.0.8
39112995		OIG-5015	Query API returns incorrect totalResults when groupBy is used
Description:		When the Query API is invoked with the groupBy parameter, the totalResults value in the response is incorrect. Instead of returning the total number of groups produced by the groupBy attribute, the response returns the total number of records matching the q attribute.
Resolution:		The Query API now returns the correct totalResults value when groupBy is used, reflecting the total number of groups produced by the groupBy attribute.
39113969		OIG-5016	OAuth RestClientBuilder lookup fails due to duplicate enum keys across authentication feature enums
Description:		A key mismatch occurred 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
Backports:		4.25.1.0.7
39128524		OIG-5037	ORA‑06502 when querying a base view with column names longer than 30 characters in on‑prem deployment.
Description:		When a base view contains column names beyond 30 characters, the on‑prem runtime raises ORA‑06502: PL/SQL: numeric or value error: character string buffer too small while retrieving the result set.
Resolution:		Data transfer on on‑prem deployments now handles columns longer than 30 characters without raising ORA‑06502.
39362898		OIG-5126	PHI logging includes unmatched 'left joins' rows
Description:		When a query selects a PHI column from the right side of a LEFT JOIN, PHI logging is created for all rows from the left-side table, including rows where the joined row does not exist. In those cases the PHI column is effectively null, but a PHI log event is still written. This leads to incorrect PHI audit entries for rows that did not actually expose PHI.
Resolution:		When the joined column is marked as PHI but there is no match, no PHI Event is logged for that missing column.
Backports:		4.25.1.0.10
38779285		OIG-4840	File count incorrectly shown as 1 instead of 0 when multiple data transfer requests are dequeued together
Description:		A concurrency issue was identified in the data transfer dequeue processing logic. When multiple data transfer requests are dequeued and processed together, if one of the requests does not return any data, the system incorrectly reports the file_count as 1 instead of 0. This issue does not occur when requests are dequeued and processed individually. The incorrect file count is observed only in concurrent dequeue scenarios.
Resolution:		The dequeue processing logic has been corrected to ensure that the file_count is properly initialised and calculated independently for each request during concurrent processing.
38789085		OIG-4849	Data transfer requests fail with ORA-06502 when the schema name exceeds 30 characters.
Description:		Data transfer requests fail with the error ORA-06502: PL/SQL numeric or value error character string buffer too small when the schema name is longer than 30 characters.
Resolution:		A fix has been implemented in the data transfer functionality to support schema names of up to 120 characters.
38969008		OIG-4942	Remove GET support on datafilesets IP
Description:		Remove the GET operation on the datafilesets IP endpoint as it is no longer required.
Resolution:		Removed the GET operation on the datafilesets IP endpoint.
39410226	4-0002782929	OIG-5156	Mark cacheEnabled and invalidateLater as volatile in DynamicLogicServiceImpl to prevent stale cache state across threads
Description:		After dynamic logic was updated through CMT while the dynamic logic cache was disabled, some application nodes could continue executing the previously cached dynamic logic executable after the cache was enabled again. This could result in inconsistent calculation behavior across nodes because the latest dynamic logic definition from the database was not always used immediately after the CMT update.
Resolution:		The dynamic logic cache state flags used for cache enablement and delayed invalidation were made safely visible across threads. With this change, delayed invalidation requests made while the cache is disabled are reliably applied when the cache is enabled again. This ensures stale dynamic logic executables are invalidated and subsequent executions use the updated dynamic logic definition.
38223676	3-41237424921	OIG-4518	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.
Backports:		4.25.1.0.2
38400805		OIG-4617	keyboardshortcuts API should be part of CO0019 function code
Description:		keyboardshortcuts API and floorplans.enhance IP should be added to CO0019 function code
Resolution:		keyboardshortcuts API and floorplans.enhance IP added to CO0019 function code and also removed duplicate access from setup access role
Backports:		4.25.1.0.3
38761759		OIG-4829	Recovery of exchange failed or timed out on CheckDataTransferStatus step leads to out of memory scenario
Description:		When an exchange that failed or timed out on CheckDataTransferStatus step is recovered, the exchange gets stuck processing that step. This later leads to system running out of memory and errors are seen in application logs.
Resolution:		Recovering an exchange in the CheckDataTransferStatus step starts processing the exchange properly without getting stuck in that step or running out of memory.
Backports:		4.25.1.0.4
38471119		OIG-4656	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
Backports:		4.25.1.0.2
37995011	3-40662938551	OIG-4447	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.
Backports:		4.24.1.0.4, 4.25.1.0.1
37923625		OIG-4411	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
Backports:		4.25.1.0.1, 4.24.1.0.4
38424471	3-42116427601	OIG-4625	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.
Backports:		4.25.1.0.2
38167821		OIG-4492	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.
Backports:		4.25.1.0.2
37874761		OIG-4380	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.
Backports:		4.25.1.0.2
37994231		OIG-4444	'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
Backports:		4.24.1.0.4, 4.25.1.0.1
38014596	3-40938840831	OIG-4455	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
Backports:		4.24.1.0.4, 4.25.1.0.1
38819746	4-0001674695	OIG-4861	Dynamic logic fails when an output writer is created but no data is written in data file stored in object storage
Description:		Dynamic logic fails when the output writer is instantiated even though there is no data to process and no write operation is performed on the data file stored in object storage
Resolution:		The system allows the output writer to be instantiated and closed without performing any actual write operation on data file stored in object storage.
Backports:		4.25.1.0.6
38582447	4-0001341177	OIG-4697	Writing incident data files in Object Storage fails intermittently
Description:		Writing an incident data file in Object Storage fails intermittently with NoSuchElementException
Resolution:		The intermittent issue that prevented incident data files from being written to Object Storage has been resolved. The fix improves the reliability of file creation and storage operations.
38210048	3-41510962871	OIG-4509	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.
Backports:		4.23.1.0.10, 4.25.1.0.2
38309327		OIG-4569	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.
Backports:		4.25.1.0.2
38587006		OIG-4705	javax.persistence.NoResultException in CalculationPeriodRepositoryImpl
Description:		Log pollution is occurring due to inconsistent log levels, specifically using 'error' where 'warn' was appropriate.
Resolution:		Adjusted the log level from error to warn to reduce unnecessary log noise.
38669215	3-42706054381	OIG-4772	Recovery of failed or timed out ReceiveNotification step is unsuccessful if event store is used as error destination
Description:		If an OIG exchange fails or times out in the ReceiveNotification step and event store is used as error destination, an event is created by the error workflow. However, the location header present in exchange properties used for checking the external activity status gets overwritten with the URI of the created event. When the exchange is recovered, it is unsuccessful with a HTTP 401 Unauthorized error.
Resolution:		When an OIG exchange fails or times out in the ReceiveNotification step and event store is used as error destination, an event is created by the error workflow but it no longer overwrites the location header in exchange properties. As a result, recovery of exchange is successful, processing the exchange from the failed or timed out step.
Backports:		4.25.1.0.4
38077381		OIG-4463	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.
Backports:		4.25.1.0.2
38001704	3-40812684771	OIG-4450	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'
Backports:		4.25.1.0.1, 4.24.1.0.4
38525986	3-42385139441	OIG-4676	OHI Agent shuts down if connection with OIG is lost
Description:		If OHI Agent loses connection with OIG, it does not attempt to re-connect to OIG and shuts down.
Resolution:		OHI Agent now automatically attempts to reinstate its connection with OIG after a connection loss.
Backports:		4.25.1.0.3
38503418	3-42254456831	OIG-4669	OHI Agent fails to start if certain modules are disabled
Description:		OHI Agent fails to start when modules as2805_a and as2805_b are disabled through configuration properties.
Resolution:		OHI Agent now starts successfully when modules as2805_a and as2805_b are disabled through configuration properties.
Backports:		4.25.1.0.3
38832419	4-0001730662	OIG-4865	HICAPS/healthpoint requests are not being processed by the agent
Description:		The OHI Agent is unable to log on to HICAPS/HealthPoint devices and is failing to process requests.
Resolution:		OHI Agent is now able to log on to HICAPS/HealthPoint devices and processing requests successfully.
Backports:		4.25.1.0.6
38644039		OIG-4756	Successful transformation logic in the Delivery by Agent step re-executes during failed exchange recovery
Description:		If the Exchange fails at the Delivery by Agent step after the transformation logic of the Delivery has completed successfully, the same is re-executed during exchange recovery. This re-execution is unnecessary and should be skipped.
Resolution:		The successful transformation logic of Delivery step does not re-execute during the failed exchange recovery.
Backports:		4.25.1.0.9
39349791	4-0002679067	OIG-5124	Function API access mapping is missing for User View Preferences API
Description:		A user who has the ALL_FUNCTIONS_ACCESS_ROLE gets an error while using Exchanges page. User View Preferences API access is missing in JET login access role - CO0019 which leads to Not Authorized error.
Resolution:		User View Preferences API access is added to CO0019 function access so that there is no access error
Backports:		4.25.1.0.9
39401617		OIG-5153	Work manager ws-work-manager is not used for API/IP requests
Description:		Work manager ws-work-manager is not used for API/IP requests. As a result, when a large number of API/IP requests are submitted at the same time, the system may process more requests concurrently than expected instead of applying the usual throttling or queuing behavior. This can contribute to degraded performance or service instability under heavy load.
Resolution:		The fix restores the intended request handling behavior so API/IP traffic is processed with the appropriate concurrency limits.
39026116	4-0002140463	OIG-4951	Exchange IP 400 response for null/invalid exchange parameters did not identify which parameter(s) were null.
Description:		The issue occurs because the connector configuration can trigger Exchange requests with null parameter values. Previously, this resulted in a NullPointerException (NPE), causing OIG Exchange IP to return a 500 Internal Server Error. As part of the fix, the service was updated to return a 400 Bad Request instead when invalid or null parameters are received. However, the current 400 Bad Request response does not identify which exchange parameter is null or invalid. Including the name of the offending parameter in the error response would make troubleshooting connector configuration issues significantly easier.
Resolution:		The Exchange endpoint has been enhanced to include details of any null parameters in its 400 Bad Request response, making it easier to identify and troubleshoot invalid requests. The implementation, along with the associated integration tests, has been completed and merged into the Gateway application and the issue has been resolved.
38891996	4-0001624549	OIG-4889	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.
Backports:		4.25.1.0.7
38904287	4-0001784507	OIG-4903	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'
Backports:		4.25.1.0.7
39118292	4-0002256434	OIG-5018	Index.html is getting appended to url post login
Description:		index.html is getting appended to url after user logs into the application using custom authentication provider
Resolution:		index.html is not visible in url after user logs into the application using custom authentication provider
Backports:		4.25.1.0.8
39287333		OIG-5109	Domain attribute allowlist property set through API was not applied at runtime
Description:		The property ohi.untrusteddata.allowlist.domainattribute was not being applied when configured through the API. The same property continued to work correctly when set in the properties file. As a result, valid requests could still be flagged by the default untrusted-data intrusion check after the property was updated through the API.
Resolution:		Fixed the allowlist refresh behavior so updated domain attribute values are picked up immediately, preventing valid requests from being incorrectly flagged by the default untrusted-data intrusion check.
39811182		OIG-5282	Save integrations after navigating between activity steps not working
Description:		When users open an integration with multiple activity steps, navigate from one activity step to another, modify the second step, and save the integration, the application displays GEN-PROC-ERROR and does not save the changes
Resolution:		The Integrations page now saves the integration correctly after users navigate to another activity step and modifies it.
38614107	3-42478044721	OIG-4721	Stop dynamic logic processing upon exchange failure
Description:		When a user explicitly fails an exchange (POST api/exchanges/{id}/failure), any running dynamic logic transaction should be stopped as well. Currently, running dynamic logic transactions keep running in the background while the exchange indicates a failure status.
Resolution:		Explicit failure of the exchange stops running dynamic logic transactions on OIG
38364312	3-41897697051	OIG-4597	Exchanges Screen does not have access rights to search for widgets by default
Description:		On accessing exchanges screen with page access only, results in error with message: GEN-HTTP-004: Not authorized for this operation on this resource.
Resolution:		On accessing the exchanges screen, no error is shown with respect to widgets access
Backports:		4.25.1.0.3
39542981	4-0002052910	OIG-5193	Correcting exchange detail retrieval when an exchange step has no data file set reference
Description:		Fetching expanded exchange details fails when a data file set referenced by an exchange step has been purged.
Resolution:		Expanded exchange details are now returned successfully without attempting to retrieve the missing data file set for affected exchange step payloads.
37853887		OIG-4373	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.
Backports:		4.24.1.0.4, 4.25.1.0.1, 4.23.1.0.10
39142739		OIG-5040	PHI audit logs corrected for aliased base views in data transfer payloads
Description:		In specific data transfer scenarios, when a base view is queried through an alias and the Base View is outside of the Relation context, PHI logging was not generated correctly.
Resolution:		The system now generates the PHI audit logs correctly for these aliased base view scenarios.
Backports:		4.25.1.0.10
38179057		OIG-4497	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.
Backports:		4.25.1.0.1
38725905		OIG-4526	Task processing integration point restart and restart all operations did not resolve associated system event log
Description:		Invoking Task Processing IP Restart or Restart All operations on tasks in ERRORED status did not resolve the associated SystemEventLog, leaving log entries unresolved
Resolution:		System event logs associated with ERRORED tasks are now resolved when attempting restart
39522239	4-0002897772	OIG-5188	Exchange was marked as completed even though one of its related sub-exchanges had not finished and had timed out.
Description:		During recovery of timed out sequential subflows, the main exchange moved ahead to early and could be marked as completed before all sub-exchanges had actually finished
Resolution:		The recovery flow is corrected, the parent exchange waits properly on recovery of the timed-out sub-exchanges. If the sub-exchange times out again, the main exchange shows the correct status timed out.
39741385		OIG-5251	ZIP files are not scanned during exchange invocation
Description:		Previously, an on-demand antivirus scan for a data file set with ZIP content but no extracted data files could return a successful result without scanning the ZIP content. The on-demand scan decision only evaluated child data file scan statuses and did not consider the parent data file set status used for ZIP content.
Resolution:		The on-demand antivirus scan flow now considers the parent data file set scan status when ZIP content is present.
Backports:		4.25.1.0.10
38204812	3-41450968961	OIG-4506	NullPointerException when a substitution parameter value Is missing
Description:		When a configured substitution parameter in an integration step does not have a corresponding runtime value in the exchange, the system throws a NullPointerException.
Resolution:		Added validation to handle missing substitution parameter values gracefully. The system now detects the missing runtime value and returns a clear error message instead of throwing a NullPointerException. Also, OIG now supports optional substitution parameters in integration configuration using syntax: {?parameterName}
38226924	3-40724895331	OIG-4521	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.
Backports:		4.24.1.0.4, 4.25.1.0.2
38412648	3-42058901561	OIG-4618	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.
Backports:		4.25.1.0.2
38396440		OIG-4613	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.
Backports:		4.25.1.0.2
38774363		OIG-4838	Data Transfer step - columns wrongly set mandatory in typeConfig
Description:		In the OIG data transfer step typeConfig, currently fields 'Where' and 'Columns' are defined as mandatory. They should be optional.
Resolution:		'Where' and 'Columns' are optional now in Type config section
38021462	3-38637505211	OIG-4458	Unable to search a record having apostrophe
Description:		Users are unable to search for records when a field value contains an apostrophe. For example, if the integration description is 'Test' Int', the API returns an error instead of the expected result.
Resolution:		UI handles apostrophe in search input and returns expected results. When configuring filter, prefilter, prefilterList, widget query etc users must manually escape apostrophes in the value of the query expression by using another apostrophe.
39823034		OIG-5287	Navigating from View log lines of a sub exchange using back button is not working properly
Description:		When users open View Log Lines from a Sub Exchange, clicking the Back button does not return them to the originating Sub Exchange detail page. Instead, navigation context is lost and users may be directed to the main Exchanges page.
Resolution:		The Back button now returns users to the originating Sub Exchange detail page, preserving the navigation context.
38441003	3-42115849931	OIG-4632	Delivery By Agent step is marked done even though OHI Agent fails to deliver files
Description:		If OHI Agent fails to retrieve an access token for connecting with OIG, it fails to fetch the files to be delivered. Later, it sends an empty notification to OIG which is misinterpreted as a successful delivery and the Delivery by Agent step is marked as Done.
Resolution:		OIG no longer marks Delivery by Agent step as done if an empty notification is sent by OHI Agent, and an error message is added in exchange logs. Also, OHI Agent now attempts to retrieve an access token again in case of a failure during token retrieval.
Backports:		4.25.1.0.3
38438836		OIG-4629	Access role codes are not logged in security log when all the access roles are revoked from user
Description:		When all the access roles are revoked from a user, the security log records the user who performed the revocation and the user from whom the roles were revoked, but it does not record the access role codes.
Resolution:		The security log now also records the access role codes when all the access roles are revoked from a user.
37449175		OIG-4185	Inconsistent sequential processing parameter for subflow step configuration
Description:		Sequential or parallel processing of sub exchanges can be configured through API using parameter 'subflowProcessInSequence' in subflow step configuration. However, the naming of this parameter is inconsistent with the value defined in documentation.
Resolution:		The subflow parameter has been renamed from subflowProcessInSequence to processSubflowInSequence for consistency. Existing configurations do not require any changes, except for custom/new floorplans for subflowsteps, where the new field name must be used. For new subflow steps configured through the API, use processSubflowInSequence.
38274089		OIG-4514	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.
Backports:		4.25.1.0.1
38186883		OIG-4499	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.
Backports:		4.25.1.0.1
39160126	4-0002113383	OIG-5058	Memory exhaustion in Gateway due to dynamic logic creating multiple data files in Object Storage
Description:		A problem was identified where memory was not being properly freed after using writers in dynamic logic to create data files in Object Storage. When many files were created over time, this unused memory built up and could eventually cause the application to run out of memory and fail.
Resolution:		The cleanup process has been improved to ensure that memory and related resources are fully released whenever the writer is closed. By default, the system closes writers at the end of a dynamic logic transaction automatically thereby releasing the memory. However, in case multiple writers are opened within a single dynamic logic, memory exhaustion could still happen at runtime. It is therefore recommended to close readers and writers explicitly in dynamic logic. Please investigate if explicit closure of readers and writers is implemented in the dynamic logics. The documentation has been updated with examples of explicit closure of reader and writers. See Transformation Dynamic Logic chapter in the Developer Guide.
Backports:		4.25.1.0.8
39163836	4-0002187135	OIG-5060	Improve resilience for Object Storage file downloads from ohi when long-running data file processing causes HTTP streams to remain open for extended periods, reducing failures from truncated responses.
Description:		File downloads from OCI Object Storage could intermittently fail during long-running reads with truncated-response errors such as ConnectionClosedException (“Premature end of Content-Length delimited message body”). Because OHI ObjectStorageDataFileReader relied on a single InputStream, any mid-transfer interruption caused the CSV reader to receive only a partial payload, resulting in exchange failure. Need implementation to supports retry and byte-range resume for interrupted downloads.
Resolution:		Enhanced Object Storage download handling for scenarios where data files are processed slowly and the HTTP stream remains open for an extended period. Previously, long-running reads could fail with truncated-response errors such as ConnectionClosedException, causing the CSV reader to receive incomplete content and the exchange to fail. The implementation now improves resilience by retrying interrupted downloads and resuming from the last successfully read byte offset, while failing only after 3 consecutive recovery attempts without progress.
Backports:		4.25.1.0.8
38655758	3-42551002131	OIG-4762	OHI Agent fails to read the property file
Description:		OHI Agent fails to read the properties file (application.properties) if the file is present in the same folder as OHI Agent. As a result, OHI Agent fails to start if the file is present in the same folder, also referred to as AGENT_HOME.
Resolution:		OHI Agent starts successfully after reading the properties file (application.properties) when the file is present in the same folder as OHI Agent.
Backports:		4.25.1.0.4
38848649	4-0001730662	OIG-4879	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.
Backports:		4.25.1.0.7
38819456	4-0001350333	OIG-4859	Reading large files from object storage fails due to non-configurable read timeout.
Description:		OHI does not provide configurable timeout settings (connection and read timeouts) while reading or streaming files from Object Storage (OS). As a result, file read operations rely on default OCI SDK timeout values, which are not suitable for large files or long-running streaming use cases. When files are read record-by-record, the read operation may exceed the default socket read timeout, leading to java.net.SocketTimeoutException: Read timed out. This causes long-running processes to fail unexpectedly, even though the connection itself is healthy.
Resolution:		Support for configurable Object Storage timeouts has been added to improve reliability when processing large files and long-running streaming workloads. Two new properties are now available: a. ohi.object.storage.read.timeout.millis b. ohi.object.storage.connect.timeout.millis Both default to 60,000 ms (60 seconds) and can be increased as needed to prevent read timeouts errors during extended Object Storage operations
Backports:		4.25.1.0.8
38769145	4-0001366319	OIG-4832	Extract failures are now handled at the receivenotification step to ensure proper and efficient recovery flow
Description:		Recovering a failed extracts exchange doesn’t restart the collectData step making the recovery inefficient. To improve recovery handling, extract failures should be marked in the InvokeExtract step rather than in notificationCollectMessages step. On recovering the exchange after manual recovery of extracts, steps from InvokeExtract should be restarted.
Resolution:		For Extract use case, auto-recovery is always enabled. So code changes implemented in such a way when an Extract fails with Notification status marked as FAILED, the check recovery step fails all steps up to InvokeExtract. During manual recovery, the Extract recovery is initiated using the recovery link from InvokeExtract, ensuring proper restart of the recovery flow.
Backports:		4.25.1.0.6
38474146	3-42065414021	OIG-4663	Exchange endpoint returns Unsupported Media Type for certain XML files.
Description:		Certain XML files are misidentified as HTML files because of a bug in Apache Tika, the third-party dependency used for file type validation. As HTML files are not allowed as an input to exchange endpoint, Unsupported Media Type exception is returned as response.
Resolution:		While the bug in Tika is being resolved by Apache, we are allowing HTML files in exchange endpoint as a temporary fix. We will disallow HTML files again once the bug fix is delivered by Apache.
Backports:		4.25.1.0.6
38926038		OIG-4915	Add Widget tile is not visible in Dashboard page
Description:		When user logs in with access CO0019, add widget tile is not visible in view edit Dashboard page because user preference API has only retrieve access and not update.
Resolution:		Seed data is updated for CO0019 access restriction and user will be able to see Add Widget tile
36981547		OIG-974	View Log Lines Page - Column Header should be Exchange Step Status instead of Exchange Step
Description:		In View Log Lines page, displayed values are Exchange Step Status but header is Exchange Step
Resolution:		Included integration step and sub step information in View Log Lines page and modified column header from Exchange Step to Exchange Step Status
37386890		OIG-4161	Correcting the Notification IP response error message when exchange is not in WaitingOnExternalSystem(W) status
Description:		Oracle Insurance Gateway now returns HTTP 409 Conflict with error code OIG-GATE-066 when a notification is received for an exchange that is no longer in WaitingOnExternalSystem (W) status, instead of returning HTTP 204 No Content in the Notification IP.
Resolution:		When the exchange is not in WaitingOnExternalSystem(W) status, a HTTP 409 Conflict response is returned with error code OIG-GATE-066. Example error message: OIG-GATE-066: Exchange with id {exchangeId} for integration code {integrationCode} received notification for step {exchangeStepId} with code {integrationStepCode}, which could not be parsed properly due to: Exchange {exchangeId} is in state {exchangeStatus} (incorrect state for receiving a notification)
Backports:		4.25.1.0.10

Issues that were backported in previous Release / Patch

BugDB	Internal	Summary	Backport	BugDB	SR
37386890	OIG-4161	Correcting the Notification IP response error message when exchange is not in WaitingOnExternalSystem(W) status	4.25.1.0.10	39099774
37782138	OIG-4319	Search on exchanges is very slow when access restriction is defined	4.25.1.0.3	37782153	3-39282478411
37832181	OIG-4353	OHI Agent startup fails due to security protocol version mismatch	4.25.1.0.0	37832221	3-40337961631
37832181	OIG-4353	OHI Agent startup fails due to security protocol version mismatch	4.24.1.0.3	37832220	3-40337961631
37853887	OIG-4373	Performance degradation during OIG purge operations	4.24.1.0.4	37994213
37853887	OIG-4373	Performance degradation during OIG purge operations	4.25.1.0.1	37994183
37853887	OIG-4373	Performance degradation during OIG purge operations	4.23.1.0.10	37994165
37874761	OIG-4380	Exchange invocation fails with Internal Server Error (500 response code) if payload contains a null value	4.25.1.0.2	38445972
37882217	OIG-4399	Zip and Unzip operations in Data File Sets IP return HTTP 405 in SaaS	4.25.1.0.4	38575973
37923625	OIG-4411	When a field of type Number is configured as LOV in Search, it is returning 'undefined'	4.25.1.0.1	37923644
37923625	OIG-4411	When a field of type Number is configured as LOV in Search, it is returning 'undefined'	4.24.1.0.4	37923651
37994231	OIG-4444	'UserJET' property should expose userid, login name, display name, last login timestamp, defaultCountry information	4.24.1.0.4	37994294
37994231	OIG-4444	'UserJET' property should expose userid, login name, display name, last login timestamp, defaultCountry information	4.25.1.0.1	37994275
37995011	OIG-4447	User information is not available in floorplans using userJET property	4.24.1.0.4	37995022	3-40662938551
37995011	OIG-4447	User information is not available in floorplans using userJET property	4.25.1.0.1	37995019	3-40662938551
38001704	OIG-4450	Implement retry mechanism and content length verification during data file download in OIG	4.25.1.0.1	38004405
38001704	OIG-4450	Implement retry mechanism and content length verification during data file download in OIG	4.24.1.0.4	38001709
38014596	OIG-4455	Permissions error thrown in exchange search page	4.24.1.0.4	38014606
38014596	OIG-4455	Permissions error thrown in exchange search page	4.25.1.0.1	38014602
38077381	OIG-4463	eventDate attribute in logapplicationevents and logdynamiclogicevents resources ignores time component	4.25.1.0.2	38350833
38167821	OIG-4492	Enhance OHI Agent logging for keystore and token retrieval failures	4.25.1.0.2	38179132
38171208	OIG-4494	Data transfer export to Oracle directory has issues with CSV and JSON formats	4.25.1.0.4	38683690
38179057	OIG-4497	The datatype of the type_config column in the oig_integration_steps table should be modified to CLOB to accommodate larger typeconfig objects.	4.25.1.0.1	38179115
38186883	OIG-4499	collectDataTransfer step is failing with unique constraint error while downloading more than 1 file	4.25.1.0.1	38186900
38210048	OIG-4509	Delivery by OHI Agent is unsuccessful when there are more than 50 files to deliver	4.23.1.0.10	38210155
38210048	OIG-4509	Delivery by OHI Agent is unsuccessful when there are more than 50 files to deliver	4.25.1.0.2	38210085	3-41510962871
38274089	OIG-4514	All the servers experience decline in performance after invoking dynamiclogic/invalidateall	4.25.1.0.1	38210135
38223676	OIG-4518	Duplicate entries in OHI_TABLE_COLUMNS	4.25.1.0.2	38234379	3-41237424921
38226924	OIG-4521	Tracking/Tracing of requests should not be sent to external systems	4.24.1.0.4	38282097
38226924	OIG-4521	Tracking/Tracing of requests should not be sent to external systems	4.25.1.0.2	38226942	3-40724895331
38309327	OIG-4569	Add error handling for duplicate columns in base view generation	4.25.1.0.2	38309334
38364312	OIG-4597	Exchanges Screen does not have access rights to search for widgets by default	4.25.1.0.3	38364325	3-41897697051
38396440	OIG-4613	Exchanges with Data Transfer stop processing after invoking the Data Transfer	4.25.1.0.2	38416418
38400805	OIG-4617	keyboardshortcuts API should be part of CO0019 function code	4.25.1.0.3	38461343
38412648	OIG-4618	Exchange status filters are still applied after deselecting the filter records	4.25.1.0.2	38412676	3-42058901561
38424471	OIG-4625	Function Access mapping missing in IG0003 for Data Transfer step	4.25.1.0.2	38429684	3-42116427601
38441003	OIG-4632	Delivery By Agent step is marked done even though OHI Agent fails to deliver files	4.25.1.0.3	38441032	3-42115849931
38471119	OIG-4656	In Activity pages, for Column 'created By', values are not displayed on scroll	4.25.1.0.2	38471133
38474146	OIG-4663	Exchange endpoint returns Unsupported Media Type for certain XML files.	4.25.1.0.6	38474169	3-42065414021
38503418	OIG-4669	OHI Agent fails to start if certain modules are disabled	4.25.1.0.3	38503443	3-42254456831
38525986	OIG-4676	OHI Agent shuts down if connection with OIG is lost	4.25.1.0.3	38526002	3-42385139441
38634091	OIG-4748	Integration invocation with ZIP file fails	4.25.1.0.10	38634119	4-0001407551
38644039	OIG-4756	Successful transformation logic in the Delivery by Agent step re-executes during failed exchange recovery	4.25.1.0.9	39378078
38655758	OIG-4762	OHI Agent fails to read the property file	4.25.1.0.4	38655769	3-42551002131
38669215	OIG-4772	Recovery of failed or timed out ReceiveNotification step is unsuccessful if event store is used as error destination	4.25.1.0.4	38669224	3-42706054381
38761759	OIG-4829	Recovery of exchange failed or timed out on CheckDataTransferStatus step leads to out of memory scenario	4.25.1.0.4	38761785
38769145	OIG-4832	Extract failures are now handled at the receivenotification step to ensure proper and efficient recovery flow	4.25.1.0.6	38769154	4-0001366319
38774302	OIG-4837	Exchange recovery fails for Fusion job timeouts	4.25.1.0.10	38774365	4-0001329840
38819456	OIG-4859	Reading large files from object storage fails due to non-configurable read timeout.	4.25.1.0.8	38819476	4-0001350333
38819746	OIG-4861	Dynamic logic fails when an output writer is created but no data is written in data file stored in object storage	4.25.1.0.6	38819818	4-0001674695
38832419	OIG-4865	HICAPS/healthpoint requests are not being processed by the agent	4.25.1.0.6	38832618	4-0001730662
38848649	OIG-4879	OHI agents fail to start in a Coherence cluster	4.25.1.0.7	38848677	4-0001730662
38856814	OIG-4881	Missing secrets for OAuth clients while ohistore is used as keystore	4.25.1.0.7	38856821	4-0001793793
38876933	OIG-4887	Exchange should continue processing if the datatransfer query doesn’t return any results.	4.25.1.0.6	38876947	4-0001800026
38891996	OIG-4889	Upload to UCM is not successful when Object Storage is enabled	4.25.1.0.7	38892045	4-0001624549
38904287	OIG-4903	System throwing NullPointerException when there is no value for EXCL_PHI_LOGGING in the OHI_REPORTING_VIEWS table	4.25.1.0.7	38904292
39267154	OIG-4952	Resources cannot be searched when code starts with %255%	4.25.1.0.8	39267275	4-0002125064
38974021	OIG-4960	Exchange is failing while trying to create with xml fileupload or payload	4.25.1.0.8	39124748
39079821	OIG-4982	Flex Code Base Views are both removed and updated at the same time	4.25.1.0.8	39079862
39086926	OIG-4989	Dates not populated when using JET on virtual box	4.24.1.0.5	39086947	4-0002256434
39086926	OIG-4989	Dates not populated when using JET on virtual box	4.25.1.0.7	39086977	4-0002256434
39113969	OIG-5016	OAuth RestClientBuilder lookup fails due to duplicate enum keys across authentication feature enums	4.25.1.0.7	39114088
39118292	OIG-5018	Index.html is getting appended to url post login	4.25.1.0.8	39118343
39142739	OIG-5040	PHI audit logs corrected for aliased base views in data transfer payloads	4.25.1.0.10	39526236
39160126	OIG-5058	Memory exhaustion in Gateway due to dynamic logic creating multiple data files in Object Storage	4.25.1.0.8	39160130	4-0002113383
39163836	OIG-5060	Improve resilience for Object Storage file downloads from ohi when long-running data file processing causes HTTP streams to remain open for extended periods, reducing failures from truncated responses.	4.25.1.0.8	39163849	4-0002187135
39349791	OIG-5124	Function API access mapping is missing for User View Preferences API	4.25.1.0.9	39349804	4-0002679067
39362898	OIG-5126	PHI logging includes unmatched 'left joins' rows	4.25.1.0.10	39444641
39436234	OIG-5160	Stash items are now read in a deterministic order	4.25.1.0.10	39436246
39741385	OIG-5251	ZIP files are not scanned during exchange invocation	4.25.1.0.10	39741614

Known Issues

BugDB	SR	Internal	Summary
36413617		OIG-2902	Displaying back button on exchange home screen
Description:		Displaying back button on exchange home screen
35777257		OIG-3389	Boilerplate seen in JET dynamiclogic page
Description:		Boilerplate seen in JET dynamiclogic search page for labels
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
39106464		OIG-4435	Recovery of parallel sub-exchanges sometimes gives optimistic lock
Description:		Sometimes on recovery of exchanges with parallel sub-exchanges an optimisticLock exception is seen.
39914828		OIG-5321	Incorrect audit record generation for subflow create and update operations
Description:		Inconsistencies observed in audit record generation for subflows: * When a subflow is created, two audit records are generated (one for the integrations table and another for the subflows table) * When an existing subflow is updated, no audit record is generated
39926925		OIG-5329	Audit API should inherit the access restriction of its parent resource
Description:		Currently, Audit API resources have their own newly created access restriction instead of inheriting the access restriction of the corresponding resource. As a result, a user who already has access to a resource (for example, Policies) may still be unable to access that resource Audit API unless an additional Audit API-specific access restriction and grant are provided. The Audit API must work by default for users who are authorized to access the underlying resource. It should therefore use the same access restriction as its parent resource, rather than requiring a separate restriction.

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