Release Notes for Oracle Insurance Gateway Release 3.21.2.0.0

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

Version compatibility: Oracle Insurance Gateway Release 3.21.2.x is only compatible with other Oracle Health Insurance applications release version 3.21.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	Description
NXT-21417	PHI Audit logs must be written in the same transaction as PHI / PII access occurs	PHI logs were initially written to a local buffer file before being persisted in the database. For compliance it is required to persist PHI audit logs in the same transaction as PHI access occurs. If system property 'ohi.logging.target' is set to value 'database', OHI applications persist PHI access in the database as part of the HTTP API or ADF UI request in which PHI data was accessed. If the value for system property 'ohi.logging.target' is set to 'log', which is also the default if no value is specified, then PHI access continues to be logged using any configured Logback Appender for which the PHI filter is applied.
OIG-1130	Delivery Step should be able to configure which integration step’s output, it should deliver	By default, a delivery step delivers the latest exchange step’s output. For most situations that is the desired behavior. This enhancement allows the user to configure the output of any of the prior steps in the process to be delivered by the delivery step.
OIG-1514	Download messages should take care of multiple messages links	It is possible for the notification to have multiple messages links. OIG currently only fetches one such link and download messages for that, it should be changed to download messages from multiple links with messages rel.
OIG-1550	JET UI Page: Configuration Migration Sets	JET UI page to create and maintain configuration migration sets is added to claims, policy, and OIG applications.
OIG-1877	Introduce exchange.transactionIdentifier attribute to search for previous exchanges	The index that supports searching Exchange properties was updated for every transaction. As that is a relatively resource-intensive system operation that behavior was changed.
OIG-1886	Introduce ability to validate XML against XSD	Functionality is required that allows XSD validation of payloads from dynamic logic, as part of exchange interactions.
OIG-699	Extracts are not treated as incremental if the parameters of the current invocation are not the same as previous exchange	If invocation parameter extractIncremental was set to true, which is the default value, then the system always generated an incremental Extract query, regardless of the parameters of the query part of the request.
OIG-753	Destination: certain attributes are not valid for types of destinations	Destination is an inheritance based structure, not all attributes are relevant for all types. With this enhancement, the cleanup of such destinations is implemented.
POL-7036	LOV enhancement : Search on all the fields by default, the gear (for field selection) is made optional.	In JET application, LOVs have a field selection feature, the search is then performed on the selected fields. This selection feature is made optional. By default search will be enabled on all the properties. To enable this feature property propertySelection must be set to true in the lov floorplans.
POL-7040	Ability to make search criteria for quick search and LOVs mandatory	With this enhancement, it is possible to make criterion mandatory for quick search in pages and LOV search. This can be achieved by setting criteriaMandatory property in quick search / referenced property configuration to true.
POL-7124	Theming Changes to JET application	Oracle Javascript Extension Tool Kit ( JET) support for Alta Theme is deprecated with newer Oracle JET versions. A new theme - Redwood is now introduced from Oracle JET version 9. This theme is designed for better usability and responsiveness in comparison to Alta. In addition, to make use of newer and better components and features introduced with newer JET versions, it is important for the OHI application to be continuously on the latest version of JET, and therefore OHI javascript-based applications are now migrated to a new theme. Key changes : Overall color scheme Search page template Forms - Field layouts Additional configuration requirement: For Oracle Health Insurance applications that feature a JET UI, the userâ€™s browser client needs to be able to access the Oracle Content Delivery Network (CDN). Oracle recommends referencing the bundles configuration script file on Oracle CDN because Oracle maintains the configuration for each release. Pointing the application to the current bundles configuration ensures that the application runs with the latest supported library and module versions. Oracle Health Insurance applications follow these recommendations. Make sure that the userâ€™s browser clients can access CDN URIs that start with https://static.oracle.com/cdn. If CDN is not accessible from the userâ€™s browser client, the JET UI will not work.
POL-7238	Ability to specify whether a floorplan applies for create mode or not	Before this release, all the floorplans that are configured are shown under the "add"/"create" options. The user can make use of tagging to select appropriate detail object plans but it is not possible to further filter out floorplans that should be shown under the "add" action. This enhancement makes it possible that the floor plan is available for view/edit, but not for action create.

Summary

Description

Included in Patch

NXT-21417

PHI Audit logs must be written in the same transaction as PHI / PII access occurs

