Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.25.1.0.1

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

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-31617

Increase the length of scope attribute on OAuthClientCredentialsGrantConfiguration entity

The scope attribute in the OAuthClientCredentialsGrantConfiguration entity is currently limited to 100 characters which is insufficient to store scope values.

4.24.1.0.11

POL-17288

Support for Advanced payments

This enhancement introduces ability to support advanced payments. Advanced payments are calculation results produce using run and produce invoice much before the billing date. Premium calculation activity today reverses results which are beyond the due billing cycle. This behavior is made configurable by adding a new system property ohi.policies.calculate.future.calculationresult.reversal

POL-17301

Additional Dynamic Fields on Policies entity.

This enhancement increases the number of single-value non-time-valid dynamic fields that can be stored on the Policies entity.

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

Ref Action Description

POL-17288

Added

ohi.policies.calculate.future.calculationresult.reversal

When set to false, only future results after a mutation’s effective date are reversed if a mutation exists. When true, all future results are reversed regardless of mutations. Default is true.

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

Ref Action Description

POL-17342

Modified

Process Flow pages, Group Clients page, Group Account Products page

System floorplan for groupaccountproducts, groupclientbillingaccounts, grouprulesteps, policypendrulesteps, policyrulesteps is modified for filter condition on contactRelation, insurableClass, pendRule, calloutRule, validationRule. Custom floorplans if any need to be modified by referring to system floorplan accordingly.

Bug Fixes

BugDB SR Internal Summary

37400070

3-38989900081

POL-16397

Members page should show policy code instead of status

Description:

Members search page should show policy code. The color of the policy code should be based on the status.

Resolution:

Updated the members search page to display policy code and status, with status label color reflecting the policy status.

37689181

POL-16768

PCPs with forward billing are skipped for apply registrations

Description:

A change in Collection Setting can result in consecutive Policy Calculation Periods (based on the start- and end date of those Policy Calculation Periods) having different pay dates. In most cases the pay date of the latest Policy Calculation Period will also be later compared to the pay date of the earliest Policy Calculation Period. But, when the earliest Policy Calculation Period was not paid for in the first place, the pay date will be pushed according to the principle of forward billing. This could result in a scenario where the latest Policy Calculation Period (based on start date), has a pay date which is earlier compared to its predecessor. When a registration is processed, the system starts applying the registration to the Policy Calculation Period with the earliest pay date and skip the forward billed Policy Calculation Period.

Resolution:

When there are Policy Calculation Periods found without a corresponding Calculation Result, the system skips Process Registrations and adds the informative message POL-FL-PREG-004 to the activity. If there is no activity spawned, no informative message is added.

37914279

3-40216895161

POL-17119

Group Account Adjustments are not shown for a group account with no end date in time period

Description:

When a group account has a time period without end date, in Group Account Adjustment Overrides page, no rows are displayed for that time period. So the user cannot add overrides for the Group Account Adjustments

Resolution:

Group Account Adjustment Overrides are shown in UI for a group account which has a time period without end date

37257492

3-38637505211

POL-16214

Query API does not return correct results when the search criteria contains an apostrophe

Description:

Query API does not return correct results when the search criteria contains an apostrophe.

Resolution:

The grammar definition for parser is changed such that it’ll escape apostrophe in strings and sql package is changed such that it’ll treat apostrophe as a part of the string/name.

37908122

3-39664837951,3-39711991321

POL-17102

Plan Objects Not Cleaned Up When OutOfMemoryProtector Triggers During Calculate Premium Activity

Description:

Necessary configurations for Calculate Premium activity are fetched once and stored in plan objects within the distributed Coherence cache. When OutOfMemoryProtector triggers, activity remains stuck in IP status and plan cache does not get cleared, overtime this degrades JVM performance.

Resolution:

Clearing plan cache when system reaches CRITICAL state reduces GC overhead, improving JVM performance. It also allows stuck activities to reach final state.

37812730

POL-16956

Unsaved changes dialog is not displayed for tabs in expanded view mode

