Release Notes for Oracle Insurance Gateway Patch 4.23.2.0.2

This document contains the release notes for Oracle Insurance Gateway Patch 4.23.2.0.2.

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

In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases.

Enhancements

ID	Summary	Patch
CPN-3079	Auto purge feature As data volume in Oracle Health Insurance applications continue to grow with the processing of more data, it becomes essential to manage the database efficiently. Oracle Health Insurance applications include various PL/SQL packages for purging processes. However, these processes currently require manual intervention by customer DBAs/AMS team to configure and schedule purge jobs during planned maintenance windows. To streamline this process and automate database maintenance, we are introducing an auto-purge job feature. This feature eliminates the need for manual scheduling of various purge jobs and ensures that data is regularly purged according to predefined criteria. As part of this enhancement, we have a introduced a new PL/SQL package ohi_auto_purge_pkg.purge_all and modified the following functionalities : The structure of the following procedures has been revised, introducing an optional input parameter p_commit_size to enhance flexibility and control over the purging process cla_data_purge_pkg.purge_data ohi_repl_purge_pkg.purge_data Log message purging is now integrated into the auto-purge feature, and as a result, the following HTTP API resources have been made read-only. logeventretentionperiods API loglevelretentionperiods API Purging of PHI logs is now integrated into the auto-purge feature. So, the property ohi.logging.phi.min.retentionperiod is removed The process now integrates purging of all datafile sets into the auto-purge system, eliminating the need for separate scheduled scavenging and purging of incident files. So, the property ohi.incident.datafileset.retentionperiod is removed Oracle recommends frequent and automatic purging of technical data and operational data using the auto-purge job feature. For example, customer DBA/AMS team (in SaaS) can set up auto purge through the use of a DBMS_SCHEDULER job. See the user guide for more details and for a sample SQL script that creates auto purge job using DBMS_SCHEDULER.create_job PL/SQL procedure. Note that the initial purge job might take longer if the volume of the data is very high (for example, if the system has two years of data to purge and if the retention days for technical data are set to 60 days). So, Oracle recommends the DBA/AMS team to set a higher retention period (for example, one year and 11 months) for the initial run (so only 30 days of data is purged in the very first run). The retention days can be reduced gradually until the historical data is purged. Documentation Links: Administration Guide - Datafile Set Trace Files Retention Administration Guide - Purging Data from Replication Technical Tables Administration Guide - Purging Data from Technical Tables Administration Guide - Auto Purge Developer Guide - Purge Exchanges	4.23.1.0.7, 4.24.1.0.0
NXT-24066	WebLogic authentication implemented compliant with the Java Authorization and Authentication Service (JAAS) specification This enhancement introduces support for the SAML 2.0 authentication mechanism in the Oracle Health Insurance. Additionally, a new JAR file named "CustomIdentityAsserter" has been created to accommodate the Basic Auth configuration. Refer installation guide for further detail. Documentation Links: Installation Guide - Users and Authentication	4.23.1.0.6, 4.24.1.0.0
OIG-3525	AS2805_A Claim Quote Reversal Handling Claim quote reversals are considered redundant in AS2805_A. This enhancement introduces a feature to handle Quote reversals in OHI Agent without using OIG. If OHI Agent receives a Claim quote reversal or Claim quote reversal repeat message from the AS2805_A switch, the Agent returns a 0430-171000 response. The response message is a standard 0430 response which is an echo of the incoming request with the following fields set additionally: * Transmission date time: current date and time * Response code: 00	4.23.1.0.6, 4.24.1.0.0
POL-12956	Purge data files In Oracle Health Insurance applications, data files generated during various activities (e.g., extract activity, financial messages activity and data files uploaded to initiate long-running operations) remain in the system even after they have been processed/consumed. Currently, there is no mechanism in place to automatically clean up these data files once they have been processed/consumed, leading to inefficiency of the database storage space. This enhancement aims to automate the cleanup process and optimize database storage space. To enable purging data files, we have introduced a new PL/SQL package ohi_purge_datafileset_pkg. Documentation Links: Administration Guide - Purging Data from Data File Sets	4.23.1.0.7, 4.24.1.0.0

Summary

Patch

CPN-3079

Auto purge feature