PHI logs were initially written to a local buffer file before being persisted in the database. For compliance it is required to persist PHI audit logs in the same transaction as PHI access occurs. If system property 'ohi.logging.target' is set to value 'database', OHI applications persist PHI access in the database as part of the HTTP API or ADF UI request in which PHI data was accessed. If the value for system property 'ohi.logging.target' is set to 'log', which is also the default if no value is specified, then PHI access continues to be logged using any configured Logback Appender for which the PHI filter is applied.

OIG-1130

Delivery Step should be able to configure which integration step’s output, it should deliver

By default, a delivery step delivers the latest exchange step’s output. For most situations that is the desired behavior. This enhancement allows the user to configure the output of any of the prior steps in the process to be delivered by the delivery step.

OIG-1514

Download messages should take care of multiple messages links

It is possible for the notification to have multiple messages links. OIG currently only fetches one such link and download messages for that, it should be changed to download messages from multiple links with messages rel.

OIG-1550

JET UI Page: Configuration Migration Sets

JET UI page to create and maintain configuration migration sets is added to claims, policy, and OIG applications.

OIG-1877

Introduce exchange.transactionIdentifier attribute to search for previous exchanges

The index that supports searching Exchange properties was updated for every transaction. As that is a relatively resource-intensive system operation that behavior was changed.

OIG-1886

Introduce ability to validate XML against XSD

Functionality is required that allows XSD validation of payloads from dynamic logic, as part of exchange interactions.

OIG-699

Extracts are not treated as incremental if the parameters of the current invocation are not the same as previous exchange

If invocation parameter extractIncremental was set to true, which is the default value, then the system always generated an incremental Extract query, regardless of the parameters of the query part of the request.

OIG-753

Destination: certain attributes are not valid for types of destinations

Destination is an inheritance based structure, not all attributes are relevant for all types. With this enhancement, the cleanup of such destinations is implemented.

POL-7036

LOV enhancement : Search on all the fields by default, the gear (for field selection) is made optional.

In JET application, LOVs have a field selection feature, the search is then performed on the selected fields. This selection feature is made optional. By default search will be enabled on all the properties.

To enable this feature property propertySelection must be set to true in the lov floorplans.

POL-7040

Ability to make search criteria for quick search and LOVs mandatory

With this enhancement, it is possible to make criterion mandatory for quick search in pages and LOV search. This can be achieved by setting criteriaMandatory property in quick search / referenced property configuration to true.

POL-7124

Theming Changes to JET application

Oracle Javascript Extension Tool Kit ( JET) support for Alta Theme is deprecated with newer Oracle JET versions. A new theme - Redwood is now introduced from Oracle JET version 9. This theme is designed for better usability and responsiveness in comparison to Alta. In addition, to make use of newer and better components and features introduced with newer JET versions, it is important for the OHI application to be continuously on the latest version of JET, and therefore OHI javascript-based applications are now migrated to a new theme.

Key changes :

Overall color scheme
Search page template
Forms - Field layouts

Additional configuration requirement:

For Oracle Health Insurance applications that feature a JET UI, the userâ€™s browser client needs to be able to access the Oracle Content Delivery Network (CDN).

Oracle recommends referencing the bundles configuration script file on Oracle CDN because Oracle maintains the configuration for each release. Pointing the application to the current bundles configuration ensures that the application runs with the latest supported library and module versions.

Oracle Health Insurance applications follow these recommendations. Make sure that the userâ€™s browser clients can access CDN URIs that start with https://static.oracle.com/cdn. If CDN is not accessible from the userâ€™s browser client, the JET UI will not work.

POL-7238

Ability to specify whether a floorplan applies for create mode or not

Before this release, all the floorplans that are configured are shown under the "add"/"create" options. The user can make use of tagging to select appropriate detail object plans but it is not possible to further filter out floorplans that should be shown under the "add" action.

This enhancement makes it possible that the floor plan is available for view/edit, but not for action create.

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

Additional Upgrade Steps for Installation

The following phases are defined:

pre-upgrade: Application is still running
pre-undeploy: Application is stopped, but not undeployed.
post-undeploy: Application is undeployed. Database is backed up
post-upgrade: Released upgrade script has run.
post-deploy: New application is deployed and is up and running.

