Release Notes for Oracle Insurance Gateway Patch 4.25.1.0.6

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

Version compatibility: Oracle Insurance Gateway Release 4.25.1.x is only compatible with other Oracle Health Insurance applications release version 4.25.1.x unless explicitly stated otherwise.
In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases.

Enhancements

ID Summary Patch

NXT-32017

UI: Additional Features Advanced Search

With this enhancement, the following multiple capabilities are added to the advanced search:

  • Ability to select query operators for different search criteria.

  • Ability to specify selected criteria as mandatory in advanced search.

  • Multiple adjustments to reference sheet lines, page searches, and sort, including the ability to search on nulls, the ability to sort on start and end dates, view last updated by, and time details.

4.26.1.0.0

NXT-32633

UI: Additional Features Sort

With this enhancement, the sort component is updated to display null values based on the sort order, that is, for Default and Criteria:

  • If the sort order is descending, nulls last is applied.

  • If the sort order is ascending, nulls first is applied.

It is now possible to specify sorting criteria for a multi-value property (list) configuration in a form and region.

4.26.1.0.0

POL-18132

UI: Conditional display of row-level actions: edit and delete for tabs.

This enhancement introduces the ability to control the display of actions (edit/delete) through initconditions.

4.25.1.0.4, 4.26.1.0.0

Additional Upgrade Steps

Pre-Upgrade Phase

1) OHI Agent upgrade

  1. Upgrade OHI Agent: Refer to Downloading and Running Oracle Health Insurance Agent for steps to perform the Agent upgrade.

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

  1. Perform any pre-upgrade steps.

  2. Stop all the managed nodes running the existing version of the application.

  3. Perform any pre-undeploy steps.

  4. Undeploy the existing version of the application.

  5. Back up the database.

  6. Perform any post-undeploy steps.

  7. Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.

  8. Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.

  9. Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.

  10. Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)

  11. 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 .

  12. Make the required changes to the ohi properties file

  13. Perform any post-upgrade steps

  14. Start WebLogic application server

  15. Deploy the Application

  16. Perform any post-deploy steps

Additional Upgrade Steps for Installation

The following phases are defined:

  1. pre-upgrade: Application is still running.

  2. pre-undeploy: Application is stopped, but not undeployed.

  3. post-undeploy: Application is undeployed. Database is backed up.

  4. post-upgrade: Released upgrade script run is complete.

  5. post-deploy: New application is deployed, and is up and running.

Post-Upgrade phase

  1. Execute the following SQL when upgrading from a version of 4.25.1.0.4 or lower to a version of 4.25.1.0.5 or higher:

    update ohi_reporting_views
    set excl_phi_logging =
        case
            when code in ('LOG_PHI_EVENTS_BV', 'PHI_LOG_PHI_EVENTS_BV', 'LOG_SECURITY_EVENTS_BV', 'PHI_LOG_SECURITY_EVENTS_BV')
            then 'Y'
            else 'N'
        end
    ;

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

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Access Restrictions

This section intentionally left blank.

Bug Fixes

BugDB SR Internal Summary

38876947

4-0001800026

OIG-4888

Exchange should continue processing if the datatransfer query doesn’t return any results.

Description:

When the query does not return any results(datatransfer location header gives a 204 response code), the data transfer exchange fails at the CheckDataTransferStatus step with the OIG-GATE-029 error. In the sub-exchange, the CheckDataTransferStatus fails with a NullPointerException under the same condition. In both cases, the exchange should continue processing and skip the CollectDataTransferData step.

Resolution:

Enhanced data transfer handling by skipping the CollectDataTransferData step when a 204 (No Content) response is received from CheckDataTransferStatus. This improvement applies to both the main flow and subflows.

38819818

4-0001674695

OIG-4862

Dynamic logic fails when an output writer is created but no data is written in data file stored in object storage

Description:

Dynamic logic fails when the output writer is instantiated even though there is no data to process and no write operation is performed on the data file stored in object storage

Resolution:

The system allows the output writer to be instantiated and closed without performing any actual write operation on data file stored in object storage.

38832618

4-0001730662

OIG-4866

HICAPS/healthpoint requests are not being processed by the agent

Description:

The OHI Agent is unable to log on to HICAPS/HealthPoint devices and is failing to process requests.

Resolution:

OHI Agent is now able to log on to HICAPS/HealthPoint devices and processing requests successfully.

38769154

4-0001366319

OIG-4833

Extract failures are now handled at the receivenotification step to ensure proper and efficient recovery flow

Description:

Recovering a failed extracts exchange doesn’t restart the collectData step making the recovery inefficient. To improve recovery handling, extract failures should be marked in the InvokeExtract step rather than in notificationCollectMessages step. On recovering the exchange after manual recovery of extracts, steps from InvokeExtract should be restarted.

Resolution:

For Extract use case, auto-recovery is always enabled. So code changes implemented in such a way when an Extract fails with Notification status marked as FAILED, the check recovery step fails all steps up to InvokeExtract. During manual recovery, the Extract recovery is initiated using the recovery link from InvokeExtract, ensuring proper restart of the recovery flow.

38474169

3-42065414021

OIG-4664

Exchange endpoint returns Unsupported Media Type for certain XML files.

Description:

Certain XML files are misidentified as HTML files because of a bug in Apache Tika, the third-party dependency used for file type validation. As HTML files are not allowed as an input to exchange endpoint, Unsupported Media Type exception is returned as response.

Resolution:

While the bug in Tika is being resolved by Apache, we are allowing HTML files in exchange endpoint as a temporary fix. We will disallow HTML files again once the bug fix is delivered by Apache.

Issues that were backported in previous Release / Patch

No backports.