Release Notes for Oracle Insurance Gateway Patch 3.20.3.0.3

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

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
OIG-1434	Dynamic Logic Framework should allow to use package statement in the logic	Currently the dynamic logic framework, assumes all scripts to be written in a default package ohi.dynamiclogic. This is done to apply the security restrictions and to allow for logging only in scripts defined in the aforementioned package. This causes problems with reusability, as every logic that requires to use the reusable code, needs to append ohi.dynamiclogic before importing it. This makes it difficult to manage and tests these groovy logic in isolation. On top of that, dynamic logic framework does not play well, if the package statement is explicitly included as ohi.dynamiclogic, as it appends another ohi.dynamiclogic in front of it. With this enhancement, it is possible to declare packages in the script and the framework will work with the package defined. It is however important, that the packages defined should start with ohi.dynamiclogic, otherwise security restrictions will be enforced.
OIG-1513	Introduce holding the integration processing after a delivery step	Several delivery steps trigger a process in another application, like FUSION_SUBMIT. It is sometimes desired for these processes/delivery steps to finish processing before moving forward with the integration steps. This enhancement allows for the 'waiting for notification' capability to resume the exchange after a delivery step. This functionality also brings the possibility to timeout the exchange, if the notification is not received after a stipulated time. Notifications are received at the notification endpoint. Support for download messages or download data is not included, as that is intended for OHI related jobs and is covered through Process and Activity Step
POL-6797	Dynamic Logic Framework should allow for reusable groovy classes to be created and used	With this enhancement, dynamic logic framework allows for coding reusable classes to be reused as structures in other groovy scripts. This enhancement also introduces a new signature name for coding such reusable classes/scripts. The name of the signature is REUSABLE CODE and does not have any specific bindings.

Summary

Description

Included in Patch

OIG-1434

Dynamic Logic Framework should allow to use package statement in the logic

Currently the dynamic logic framework, assumes all scripts to be written in a default package ohi.dynamiclogic. This is done to apply the security restrictions and to allow for logging only in scripts defined in the aforementioned package.

This causes problems with reusability, as every logic that requires to use the reusable code, needs to append ohi.dynamiclogic before importing it. This makes it difficult to manage and tests these groovy logic in isolation. On top of that, dynamic logic framework does not play well, if the package statement is explicitly included as ohi.dynamiclogic, as it appends another ohi.dynamiclogic in front of it.

With this enhancement, it is possible to declare packages in the script and the framework will work with the package defined. It is however important, that the packages defined should start with ohi.dynamiclogic, otherwise security restrictions will be enforced.

OIG-1513

Introduce holding the integration processing after a delivery step

Several delivery steps trigger a process in another application, like FUSION_SUBMIT. It is sometimes desired for these processes/delivery steps to finish processing before moving forward with the integration steps. This enhancement allows for the 'waiting for notification' capability to resume the exchange after a delivery step.

This functionality also brings the possibility to timeout the exchange, if the notification is not received after a stipulated time. Notifications are received at the notification endpoint. Support for download messages or download data is not included, as that is intended for OHI related jobs and is covered through Process and Activity Step

POL-6797

Dynamic Logic Framework should allow for reusable groovy classes to be created and used

With this enhancement, dynamic logic framework allows for coding reusable classes to be reused as structures in other groovy scripts. This enhancement also introduces a new signature name for coding such reusable classes/scripts. The name of the signature is REUSABLE CODE and does not have any specific bindings.

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.

ID	Upgrade Step	Phase
1	Remove duplicate boilerplate text records	pre-upgrade

Upgrade Step

Phase

Remove duplicate boilerplate text records

pre-upgrade

Remove duplicate boilerplate text records

Run the following SQL script as OIG owner:

delete
from   ohi_boilerplate_texts_b
where     (id = 22728570 and code = 'DOMAIN_INTEGRATIONSUBSTEP_SUBMITLOADJOB')
       or (id = 22728370 and code = 'DOMAIN_INTEGRATIONSUBSTEP_CHECKJOBSTATUS')
       or (id = 22728600 and code = 'DOMAIN_INTEGRATIONSUBSTEP_UPLOADTOUCM')
       or (id = 22728560 and code = 'DOMAIN_INTEGRATIONSUBSTEP_SUBMITIMPORTJOB')
       or (id = 22728530 and code = 'DOMAIN_INTEGRATIONSUBSTEP_PUBLISHDOCUMAKERDOCUMENT');