The OHI Logback Database Appender can no longer be configured for logType 'phi'. Remove any appender of class 'com.oracle.healthinsurance.loggingsupport.appender.impl.OhiAppender' for logType 'phi' from the Logback configuration. To continue persisting PHI access in the database, set system property 'ohi.logging.target' to value 'database'. Note that use of the appender of class 'com.oracle.healthinsurance.loggingsupport.appender.impl.OhiAppender' for logType 'application' or logType 'dylo' is unaffected.

Run the following SQL statement as ohi_oig_owner and commit any changes:

update log_phi_events set event_doc = json_mergepatch( json_mergepatch( nvl(event_doc, '{}'), json_object('sourceapp' value nvl(json_value(event_doc, '$.sourceapp' returning varchar2(30 char)), 'oig')) ), json_object('sourceappversion' value nvl(json_value(event_doc, '$.sourceappversion' returning varchar2(60 char)), 'pre-3.21.1.0.0')) ) where virtual_application is null or virtual_application_version is null;

Configuration Properties

Ref	Action	Subject	Description
NXT-21417	Added	ohi.logging.target	Defines the target for logging PHI access. Possible values are 'database', for logging to the database, or 'log' for logging PHI access to the Logback appender configured for it. Default value is 'log'.
OIG-1550	Added	ohi.jsui.cmt.payload.max.items.limit	Defines the maximum number of items that can be included in the payload. Property: ohi.jsui.cmt.payload.max.items.limit Default: 300
OIG-1861	Added	ohi.exchange.await.poll.factor
OIG-1861	Added	ohi.exchange.await.poll.divider
OIG-1861	Removed	ohi.exchange.await.poll.interval

Ref

Action

Subject

Description

NXT-21417

Added

ohi.logging.target

Defines the target for logging PHI access. Possible values are 'database', for logging to the database, or 'log' for logging PHI access to the Logback appender configured for it. Default value is 'log'.

OIG-1550

Added

ohi.jsui.cmt.payload.max.items.limit

Defines the maximum number of items that can be included in the payload.

Property: ohi.jsui.cmt.payload.max.items.limit Default: 300

OIG-1861

Added

ohi.exchange.await.poll.factor

OIG-1861

Added

ohi.exchange.await.poll.divider

OIG-1861

Removed

ohi.exchange.await.poll.interval

Web Services

Ref	Action	Subject	Description
NXT-21417	Modified	logphievents API	The following attributes are removed: eventDoc; eventTimestamp; eventLevel; eventThread; contextItemId; contextItemType
OIG-1130	Modified	Integrations resource	Added type config parameter inputIntegrationStep for an Integration Step of subtype DELIVERY. The value for the parameter must point to the code of a preceding Integration Step in the same Integration. The Delivery step delivers the output of the given Integration Step.
POL-7238	Modified	floorplans API	Added createEnabled attribute

Ref

Action

Subject

Description

NXT-21417

Modified

logphievents API

The following attributes are removed: eventDoc; eventTimestamp; eventLevel; eventThread; contextItemId; contextItemType

OIG-1130

Modified

Integrations resource

Added type config parameter inputIntegrationStep for an Integration Step of subtype DELIVERY. The value for the parameter must point to the code of a preceding Integration Step in the same Integration. The Delivery step delivers the output of the given Integration Step.

POL-7238

Modified

floorplans API

Added createEnabled attribute

Data Conversion

Ref	Action	Subject	Description
NXT-21417	Modified	Log PHI Events	Newly added attributes are derived from event_doc
POL-7238	Modified	Floor Plan	IND_CREATE_ENABLED is set to 'Y' for all floor plans with template set to 'HIERARCHICAL RECURSIVE'

Ref

Action

Subject

Description

NXT-21417

Modified

Log PHI Events

Newly added attributes are derived from event_doc

POL-7238

Modified

Floor Plan

IND_CREATE_ENABLED is set to 'Y' for all floor plans with template set to 'HIERARCHICAL RECURSIVE'

Dynamic Logic

This section intentionally left blank.

UI Changes