Description:

Unsaved changes pop up is not displayed when user updates any value in the tab in expanded view mode and tries to navigate away from the page

Resolution:

Unsaved changes dialog is displayed for tabs in expanded view mode and create mode as well

37914204

POL-17117

Prefilter criteria is retained when multiple custom floorplans are configured in Payment Registrations page

Description:

In Payment Registrations page, when multiple custom floor plans are configured with at least one floorplan with prefilter option, prefilter criteria is retained and not cleared while switching between the floorplans

Resolution:

Pre-filter criteria is cleared while switching between the floorplans

37888229

POL-17075

Generateaccountingmessage IP populates reversal as false for null reversal accounting details

Description:

Reversal has been made optional for POL-16484 since an option is added to not group accounting details on reversals, but the generate account message operation was not adjusted to reflect that the reversal indicator could be empty.

Resolution:

In case reversal is null, it is not displayed in payload (as all null values do) and accounting details will be grouped based on either reversal being true or false or null.

37906801

POL-17095

Run example calculation returning 500 status when member has a relation link

Description:

Run example calculation API returning 500 status when member has a relation link record.

Resolution:

The Run Example Calculation API now works as expected when the member has a relation link record.

37867881

3-40372816341

POL-17061

Conditional loading of value does not work in List Of Values dropdown once the value is selected

Description:

Filter is not applied correctly to the dependent List Of Values dropdown whenever a conditional trigger is used to update the filter.

Resolution:

The filter is applied consistently, displaying the correct value in the LOV.

37913485

POL-17115

Not able to retrieve parent context values in view mode of the page in a tab

Description:

For a use case when a user wants to filter out a field in the tab, based on the type of the claim, the following condition works correctly in create mode : "condition": "context.claim.type === 'R'". It does not work when the page is opened in view mode

Resolution:

For tab details pages conditional evaluation issue fixed for both create and edit mode

37913462

POL-17114

Labels for regular flex code fields are not working while configuring it in search page

Description:

Labels are not getting displayed in search page, it works fine in hierarchical recursive page

Resolution:

Labels for flex code fields are working as expected when configured in search page

37950439

POL-17169

User information is not available to use in floorplans using userJET property

Description:

The userJET property in the floorplan does not support setting default values or filtering data based on the current user.

Resolution:

Fields 'id' and 'displayName' of userJET property can be used in the floorplan for setting default values or filtering data based on the current user.

37914251

POL-17118

Attributes, Segments, More Section retain previous search result values in Accounting details page

Description:

In policy accounting details page, when a new search is done without closing Attributes, Segments and more section from previous search, these sections are not refreshed. It retains previous data.

Resolution:

Attributes, Segments, More Section don’t retain previous search result values in Accounting details

38015338

POL-17254

Performance degradation in activity processing due to the overhead caused by the heartbeat query

Description:

The cleanup_act_status activity monitoring heart-beat query, which performs a SELECT on the ACT_ACTIVITIES table to fetch records with status 'IP', is experiencing performance issues. The query is currently executing a full table scan as the status field is not indexed, resulting in increased execution time.

Resolution:

The query was optimized by using the VIRTUAL_UNPROCESSED_STATUS column, which is indexed and offers better performance.

38089610

POL-17328

Policy details page is not loading when user validates any policy which is in edit status, also auto refresh not working after validation

Description:

When user validates any policy which is in edit status, also auto refresh not working after validation and there is an error in console related to processStep being undefined

Resolution:

Policy page loads now after Validate Operation without error. Note: There is a known issue that loading icon sometimes doesn’t get closed automatically in expanded view mode

38014158

POL-17249

Incorrect cause shown in policy output history

Description:

Incorrect cause shown in policy output history. When the cause is Manual Output Generation, the system shows change event.

Resolution:

Policy output history now displays correct cause.

38010579

POL-17244

Property 'userJET' should expose userid, login name, display name, last login timestamp, defaultCountry information

Description:

