Release Notes for Oracle Insurance Gateway Patch 3.20.3.0.4

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

Version compatibility: Oracle Insurance Gateway Release 3.20.3.x is only compatible with other Oracle Health Insurance applications release version 3.20.3.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	Included in Patch
OIG-1587	Workflow events will always contain an exception binding for the creation of workflow payload	Whenever a workflow payload needs to be created, an exception binding as part of the dynamic logic context, from now on will always be provided. This means that in dynamic logic there is no need any longer to check whether such a binding is present.

Summary

Description

Included in Patch

OIG-1587

Workflow events will always contain an exception binding for the creation of workflow payload

Whenever a workflow payload needs to be created, an exception binding as part of the dynamic logic context, from now on will always be provided. This means that in dynamic logic there is no need any longer to check whether such a binding is present.

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

This section intentionally left blank.

Web Services

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

Ref	Action	Subject	Description
OIG-1587	Modified		Dynamic logic that constructs payload for workflow, can assume that the 'exception' binding always holds a value.

Ref

Action

Subject

Description

OIG-1587

Modified

Dynamic logic that constructs payload for workflow, can assume that the 'exception' binding always holds a value.

UI Changes

This section intentionally left blank.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

Ref	Action	Subject	Description
OIG-1652		HTTP Headers	The following HTTP Header names: ohi.exchange.allowed.time.ms; ohi.exchange.execute.immediately; ohi.exchange.execute.blocking; ohi.exchange.description; ohi.integration.validation.allowed.time.seconds must be changed into respectively: ohi-exchange-allowed-time-ms; ohi-exchange-execute-immediately; ohi-exchange-execute-blocking; ohi-exchange-description; ohi-integration-validation-allowed-time-seconds

Ref

Action

Subject

Description

OIG-1652

HTTP Headers

The following HTTP Header names: ohi.exchange.allowed.time.ms; ohi.exchange.execute.immediately; ohi.exchange.execute.blocking; ohi.exchange.description; ohi.integration.validation.allowed.time.seconds must be changed into respectively: ohi-exchange-allowed-time-ms; ohi-exchange-execute-immediately; ohi-exchange-execute-blocking; ohi-exchange-description; ohi-integration-validation-allowed-time-seconds

Bug Fixes

BugDB	SR	Internal	BP	Summary
32241331	3-24514949761	OIG-1490	BP	Multiple issues in Config Migration when trying to import DataSets through API
Description:	The following issues with configuration migration import process via api (dataexchanges) occur 1. An exception is shown in the logfile when at the end of an import the temporary file needs to be deleted 2. When a createandexport request is posted only with code (and no description), this caused later import processes to fail.
Resolution:	The createandexport for dataexchange will use the code of the set as description when a description is not provided. The error message about deleting temporary is not present anymore
32251682		OIG-1580	BP	An error is coming when user tries to save the LOV value without selecting from the search results
Description:	An error is coming when user tries to save the LOV value without selecting from the search results. If the user doesn’t select any value, the value does not get saved.
Resolution:	If the user wants to select a value from an LOV, then they must enter the complete value of the LOV and press Enter key. This will pick the first value from the search results of LOV.
32363911	3-24886233961	OIG-1620	BP	Extracts do not work with subflows
Description:	Incremental extracts with subflows do not return any results as the previous exchanges are not correctly fetched.
Resolution:	Incremental extracts now work with subflows. The previous parent exchanges are correctly fetched.
32417954	3-25003397991	OIG-1653	BP	Replace dots ( . ) in headers with dashes ( - ) to follow networking conventions
Description:	HTTP Headers using dot-notation ran the risk of being removed from an HTTP request by components like gateways or loadbalancers.
Resolution:	Dots ( . ) in HTTP headers are replaced by dashes ( - ) to follow networking (infrastructure) conventions. This should prevent these HTTP Headers from being removed from requests by components like gateways or loadbalancers.
32421511		OIG-1655	BP	Member Identifier and line items missing on as2805 cancellation responses
Description:	The information of the private data field (field #48) of the claim cancellation response includes the member identifier but is missing the 'canceled amount' and item response code. This results in the receipt printed at the terminal to contain garbled data. It turns out that the original fix (listed as bug: 32257926, OIG-1585) is not complete.
Resolution:	The implementation is corrected to properly include the 'canceled amount' and item response code per line item present.
32421525		OIG-1657	BP	Member Identifier missing on as2805 claim responses when transaction/quote fails.
Description:	The information of the private data field (field #48) of the claim transaction/quote response includes the member identifier but is missing the approved amount and item response code. This results in the receipt printed at the terminal to contain garbled data. It turns out that the original fix (listed as bug: 32200189, OIG-1515) is not complete.
Resolution:	The implementation was corrected to properly include the approved amount and item response code per line item present.

BugDB

Internal

Summary

32241331

3-24514949761

OIG-1490

Multiple issues in Config Migration when trying to import DataSets through API

Description:

The following issues with configuration migration import process via api (dataexchanges) occur 1. An exception is shown in the logfile when at the end of an import the temporary file needs to be deleted 2. When a createandexport request is posted only with code (and no description), this caused later import processes to fail.

Resolution:

The createandexport for dataexchange will use the code of the set as description when a description is not provided. The error message about deleting temporary is not present anymore

32251682

OIG-1580

An error is coming when user tries to save the LOV value without selecting from the search results

Description:

An error is coming when user tries to save the LOV value without selecting from the search results. If the user doesn’t select any value, the value does not get saved.

Resolution:

If the user wants to select a value from an LOV, then they must enter the complete value of the LOV and press Enter key. This will pick the first value from the search results of LOV.

32363911

3-24886233961

OIG-1620

Extracts do not work with subflows

Description:

Incremental extracts with subflows do not return any results as the previous exchanges are not correctly fetched.

Resolution:

Incremental extracts now work with subflows. The previous parent exchanges are correctly fetched.

32417954

3-25003397991

OIG-1653

Replace dots ( . ) in headers with dashes ( - ) to follow networking conventions

Description:

HTTP Headers using dot-notation ran the risk of being removed from an HTTP request by components like gateways or loadbalancers.

Resolution:

Dots ( . ) in HTTP headers are replaced by dashes ( - ) to follow networking (infrastructure) conventions. This should prevent these HTTP Headers from being removed from requests by components like gateways or loadbalancers.

32421511

OIG-1655

Member Identifier and line items missing on as2805 cancellation responses

Description:

The information of the private data field (field #48) of the claim cancellation response includes the member identifier but is missing the 'canceled amount' and item response code. This results in the receipt printed at the terminal to contain garbled data. It turns out that the original fix (listed as bug: 32257926, OIG-1585) is not complete.

Resolution:

The implementation is corrected to properly include the 'canceled amount' and item response code per line item present.

32421525

OIG-1657

Member Identifier missing on as2805 claim responses when transaction/quote fails.

Description:

The information of the private data field (field #48) of the claim transaction/quote response includes the member identifier but is missing the approved amount and item response code. This results in the receipt printed at the terminal to contain garbled data. It turns out that the original fix (listed as bug: 32200189, OIG-1515) is not complete.

Resolution:

The implementation was corrected to properly include the approved amount and item response code per line item present.

Issues that were backported in previous Release / Patch

No backports.