Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.3

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

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

ID	Summary	Patch
POL-15555	Accept enriched enrollment requests This enhancement introduces the ability to access user-defined attributes included in the enrollment request payload, within the context of the enrollment response definition groovy function. By enabling the option to put in additional parameters and use them while building a response payload, the response can become more concise to the specific situation of the claim. Documentation Links: Developer Guide - Integration Points - Enrollment Status Response Integration Point Developer Guide - Dynamic Logic - References - Functions
POL-16770	Ability to configure function change event rule for additional entities This enhancement enables the use of function change event rules on the following entities: Address Relation Identifier Attached Policy Data Registration Documentation Links: Configuration Guide - Change Events - Change Event Rules Developer Guide - Dynamic Logic - References - Functions
POL-16791	Explanation of Premium Calculation Results This enhancement introduces a new field on the calculation result line, called "calculationContext". The purpose of this new field is to convey information that explains why the adjustment or premium line was selected. The value of this new context field is driven through configuration. Documentation Links: Administration Guide - Database - Data Masking Process Configuration Guide - Premium and Fees - References - Schedule Definitions Developer Guide - Integration Points - Quote Integration Point Developer Guide - Integration Points - Sample Process and Apply Registrations to Periods Developer Guide - Integration Points - Run Example Calculation for a Policy Developer Guide - Dynamic Logic - References - Conditions Developer Guide - Dynamic Logic - References - Functions Operations Guide - Premium Calculation - Activities - Calculate Premium Security Guide - User Access - Data Access Restriction
POL-17172	Policy Processing Errors With this enhancement, the policy page always displays the technical processing errors irrespective of the policy status
POL-17575	Reset a value using floorplan conditions With this enhancement, a new optional floorplan property `resetValue` is introduced, which can be used within the condition block to reset the value for a field. Documentation Links: Developer Guide - JET User Interface - References - Properties - Properties Developer Guide - JET User Interface - References - Components - Condition

POL-15555

Accept enriched enrollment requests

This enhancement introduces the ability to access user-defined attributes included in the enrollment request payload, within the context of the enrollment response definition groovy function. By enabling the option to put in additional parameters and use them while building a response payload, the response can become more concise to the specific situation of the claim.

Documentation Links:
Developer Guide - Integration Points - Enrollment Status Response Integration Point
Developer Guide - Dynamic Logic - References - Functions

POL-16770

Ability to configure function change event rule for additional entities

This enhancement enables the use of function change event rules on the following entities:

Address
Relation Identifier
Attached Policy Data
Registration

Documentation Links:
Configuration Guide - Change Events - Change Event Rules
Developer Guide - Dynamic Logic - References - Functions

POL-16791

Explanation of Premium Calculation Results

This enhancement introduces a new field on the calculation result line, called "calculationContext". The purpose of this new field is to convey information that explains why the adjustment or premium line was selected. The value of this new context field is driven through configuration.

Documentation Links:
Administration Guide - Database - Data Masking Process
Configuration Guide - Premium and Fees - References - Schedule Definitions
Developer Guide - Integration Points - Quote Integration Point
Developer Guide - Integration Points - Sample Process and Apply Registrations to Periods
Developer Guide - Integration Points - Run Example Calculation for a Policy
Developer Guide - Dynamic Logic - References - Conditions
Developer Guide - Dynamic Logic - References - Functions
Operations Guide - Premium Calculation - Activities - Calculate Premium
Security Guide - User Access - Data Access Restriction

POL-17172

Policy Processing Errors

With this enhancement, the policy page always displays the technical processing errors irrespective of the policy status

POL-17575

Reset a value using floorplan conditions

With this enhancement, a new optional floorplan property resetValue is introduced, which can be used within the condition block to reset the value for a field.

Documentation Links:
Developer Guide - JET User Interface - References - Properties - Properties
Developer Guide - JET User Interface - References - Components - Condition

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

Ref	Action	Description
POL-15555	Modified	Enrollment Status Response Integration Point Add additional (user configurable) parameters to the request
POL-16791	Modified	Sample process and apply registrations IP The calculationContext on the calculation result line is added to the response. EnrollmentType (code, displayname) is added to policyEnrollment.
POL-16791	Modified	Premium calculation The context that is derived for a premium schedule line or adjustment rule is stamped on the calculation result line
POL-16791	Modified	generic/calculationresultlines API Added attribute calculationContext (PII)
POL-16791	Modified	generic/scheduledimensions API Added indicator calculationContext
POL-16791	Modified	Quote IP The calculationContext on the calculation result line is added to the response. EnrollmentType (code, displayname) is added to policyEnrollment.
POL-16791	Modified	Example calculation IP The calculationContext on the calculation result line is added to the response. EnrollmentType (code, displayname) is added to policyEnrollment.

Ref

Action