Ref	Action	Subject	Description
OIG-1130	Added	Integrations - Delivery Step	With this custom property, user can select any of the prior integration steps that has been added.
OIG-1550	Added	Configuration Migration Sets	Configuration Migration Sets page added
OIG-1868	Modified	Integration	Integration Page Floorplan "Errordestination" field reftype corrected
OIG-753	Modified	SFTP Destinations and Agent Destinations Page	Attribute addressKey removed from sftp and agent destinations page.
POL-7036	Modified	All JET pages having LOV’s	By default search on all properties for an lov
POL-7040	Modified	All JET pages having Quick Search and LOV’s	Added criteriaMandatory property in Quick Search and LOV component
POL-7238	Modified	Floorplan	Floorplans with createEnabled set to false are not shown as an option under "create" (top-level") or "add" detail level

Ref

Action

Subject

Description

OIG-1130

Added

Integrations - Delivery Step

With this custom property, user can select any of the prior integration steps that has been added.

OIG-1550

Added

Configuration Migration Sets

Configuration Migration Sets page added

OIG-1868

Modified

Integration

Integration Page Floorplan "Errordestination" field reftype corrected

OIG-753

Modified

SFTP Destinations and Agent Destinations Page

Attribute addressKey removed from sftp and agent destinations page.

POL-7036

Modified

All JET pages having LOV’s

By default search on all properties for an lov

POL-7040

Modified

All JET pages having Quick Search and LOV’s

Added criteriaMandatory property in Quick Search and LOV component

POL-7238

Modified

Floorplan

Floorplans with createEnabled set to false are not shown as an option under "create" (top-level") or "add" detail level

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

Ref	Action	Subject	Description
NXT-21417	Modified	log_phi_events	Column event_doc is removed
OIG-1877	Modified		The index that supports searching Exchange properties is no longer updated for every transaction. Instead it is updated every 15 minutes. That means Exchange properties cannot be used for near real-time searches for Exchanges.
OIG-699		Type Config attribute resourceName must be a constant	The root resource for the Extract operation must be specified as a constant value. Use of a parameter results in validation exception OIG-GATE-057.
POL-7124	Added	POL-7124	For Oracle Health Insurance applications that feature a JET UI, the userâ€™s browser client needs to be able to access the Oracle Content Delivery Network (CDN). Oracle recommends referencing the bundles configuration script file on Oracle CDN because Oracle maintains the configuration for each release. Pointing the application to the current bundles configuration ensures that the application runs with the latest supported library and module versions. Oracle Health Insurance applications follow these recommendations. Make sure that the userâ€™s browser clients can access CDN URIs that start with https://static.oracle.com/cdn. If CDN is not accessible from the userâ€™s browser client, the JET UI will not work.

Ref

Action

Subject

Description

NXT-21417

Modified

log_phi_events

Column event_doc is removed

OIG-1877

Modified

The index that supports searching Exchange properties is no longer updated for every transaction. Instead it is updated every 15 minutes. That means Exchange properties cannot be used for near real-time searches for Exchanges.

OIG-699

Type Config attribute resourceName must be a constant

The root resource for the Extract operation must be specified as a constant value. Use of a parameter results in validation exception OIG-GATE-057.

POL-7124

Added

POL-7124

For Oracle Health Insurance applications that feature a JET UI, the userâ€™s browser client needs to be able to access the Oracle Content Delivery Network (CDN).

Bug Fixes

BugDB	SR	Internal	Summary
32498946	3-25132551311	OIG-1712	An Exchange ends up in a failed state if Fusion applications return an unknown Fusion Job State
Description:	An unknown Fusion Job State resulted in a NullPointerException
Resolution:	If the system encounters a Fusion Job State it cannot resolve internally the Exchange fails with an IllegalStateException instead of with a NullPointerException later in the process
32519567	3-25136475409	OIG-1729	File Upload with multiple files through JET fails
Description:	When invoking an OIG exchange through the JET UI and selecting multiple csv files, the exchange fails. It seems the data file creation is not handling multiple input files correctly. As a result, the dynamic logic, expecting several files, is not able to read the files and fails. This feature is needed to do enrollment product upload where for each type of premium a csv file is created. All files need to be uploaded to OIG for a single exchange.
Resolution:	Now the user can successfully attach multiple files and upload them, the exchange will be successful. File names are being sent correctly, the dynamic logic especting multiple files can seperate the uploaded files by name now. While doing the enrollment product upload multiple csv files can be uploaded for a single instance in OIG.
32712231		OIG-1742	Function code FN0025 for access roles page is missing for access restrictions
Description:	Function code IG0009 was wrongly mapped to access roles page instead of FN0025 function code
Resolution:	Access roles page function code FN0025 is mapped correctly and IG0009 function code is removed through liquibase script
32542466		OIG-1764	Tab with Table component having auto fetch set to true is not displaying all the search results.
Description:	When a page have tab resource configured with table component and auto fetch of the results is set to true, it is not displaying all the rows of search results until user explicitly click on search icon.
Resolution:	All rows of search results are visible, When a page have tab resource configured with table component and auto fetch of the results is set to true.
32564689		OIG-1777	View sub exchanges page keeps loading when user navigate to it from sub exchange creator step.
Description:	When user try to navigate to sub exchanges page using subexchange creator step, page keeps on loading with busy state icon. View exchange page shall load properly while navigating back to sub exchange page.
Resolution:	Now view Sub Exchanges page loads properly when the user navigates to it from sub exchanges creator step.
32567171		OIG-1795	Configure ohi.resource.client.timer Resource Tag construction
Description:	For gathering metrics, it must be possible to control the resource tag for an "ohi.resource.client.timer" to point to the name of the resource (and not be more specific than that).
Resolution:	The new system property "ohi.instrumentation.resourceclienttimer.segment.prefixes" provides control in determining the resource tag value for an "ohi.resource.client.timer".
32574663		OIG-1797	Some logfilesetspecifications stay on specified status
Description:	If no log messages are applicable for the specified logfilesetspecification, the logfilesetspecification stays on S(pecified), and no error is present. Also specifications with status S are not cleaned. The required fields of logfilesetspecifications generic resource metadata show following not required fields: errorMessage, fileSetStatus and dataFileSet
Resolution:	Logfilesetspecifications are set to status processed when no events are present. These specifications are cleaned up as well. The metadata required fields only shows required fields
32581671		OIG-1806	Create-form link shall not be available for baseviews, baseviewgeneration and baseviewcolumn resources
Description:	Before this release, create-form link is visible for baseviews, baseviewgeneration and baseviewcolumn resources. Also baseviewerrors is not listed as a resource.
Resolution:	Create-form links for baseviews, baseviewgeneration and baseviewcolumn resources are removed. Baseviewerrors resource is now listed as a resource.
32615811	3-25325702161	OIG-1841	HICAPS Cancel response should populate DE48 zeroes (excl. DOS) on unmatched cancel
Description:	Whenever a cancel request does not yield a single candidate exchange with a claim to be canceled, line items in the response as contained by DE48 (data element 48, aka additional data private) are missing. This leads to problems in processing the response message through the network of systems all the way through to the printed receipt at the terminal.
Resolution:	With this release, whenever a single candidate is not found (i.e. unmatched cancel), the system will return one line item in DE48 with all zeroes (except DOS, date of service). This allows the network of system to properly deal with this cancellation response and the receipt to come out correctly.
32615804	3-25325702161	OIG-1842	HICAPS Cancel response should populate DE48 with appropriate line items
Description:	Whenever a cancel candidate can be found for a claim cancel request, line items in the response as contained by DE48 (data element 48, aka additional data private) are currently copied from the original claim transaction request. This leads to problems in processing the response in downstream systems, all the way down through the printed receipt at the terminal.
Resolution:	Instead of copying DE48 of the claim transaction request into the claim cancellation response, DE48 of the claim cancellation response is taken and copied to the claim cancellation response. Note that this could mean that on the actual receipt that is printed at the terminal for claim cancellations, the values returned on the charged amount line items potentially do not sum up to the charged amount specified on the 'header'. This situation is known and apparently is related to some restriction of the HICAPS system, with which OIG communicates.
32614650	3-25389473495	OIG-1868	"Errordestination" field reftype is wrongly configured in integration page floorplan.
Description:	Integration page is unable to fetch error destination field reftype values. So while creating an Integration, error destination cannot be saved.
Resolution:	Integration page floorplan is modified to fetch error destination field reftype values correctly. Now error destination is correctly saved while creating Integrations.
32646146		OIG-1878	Healthpoint Cancel response should populate DE48 with appropriate line items
Description:	Whenever a cancel candidate can be found for a claim cancel request, line items in the response as contained by DE48 (data element 48, aka additional data private) are currently copied from the original claim transaction request. This leads to problems in processing the response in downstream systems, all the way down through the printed receipt at the terminal.
Resolution:	With this release DE48 of the cancel response is copied from the DE48 field of the original claim transaction response.
32696829	3-25474233841	OIG-1908	Scheduled integrations are triggered twice when the server node is bounced
Description:	In a clustered OIG environment with at least two OIG nodes, is observed that when a non-senior node is bounced/stopped, integrations that run on a specific schedule are scheduled an additional time by the senior node. A senior node in this context refers to the OIG node that has been around the longest or has been designated as the 'leader' in a cluster.
Resolution:	With this fix, every time a 'Member Left Event' is detected by the senior node, that senior node first checks whether it is already known as the 'scheduler node' in the cluster. In case it is not, the system promotes the node to the 'scheduler node' and reschedules all integrations that need to run on a specific schedule.
32776399	3-25639270801	OIG-1927	Failing Fusion integration Exchange Steps mark the Exchange as failed and trigger a Workflow Event
Description:	If Fusion applications do not accept a job request or if a job fails then the Exchange should not only fail; a workflow event should also be triggered.
Resolution:	In case Fusion Fusion applications do not accept a job request or if the Fusion job fails then this fails the Exchange and also triggers a workflow event
32859106	3-25866611631	OIG-1974	Fusion Exchange ends in failed state if a Data File Set is not available for upload to UCM
Description:	A Fusion Integration that requires a Data File Set to be uploaded to UCM ends up in an endless loop if a Data File Set is not available
Resolution:	If a Data File Set is not available for upload to UCM then the Exchange fails with error OIG-GATE-061
31550459	3-23340260361	OIG-697	Application get hangup when "\\" is included in File Name Pattern field
Description:	In Agent Configuration page, if we add â€œ\\â€ in file name pattern field while creating/editing item, application hangs after getting 400 error in the API response
Resolution:	Application does not hang, when file name pattern field contains "\\" in it instead an error message is shown on the Agent configuration page.

BugDB

Internal

Summary

32498946

3-25132551311

OIG-1712

An Exchange ends up in a failed state if Fusion applications return an unknown Fusion Job State

Description:

An unknown Fusion Job State resulted in a NullPointerException

Resolution:

If the system encounters a Fusion Job State it cannot resolve internally the Exchange fails with an IllegalStateException instead of with a NullPointerException later in the process

32519567

3-25136475409

OIG-1729

File Upload with multiple files through JET fails

Description:

When invoking an OIG exchange through the JET UI and selecting multiple csv files, the exchange fails. It seems the data file creation is not handling multiple input files correctly. As a result, the dynamic logic, expecting several files, is not able to read the files and fails. This feature is needed to do enrollment product upload where for each type of premium a csv file is created. All files need to be uploaded to OIG for a single exchange.

Resolution:

Now the user can successfully attach multiple files and upload them, the exchange will be successful. File names are being sent correctly, the dynamic logic especting multiple files can seperate the uploaded files by name now. While doing the enrollment product upload multiple csv files can be uploaded for a single instance in OIG.

32712231

OIG-1742

Function code FN0025 for access roles page is missing for access restrictions

Description:

Function code IG0009 was wrongly mapped to access roles page instead of FN0025 function code

Resolution:

Access roles page function code FN0025 is mapped correctly and IG0009 function code is removed through liquibase script

32542466

OIG-1764

Tab with Table component having auto fetch set to true is not displaying all the search results.

Description:

When a page have tab resource configured with table component and auto fetch of the results is set to true, it is not displaying all the rows of search results until user explicitly click on search icon.

Resolution:

All rows of search results are visible, When a page have tab resource configured with table component and auto fetch of the results is set to true.

32564689

OIG-1777

View sub exchanges page keeps loading when user navigate to it from sub exchange creator step.

Description:

When user try to navigate to sub exchanges page using subexchange creator step, page keeps on loading with busy state icon. View exchange page shall load properly while navigating back to sub exchange page.

Resolution:

Now view Sub Exchanges page loads properly when the user navigates to it from sub exchanges creator step.

32567171

OIG-1795

Configure ohi.resource.client.timer Resource Tag construction

Description:

For gathering metrics, it must be possible to control the resource tag for an "ohi.resource.client.timer" to point to the name of the resource (and not be more specific than that).

Resolution:

The new system property "ohi.instrumentation.resourceclienttimer.segment.prefixes" provides control in determining the resource tag value for an "ohi.resource.client.timer".

32574663

OIG-1797

Some logfilesetspecifications stay on specified status

Description:

If no log messages are applicable for the specified logfilesetspecification, the logfilesetspecification stays on S(pecified), and no error is present. Also specifications with status S are not cleaned.

The required fields of logfilesetspecifications generic resource metadata show following not required fields: errorMessage, fileSetStatus and dataFileSet

Resolution:

Logfilesetspecifications are set to status processed when no events are present. These specifications are cleaned up as well.

The metadata required fields only shows required fields

32581671

OIG-1806

Create-form link shall not be available for baseviews, baseviewgeneration and baseviewcolumn resources

Description:

Before this release, create-form link is visible for baseviews, baseviewgeneration and baseviewcolumn resources. Also baseviewerrors is not listed as a resource.

Resolution:

Create-form links for baseviews, baseviewgeneration and baseviewcolumn resources are removed. Baseviewerrors resource is now listed as a resource.

32615811

3-25325702161

OIG-1841

HICAPS Cancel response should populate DE48 zeroes (excl. DOS) on unmatched cancel

Description:

Whenever a cancel request does not yield a single candidate exchange with a claim to be canceled, line items in the response as contained by DE48 (data element 48, aka additional data private) are missing. This leads to problems in processing the response message through the network of systems all the way through to the printed receipt at the terminal.

Resolution:

With this release, whenever a single candidate is not found (i.e. unmatched cancel), the system will return one line item in DE48 with all zeroes (except DOS, date of service). This allows the network of system to properly deal with this cancellation response and the receipt to come out correctly.

32615804

3-25325702161

OIG-1842

HICAPS Cancel response should populate DE48 with appropriate line items

Description:

Whenever a cancel candidate can be found for a claim cancel request, line items in the response as contained by DE48 (data element 48, aka additional data private) are currently copied from the original claim transaction request. This leads to problems in processing the response in downstream systems, all the way down through the printed receipt at the terminal.

Resolution:

Instead of copying DE48 of the claim transaction request into the claim cancellation response, DE48 of the claim cancellation response is taken and copied to the claim cancellation response. Note that this could mean that on the actual receipt that is printed at the terminal for claim cancellations, the values returned on the charged amount line items potentially do not sum up to the charged amount specified on the 'header'. This situation is known and apparently is related to some restriction of the HICAPS system, with which OIG communicates.

32614650

3-25389473495

OIG-1868

"Errordestination" field reftype is wrongly configured in integration page floorplan.

Description:

Integration page is unable to fetch error destination field reftype values. So while creating an Integration, error destination cannot be saved.

Resolution:

Integration page floorplan is modified to fetch error destination field reftype values correctly. Now error destination is correctly saved while creating Integrations.

32646146

OIG-1878

Healthpoint Cancel response should populate DE48 with appropriate line items

Description:

Resolution:

With this release DE48 of the cancel response is copied from the DE48 field of the original claim transaction response.

32696829

3-25474233841

OIG-1908

Scheduled integrations are triggered twice when the server node is bounced

Description:

In a clustered OIG environment with at least two OIG nodes, is observed that when a non-senior node is bounced/stopped, integrations that run on a specific schedule are scheduled an additional time by the senior node. A senior node in this context refers to the OIG node that has been around the longest or has been designated as the 'leader' in a cluster.

Resolution:

With this fix, every time a 'Member Left Event' is detected by the senior node, that senior node first checks whether it is already known as the 'scheduler node' in the cluster. In case it is not, the system promotes the node to the 'scheduler node' and reschedules all integrations that need to run on a specific schedule.

32776399

3-25639270801

OIG-1927

Failing Fusion integration Exchange Steps mark the Exchange as failed and trigger a Workflow Event

Description:

If Fusion applications do not accept a job request or if a job fails then the Exchange should not only fail; a workflow event should also be triggered.

Resolution:

In case Fusion Fusion applications do not accept a job request or if the Fusion job fails then this fails the Exchange and also triggers a workflow event

32859106

3-25866611631

OIG-1974

Fusion Exchange ends in failed state if a Data File Set is not available for upload to UCM

Description:

A Fusion Integration that requires a Data File Set to be uploaded to UCM ends up in an endless loop if a Data File Set is not available

Resolution:

If a Data File Set is not available for upload to UCM then the Exchange fails with error OIG-GATE-061

31550459

3-23340260361

OIG-697

Application get hangup when "\\" is included in File Name Pattern field

Description:

In Agent Configuration page, if we add â€œ\\â€ in file name pattern field while creating/editing item, application hangs after getting 400 error in the API response

Resolution:

Application does not hang, when file name pattern field contains "\\" in it instead an error message is shown on the Agent configuration page.

Issues that were backported in previous Release / Patch

BugDB	Internal	Summary	Backport	BugDB	SR
32615811	OIG-1841	HICAPS Cancel response should populate DE48 zeroes (excl. DOS) on unmatched cancel	3.21.1.0.1	32653996	3-25325702161
32615804	OIG-1842	HICAPS Cancel response should populate DE48 with appropriate line items	3.21.1.0.1	32654013	3-25325702161
32646146	OIG-1878	Healthpoint Cancel response should populate DE48 with appropriate line items	3.21.1.0.1	32654811	3-25396702411
32696829	OIG-1908	Scheduled integrations are triggered twice when the server node is bounced	3.21.1.0.2	32696856	3-25474233841
32776399	OIG-1927	Failing Fusion integration Exchange Steps mark the Exchange as failed and trigger a Workflow Event	3.21.1.0.3	32823839	3-25639270801
32859106	OIG-1974	Fusion Exchange ends in failed state if a Data File Set is not available for upload to UCM	3.21.1.0.3	32939403	3-25866611631
31550459	OIG-697	Application get hangup when "\\" is included in File Name Pattern field	3.21.1.0.1	31581071

Known Issues

BugDB	SR	Internal	Summary
31523984		OIG-1284	Search Exchanges: pagination is not working properly
Description:	Search Exchanges: pagination is not working properly. When filtered the search results based on certain conditions. When changed the search results count from the default(10 rows), it is displaying as the text area. After applying the filter conditions, pagination is not displayed.
32477952		OIG-1702	Base view generator does not support dynamic data in JSON format
Description:	OIG_AGENT_CONFIGURATIONS, OIG_DESTINATIONS and OIG_EXCHANGES store dynamic data in JSON format. The base view generation does not support that. So dynamic data for those tables is not exposed as separate fields in base views.
32560431		OIG-1785	Baseview generation sometimes might result in error: ORA-01461
Description:	Occasionally baseview generation results in error: ORA-01461. In the event that this happens, typically resubmitting the generation process resolves the problem.
32950841		OIG-1914	Add basic access grants needed for JET UI user login with setup access role.
Description:	Add basic access grants needed for JET UI user login with setup access role.
32987098		OIG-2050	Blank search on search list is not rendering the results in UI.
Description:	When user perform blank search on pages where search list template is used, search results are not getting rendered in UI.
32987139		OIG-2051	Sometimes JET UI pages with large number of fields might cause a bad request error due to a large request header.
Description:	Sometimes JET UI pages with large number of fields might cause a bad request error due to a large request header like - "Request Header Or Cookie Too Large" thereby not rendering the page. In such a case the floorplan might need to be modified to reduce the number of fields and thereby reducing the accept header size. There is an enhancement planned in 3.21.3.0.0 to reduce the accept header size.

BugDB

Internal

Summary

31523984

OIG-1284

Search Exchanges: pagination is not working properly

Description:

Search Exchanges: pagination is not working properly.

When filtered the search results based on certain conditions.
When changed the search results count from the default(10 rows), it is displaying as the text area.
After applying the filter conditions, pagination is not displayed.

32477952

OIG-1702

Base view generator does not support dynamic data in JSON format

Description:

OIG_AGENT_CONFIGURATIONS, OIG_DESTINATIONS and OIG_EXCHANGES store dynamic data in JSON format. The base view generation does not support that. So dynamic data for those tables is not exposed as separate fields in base views.

32560431

OIG-1785

Baseview generation sometimes might result in error: ORA-01461

Description:

Occasionally baseview generation results in error: ORA-01461. In the event that this happens, typically resubmitting the generation process resolves the problem.

32950841

OIG-1914

Add basic access grants needed for JET UI user login with setup access role.

Description:

Add basic access grants needed for JET UI user login with setup access role.

32987098

OIG-2050

Blank search on search list is not rendering the results in UI.

Description:

When user perform blank search on pages where search list template is used, search results are not getting rendered in UI.

32987139

OIG-2051

Sometimes JET UI pages with large number of fields might cause a bad request error due to a large request header.

Description:

Sometimes JET UI pages with large number of fields might cause a bad request error due to a large request header like - "Request Header Or Cookie Too Large" thereby not rendering the page. In such a case the floorplan might need to be modified to reduce the number of fields and thereby reducing the accept header size. There is an enhancement planned in 3.21.3.0.0 to reduce the accept header size.