Property 'userJET' is exposing only displayName and id fields and not rest of the information in UserInformation IP

Resolution:

Property 'userJET' gives access to user id, login name, display name, last login timestamp, defaultCountry information about the logged-in user

38033071

POL-17278

'Submit after update?' field is not displaying correctly on the macro screens

Description:

When executing a macro for a Group Client or Group Account, the 'Submit after update?' field in the "Parameters" tab is not getting reflected.

Resolution:

Fix added to display value for 'Submit After Update' field in parameter tab.

38094534

POL-17339

Policy process flow: Value is not shown in read only mode for policy rule step

Description:

Inside policy process flow record when user views any policy rule step ( validation rule / call out rule), it is shown blank

Resolution:

Value is now displayed for policy rule step in readonly mode also

38014579

POL-17251

Permissions error thrown on attached policy data

Description:

In policy details page, clicking the attached policy data throws error related to access missing for tab resource

Resolution:

There is no error thrown now in attached policy data page related to access

38105907

POL-17359

Group Account Activity - Boilerplate issue in Activity messages tab

Description:

Boilerplate value is not shown in Group Account Activity - Messages tab

Resolution:

Fixed added to show correct boilerplate value in Group Account Activity page

37947792

POL-17164

Bill Receiver is missing in More section for Premium Bill Allocation tab on Policies Page

Description:

Bill Receiver is missing in More section for Premium Bill Allocation tab on Policies Page

Resolution:

Bill Receiver has been added as a region in Billing allocations tab

38021438

3-38637505211

POL-17260

Unable to search policy/person for member having apostrophe in the name.

Description:

Users are unable to search for a person or policy when the member’s name contains an apostrophe. For example, if the person’s last name is D' Souza, the API throws an error instead of returning the expected result.

Resolution:

UI handles apostrophe in search input and returns expected results. When configuring filter, prefilter, prefilterList, widget query etc users must manually escape apostrophes in the value of the query expression by using another apostrophe.

38068144

POL-17312

Added custom content-Length header (X-Content-Length) to the data file response for validation during file downloads in OIG

Description:

Enhance the getFileContents API in DataFile to include a custom response header X-Content-Length, allowing the calling application to verify if the full content has been received.

If there’s a mismatch or if the response header is missing (incase of partial response) , the application can retry the API to retrieve the complete content

Resolution:

To address issues of incomplete or failed data file downloads in Oracle Insurance Gateway (OIG), content length validation has been implemented. This validation is triggered when OIG detects partial data by comparing the actual content length with the expected value provided in the custom response header "X-Content-Length". This header is now included in the POL data file response to enable accurate validation.

38030659

POL-17274

Download button is lost when there are no search results

Description:

Download button is lost when there are no search results in search table template

Resolution:

Fix added to show download button consistently when data is present

38018234

3-40799088818

POL-17258

Numeric search is not working in lookup dialog

Description:

Search on number field like pincode is not working in lookup dialog. It is not retrieving any results

Resolution:

Number field search works fine and returns expected results in lookup dialog

38095055

3-41205595461

POL-17342

Unable to add a new validation rule, pend rule, or callout in the policy process flow

Description:

Unable to add a new validation rule, pend rule, or callout in the policy process flow. Getting "GEN-PROC-002: Value "undefined" provided is not of type Number (post , policyvalidationrules)" error. Similar issue is observed in Billings account Contact Relation field, Insurable class in Group account product and Group pend rules in Group process flow

Resolution:

It is possible to add a new validation rule, pend rule, or callout in the policy process flow. Similarly in group process flow, contact relation LOV, insurable class LOV in Group Account Products page

38060673

POL-17308

Dynamic fields information not shown in policy Bill receivers

Description:

Dynamic fields information not shown in policy Bill receivers since it is moved to 'more' section under Policy Bill Allocations as form table

Resolution:

Changes are made in the system specific floorplan to show Policy Bill Allocations as tab instead of form table

Issues that were backported in previous Release / Patch

No backports.