Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.1.0.5

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

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

No enhancements.

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.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal BP Summary

34609163

POL-11383

BP

Reference Property defaults do not work with Display type never setting

Description:

Setting default on a mandatory field like Languages in Persons page with display 'never' setting doesn’t work and on saving the record an error is thrown that Language is mandatory for Person entity

Resolution:

Reference Property defaults work with display type never setting on fixed fields related to an entity.

34573224

POL-11311

BP

Pay date on policy calculation period may be incorrect if zero amount registrations are followed by a non-zero amount registration

Description:

Given multiple consecutive zero-premium policy calculation periods, when a zero-amount registration is sent for the first, then the pay date of all will be set to the pay date of the first zero-amount registration, as expected.

However, when there is also a non-zero amount registration after the zero-amount registration, then incorrectly, the non-zero amount registration’s pay date will be used as pay date for following policy calculation periods.

Resolution:

Pay dates of zero-premium policy calculation periods are set correctly, also if there are non-zero amount registrations after zero amount registrations.

34528277

3-30378990201

POL-11224

BP

Generate policy mutation activity runs slower if there are premium schedule level policy events

Description:

Same applies for events at level 'Adjustment/Surcharge Schedule Definition'.

Resolution:

Optimized queries to select policy events eligible for policy mutations.

34593385

POL-11341

BP

Cannot save the page when a single value type of record definition is configured

Description:

When a single value record definition is configured which further has some mandatory picklist or flex code fields, while creating and saving a policy, getting error for mandatory field even if value is selected

Resolution:

A single value record definition can be configured with a mandatory picklist or flex code field and it works fine

34507890

3-30225001091

POL-11177

BP

Premium tier calculation is not correct when there is change in policy enrollments

Description:

When there is a change in policy enrollments in mid/between of a contract period, the calculation results for the last calculation period is not correct

Resolution:

For contract period based calculation if policy enrollments changes in between the contract period, the reconciliation won’t happen for the last calculation period . Last calculation period result will be calculated similarly as any other normal calculation periods.

34557592

3-30412956601

POL-11284

BP

OIG throws Bad Request Error when an empty Data File Set is sent from the OHI Integration Connector

Description:

When the OHI Integration Connector sends out an empty Data File Set to an OIG configured endpoint, the system will throw a Client Side Error saying "The response received is Bad Request"

Resolution:

When an Data File Set is empty, the system will not send the Data File Set to the configured endpoint. The Message Published Result will be successful.

34592457

POL-11338

BP

When a parameter values are attached to a policy, after saving the policy, those values are not appearing

Description:

Steps to reproduce: Create a Policy and Save Under Enrollments Tab, add member details. Under Policy Enrollment Products Tab, add Enrollment products Further down, add Add on products and parameter values Save the Policy. Come back to Enrollments tab and try to expand products to see if all details are displayed and then further down click on add on details as well as parameter values tabs to check the details saved. Parameter values are not displaying, only the expansion icon is displayed, though the details appear when we expand the rows.

Resolution:

When a parameter values are attached to a policy and policy is saved, the values are displayed in the page along with the expansion icon in drill down view mode

34689359

POL-11464

BP

Adjustment Schedule is not displaying for the selected time period in Group Account Adjustment Overrides page

Description:

Create a group account product in such way that it should have valid adjustment with overrides data setup. Navigate to Group Accounts -→ Products -→ Adjustment Overrides and click on Time Period. Adjustment Schedule is not displaying for the selected time period

Resolution:

Adjustment Schedule is displayed for the selected time period in Group Account Adjustment Overrides page

34621871

POL-11401

BP

GroupClients are getting stuck in INPROCESS status

Description:

GroupClients are getting stuck in INPROCESS status when it gets hit by multiple threads.

Resolution:

GroupClients will now be approved and will no longer be in inprocess status when resource is hit by multiple threads.

34607918

POL-11378

BP

Default Value on a field that has flexcode is not working

Description:

The default value on flex code is not working when set on KeyValue/descriptor.

Resolution:

Default value on flex code is picked up and saved when specified as "name": "keyValue", "value": "N".The default value for flex codes can be set on the descriptor and keyValue only.

34632604

3-28742140171

POL-11409

BP

Descriptor not shown in the list of values after making changes in flex code field usages.

Description:

Descriptor not shown in the list of values after making changes in flex code field usages.

Resolution:

Descriptor is now shown in the list of values. If the values exist for a FlexCodeDefinition and if no FieldUsage is a descriptor, a non-descriptor FieldUsage is allowed to be marked as descriptor. But if values exist and there is FieldUsage marked as descriptor, then it cannot be unmarked as a descriptor.

34637767

POL-11414

BP

Unable to create numeric LOVs using custom floorplans

Description:

Users cannot set a picklist for Numeric fields on a dynamic record. Configuration of custom LOVs on numeric fields is not working

Resolution:

It is possible to create a picklist for numeric fields on a dynamic record in JET, provided users configure key field of flex code same as the numeric values. Also support on custom LOVs on 'Date' field is deprecated

34673883

POL-11439

BP

Conditional loading of tabs at create policy page is not working.

Description:

In Create Policy page, the Policy Holder List and Policy Group Account List tabs are not supposed to be shown when the code is null which is configured through conditional display of tabs in the floorplan, but these tabs are shown and also console errors are shown.

Resolution:

Conditional loading of tabs works in Create Policy page and no console errors are shown.

Issues that were backported in previous Release / Patch

No backports.