Description

POL-15555

Modified

Enrollment Status Response Integration Point

Add additional (user configurable) parameters to the request

POL-16791

Modified

Sample process and apply registrations IP

The calculationContext on the calculation result line is added to the response. EnrollmentType (code, displayname) is added to policyEnrollment.

POL-16791

Modified

Premium calculation

The context that is derived for a premium schedule line or adjustment rule is stamped on the calculation result line

POL-16791

Modified

generic/calculationresultlines API

Added attribute calculationContext (PII)

POL-16791

Modified

generic/scheduledimensions API

Added indicator calculationContext

POL-16791

Modified

Quote IP

The calculationContext on the calculation result line is added to the response. EnrollmentType (code, displayname) is added to policyEnrollment.

POL-16791

Modified

Example calculation IP

The calculationContext on the calculation result line is added to the response. EnrollmentType (code, displayname) is added to policyEnrollment.

Data Conversion

Ref	Action	Description
POL-16791	Added	Schedule Dimension The new, mandatory, indicator calculationContext? is set to N for existing dimensions.

Ref

Action

Description

POL-16791

Added

Schedule Dimension

The new, mandatory, indicator calculationContext? is set to N for existing dimensions.

Dynamic Logic

Ref	Action	Description
POL-16791	Modified	Schedule Dimension Evaluation Condition Added the possibility to set the context/reason for the selected premium schedule line or adjustment rule. This only applies to premium schedule line evaluation and adjustment rule evaluation
POL-16791	Modified	Adjustment Function Added the possibility to set the calculationContext of the applied adjustment
POL-16791	Modified	Premium Function Added to possibility to set the calculationContext of the calculated premium

Ref

Action

Description

POL-16791

Modified

Schedule Dimension Evaluation Condition

Added the possibility to set the context/reason for the selected premium schedule line or adjustment rule. This only applies to premium schedule line evaluation and adjustment rule evaluation

POL-16791

Modified

Adjustment Function

Added the possibility to set the calculationContext of the applied adjustment

POL-16791

Modified

Premium Function

Added to possibility to set the calculationContext of the calculated premium

UI Changes

Ref	Action	Description
POL-16770	Modified	PO0032 (Change event rules) These entities are newly added for Subject field * Address * Relation Identifier * Attached Policy Data * Registration
POL-16791	Modified	Premium Schedules CalculationContext indicator is added
POL-16791	Modified	Schedule Definition CalculationContext indicator is added to schedule dimension.
POL-16791	Modified	Adjustment Rules CalculationContext indicator is added
POL-16791	Modified	Calculation Results CalculationContext is added to calculation result line
POL-17172	Modified	Policies Page With this enhancement, the policy page always displays the technical processing errors irrespective of the policy status and restart link is enabled for messages in 'TE' & 'CT' status

Ref

Action

Description

POL-16770

Modified

PO0032 (Change event rules)

These entities are newly added for Subject field * Address * Relation Identifier * Attached Policy Data * Registration

POL-16791

Modified

Premium Schedules

CalculationContext indicator is added

POL-16791

Modified

Schedule Definition

CalculationContext indicator is added to schedule dimension.

POL-16791

Modified

Adjustment Rules

CalculationContext indicator is added

POL-16791

Modified

Calculation Results

CalculationContext is added to calculation result line

POL-17172

Modified

Policies Page

With this enhancement, the policy page always displays the technical processing errors irrespective of the policy status and restart link is enabled for messages in 'TE' & 'CT' status

Breaking Changes

Ref	Action	Description
POL-17423	Modified	Bill Allocation and Group account available product tabs System floorplan for premiumbillallocations, groupaccountproducts is modified for filter condition on Group client billing account, insurableClass, Enrollment Product, Enrollment Product Category, Group account Available Product Add On. Custom floorplans if any need to be modified by referring to system floorplan accordingly.

Ref

Action

Description

POL-17423

Modified

Bill Allocation and Group account available product tabs

System floorplan for premiumbillallocations, groupaccountproducts is modified for filter condition on Group client billing account, insurableClass, Enrollment Product, Enrollment Product Category, Group account Available Product Add On. Custom floorplans if any need to be modified by referring to system floorplan accordingly.

Bug Fixes

