Release Notes for Oracle Insurance Gateway Release 4.23.2.0.0
This document contains the release notes for Oracle Insurance Gateway Release 4.23.2.0.0.
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. It is mandatory to upgrade to 4.23.2.0.2 patch version. This will ensure that JET floorplan conversion is done with the script delivered in the Bug 37563961 which is part of 4.23.2.0.2. |
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 |
---|---|---|
AUT-3268 |
Metrics internal code optimization This enhancement adds a metric set for every OHI metric category. The property "ohi.instrumentation.gather.applicationmetrics" controls all metrices and can be used to switch on/off all the OHI metrices. The property "ohi.instrumentation.gather.{0}" controls a single metric set or category of metrices The placeholder value is the code of the metric set such as "activityprocessing", "persistence", "springbatch", "datareplication". The following properties have been removed:
Documentation Links: |
|
AUT-3423 |
Spring Batch Metrics included in Prometheus for Import and Export This enhancement introduces the inclusion of spring batch metrics in Prometheus for import and export. These metrics provide useful information for CMT import and export. Documentation Links: |
|
AUT-3561 |
Remove environment identifier from healthcheck As part of this enhancement, environment identifier has been removed from healthcheck. |
|
NXT-24398 |
Cache query (by code) results on configuration entities This enhancement implements caching for all the configuration entities using code. This has been previously implemented only for a few entities. |
|
NXT-25486 |
Multiscreen support in JET This enhancement adds multiple screens with tabs feature to JET to allow users to switch between the screens easily. |
|
NXT-26266 |
JET: Enhance View and Edit template to support different layouts for information presentation This enhancement introduces a new component Form. Form component allows for multi sections - multi column configuration. This enhancement also makes it possible to have a multi column configuration within the region component. Documentation Links: |
|
NXT-27369 |
Upgrade to Java 11 and WebLogic 14.1.1 This enhancement upgrades Java to version 11 and WebLogic to version 14.1.1. See "Additional Upgrade Steps for Installation" below and the installation guide for more details. Documentation Links: |
|
NXT-27376 |
Migration of credentials from OPSS to ohistore Weblogic 14.1.0.0 has removed support for OPSS; hence, existing secrets must be migrated to a new secret store. |
|
NXT-27927 |
UI: Download feature in Results Component This enhancement introduces the ability to download data displayed within the results component in search pages and tabs in view and edit pages. Documentation Links: |
|
NXT-28213 |
UI: Application to support Small and Large scales This enhancement introduces the possibility for the user to choose an application scale 1) large or 2) small by setting the user preference attribute Large fonts? Large fonts, when set to |
|
OIG-3266 |
Cascade parent exchange failure to sub exchanges This enhancement enables a user to explicitly fail running sub exchanges by failing the parent exchange. Documentation Links: |
|
OIG-3496 |
Include TimedOut status in exchange metrics This enhancement adds a metric for exchanges that time out to metric name ohi.exchange.timer. Documentation Links: |
|
OIG-3575 |
Upgraded OHI Agent to Java 17 The Oracle Health Insurance Agent is upgraded and now needs Java Runtime Environment 17 to run. |
|
POL-12478 |
Exclude reference resources for generic GET operation This enhancement introduces a new resource representation parameter excludereferenceresources. When set to Additionally, for the search requests originating from UI, excludereferenceresources is set to Documentation Links: |
|
POL-13552 |
JET: Default override for UI operations For the API requests originating from the UI for create, update, and delete operations, the defaultoverride parameter is set to true to reduce the overall response payload. Documentation Links: |
|
POL-13590 |
UI: Deeplinks to support full screen mode This enhancement will make it possible to configure deep links to open in a 1) Drawer or 2) full screen in a new tab in the view mode. Documentation Links: |
|
POL-3449 |
UI: Keyboard shortcuts This enhancement introduces configurable shortcut keys for header’s action buttons. Documentation Links: |
Additional Upgrade Steps
This section describes the steps that a functional application manager will take during the upgrade. These steps to be performed as an application user who is authorized to access the IPs.
Pre-Upgrade Phase
-
Export the keystore from OPSS/Vault
Invoke the following "GET" request to export the keystore:
http://[hostName]:[portNumber]/[api-context-root]/keystores/export
. The response of this request can be saved anywhere on the file system as e.g.keystores.json
. -
Export the credentials from OPSS/Vault
Invoke the following "GET" request to export the credentials:
http://[hostName]:[portNumber]/[api-context-root]/credentials/export
. The response of this request can be saved anywhere on the file system as e.g.credentials.json
.
Post-Deploy Phase
-
Import the saved keystore
Invoke the following "POST" request to import the keystore:
http://[hostName]:[portNumber]/[api-context-root]/keystores/import
. This request will take the previously saved file as the input (e.g.keystores.json
). The parameter name is "keystore". -
Import the saved credentials
Invoke the following "POST" request to import the keystore:
http://[hostName]:[portNumber]/[api-context-root]/credentials/import
. This request will take the previously saved file as the input (e.g.credentials.json
). The parameter name is "credentials".
Upgrade Steps for Installation
To perform the upgrade, perform the following steps:
-
Perform any pre-upgrade steps.
-
Stop all the managed nodes running the existing version of the application.
-
Perform any pre-undeploy steps.
-
Undeploy the existing version of the application.
-
Back up the database.
-
Perform any post-undeploy steps.
-
Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.
-
Change Installation Configuration: In
<OHI_ROOT>/util/install
, make a copy ofohi_install.cfg.template
and name itohi_install.cfg
. -
Edit
ohi_install.cfg
to contain your specific database connection data and other configuration settings. The settings are explained in the file itself. -
Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)
-
Run the Upgrade script:
-
Open a command window and browse to
<OHI_ROOT>/util/install
. -
Run ohi-credential-store-install.sh to create credential store schema.
-
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
Additional Upgrade Steps for Installation
The following phases are defined:
|
Pre-Upgrade phase
-
Verify that version 4.23.1.0.2 or later is installed.
-
Configure property "ohi.credential.migration.enabled" either in the database or property file and set the property value to "true". This property will allow the end user to access the endpoint to export/import the secrets i.e. keystore and credentialstore.
-
Restart the application for the change to take effect.
-
Have the Application User user export the keystore and credentials as described earlier in this document.
-
Execute the below SQL statement with the user: OHI_OIG_OWNER and commit.
declare
n int := 0;
begin
select count(*)
into n
from databasechangelog
where filename = '2023-11-28_PCO-31_OHI_FLOOR_PLAN_CONVERTION.xml';
if n = 0 then
execute immediate 'INSERT INTO DATABASECHANGELOG (ID, AUTHOR, FILENAME, DATEEXECUTED, ORDEREXECUTED, EXECTYPE, MD5SUM, DESCRIPTION, COMMENTS, TAG, LIQUIBASE, CONTEXTS, LABELS, DEPLOYMENT_ID) VALUES (''1'', ''raharipr'', ''2023-11-28_PCO-31_OHI_FLOOR_PLAN_CONVERTION.xml'', TO_TIMESTAMP(''18-12-23 12:56:45.461573000 PM'', ''DD-MM-RR fmHH12:fmMI:SSXFF AM''), 144794, ''EXECUTED'', ''8:cf2dfe7841f8a217182b7fa3327d8ba6'', ''sql'', NULL, NULL, ''4.19.0'', NULL, NULL, ''2900599765'')';
end if;
end;
Post-Undeploy phase
-
Upgrade to JDK 11 and WebLogic 14.1.1.0
4.23.2.0.0 major release of OHI applications are certified to work with Java 11 and Weblogic 14.1.1.0. See the Installation Guide, section "Required Software", for an overview of the minimal patches that must be applied. Java and Weblogic software should be installed before the upgrade.
-
Install the latest JDK 11 (11.0.3 or higher patch version)
-
Install WebLogic 14.1.1.0.0. Make sure to use the "Generic Installer"
-
Install the mandatory patches as mentioned in "Required Software" section of the Installation Guide
-
Stop the managed servers, admin server and node manager in the existing WebLogic 12.2.1.4 domain
-
Take a backup of the existing domain directory
-
The existing domain that was created using Oracle Fusion Middleware 12.2.1.4 can not be upgraded to WebLogic 14.1.1.0.0. So, a new domain needs to be created:
-
Set JAVA_HOME to Java 11 before creating a new domain using configuration wizard
-
See the sections "Install and Configure Oracle WebLogic" and "Install Application" in the Installation Guide for more details
-
Copy the contents of set<Application>Env.sh (mentioned in "Install and Configure Oracle Fusion Middleware" section of the Installation Guide) from the existing domain to the new domain (review the contents before copying and make changes if necessary)
-
Review any additional configuration/JAVA_OPTIONS from the existing domain such as the changes made to startWebLogic.sh etc and make similar changes in the new domain
-
-
Post-Deploy phase
-
Have the Application User user import the keystore and credentials as described earlier in this document.
-
Configure property "ohi.credential.migration.enabled" either in the database or property file and set the property value to "false". This property will disable end user access to the endpoint to export the secrets i.e. keystore and credentialstore.
-
Restart the application for the change to take effect.
Configuration Properties
Ref | Action | Description |
---|---|---|
NXT-27376 |
Modified |
NXT-27376 Allowed values for property "ohi.secure.secrets.store" are one of the following: "vault", "ohistore". |
Web Services
Ref | Action | Description |
---|---|---|
NXT-27376 |
Added |
Import Keystores Import keystore |
NXT-27376 |
Added |
Export Keystores Export existing keystores |
NXT-27376 |
Added |
Export Credentials Export existing credentials |
NXT-27376 |
Added |
Import Credentials Import credentials |
Data Conversion
Ref | Action | Description |
---|---|---|
NXT-26266 |
Modified |
All floorplans that support region Region with set1, set2, set3 is converted to sets array |
UI Changes
Ref | Action | Description |
---|---|---|
NXT-25486 |
Modified |
All pages Adds tabs feature to JET for easy switching between the pages/screens |
NXT-26266 |
Modified |
Claim, Claimlines, CTR claims, CTR claimlines The floorplan for the mentioned pages is modified to support the form layout. Form layout is configurable for other View and Edit pages. |
NXT-26266 |
Modified |
Policy, Enrollment, Enrollment Product, Group client, Group account, and Product The floorplan for the mentioned pages is modified to support the form layout. Form layout is configurable for other View and Edit pages. |
NXT-27927 |
Modified |
All Search pages and tabs results Added capability to download results in a csv of search page and tabs for list configuration. |
NXT-28213 |
Added |
Application Scaling/FontSize JET applications support multiple Scales. 1. Large. 2. Small. Small is the default scale configured. Users can switch the scale value by using the checkbox present in the preference dialog. |
POL-13590 |
Modified |
Persons, Policies Extended Deeplink Functionality to open the field PECOs and Policy Holder in a new tab on view. |
POL-3449 |
Added |
KeyboardShortcuts(CO0021) Added keyboard shortcuts entry under user preferences dropdown. On clicking, a dialog opens up where user can view or update shortcut entries for page actions.Also added shortcuts enabled indicator under user preferences |
Breaking Changes
Ref | Action | Description |
---|---|---|
AUT-3561 |
Removed |
"environment" property Now, as part of health response the above property is not there anymore. |
NXT-27369 |
Modified |
Timestamp The default timestamp format in the error message argument has changed after the Java 11 upgrade. The format in use now is YYYY-MM-DDTHH:MM:SS. Example: Error text before this release was, 'CLA-IP-LIMI-024: Start date-time "1/1/11 12:00 AM" cannot be greater than the end date-time "1/1/10 12:00 AM" of the transaction period'. This is now changed to 'CLA-IP-LIMI-024: Start date-time "2011-11-01T00:00:00" cannot be greater than the end date-time "2010-11-01T00:00:00" of the transaction period'. |
NXT-27376 |
Modified |
Replacement of OPSS/Vault With the upgradation of Weblogic 14.1.0.0.x, the default secret store, which was earlier "OPSS," has been changed to "ohistore". The ohistore is a custom solution built within the product to provide similar functionality. If any secret has been stored in OPSS/Vault, then those are supposed to be migrated. See NXT-27376 for migration. |
OIG-3575 |
Modified |
OIG Agent The agent now requires JRE 17. If the OHI agent uses Vault as secrets store, re-configure Vault access using the Vault certificate URL (in PEM format). |
Bug Fixes
BugDB | SR | Internal | Summary |
---|---|---|---|
35589618 |
3-33633802101 |
OIG-3238 |
The error comes up during the creation of a new version of integration if we delete a step and click on save |
Description: |
The error comes up during the creation of a new version of an Integration if we delete a step and click on Save. Error : GEN-ORA-01400: "CODE" column is mandatory for table "OIG_INTEGRATION_STEPS" |
||
Resolution: |
A new version of an Integration can be created even if we delete a step and click on Save |
||
35548144 |
3-33515434791 |
OIG-3212 |
Improve log messages to point to log file when appropriate |
Description: |
Improve log messages to point to log file when appropriate. For example, when parsing the XML financial message fails in dynamic logic, the error reported in the dynamic logic is "java.lang.RuntimeException: Failed to acquire value for elementName financialMessage", which does not point to how and where more information can be found. |
||
Resolution: |
|||
35855211 |
OIG-3417 |
Dynamic logic cache reloads every time on business cache invalidation, even if there is no dynamic logic update |
|
Description: |
Dynamic logic cache uses a business process cache, which is invalidated on any change in configuration entities (that implements ProcessCacheInvalidating) even though there is no change in dynamic logic itself. On invalidation of the cache, byte code is loaded again for all the dynamic logic, which is CPU intensive and can slow down other processes running in parallel during the class loading. |
||
Resolution: |
The cache invalidation and reloading happen only on changes in the dynamic logic entity. |
||
Backports: |
4.23.1.0.1, 3.22.2.0.13 |
||
34979921 |
3-31796002821 |
OIG-2948 |
Dynamic logic timeout property is ignored when compiling dynamic logic at startup time |
Description: |
The dynamic logic timeout property (ohi.dynamiclogic.timeout or ohi.dynamiclogic.timeout.{0}) is ignored when the dynamic logic is compiled at system startup time. |
||
Resolution: |
Load the system property from the database if the loading of system properties is not completed. If loading of system property is completed, then load from cache. |
||
Backports: |
4.23.1.0.1, 3.22.2.0.14 |
||
35680943 |
OIG-3324 |
Table pages: Only the first few records are loaded in UI; no scrolling is possible after those first few records |
|
Description: |
In table pages, all the records are not rendered in UI. Fewer records are displayed than the total records available. When we add a new record, it is not shown in the UI after scrolling but displayed on search. |
||
Resolution: |
Scrolling is possible after the first few records, and all the results loaded are visible in the UI. |
||
35775547 |
OIG-3380 |
Exchanges with autoRecovery which fail generate stacktraces with NullPointerException |
|
Description: |
When a process invoked by an integration with autoRecovery true results in failure, the exchange fails as expected. In this case, it is also generating stacktraces with NullPointerException. |
||
Resolution: |
The NullPointerException no longer occurs in this case. |
||
Backports: |
4.23.1.0.2, 3.22.2.0.14 |
||
35027005 |
OIG-2956 |
JET application stuck with splash screen when HTTP error occurs |
|
Description: |
The JET application is stuck with the splash screen when an HTTP error occurs, such as UnAuthorized. Instead, the error should be shown on the UI, and the message should be communicated to the user. |
||
Resolution: |
JET application is not stuck with a splash screen when an HTTP error occurs like UnAuthorized; instead, the user is shown an error message. The message is similar to what is returned in the API response. |
||
35722655 |
OIG-3354 |
Exchange fails with NPE at step level timeout when the status of the process fails |
|
Description: |
When the notification endpoint is not set for OIG, and the external process fails, the exchange fails with Null Pointer Exception at step-level timeout. |
||
Resolution: |
The NullPointerException is handled in this scenario. |
||
Backports: |
4.23.1.0.1 |
||
35639830 |
3-33725336541 |
OIG-3294 |
JET UI hanging and no error message when attempting to invoke a disabled integration |
Description: |
When attempting to invoke a disabled integration in JET UI, the pinwheel on the screen displays indefinitely, and no HTTP error message is shown in the UI. |
||
Resolution: |
When attempting to invoke a disabled integration in JET UI, an HTTP error message is shown in the UI. |
||
35716416 |
OIG-3346 |
Agent Configuration Integrations - The page is not opening |
|
Description: |
When we click on the Add button under the Agent Configuration Integrations tab, the page was not loading completely for the following pages:
|
||
Resolution: |
The Agent Configuration page doesn’t give a console error when clicking the Add button under the Agent Configuration Integrations tab. |
||
Backports: |
4.23.1.0.1 |
||
35657376 |
3-33723635841 |
OIG-3300 |
Recovery of failed exchanges with Time Guard fails with Optimistic Locking Exception |
Description: |
For Failed and Timed Out exchanges with auto-recovery configured and incomplete Time Guard tasks, recovery operation on exchange fails with Optimistic Locking Exception. |
||
Resolution: |
For Failed and Timed Out exchanges, incomplete Time Guard tasks are marked as Dismissed. Recovery operation on Failed and Timed Out exchanges with auto-recovery configured no longer fail with Optimistic Locking Exception. |
||
Backports: |
4.23.1.0.1, 3.22.2.0.12 |
||
35760614 |
3-33899684681 |
OIG-3377 |
Timeallowed parameter for the subtype activity under subflow integration step is not viewable/editable |
Description: |
Timeallowed parameter for the subtype activity under subflow integration step is not viewable/editable. |
||
Resolution: |
Timeallowed parameter for the subtype activity under subflow integration step is added to the system floorplan. |
||
36029226 |
3-34889024331 |
OIG-3484 |
NullPointerException upon exchange recovery |
Description: |
When an activity step fails to return an appropriate response, the exchange can come into a state where recovery is impossible due to a NullPointerException occurring. |
||
Resolution: |
If upon recovery the activity notification does not exist, it is fetched with the location header |
||
Backports: |
4.23.1.0.8, 4.24.1.0.1, 4.23.2.0.2 |
||
35599504 |
3-33533327711 |
OIG-3251 |
OIG shouldn’t accept an empty notification and throw a meaningful error back. |
Description: |
In case of Null or incorrect notification, post receive notifications were failing. |
||
Resolution: |
In case of Null or incorrect notification, the notification received won’t be accepted. |
||
Backports: |
3.22.2.0.12, 4.23.1.0.0 |
||
35958808 |
OIG-3427 |
Dynamic logic is not compiled at startup |
|
Description: |
Dynamic logic was not always recompiled at application startup. |
||
Resolution: |
Any dynamic logic with tec_byte_code as null will be compiled during application startup, and tec_byte_code will be populated accordingly. |
||
Backports: |
4.23.1.0.1, 3.22.2.0.14 |
Issues that were backported in previous Release / Patch
BugDB | Internal | Summary | Backport | BugDB | SR |
---|---|---|---|---|---|
34979921 |
OIG-2948 |
Dynamic logic timeout property is ignored when compiling dynamic logic at startup time |
4.23.1.0.1 |
35854453 |
|
34979921 |
OIG-2948 |
Dynamic logic timeout property is ignored when compiling dynamic logic at startup time |
3.22.2.0.14 |
35850642 |
|
35599504 |
OIG-3251 |
OIG shouldn’t accept an empty notification and throw a meaningful error back. |
3.22.2.0.12 |
35599543 |
3-33533327711 |
35599504 |
OIG-3251 |
OIG shouldn’t accept an empty notification and throw a meaningful error back. |
4.23.1.0.0 |
35705403 |
3-33533327711 |
35657376 |
OIG-3300 |
Recovery of failed exchanges with Time Guard fails with Optimistic Locking Exception |
4.23.1.0.1 |
35731611 |
3-33723635841 |
35657376 |
OIG-3300 |
Recovery of failed exchanges with Time Guard fails with Optimistic Locking Exception |
3.22.2.0.12 |
35657385 |
3-33723635841 |
35716416 |
OIG-3346 |
Agent Configuration Integrations - The page is not opening |
4.23.1.0.1 |
35716436 |
|
35722655 |
OIG-3354 |
Exchange fails with NPE at step level timeout when the status of the process fails |
4.23.1.0.1 |
35722659 |
|
35775547 |
OIG-3380 |
Exchanges with autoRecovery which fail generate stacktraces with NullPointerException |
4.23.1.0.2 |
35775565 |
|
35775547 |
OIG-3380 |
Exchanges with autoRecovery which fail generate stacktraces with NullPointerException |
3.22.2.0.14 |
35775568 |
|
35855211 |
OIG-3417 |
Dynamic logic cache reloads every time on business cache invalidation, even if there is no dynamic logic update |
4.23.1.0.1 |
35855228 |
|
35855211 |
OIG-3417 |
Dynamic logic cache reloads every time on business cache invalidation, even if there is no dynamic logic update |
3.22.2.0.13 |
35855222 |
|
35958808 |
OIG-3427 |
Dynamic logic is not compiled at startup |
4.23.1.0.1 |
35958842 |
|
35958808 |
OIG-3427 |
Dynamic logic is not compiled at startup |
3.22.2.0.14 |
null |
|
36029226 |
OIG-3484 |
NullPointerException upon exchange recovery |
4.23.1.0.8 |
37438058 |
3-34889024331 |
36029226 |
OIG-3484 |
NullPointerException upon exchange recovery |
4.24.1.0.1 |
37438084 |
3-34889024331 |
36029226 |
OIG-3484 |
NullPointerException upon exchange recovery |
4.23.2.0.2 |
37438064 |
3-34889024331 |
Known Issues
BugDB | SR | Internal | Summary |
---|---|---|---|
34164754 |
OIG-2567 |
Outbound exchange attributes are not set |
|
Description: |
When trying to build a data set the attributes exactVersionMatch and disableDeleteByOmission are not getting updated. The attribute inclusionDate is not updated when passing an empty value. |
||
36413617 |
OIG-2902 |
Displaying back button on exchange home screen |
|
Description: |
Displaying back button on exchange home screen |
||
35143264 |
OIG-3006 |
Create configuration migration set overwrites existing sets when entered through JET & API |
|
Description: |
In the JETUI, if a new configuration migration is created and a code is used of a CMT set that already exists, the existing migration set is overwritten with the data of the "new" set. The expectation is that saving that "new" set would fail because there already is an existing set with that code. |
||
35544838 |
3-33374204261 |
OIG-3209 |
Whenever there is a IP error response, errorCode, errorPath and errorDetails should be prefixed with 'o:' to follow the REST standards. |
Description: |
Few IP error responses are not inline with REST standards. 'o:' is missing. |
||
35686796 |
OIG-3322 |
Dynamic logic unit test statistics are incorrect |
|
Description: |
When the user queries something in the testunit dynamic logic and then tests another dynamic logic in the same testunit dynamic logic, the value/count for all query parameters displays incorrect |
||
35777257 |
OIG-3389 |
Boilerplate seen in JET dynamiclogic page |
|
Description: |
Boilerplate seen in JET dynamiclogic search page for labels |
||
35942075 |
3-33802793381 |
OIG-3456 |
OptimisticLockException in log instead of exchange log timeout in blocking exchanges |
Description: |
Blocking exchanges which time out during transformation step with HTTP 504 Gateway timeout, result in an OptimisticLockException in the log file. |
||
36001095 |
OIG-3476 |
Integration version : Dynamic logic is not copied for the newly created version |
|
Description: |
When new version of integration created, dynamic logic of the steps are not copied. Steps to reproduce : 1. Create a integration with transform step and a attached dylo. 2. Create new version of the integration using 'Create new version' button and save. |
||
36067277 |
3-34591482241 |
OIG-3505 |
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. |
||
36086332 |
3-34871101921 |
OIG-3516 |
Invoking exchange with filename containing diacritics corrupts created datafile name |
Description: |
Invoking exchange with file upload, where the filename contains diacritics, erroneously transforms the filename to some other characters. |
||
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 |
||
36189878 |
OIG-3593 |
Execute datafile incident cleanup job (scavenging scheduler job) only on single node |
|
Description: |
The datafile set scavenging/cleanup job is scheduled to clean up application incidents (trace files) every day at midnight. This Spring scheduling job is executed on all the nodes, which is an unwanted use of resources, it is it would be efficient to run this only once (eg: on the master/oldest node in the coherence cluster). |
||
36194857 |
OIG-3605 |
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 |
||
36270312 |
OIG-3606 |
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. |
||
36251883 |
OIG-3607 |
All records are not shown in downloaded file, only 10 records are shown even after scrolling in table page |
|
Description: |
When a user scrolls through a set of records and clicks on download action in the table, the downloaded file doesn’t show the correct result. |
||
36204176 |
3-34786906091 |
OIG-3621 |
Dynamic logic byte code is not loaded during server startup on non master nodes after invalidateall API is invoked |
Description: |
Dynamic logic byte code is expected to load at the startup of non-master nodes if the invalidateall API was invoked in master node but was not being observed. |
||
36209617 |
3-35422276881 |
OIG-3631 |
Query Step failed in Subflows |
Description: |
When a Subflow configured with a Query step is executed, the Exchange fails with a Null Pointer Exception. |
||
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. |
||
36241409 |
OIG-3649 |
Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release |
|
Description: |
Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release |
||
36269912 |
OIG-3667 |
Unable to edit values in drawer when a field is configured as deeplink |
|
Description: |
It is not possible to edit resources which are configured as Deeplinks. For example in Individual providers, it is not possible to edit service address in rendering address tab. On click of edit button in service address drawer, its directly navigating back to individual providers page and not possible to edit/save |
||
36281259 |
OIG-3672 |
Non-selective criteria in reference objects cause OHI to load too many objects in memory. |
|
Description: |
Non-selective criteria in reference objects cause OHI to load too many objects in memory. |
||
36281924 |
3-35703331611 |
OIG-3673 |
OHI Agent will not start when more than 50 agent configurations are defined |
Description: |
If there are more than 50 agent configurations defined in OIG, the agent gets stuck in an endless loop at startup. |
||
36282331 |
3-35406309051 |
OIG-3676 |
Add additional loggers when agents are down |
Description: |
Add additional loggers in agent code when it is down. |
||
36309098 |
3-35614505731 |
OIG-3683 |
Exchange gets stuck in collect messages step when there are more than 50 messages to collect |
Description: |
In an exchange which invokes an OHI process, if there are more than 50 activity messages to collect, it will keep collecting the same 50 messages over and over, rather than paginate to get the rest of the messages. |
||
36317310 |
OIG-3687 |
Generate baseviews fails intermittently with CacheCreationException |
|
Description: |
Generate baseviews fails intermittently with CacheCreationException: Name of the cache entityNamePropertyCache already exists. |
||
36325016 |
3-35757295771 |
OIG-3690 |
Unable to add parameters to integration steps |
Description: |
unable to add parameters to integration steps |
||
36331378 |
3-35676286031 |
OIG-3692 |
Add additional loggers and exceptional handling during token refresh code |
Description: |
OHI Agent needs to refresh the oAuth token on a regular basis. Sometimes, this process of retrieving a new token from IDCS halts, and agent stops responding and/or writing entries to the logfile. |
||
36368157 |
OIG-3702 |
Dismissed timeguard tasks are picked up for processing and marked complete after 5 minutes |
|
Description: |
When an exchange fails before it times out, the time guard task (responsible for timing out the exchange) is set to status 'Dismissed', but keeps waiting for its configured time out. If the exchange is recovered before the time guard task is triggered to run, it will time out the recovered exchange too early (as per the original time out). |
||
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 |
||
36369274 |
3-35833647381 |
OIG-3706 |
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. |
||
36377459 |
OIG-3712 |
Save and Cancel shortcuts aren’t working for create Hierarchical Recursive pages |
|
Description: |
Save and Cancel shortcuts aren’t working for create Hierarchical Recursive pages |
||
36407208 |
3-36041383791 |
OIG-3720 |
Agent continues to invoke the exchanges when the archive folder is not writable |
Description: |
Agent continues to invoke exchange when it doesn’t have enough rights to write to archive folder. File remains in the 'inFolder' and exchanges are continuously invoked. When the folder is not writable, the agent should produce an appropriate error message and stop. |
||
36409950 |
3-34612052061 |
OIG-3723 |
JWT bearer grant type is not working |
Description: |
OHI supports both client_credentials and urn:ietf:params:oauth:grant-type:jwt-bearer (shortly referred as JWT bearer) grant types in OAuth, however JWT bearer grant type is not working as expected. |
||
36416510 |
3-34612052061 |
OIG-3736 |
OAuth parameters should be configurable |
Description: |
OHI product supports only standard OAuth parameters. As its value/name can deviate across OAuth server, OHI application isn’t able to establish connection with OAuth server. |
||
36519138 |
3-36337751321 |
OIG-3766 |
Agent is picking up files before file upload is complete. |
Description: |
Agent does not check if uploaded file is complete. This can cause errors in the OIG exchange because of incomplete uploaded file. For example, when an enrollment file is uploaded Agent picks it up before the file upload is complete. This can cause errors when uploading to policies. |
||
36604526 |
3-36421449471,3-36886229061 |
OIG-3819 |
Handling NPEs During Eclipse Transactions |
Description: |
Handling NPEs and adding logs during failure scenarios of proda token retrieval |
||
36626175 |
OIG-3825 |
Translations not working in few pages |
|
Description: |
Following pages/buttons are not translatable: Persons page Actions dropdown, MenuItem for BookMarks GroupClients page - Set Status to Change Dialog text |
||
36662845 |
3-36788604651 |
OIG-3830 |
Exchange stops processing when Fusion ERP Job status polling fails due to an Error response from Fusion |
Description: |
If Fusion ERP Job status polling fails due to an Error response from Fusion (eg - 502 Bad Gateway), exchange stays in Waiting on External System (W) status. No logs are added, exchange does not Fail and recovery is not possible from this scenario. |
||
36662882 |
3-36813495181 |
OIG-3833 |
Buffer too small for CLOB to CHAR conversion during subflow recovery |
Description: |
In the sub-exchanges during recovery , using a VARCHAR2 data type as a placeholder to parse the Exchange Properties JSON string of data type CLOB caused issues when the string length exceeded 32700 bytes. This is a code-related issue. |
||
36668902 |
3-36840886581 |
OIG-3838 |
Scheduled Exchanges are triggered multiple times |
Description: |
If multiple Integrations with schedule are updated at a time, then all future scheduled exchanges are rescheduled. In a multi-node setup, due to an issue with scheduling mechanism, it is executed on multiple nodes at the same time. As a result, multiple instances of exchanges would be triggered. |
||
36684728 |
3-36839446281 |
OIG-3842 |
OIG OOM issue due to accumulating of in-memory logs |
Description: |
The issue is due to the buildup in OIG heap memory caused by already opened financial transactions in policies that push notification messages. |
||
36690441 |
3-36929894621 |
OIG-3858 |
Boilerplate text is not displaying correctly in OIG sub exchange search table. |
Description: |
Boilerplate text is not displaying correctly in OIG sub exchange search table. |
||
36719869 |
OIG-3862 |
Files Deleted Date field missing in Exchange and Subexchange seeded floorplan |
|
Description: |
Files Deleted Date field missing in Exchange and Subexchange seeded floorplan |
||
36733265 |
3-37002072411 |
OIG-3867 |
Exchange incorrectly marked completed during recovery without file delivery to agent |
Description: |
When an exchange containing a 'deliverByAgent' step fails and is subsequently recovered after resolving the underlying issue, the exchange is incorrectly marked as completed without actually delivering the file via the Agent. This behavior is also observed in sub-exchanges. |
||
36809689 |
OIG-3903 |
Additional fields drawer: Client side error not shown for mandatory fields |
|
Description: |
If we have a mandatory field to be filled in Additional Fields drawer and the user is not notified with this |
||
36833563 |
OIG-3918 |
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 |
||
36909513 |
OIG-3922 |
Download Message checkbox appearing twice in Integration Steps page. |
|
Description: |
Download Message checkbox appearing twice in Integration Steps page. |
||
36870906 |
3-37313793651 |
OIG-3928 |
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 |
||
36870916 |
3-37313793651 |
OIG-3930 |
All the saved Parameters are not shown in View mode in Integrations page |
Description: |
Goto Integrations page, Create New Integration and Add Activity step, add more than 4 parameter values and save, on edit of parameters and save few parameters are missing. |
||
36908526 |
3-37567131801 |
OIG-3945 |
NoClassDefFoundError error is returned when creating a new dynamic logic with trace logging enabled for the logger ohi.dynamiclogic |
Description: |
A NoClassDefFoundError occurs when attempting to create a new dynamic logic with trace logging enabled for the ohi.dynamiclogic logger, instead of successfully creating the dynamic logic. |
||
36970162 |
3-37743857111 |
OIG-3967 |
Incorrect use of ohi.ws.client.readtimeout propperty to set the entire request/response timeout |
Description: |
The system property ohi.ws.client.readtimeout is intended to control the time (in milliseconds) that the client will wait for a response from the server after sending a request. However, it is currently being incorrectly applied to set the timeout for the entire request/response conversation, rather than just the response wait time. |
||
36972779 |
3-37582942001 |
OIG-3969 |
Large chronicle queue files of size 180GB were created by applicationDBAppender while capturing application log events |
Description: |
The applicationDBAppender that captures the application log events in DB generated a large chronicle queue files of size 180GB due to an exception that got re-queued in an end-less while loop |
||
36994044 |
OIG-3975 |
Action button missing on exchange pages |
|
Description: |
All Action Buttons were missing from exchanges pages |
||
37007918 |
OIG-3981 |
Failure on the postProcess step is marked incorrectly in previous exchange step |
|
Description: |
If the postProcess dynamic logic fails it should be marked in postProcess step itself. Its being marked in previous exchange step. |
||
37093031 |
3-37860226571 |
OIG-4058 |
NPE in Eclipse Integrations |
Description: |
NPEs are raised for some eclipse integrations when the token is not retrieved successfully |
||
37223310 |
OHISD-3966 |
OIG-4105 |
Invoke exchanges tiles are shown with only retrieve access to exchanges. |
Description: |
Invoke exchanges tiles are shown with only retrieve access to exchanges. |
||
37248628 |
OIG-4110 |
Error when attempting to upload files to OIG |
|
Description: |
User experiences 406 (Not Acceptable) Error when attempting to upload files to OIG |
||
37343570 |
OIG-4153 |
Combination of quick search and advanced search isn’t working |
|
Description: |
When user does a search with some criteria in quick search & then add another criteria in advanced search, the quick search criteria is ignored and only advanced search criteria is considered but the advance search criteria should be in concatenation with quick search |
||
37379336 |
3-38942079481 |
OIG-4160 |
Sequence of Exchange steps does not follow the sequence defined for Integration steps |
Description: |
The sequence of Exchange steps does not follow the sequence defined for Integration steps when Integration step IDs are out of order compared to the steps sequence. Eg: For two integration steps defined in following sequence - Step 1 with a higher step ID and Step 2 with a lower step ID, when exchange is invoked, Step 2 is executed first, followed by Step 1. |
||
37506977 |
OIG-4198 |
Exchange Invocation Headers should be treated as case sensitive |
|
Description: |
When an exchange is invoked with exchange specific headers like ohi-exchange-description but with uppercase letters like Ohi-Exchange-Description, it is ignored because it is not in lowercase. According to HTTP RFC standard, headers should be treated as case insensitive and so OIG should accept the headers irrespective of case. |
||
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. |
||
37583232 |
3-39142193471 |
OIG-4237 |
Query step fails when more than 40 fields are specified |
Description: |
During invocation of an exchange in OIG, the Query Step is returning a 500 error with the message 'Bad Request: Request header too large.' This issue occurs when attempting to execute the query for more than 40 fields. While providing the same number of fields in Postman, we are getting the correct output. However, it is not working with the Query Steps in OIG exchange steps. |
||
37607157 |
3-39759321701 |
OIG-4247 |
Deliverbyagent fails with npe when there is a raw payload created by previous step instead of a datafile |
Description: |
CheckAgentAvailability, DeliverByAgent, and ReceiveAgentNotification should be skipped when the previous step creates a raw payload instead of a datafile, as there are no files to deliver. |
||
37738039 |
3-40043354421 |
OIG-4284 |
Improve exception handling during storage of External Process response in exchange logs |
Description: |
If an exception is encountered during storing external process response in exchange logs, the process is retried to make sure the response is added to exchange logs. This can lead to stuck threads in which the process keeps retrying causing duplicate responses to be added to exchange logs. |
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. |
NXT-25662 |
3.22.2.0.0 |
The support to GET operations on Query API calls is deprecated. |