As data volume in Oracle Health Insurance applications continue to grow with the processing of more data, it becomes essential to manage the database efficiently. Oracle Health Insurance applications include various PL/SQL packages for purging processes. However, these processes currently require manual intervention by customer DBAs/AMS team to configure and schedule purge jobs during planned maintenance windows.

To streamline this process and automate database maintenance, we are introducing an auto-purge job feature. This feature eliminates the need for manual scheduling of various purge jobs and ensures that data is regularly purged according to predefined criteria.

As part of this enhancement, we have a introduced a new PL/SQL package ohi_auto_purge_pkg.purge_all and modified the following functionalities :

The structure of the following procedures has been revised, introducing an optional input parameter p_commit_size to enhance flexibility and control over the purging process
- cla_data_purge_pkg.purge_data
- ohi_repl_purge_pkg.purge_data
Log message purging is now integrated into the auto-purge feature, and as a result, the following HTTP API resources have been made read-only.
- logeventretentionperiods API
- loglevelretentionperiods API
Purging of PHI logs is now integrated into the auto-purge feature. So, the property ohi.logging.phi.min.retentionperiod is removed
The process now integrates purging of all datafile sets into the auto-purge system, eliminating the need for separate scheduled scavenging and purging of incident files. So, the property ohi.incident.datafileset.retentionperiod is removed

Oracle recommends frequent and automatic purging of technical data and operational data using the auto-purge job feature. For example, customer DBA/AMS team (in SaaS) can set up auto purge through the use of a DBMS_SCHEDULER job. See the user guide for more details and for a sample SQL script that creates auto purge job using DBMS_SCHEDULER.create_job PL/SQL procedure.

Note that the initial purge job might take longer if the volume of the data is very high (for example, if the system has two years of data to purge and if the retention days for technical data are set to 60 days). So, Oracle recommends the DBA/AMS team to set a higher retention period (for example, one year and 11 months) for the initial run (so only 30 days of data is purged in the very first run). The retention days can be reduced gradually until the historical data is purged.

Documentation Links:
Administration Guide - Datafile Set Trace Files Retention
Administration Guide - Purging Data from Replication Technical Tables
Administration Guide - Purging Data from Technical Tables
Administration Guide - Auto Purge
Developer Guide - Purge Exchanges

4.23.1.0.7, 4.24.1.0.0

NXT-24066

WebLogic authentication implemented compliant with the Java Authorization and Authentication Service (JAAS) specification

This enhancement introduces support for the SAML 2.0 authentication mechanism in the Oracle Health Insurance. Additionally, a new JAR file named "CustomIdentityAsserter" has been created to accommodate the Basic Auth configuration.

Refer installation guide for further detail.

Documentation Links:
Installation Guide - Users and Authentication

4.23.1.0.6, 4.24.1.0.0

OIG-3525

AS2805_A Claim Quote Reversal Handling

Claim quote reversals are considered redundant in AS2805_A. This enhancement introduces a feature to handle Quote reversals in OHI Agent without using OIG. If OHI Agent receives a Claim quote reversal or Claim quote reversal repeat message from the AS2805_A switch, the Agent returns a 0430-171000 response. The response message is a standard 0430 response which is an echo of the incoming request with the following fields set additionally: * Transmission date time: current date and time * Response code: 00

4.23.1.0.6, 4.24.1.0.0

POL-12956

Purge data files

In Oracle Health Insurance applications, data files generated during various activities (e.g., extract activity, financial messages activity and data files uploaded to initiate long-running operations) remain in the system even after they have been processed/consumed. Currently, there is no mechanism in place to automatically clean up these data files once they have been processed/consumed, leading to inefficiency of the database storage space.

This enhancement aims to automate the cleanup process and optimize database storage space. To enable purging data files, we have introduced a new PL/SQL package ohi_purge_datafileset_pkg.

Documentation Links:
Administration Guide - Purging Data from Data File Sets

4.23.1.0.7, 4.24.1.0.0

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

Perform any pre-upgrade steps.
Stop all the managed nodes running the existing version of the application.
Perform any pre-undeploy steps.
Undeploy the existing version of the application.
Back up the database.
Perform any post-undeploy steps.
Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.
Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.
Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.
Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)
Run the Upgrade script:
1. Open a command window and browse to <OHI_ROOT>/util/install.
2. Run the upgrade by executing ./ohi-update.sh .
Make the required changes to the ohi properties file
Perform any post-upgrade steps
Start WebLogic application server
Deploy the Application
Perform any post-deploy steps