BugDB	SR	Internal	Summary
37455515		POL-16441	'Policies per Fatal Messages' Widget record count is incorrect
Description:	The widget 'Policies per Fatal Messages' does not display the correct value for the record count.
Resolution:	The widget 'Policies per Fatal Messages' displays the correct value for the record count.
38309080		POL-17633	Add error handling for duplicate columns in base view generation
Description:	Throw a clear and descriptive error message when duplicate columns are detected in views during base view generation. Currently, if a table has duplicate columns in its view, the base view generation fails silently without any error message, causing confusion and making it difficult to identify the root cause.
Resolution:	Added a duplicate columns check in base view generation process and throwing descriptive error message to user.
38159306	3-41533253061	POL-17423	Group client Enrollment Products : LOV Search is not working
Description:	Unable to add Insurable class and Enrollment product value. Getting "GEN-PROC-002: Value "undefined" provided is not of type Number" error. Similar issue is observed in Group Account Add On in Group account available product.
Resolution:	It is possible to add Insurable class, Enrollment product value and Group Account Available Product Add On by using LOV dropdown
38250945		POL-17546	When executing data masking, ORA-00942: table or view does not exist.
Description:	When executing ohi_data_masking_pkg.mask_data_parallel, "ORA-00942: table or view does not exist" was raised. This was caused because of seed data that controls which tables or columns have to be truncated or nullified respectively contained references to non-existing tables.
Resolution:	Removed entries for non-existing tables in seed data for data masking.
38247391	3-41569045301	POL-17527	Data file extracts to object storage were recorded with a zero content length in the database.
Description:	When data files were stored in object storage, files generated by extracts were recorded in the database with a content length of 0. As a result, the X-Content-Length header for these files was also set to 0, causing file length verification to fail.
Resolution:	The content length is accurately recorded for data files stored in object storage. The X-Content-Length header correctly reflects the actual file size, ensuring successful file length verification.
38222192		POL-17502	Boilerplates are visible in Policy process flow page on page load
Description:	On initial load of policy process flow page, boilerplates are seen for "Set Default flow" button.
Resolution:	Proper labels are loaded for "Set Default flow" submit instead of boilerplates.
38299898	3-41496402011	POL-17616	Error when creating individual and organization providers using 'Save and Next' action in JET UI
Description:	Users is getting error when creating individual and organization providers using JET UI. This error occurs when you create a provider and click 'Save and Next' button and subsequently try to create a second provider. Error : Value "undefined" provided is not of type Number (post , flexcodesetdetails).
Resolution:	Fixed the issue preventing users from creating individual and organization providers using the 'Save and Next' action.
38058862		POL-17305	Call to invalidate L2 entity-cache became recursive when memory protector kicked-in
Description:	A recursive mechanism was implemented to invalidate the L2 entity cache upon detecting corruption, allowing the process to resume. However, under memory-constrained conditions, this recursive approach led to unbounded recursion, ultimately resulting in a StackOverflowError and further degrading the application’s memory state
Resolution:	The issue was resolved by introducing a conditional check to ensure that cache clearing and the associated recursive logic are executed only when the application’s memory state is healthy. This prevented unbounded recursion and stabilized memory usage.
38234366		POL-17520	Tracking/Tracing of requests should not be sent to external systems
Description:	Tracing headers (such as B3 headers) are being sent to external systems. This leads to a 500 error response. However, when the spanId header is removed, the request goes through successfully with a 201 response
Resolution:	B3 Tracing headers will be added when the host of the request and the application are identical.
38229231		POL-17511	Boilerplates are visible in Policy process flow page on page load
Description:	On initial load of policy process flow page, boilerplates are seen for "Set Default flow" dialog
Resolution:	Proper labels are loaded for "Set Default flow" dialog instead of boilerplates.
38084855		POL-17324	The automatic generation of SQL Monitor report for query API calls is not functioning as expected
Description:	Despite enabling enableSQLMonitorReport, SQL Monitor reports were not being generated automatically for query API calls. The issue was caused by case-sensitive header comparisons
Resolution:	The enableSQLMonitorReport header is now compared in a case-insensitive manner
37460477		POL-16445	adjustmentRule.scheduleDefinition returns Null in dynamic logic with adjustment rule signature
Description:	adjustmentRule.scheduleDefinition returns null when used within an adjustment rule evaluation condition in dynamic logic. This prevents access to schedule definition fields despite a valid schedule definition being associated.
Resolution:	The adjustmentRule/premiumScheduleLine passed for the condition evaluation and amount calculation of the Adjustment Rule/Premium Schedule Line is not the actual rule/line, but a schedule dimension where configurations like ageFrom and ageTo are accessible. To access the metadata in dynamic logic, scheduleDefinition has been added as a binding for AdjustmentRule logic and premiumSchedule for PremiumScheduleLine logic.
38287609		POL-17598	Trace file link in activity messages is not correct in UI
Description:	For failed global activities, activity message is displayed in UI but the trace file link provided has small case letters
Resolution:	Trace file link in error message is now properly substituted and displayed

BugDB

Internal

Summary

37455515

POL-16441

'Policies per Fatal Messages' Widget record count is incorrect

Description:

The widget 'Policies per Fatal Messages' does not display the correct value for the record count.

Resolution:

The widget 'Policies per Fatal Messages' displays the correct value for the record count.

38309080

POL-17633