commit;

Configuration Properties

This section intentionally left blank.

Web Services

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

Ref	Action	Subject	Description
OIG-1513	Added	IG0003	The following attributes are added to deliver step indicatorExpectNotification typeConfig Display Type: Region Region Properties: timeAllowed

Ref

Action

Subject

Description

OIG-1513

Added

IG0003

The following attributes are added to deliver step

indicatorExpectNotification
typeConfig
    Display Type: Region
    Region Properties:
        timeAllowed

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB	SR	Internal	BP	Summary
32233319		OIG-1559	BP	Member identifier missing on AS2805_B Claim responses when transaction fails
Description:	For AS2805_B claim transaction interchanges that run into an unforeseen issue result in the member identifier not being present as part of the AS2805_B response message (field #48, additional data private). This manifests itself on the receipt printed at the terminal where the repeated elements (claim line) are wrongly offset on the print-out leading to meaningless data.
Resolution:	The Australian/AS2805 localization now exposes a dynamic logic setter property, with which the customer can inject the member identifier into the exchange properties as part of the incoming request message (for OHI Claims). This can and should be used in favor of a similar property on the (transformation) dynamic logic for the outgoing response message (for OIG Agent/AS2805_B front end processor), as that (transformation) dynamic logic will not be invoked whenever the system runs into an issue. In case this setter property is not used and an unforeseen issue arises, the system will fall-back to using '0000000000' as member identifier for the AS2805_B claim transaction response message.
32257926		OIG-1585		Member Identifier and line items missing on AS2805_A Cancellation Responses
Description:	Field #48 (additional data private field) on the AS2805_A response message of a cancellation, is expected to have a member identifier prepended, ahead of the repeating line elements that originate from the claim that is canceled. This was missing from that field, potentially resulting in 'shifting' of data fields on the terminal leading to garbled results.
Resolution:	We now make sure that for AS2805_A claim cancellation response message, we prepend a member identifier to start field #48 (additional data private), followed by the repeating line elements of the original claim that was canceled. Typically, this member identifier originates from the property collection of the exchange that was identified as being the candidate of the cancellation. In case no such candidate could be established, or the member identifier is not on the candidates properties collection a fallback value of '00000000' is used, to prepend #48 with.

BugDB

Internal

Summary

32233319

OIG-1559

Member identifier missing on AS2805_B Claim responses when transaction fails

Description:

For AS2805_B claim transaction interchanges that run into an unforeseen issue result in the member identifier not being present as part of the AS2805_B response message (field #48, additional data private). This manifests itself on the receipt printed at the terminal where the repeated elements (claim line) are wrongly offset on the print-out leading to meaningless data.

Resolution:

The Australian/AS2805 localization now exposes a dynamic logic setter property, with which the customer can inject the member identifier into the exchange properties as part of the incoming request message (for OHI Claims). This can and should be used in favor of a similar property on the (transformation) dynamic logic for the outgoing response message (for OIG Agent/AS2805_B front end processor), as that (transformation) dynamic logic will not be invoked whenever the system runs into an issue. In case this setter property is not used and an unforeseen issue arises, the system will fall-back to using '0000000000' as member identifier for the AS2805_B claim transaction response message.

32257926

OIG-1585

Member Identifier and line items missing on AS2805_A Cancellation Responses

Description:

Field #48 (additional data private field) on the AS2805_A response message of a cancellation, is expected to have a member identifier prepended, ahead of the repeating line elements that originate from the claim that is canceled. This was missing from that field, potentially resulting in 'shifting' of data fields on the terminal leading to garbled results.

Resolution:

We now make sure that for AS2805_A claim cancellation response message, we prepend a member identifier to start field #48 (additional data private), followed by the repeating line elements of the original claim that was canceled. Typically, this member identifier originates from the property collection of the exchange that was identified as being the candidate of the cancellation. In case no such candidate could be established, or the member identifier is not on the candidates properties collection a fallback value of '00000000' is used, to prepend #48 with.

Issues that were backported in previous Release / Patch

No backports.