Configuration Properties

Ref	Action	Description
CPN-3079	Removed	ohi.logging.phi.min.retentionperiod Purging of logs is now integrated into the auto-purge feature. So, this property is removed. The default retention for PHI logs with the auto-purge function is 2560 days (7 years) and can be managed through the autopurgemetadata API
CPN-3079	Removed	ohi.incident.datafileset.retentionperiod Purging of all datafile sets is now integrated into the auto-purge system, hence, eliminating the need for separate scheduled scavenging and purging of incident files. So, this property is removed.

Ref

Action

Description

CPN-3079

Removed

ohi.logging.phi.min.retentionperiod

Purging of logs is now integrated into the auto-purge feature. So, this property is removed. The default retention for PHI logs with the auto-purge function is 2560 days (7 years) and can be managed through the autopurgemetadata API

CPN-3079

Removed

ohi.incident.datafileset.retentionperiod

Purging of all datafile sets is now integrated into the auto-purge system, hence, eliminating the need for separate scheduled scavenging and purging of incident files. So, this property is removed.

Web Services

Ref	Action	Description
CPN-3079	Added	autopurgemetadata API Added a new autopurgemetadata API
CPN-3079	Removed	loglevelretentionperiods API loglevelretentionperiods API supports only GET operation. POST/PATCH/PUT/DELETE operations are not longer supported
CPN-3079	Removed	logeventretentionperiods API logeventretentionperiods API supports only GET operation. POST/PATCH/PUT/DELETE operations are not longer supported

Ref

Action

Description

CPN-3079

Added

autopurgemetadata API

Added a new autopurgemetadata API

CPN-3079

Removed

loglevelretentionperiods API

loglevelretentionperiods API supports only GET operation. POST/PATCH/PUT/DELETE operations are not longer supported

CPN-3079

Removed

logeventretentionperiods API

logeventretentionperiods API supports only GET operation. POST/PATCH/PUT/DELETE operations are not longer supported

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Breaking Changes

Ref	Action	Description
CPN-3079	Removed	loglevelretentionperiods API loglevelretentionperiods support only GET operation. POST/PATCH/PUT/DELETE operations are no longer supported. So, it is not possible to purge log messages based on a specific log level. Instead purging of logs (irrespective of the log level) is now integrated into the auto-purge feature
CPN-3079	Removed	logeventretentionperiods API logeventretentionperiods API support only GET operation. POST/PATCH/PUT/DELETE operations are no longer supported. So, it is not possible to purge log messages based on a specific log level. Instead purging of logs (irrespective of the log level) is now integrated into the auto-purge feature
NXT-24066	Modified	Installation Configuration Customers using the Basic Authentication mechanism must follow the installation guide to install the newly built JAR file, "CustomIdentityAsserter.jar," and configure the WebLogic security provider accordingly.
OIG-3868	Modified	deliverByAgent step If exchanges failed or timed out during the deliverByAgent step before the upgrade, it is not possible to recover them after the upgrade.

Ref

Action

Description

CPN-3079

Removed

loglevelretentionperiods API

loglevelretentionperiods support only GET operation. POST/PATCH/PUT/DELETE operations are no longer supported. So, it is not possible to purge log messages based on a specific log level. Instead purging of logs (irrespective of the log level) is now integrated into the auto-purge feature

CPN-3079

Removed

logeventretentionperiods API

logeventretentionperiods API support only GET operation. POST/PATCH/PUT/DELETE operations are no longer supported. So, it is not possible to purge log messages based on a specific log level. Instead purging of logs (irrespective of the log level) is now integrated into the auto-purge feature

NXT-24066

Modified

Installation Configuration

Customers using the Basic Authentication mechanism must follow the installation guide to install the newly built JAR file, "CustomIdentityAsserter.jar," and configure the WebLogic security provider accordingly.

OIG-3868

Modified

deliverByAgent step

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

Bug Fixes

