Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.1
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.1.
Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.23.2.x is only compatible with other Oracle Health Insurance applications release version 4.23.2.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-28449 |
Additional functionality for UI Form component With this enhancement, the UI Form component now supports:
|
|||
POL-12778 |
Extracts: Decouple bucket size from fetch size When an extract is executed, the system creates a Global Activity. This activity spawns Child Activities that each fetch a certain amount of entities and stores them in a Data File. The number of fetched entities per child activity is determined by a system property, ohi.processing.bucketsize.SELECT_EXTRACT_ITEMS. All those fetched entities are stored in the same Data File. Therefore, the fetch size equals the Data File size. When all the entities are meant to be gathered in a single Data File the system property will be set to a high value, which can cause memory issues when the same number of entities and subresources is fetched in memory. With this enhancement, we decouple the fetch size from the data file size. To decouple both values, each child activity will fetch the entities in smaller chunks which are executed sequentially and therefore reducing the memory usage. The number of entities to be gathered in a single Data File can be configured with the ohi.extract.datafilesize property, which has a default of 500. The size of a chunk can be determined with the ohi.processing.chunksize.SELECT_EXTRACT_ITEMS property, which has a default of 100. The value of this property represents the number of entities fetched at the same time in a single chunk. A low value of this property (e.g. 1 to 10) will reduce concurrent memory usage, though it will increase the duration of the Extract as the number of entities fetched at a given time is low as well. |
|||
POL-13923 |
Policy and Policy Enrollment pages for Medicare Advantage This enhancement introduces additional Policy and Policy Enrollment pages that allow users to view and maintain Medicare Advantage-related policies.
|
|||
POL-14056 |
Policy Enrollment Product page for Medicare Advantage policies A new Policy Enrollment Product page is introduced providing users the ability to view and maintain policy enrollment product details for Medicare Advantage policies. |
|||
POL-14106 |
Allow adding and removing parameter values on an enrollment product at the same time in dynamic logic This enhancement enables customers to add and remove parameter values at the same time in (validation) dynamic logic . |
4.23.1.0.3 |
||
POL-14247 |
Transaction Reply Report page A new 'Transaction Reply Report' object navigation page is introduced for Policy page providing users the ability to manage Transaction Reply Reports for Medicare Advantage policies. |
|||
POL-14595 |
Additional logs for flexcodesystem code at the level of dynamic field setup cache and for translation records in the database Policy submission led to a Null Pointer Exception because flexcodesystem code was not found at the dynamic field setup cache or because of missing entries for translation records of the code in the database. |
4.23.1.0.3 |
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 ofohi_install.cfg.template
and name itohi_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:
-
Open a command window and browse to
<OHI_ROOT>/util/install
. -
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
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) |
UI Changes
Ref | Action | Description |
---|---|---|
NXT-28449 |
Modified |
Policy Enrollment page Form Table is made editable and sort is enabled in the form table for policy enrollment page with 'MEDICARE_ADVANTAGE' tag |
POL-13923 |
Modified |
Policies page An additional Policy page is added with 'MEDICARE_ADVANTAGE' tag |
POL-13923 |
Modified |
Policy Enrollments page An additional Policy Enrollment page is added with 'MEDICARE_ADVANTAGE' tag |
POL-14056 |
Modified |
Policy Enrollment Products An additional Policy Enrollment Product page is added with 'MEDICARE_ADVANTAGE' tag |
POL-14247 |
Added |
Policy page - Transaction Reply Report (PO0212) An object navigation link and the associated floorplan for 'Transaction Reply Reports' page is added. The link is displayed only when policy type is 'Medicare Advantage'. |
Bug Fixes
BugDB | SR | Internal | Summary |
---|---|---|---|
36317048 |
POL-14624 |
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. |
||
36295733 |
POL-14590 |
Business event is not getting generated due to incorrect parameter(entity name) |
|
Description: |
JET is sending incorrect value(employmentOfMember#policyEnrollment) to entity when creating a business event rule. As it is not matching the entity name in PolicyEnrollmentEvent, Business event is not getting generated. |
||
Resolution: |
Business event is getting generated properly and proper payload is sent from JET when creating a business event rule |
||
36295842 |
3-35477511858 |
POL-14593 |
System unable to offset refund when there is an unapplied amount greater than refund |
Description: |
System unable to offset refund when there is an unapplied amount greater than refund |
||
Resolution: |
Enhanced SQL query to check if there is a registration with status 'N' and earliest offset payment date will only be set when there is no registration with status 'N' otherwise it will be NULL, and mutation recalculation will be done only when earliest offset payment is not null |
||
36246688 |
POL-14511 |
Adjustment Rules - The amount field is not accepting negative value, also few columns are missing |
|
Description: |
In the amount field of Adjustment and Surcharge Rules page, negative values are not accepted. Also 'Amount Function' and 'Amount Not Prorated' is not displayed. |
||
Resolution: |
In the amount field of Adjustment and Surcharge Rules page, negative values are accepted. Also 'Amount Function' and 'Amount Not Prorated' is displayed. |
||
36204014 |
3-34786906091 |
POL-14386 |
Dynamic logic byte code is not loaded during server startup on non master nodes after invalidateall API is invoked |
Description: |
Dynamic logic byte code is expected to load at the startup of non-master nodes if the invalidateall API was invoked in master node but was not being observed. |
||
Resolution: |
Dynamic logic byte code is now loaded at the startup of non-master nodes if the invalidateall API was invoked in master node. |
||
36151881 |
POL-14241 |
Search on Datasetdefinitiondetails should return entity name in href link of Change Event Rules |
|
Description: |
When performing search on the entity datasetdefinitiondetails, in the response the href link of Change Event Rules should end with the entity name but was null |
||
Resolution: |
The resource endpoint was not matching with the entity name, hence getting null in the href. Updated the resource endpoint to match with the entity name Change Event Rules |
||
36151850 |
3-32973122991 |
POL-14240 |
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. |
||
36315697 |
POL-14619 |
Extract status is failure when the associated activity is in 'QD' status |
|
Description: |
The notification status is showing 'failure' when it’s associated activity status is in 'QD'. The actual status should be shown is 'InProcess'. |
||
Resolution: |
Extract status should be 'InProcess' when the associated activity is in 'QD' status |
||
36227529 |
3-35379874711 |
POL-14471 |
SQL execution plan to delete selected financial transactions for large group is inefficient |
Description: |
SQL execution plan to delete selected financial transactions (at the end of generate financial messages activity) for large group is inefficient |
||
Resolution: |
The SQL is optimized |
||
36151889 |
3-35320237389 |
POL-14242 |
Enrollment IP metadata is invalid |
Description: |
Metadata returned by GET /enrollments/metadata IP is invalid. |
||
Resolution: |
Updated Metadata - Removed data related to get enrollment, and also added schema of enrollment request for post request |
||
36153617 |
POL-14248 |
PROCESS_REGISTRATIONS activity takes more than an hour to create child activities |
|
Description: |
PROCESS_REGISTRATIONS activity takes more than an hour to create child activities when the volume of policy mutations is high. |
||
Resolution: |
PROCESS_REGISTRATIONS activity will now take less time than before to create child activities when the volume of policy mutations is high. |
||
36250604 |
POL-14513 |
Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release |
|
Description: |
Length of OHI_ID_ARRAY database type is still 14 after upgrading to 4.23.1 release |
||
Resolution: |
The length of OHI_ID_ARRAY database type is updated to 19 |
||
36150543 |
POL-14236 |
Individual providers - Unable to edit service address configured as deeplink in rendering address tab |
|
Description: |
It is not possible to edit resources which are configured as Deeplinks. For example in Individual providers, it is not possible to edit service address in rendering address tab. On click of edit button in service address drawer, its directly navigating back to individual providers page and not possible to edit/save |
||
Resolution: |
Edit works fine in Deeplink drawers now and also the values are saved properly on the resource configured as deeplink |
||
36275593 |
3-35379874711 |
POL-14569 |
Slowness in calculate premium when group client parameter is specified. |
Description: |
Inserting policy-level child activities was inefficient when the group client parameter is used, resulting in a longer execution time to calculate premiums. |
||
Resolution: |
The query inserting policy-level child activities is improved to address the slowness of calculate premium activities |
||
36211500 |
3-35379874711 |
POL-14419 |
Slowness in calculate premium when group client parameter is specified. |
Description: |
Inserting policy-level child activities was inefficient when the group client parameter is used, resulting in a longer execution time to calculate premiums. |
||
Resolution: |
The query inserting policy-level child activities is improved to address the slowness of calculate premium activities |
||
36154640 |
POL-14256 |
Dynamic logic timeout property is ignored when compiling dynamic logic at startup time |
|
Description: |
The dynamic logic timeout property (ohi.dynamiclogic.timeout or ohi.dynamiclogic.timeout.{0}) is ignored when the dynamic logic is compiled at system startup time. |
||
Resolution: |
Load the system property from the database if the loading of system properties is not completed. If loading of system property is completed then load from cache. |