Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.8

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

Version compatibility: Oracle Health Insurance Enterprise Policy Administration 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-32524

Table component improvements - Usability with editable row

Introduced check (Apply) icon as a table row-level action in edit mode. Clicking the check icon returns the row from edit mode to view mode. Actions in other rows will be disabled until the user clicks on the check icon of the current row being edited. Editable row remains in edit mode and persists the data when the user clicks outside the table or switches to another browser tab.

Documentation Links:
Developer Guide - JET User Interface - Floor Plan Templates - View and Edit Object - List
Developer Guide - JET User Interface - References - Components - Table

NXT-32617

UI: Ability to exclude trailing wildcard with like search

This enhancement allows excluding the automatic inclusion of the trailing wildcard for like search in quick search, advanced search, and lookups by setting the application property ohi.ui.likesearch.wildcard.enabled to false.

The system also auto-truncates the leading and trailing white space for searches.

Documentation Links:
Installation Guide - Application Properties

NXT-32621

UI: Additional Features Quick Search

With this enhancement, the quick search component is extended, and it will be possible:

  • To include all types of fields in the quick search.

  • To have query operators like between, less than, greater than, etc, configurable in quick search.

  • To set specific search criteria flagged as mandatory.

Documentation Links:
Developer Guide - JET User Interface - References - Components - Quick Search

NXT-32629

UI: Expandable "more" section in tables

With this enhancement, the overflow region for the table ("More" link) is now expandable to a two-column layout, allowing more information to be viewed at once.

Documentation Links:
Developer Guide - JET User Interface - References - Components - Table

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.

Pre-Upgrade phase

  1. Make sure to have enabled auto-purge for (connector) activities, because the Liquibase script 2025-09-10_INT_AGGREGATE_CHANGE_EVENTS.xml (introduced to fix the bug POL-12671) contains conversion of aggregate events based on activities. This script will take a while (depending on the data volume).

  2. Disable connector configurations that are not used (anymore).

Post-Upgrade phase

  1. Execute the following SQL:

    alter table ohi_policies_owner.int_aggregate_change_events drop unused columns;
alter table ohi_policies_owner.int_outbound_messages drop unused columns;

  2. Gather statistics for INT% tables before startup of the application:

    begin
  ohi_util_pkg.gather_table_stats(p_tabname => 'INT_AGGREGATE_CHANGE_EVENTS');
  ohi_util_pkg.gather_table_stats(p_tabname => 'INT_ASSIGNED_AGGR_EVENTS');
  ohi_util_pkg.gather_table_stats(p_tabname => 'INT_OUTBOUND_MESSAGES');
  ohi_util_pkg.gather_table_stats(p_tabname => 'INT_MESSAGE_PUBLISH_RESULTS');
end;

Configuration Properties

This section intentionally left blank.

Web Services

Ref Action Description

POL-17903

Modified

generic/aggregatechangeevents API

Attributes added:

  • reference to Activity

  • reference to Connector Configuration

  • unprocessed (to be able to check on aggregate events that are not picked up yet)

Data Conversion

Ref Action Description

POL-17903

Added

Aggregate events and details

For each connector configuration aggregate events and details are created.

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

38530119

POL-17903

Database queries to pick up events for connector configuration are slow

Description:

The connector configuration queries to pick up unprocessed events are slow, making it highly CPU-intensive and placing significant load on the database.

Resolution:

Optimized the connector configuration queries.

In addition the events are picked up as soon as the activity is created, not until it is submitted. This reduces the chance of sending duplicate aggregated events.

Note: The aggregated events now refer to a (enabled) connector configuration. This means that for each enabled configuration with the same aggregated type, an aggregated event is created. For example, if there are two connector configurations with the type POLI and a change event of the same type, two aggregated events are created. This also means, that, when a policy event does not point to an existing, enabled connector configuration, unnecessary aggregate events will not be created. Also: if a connector configuration is added with an aggregate type that matches an existing one (like POLI) after aggregate events are created: the aggregate events will not be picked up for that new connector configuration. Aggregate events are processed per connector configuration they refer to, not per aggerate type.

It is recommended to disable connector configurations that are not used (anymore): this will decrease the amount of unnecessary aggregate events created.

38553507

POL-17929

Person page: titles not getting removed

Description:

In person’s page combobox property - title is not getting cleared

Resolution:

Values are getting cleared in Person Titles combobox as expected

38439958

POL-17775

Table height is not getting auto adjusted when a new row is added/copied

Description:

The table height does not auto-adjust for rows containing combo box fields. Additionally, when rows are added or copied, the row height isn’t recalculated, causing values in combo box cells to appear clipped or partially hidden

Resolution:

Fix added to adjust the table height when adding or copying rows, including those containing combo box.

38617426

3-42702599701, 3-42695355031

POL-17986

The activity thread pool size does not revert to its original value of 8 after memory usage returns to normal

Description:

During periods of high memory usage, the system automatically reduces the number of activity threads it can handle to 1, to prevent further strain. However, after memory usage returns to normal, the system does not increase this capacity back to its usual level i.e. 8. As a result, the affected node can only process one activity at a time, which causes slow performance and delays.

Resolution:

Once memory usage returns to normal, the system automatically restores it the thread-pool capacity back to the usual level of 8 threads on the impacted node. This ensures that performance returns to normal and multiple tasks can be processed at the same time, preventing delays.

38642532

POL-18027

Resend/cancel enrollment event notifications IP shows enrollment event notification in response.

Description:

According to functional documentation, only OK should be returned as response and no payload.

Resolution:

Removed enrollment event notification payload from the following IP’s: * enrollmenteventnotifications/{id}/cancel * enrollmenteventnotifications/{id}/resend

Issues that were backported in previous Release / Patch

No backports.