Add error handling for duplicate columns in base view generation

Description:

Throw a clear and descriptive error message when duplicate columns are detected in views during base view generation. Currently, if a table has duplicate columns in its view, the base view generation fails silently without any error message, causing confusion and making it difficult to identify the root cause.

Resolution:

Added a duplicate columns check in base view generation process and throwing descriptive error message to user.

38159306

3-41533253061

POL-17423

Group client Enrollment Products : LOV Search is not working

Description:

Unable to add Insurable class and Enrollment product value. Getting "GEN-PROC-002: Value "undefined" provided is not of type Number" error. Similar issue is observed in Group Account Add On in Group account available product.

Resolution:

It is possible to add Insurable class, Enrollment product value and Group Account Available Product Add On by using LOV dropdown

38250945

POL-17546

When executing data masking, ORA-00942: table or view does not exist.

Description:

When executing ohi_data_masking_pkg.mask_data_parallel, "ORA-00942: table or view does not exist" was raised. This was caused because of seed data that controls which tables or columns have to be truncated or nullified respectively contained references to non-existing tables.

Resolution:

Removed entries for non-existing tables in seed data for data masking.

38247391

3-41569045301

POL-17527

Data file extracts to object storage were recorded with a zero content length in the database.

Description:

When data files were stored in object storage, files generated by extracts were recorded in the database with a content length of 0. As a result, the X-Content-Length header for these files was also set to 0, causing file length verification to fail.

Resolution:

The content length is accurately recorded for data files stored in object storage. The X-Content-Length header correctly reflects the actual file size, ensuring successful file length verification.

38222192

POL-17502

Boilerplates are visible in Policy process flow page on page load

Description:

On initial load of policy process flow page, boilerplates are seen for "Set Default flow" button.

Resolution:

Proper labels are loaded for "Set Default flow" submit instead of boilerplates.

38299898

3-41496402011

POL-17616

Error when creating individual and organization providers using 'Save and Next' action in JET UI

Description:

Users is getting error when creating individual and organization providers using JET UI. This error occurs when you create a provider and click 'Save and Next' button and subsequently try to create a second provider. Error : Value "undefined" provided is not of type Number (post , flexcodesetdetails).

Resolution:

Fixed the issue preventing users from creating individual and organization providers using the 'Save and Next' action.

38058862

POL-17305

Call to invalidate L2 entity-cache became recursive when memory protector kicked-in

Description:

A recursive mechanism was implemented to invalidate the L2 entity cache upon detecting corruption, allowing the process to resume. However, under memory-constrained conditions, this recursive approach led to unbounded recursion, ultimately resulting in a StackOverflowError and further degrading the application’s memory state

Resolution:

The issue was resolved by introducing a conditional check to ensure that cache clearing and the associated recursive logic are executed only when the application’s memory state is healthy. This prevented unbounded recursion and stabilized memory usage.

38234366

POL-17520

Tracking/Tracing of requests should not be sent to external systems

Description:

Tracing headers (such as B3 headers) are being sent to external systems. This leads to a 500 error response. However, when the spanId header is removed, the request goes through successfully with a 201 response

Resolution:

B3 Tracing headers will be added when the host of the request and the application are identical.

38229231

POL-17511

Boilerplates are visible in Policy process flow page on page load

Description:

On initial load of policy process flow page, boilerplates are seen for "Set Default flow" dialog

Resolution:

Proper labels are loaded for "Set Default flow" dialog instead of boilerplates.

38084855

POL-17324

The automatic generation of SQL Monitor report for query API calls is not functioning as expected

Description:

Despite enabling enableSQLMonitorReport, SQL Monitor reports were not being generated automatically for query API calls. The issue was caused by case-sensitive header comparisons

Resolution:

The enableSQLMonitorReport header is now compared in a case-insensitive manner

37460477

POL-16445

adjustmentRule.scheduleDefinition returns Null in dynamic logic with adjustment rule signature

Description:

adjustmentRule.scheduleDefinition returns null when used within an adjustment rule evaluation condition in dynamic logic. This prevents access to schedule definition fields despite a valid schedule definition being associated.

Resolution:

The adjustmentRule/premiumScheduleLine passed for the condition evaluation and amount calculation of the Adjustment Rule/Premium Schedule Line is not the actual rule/line, but a schedule dimension where configurations like ageFrom and ageTo are accessible. To access the metadata in dynamic logic, scheduleDefinition has been added as a binding for AdjustmentRule logic and premiumSchedule for PremiumScheduleLine logic.

38287609

POL-17598

Trace file link in activity messages is not correct in UI

Description:

For failed global activities, activity message is displayed in UI but the trace file link provided has small case letters

Resolution:

Trace file link in error message is now properly substituted and displayed

Issues that were backported in previous Release / Patch

No backports.