BugDB	SR	Internal	Summary
36684743	3-36839446281	OIG-3843	OIG OOM issue due to accumulating of in-memory logs
Description:	The issue is due to the buildup in OIG heap memory caused by already opened financial transactions in policies that push notification messages.
Resolution:	In OIG, implemented a code fix to create a transaction and commit after every 50 downloaded notification messages as a resolution to this issue.
36662889	3-36813495181	OIG-3834	Buffer too small for CLOB to CHAR conversion during subflow recovery
Description:	In the sub-exchanges during recovery , using a VARCHAR2 data type as a placeholder to parse the Exchange Properties JSON string of data type CLOB caused issues when the string length exceeded 32700 bytes. This is a code-related issue.
Resolution:	Changed the data type of placeholder to CLOB to hold the Exchange Properties.
36067318	3-34591482241	OIG-3506	Purge requests of exchanges errors out with deadlock detected message.
Description:	Purge of exchanges errors out with deadlock detected message when the RAC database service is configured as active/active.
Resolution:	The dead lock error while purging the exchanges is resolved by removing the on delete cascade constraint on OIG_EXCHANGE_LOGS table.
37056631		OIG-4024	Action button missing on exchange pages
Description:	All Action Buttons were missing from exchanges pages
Resolution:	Action buttons are visible on the exchanges pages and are interactable.
36668969	3-36840886581	OIG-3839	Scheduled Exchanges are triggered multiple times
Description:	If multiple Integrations with schedule are updated at a time, then all future scheduled exchanges are rescheduled. In a multi-node setup, due to an issue with scheduling mechanism, it is executed on multiple nodes at the same time. As a result, multiple instances of exchanges would be triggered.
Resolution:	The scheduling mechanism executes on one node at a time, thus avoiding creation of multiple instances of scheduled exchanges.
36662857	3-36788604651	OIG-3831	Exchange stops processing when Fusion ERP Job status polling fails due to an Error response from Fusion
Description:	If Fusion ERP Job status polling fails due to an Error response from Fusion (eg - 502 Bad Gateway), exchange stays in Waiting on External System (W) status. No logs are added, exchange does not Fail and recovery is not possible from this scenario.
Resolution:	If an Error response is received during Fusion ERP Job status polling, exchange fails with proper error message in exchange logs. Upon recovery, Fusion ERP Job status polling is restarted for the same job.
37607201		OIG-4249	Deliverbyagent fails with npe when there is a raw payload created by previous step instead of a datafile
Description:	CheckAgentAvailability, DeliverByAgent, and ReceiveAgentNotification should be skipped when the previous step creates a raw payload instead of a datafile, as there are no files to deliver.
Resolution:	A conditional check has been implemented to skip the integration steps CheckAgentAvailability, DeliverByAgent, and ReceiveAgentNotification when a datafile is not available from the previous step.
36733311	3-37002072411	OIG-3868	Exchange incorrectly marked completed during recovery without file delivery to agent
Description:	When an exchange containing a 'deliverByAgent' step fails and is subsequently recovered after resolving the underlying issue, the exchange is incorrectly marked as completed without actually delivering the file via the Agent. This behavior is also observed in sub-exchanges.
Resolution:	Delivery by Agent step is now split in three sub steps i.e. check agent availability, delivery by agent and receive notification. Exchange status will now be 'waitingForExternalSystem' instead of 'waitingForAgentToSignoff' during the delivery by agent process. Agent now uses notification endpoint to send the response back to Oracle Insurance Gateway instead of using the sign off and failure integration points. It is now possible to configure 'timeAllowed' type config for the delivery step (using agent) within an integration. For the integrations responsible for delivering large file using an Agent, it is recommended to set a higher allowed time for the delivery step to prevent time outs (default wait time is 5 minutes). If exchanges failed or timed out during the deliverByAgent step before the upgrade, it is not possible to recover them after the upgrade.
36604533	3-36421449471,3-36886229061	OIG-3820	Handling NPEs During Eclipse Transactions
Description:	Handling NPEs and adding logs during failure scenarios of proda token retrieval
Resolution:	Handle NPE to throw Token Retriever Exception when proda token retrieval is null . Also added an error logging too.
36820479		OIG-3910	Incorrect result shown in Boilerplates Table
Description:	The boilerplate table shows incorrect results after performing the 'ADD' and then 'CANCEL' actions simultaneously. This behavior is generic to other table-based pages.
Resolution:	Correct results are shown after performing the 'ADD' and then 'CANCEL' actions simultaneously in table-based pages
37223332	OHISD-3966	OIG-4107	Invoke exchanges tiles are shown with only retrieve access to exchanges.
Description:	Invoke exchanges tiles are shown with only retrieve access to exchanges.
Resolution:	Invoke exchanges tiles are not shown when only retrieve access is present on exchanges.
36369291	3-35833647381	OIG-3707	Multiple filters are not working in JET UI screens once you perform quick search
Description:	Select filters by checking the checkbox on Exchange status (started, failed). Then do quick search on any Integration code. The filters are not retained while performing quick search . The results include exchanges in status complete as well.
Resolution:	The filters are retained with quick search in Exchanges page
36718864		OIG-3861	Add new row is shown at last in table pages
Description:	Click Add new in table page. A new row is getting appended in the last visible row of the screen
Resolution:	Table component is modified with the below changes: 1) On click of Add button, a new row will be added to the top of the available rows. It is a sticky row to the table 2) Two new icons are added to a new row. Check icon would add the new row to the table and clicking on Cross icon would discard the new row. 3) User will have to click on Check icon and Save to persist the newly added data
37438064	3-34889024331	OIG-4175	NullPointerException upon exchange recovery
Description:	When an activity step fails to return an appropriate response, the exchange can come into a state where recovery is impossible due to a NullPointerException occurring.
Resolution:	If upon recovery the activity notification does not exist, it is fetched with the location header
36833628		OIG-3919	Integer field values are shown with separator (12,345 instead of 12345)
Description:	Enter '12345' in integer fields like "house number" or state and country code" in Persons page, it is getting displayed as 12,345
Resolution:	Integer field values are shown without separators now
37506999		OIG-4201	Exchange Invocation Headers should be treated as case sensitive
Description:	When an exchange is invoked with exchange specific headers like ohi-exchange-description but with uppercase letters like Ohi-Exchange-Description, it is ignored because it is not in lowercase. According to HTTP RFC standard, headers should be treated as case insensitive and so OIG should accept the headers irrespective of case.
Resolution:	In order to make exchange specific headers case insensitive we are explicitly converting them to lowercase and then try to get the value of that header.
36870909	3-37313793651	OIG-3929	Auto Recovery button not working
Description:	When the auto recovery flag is set to false and saved from UI, the flag is stored as true
Resolution:	The auto recovery flag is saved with the value selected in the UI
36909333		OIG-3935	Download Message checkbox appearing twice in Integration Steps page.
Description:	Download Message checkbox appearing twice in Integration Steps page.
Resolution:	Download Message checkbox is shown only once in Integration Steps page.
37248654		OIG-4112	Error when attempting to upload files to OIG
Description:	User experiences 406 (Not Acceptable) Error when attempting to upload files to OIG
Resolution:	It is possible to upload files in OIG without any error.
37093039	3-37860226571	OIG-4060	NPE in Eclipse Integrations
Description:	NPEs are raised for some eclipse integrations when the token is not retrieved successfully
Resolution:	There was a delay in the synchronization process between the keystore and the cache, which could lead to both being out of sync temporarily. The synchronization process has changed to make them consistent.
37563961	3-36224017471	OIG-4231	Floorplan conversion script fails when the payload size is large
Description:	Floorplan conversion script fails to convert set1, set2, set3 to sets array and results in error during upgrade. This is due to large payload size which was not handled by liquibase conversion script.
Resolution:	Liquibase script is modified to handle usecase where floorplan size is large and there is no error during conversion of region set1, set2, set3 to sets[]

