Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.1.0.7

This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.1.0.7.

Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.23.1.x is only compatible with other Oracle Health Insurance applications release version 4.23.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

POL-15391

Additional rules to restrict updates on payment registrations

Australian premium calculation process depends on various settings on payments registrations, and some of these attributes can only be set by the calculation process. Currently there are no restrictions which prevents changes to these setting though API/IP. This posses a risk that apply registration process may not compute the date paid to correctly or may get completed with errors. This enhancement introduces new business rules on registration entity to prevent errors which can be caused by adjusting payment registrations though external interface.

4.24.1.0.0

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

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.

Bug Fixes

BugDB SR Internal Summary

37056493

POL-15840

Inbound & outbound exchange: Action items like build, message, download missing

Description:

In Inbound and Outbound exchange pages action buttons such as build, message, download are missing

Resolution:

Action buttons like build, message, download are visible on the Inbound and Outbound exchange pages

36853611

POL-15517

Select Financial Transaction into Set activity failing with GEN-PROC-ERR

Description:

When Financial Transaction into Set activity is ran with financailTransactionType 'PRE', activity is failing with technical error.

Resolution:

Extra spaces was introduced in dynamic sql query generation which fixed the issue allowing the activity to get successfully completed.

36896153

3-37166566681

POL-15618

Policies batch IP fails with optimistic lock failure on (GEN-RULE-020) group client

Description:

When a data file with a large number of policy payloads for the same group account (or group accounts attached to the same group client) and for existing policies (with changes on the policy group account), is processed by the Policy In Batch IP, it runs into an optimistic lock failure on group client: GEN-RULE-020: The entity GroupClientDomain Primary Key>xxx cannot be updated because it has changed or been deleted since it was last read.

Resolution:

When something on the group client set up is changed, the attributes objectLastUpdatedBy and objectLastUpdatedDate (like for instance if group accounts on the group clients are added/updated or removed) are updated. But in this case it also tried to update these attributes for updates on policy group accounts. This is removed as

a) it is not part of the setup data and

b) causes this optimistic lock as multiple processes are trying to update the same group client.

35675397

POL-13382

Table pages: Only the first 20 records are loaded in UI; no scrolling is possible after those 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.

Issues that were backported in previous Release / Patch

No backports.