Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.1.0.4

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

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

Extracts: Decouple bucket size from fetch size

When an extract is executed, the application creates a global activity. The global activity spawns multiple child activities. Each child activity fetches a specific number of entities and stores them in a data file. The ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS system property determines the number of entities fetched per child activity or the fetch size.

All the fetched entities per child activity, are stored in the same data file. Therefore, the higher the value of the system property, the higher the number of entities gathered in a single data file. This could cause memory issues when a large number of entities and subresources (from a single data file) are fetched into the memory at the same time.

This enhancement introduces properties to separate the fetch size from the data file size. Decoupling both values enables each child activity to fetch the entities in smaller chunks. Within a child activity, each chunk is processed sequentially but multiple child activities are processed in parallel. This reduces memory usage.

  • The ohi.extract.datafilesize property configures the number of entities to store in a single data file and has a default value of 500.

  • The ohi.processing.chunksize.SELECT_EXTRACT_ITEMS` property determines the size of a chunk and has a default value of 100. The value of this property represents the number of entities fetched at the same time in a single chunk. Setting a higher value for this property (for example, 500) decreases the duration of the extract as the number of entities fetched each time increases.

  • The ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS is no longer required and hence can be removed from the configuration.

The change of property values is only recommended if the application is facing issues performing at optimal levels.

Documentation Links:
Installation Guide - Application Properties

3.22.2.0.25, 4.23.2.0.1

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

Added

ohi.processing.chunksize.SELECT_EXTRACT_ITEMS

This property controls how many items the system exports in one chunk. Once a single chunk is extracted, the memory gets cleared and the system will continu with the next chunk. The default value for this property is 100. If the value of ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS is currently set to a lower value than 100, we recommend to use that value for this property as well.

POL-12778

Added

ohi.processing.chunksize.SELECT_EXTRACT_ITEMS.{0}

This property controls how many items the system exports in one chunk per entity. Once a single chunk is extracted, the memory gets cleared. The placeholder should be replaced with the entity name, to be similar as the resourceName attribute in the Extract definition.

POL-12778

Added

ohi.extract.datafilesize

This property controls how many entities are gathered in a single Data File. Therefore, this property has a similar function to the removed ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS property. The default value of this property is 500. We suggest a value between 1 and 1000, depending on the desired number of datafiles to be generated.

POL-12778

Added

ohi.extract.datafilesize.{0}

This property controls how many items are gathered in a single Data File of a specific entity.

POL-12778

Removed

ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS

This property was formerly used to determine the number of entities fetched within a single child activity and therefore also determines the number of entities to be created in a data file. Now that those sizes as decoupled, this property does not serve any function anymore. Therefore, this property can be removed from the configuration (e.g. properties file)

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

36317141

POL-14629

Generate baseviews fails intermittently with CacheCreationException

Description:

Generate baseviews fails intermittently with CacheCreationException: Name of the cache entityNamePropertyCache already exists.

Resolution:

Generation of base views works fine without any intermittent exceptions.

36151848

3-32973122991

POL-14239

All future dated mutations should be deleted when calculate premium activity is executed

Description:

Future dated mutations are not deleted when calculate premium activity is executed but are expected to be deleted.

Resolution:

All future dated mutations are deleted when calculate premium activity is executed.

36370881

3-35475079541

POL-14740

Enrollment Changes are not separated per person in Enrollment Events

Description:

During Policy Version Change functionality, the creation of policy Enrollment Events turns out to be different when a new policy is created versus when an existing one is updated. In the first case, a single event is created for all Enrollments instead of one Enrollment Event per person. This can be reproduced by creating a policy (with the compare versions process step) and then including two different enrollments with two different persons. This should result in two different events per person so the customer can identify which enrollment got changed/added. Instead, it only creates a general enrollment event, including both enrollments.

Resolution:

When a new policy (version1) is created, and the compare policy version functionality is enabled, enrollment changes are separated per person in Enrollment Events.

36314059

3-35742239861

POL-14616

End policy action in view and edit policy page ends inactive time valid records

Description:

Select an active policy which has at least one or more policy enrollment products in the past. Using End policy action, end the policy with end date as current date. Inactive time valid records are ended as well

Resolution:

Only active time valid records (enrollment products) will be ended when a Policy is ended and inactive records are not modified with policy end date

36371684

3-35948698481

POL-14757

Response time of adding a dynamic record on attached policy data using collection patch is high

Description:

If attached policy data has large number of dynamic records (for example, 1000), then adding a new dynamic record (for a different dynamic field usage) using collection patch (of 200 records) operation takes more time.

Resolution:

Reduced the number of iterations to validate the dynamic records

36355950

POL-14719

Changes are not saved for the code and description of an existing CMT Set in Jet UI

Description:

When changing the code and description of an existing CMT Set in JET UI the message 'Changes are saved successfully' appears but the changes are not stored.

Resolution:

Code, Description can be updated for an existing CMT Set and changes are saved successfully

36433108

3-36176430291

POL-14882

Dynamic records ID should be returned as string in the API response

Description:

The ID of dynamic records of resources are returned as number (Long) in the API response, they should be returned as String.

Resolution:

The Dynamic records ID was transformed from Long to String in the API response

35912742

POL-13835

Run example calculation not working if billing cycle is selected

Description:

When running the example calculations in policy administration, unexpectedly selecting the billing cycle options and then clearing the billing cycle options off doesn’t generate the proper calculation. Need to log out of the application and then login back once more, to generate the example calculations once again correctly.

Resolution:

Run example calculation works fine if billing cycle is selected or not selected and gives proper result accordingly

36463022

POL-14942

Flexcodes API returns value of ID as number instead of String

Description:

Flexcodes API returns the value of id as a number instead of String but the definition defined the type of ID as string

Resolution:

The Flexcodes API now returns value of Id, created by and last updated by as Strings as defined in the definition

36085144

3-31029430181

POL-14069

Policy search by Policy Holder name is case sensitive

Description:

When searching for a policy using POLICYHOLDER NAME with the name captured all in lowercase then no results are returned

Resolution:

Policy search with POLICYHOLDER NAME with the name captured all in lowercase letters works fine

36355823

3-35475079541

POL-14716

Adding Bank Accounts as configurable entity for Business Event Rules

Description:

Bank Accounts are added as configurable entity for Business Event Rules and are therefore part of the Compare Policy Version functionality.

Resolution:

Bank Accounts are now part of the Compare Policy Version functionality.

36414254

3-35684326321

POL-14837

Gathering statistics on technical table for every extract activity is inefficient

Description:

Gathering statistics on technical table for every extract activity is inefficient as it was enabled by default for all cases and because of parallel extracts performance was degraded.

Resolution:

A check is added which will ensure statistics are gathered only in certain cases. Hence, improving the efficiency of extract activity.

36225623

POL-14467

Policy billing account/policy Accounts object navigation link doesn’t open after we navigate from Enrollment event notification

Description:

Navigate to policies. Open any policy. Click on enrollment event notification object navigation link. Click on policy accounts /policy billing accounts. Page doesn’t load.

Resolution:

Navigation across multiple object navigation links in policies page can be done without any error

36264589

3-35378971011

POL-14533

Ensure that notification is sent only when the datafile creation for output generation activity is complete

Description:

Notification was sent when the output generation activity was complete but the datafile creation was done later in a different transaction. This led to a mismatch in the number of datafiles received in the datafile set at the time of notification.

Resolution:

Notification is only sent when the output generation activity and the datafile creation are complete. This is achieved by handling both processes in a single transaction.

Issues that were backported in previous Release / Patch

No backports.