BugDB

Internal

Summary

36684743

3-36839446281

OIG-3843

OIG OOM issue due to accumulating of in-memory logs

Description:

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

Resolution:

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

36662889

3-36813495181

OIG-3834

Buffer too small for CLOB to CHAR conversion during subflow recovery

Description:

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

Resolution:

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

36067318

3-34591482241

OIG-3506

Purge requests of exchanges errors out with deadlock detected message.

Description:

Purge of exchanges errors out with deadlock detected message when the RAC database service is configured as active/active.

Resolution:

The dead lock error while purging the exchanges is resolved by removing the on delete cascade constraint on OIG_EXCHANGE_LOGS table.

37056631

OIG-4024

Action button missing on exchange pages

Description:

All Action Buttons were missing from exchanges pages

Resolution:

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

36668969

3-36840886581

OIG-3839

Scheduled Exchanges are triggered multiple times

Description:

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

Resolution:

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

36662857

3-36788604651

OIG-3831

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

Description:

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

Resolution:

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

37607201

OIG-4249

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

Description:

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

Resolution:

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

36733311

3-37002072411

OIG-3868

Exchange incorrectly marked completed during recovery without file delivery to agent

Description:

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

Resolution:

Delivery by Agent step is now split in three sub steps i.e. check agent availability, delivery by agent and receive notification.
Exchange status will now be 'waitingForExternalSystem' instead of 'waitingForAgentToSignoff' during the delivery by agent process.
Agent now uses notification endpoint to send the response back to Oracle Insurance Gateway instead of using the sign off and failure integration points.
It is now possible to configure 'timeAllowed' type config for the delivery step (using agent) within an integration.
For the integrations responsible for delivering large file using an Agent, it is recommended to set a higher allowed time for the delivery step to prevent time outs (default wait time is 5 minutes).
If exchanges failed or timed out during the deliverByAgent step before the upgrade, it is not possible to recover them after the upgrade.

36604533

3-36421449471,3-36886229061

OIG-3820

Handling NPEs During Eclipse Transactions

Description:

Handling NPEs and adding logs during failure scenarios of proda token retrieval

Resolution:

Handle NPE to throw Token Retriever Exception when proda token retrieval is null . Also added an error logging too.

36820479

OIG-3910

Incorrect result shown in Boilerplates Table

Description:

The boilerplate table shows incorrect results after performing the 'ADD' and then 'CANCEL' actions simultaneously. This behavior is generic to other table-based pages.

Resolution:

Correct results are shown after performing the 'ADD' and then 'CANCEL' actions simultaneously in table-based pages

37223332

OHISD-3966

OIG-4107

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

Description:

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

Resolution:

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

36369291

3-35833647381

OIG-3707

Multiple filters are not working in JET UI screens once you perform quick search

Description:

Select filters by checking the checkbox on Exchange status (started, failed). Then do quick search on any Integration code. The filters are not retained while performing quick search . The results include exchanges in status complete as well.

Resolution:

The filters are retained with quick search in Exchanges page

36718864

OIG-3861

Add new row is shown at last in table pages

Description:

Click Add new in table page. A new row is getting appended in the last visible row of the screen

Resolution:

Table component is modified with the below changes: 1) On click of Add button, a new row will be added to the top of the available rows. It is a sticky row to the table 2) Two new icons are added to a new row. Check icon would add the new row to the table and clicking on Cross icon would discard the new row. 3) User will have to click on Check icon and Save to persist the newly added data

37438064

3-34889024331

OIG-4175

NullPointerException upon exchange recovery

Description:

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

Resolution:

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

36833628

OIG-3919

Integer field values are shown with separator (12,345 instead of 12345)

Description:

Enter '12345' in integer fields like "house number" or state and country code" in Persons page, it is getting displayed as 12,345

Resolution:

Integer field values are shown without separators now

37506999

OIG-4201

Exchange Invocation Headers should be treated as case sensitive

Description:

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

Resolution:

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

36870909

3-37313793651

OIG-3929

Auto Recovery button not working

Description:

When the auto recovery flag is set to false and saved from UI, the flag is stored as true

Resolution:

The auto recovery flag is saved with the value selected in the UI

36909333

OIG-3935

Download Message checkbox appearing twice in Integration Steps page.

Description:

Download Message checkbox appearing twice in Integration Steps page.

Resolution:

Download Message checkbox is shown only once in Integration Steps page.

37248654

OIG-4112

Error when attempting to upload files to OIG

Description:

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

Resolution:

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

37093039

3-37860226571

OIG-4060

NPE in Eclipse Integrations

Description:

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

Resolution:

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

37563961

3-36224017471

OIG-4231

Floorplan conversion script fails when the payload size is large

Description:

Floorplan conversion script fails to convert set1, set2, set3 to sets array and results in error during upgrade. This is due to large payload size which was not handled by liquibase conversion script.

Resolution:

Liquibase script is modified to handle usecase where floorplan size is large and there is no error during conversion of region set1, set2, set3 to sets[]

Issues that were backported in previous Release / Patch

No backports.