Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.5
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.22.2.0.5.
Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 3.22.2.x is only compatible with other Oracle Health Insurance applications release version 3.22.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 |
---|---|---|
OIG-2764 |
Reducing Application Clients Configuration This enhancement enables a user to re-use application clients, configured in the Authorization Server, across OHI REST clients. |
|
POL-12080 |
Source Process Identifier on Financial Transaction This enhancement introduces a source process identifier on financial transactions. This enables customers to untangle financial transactions that are produced simultaneously for the same policy but by different processes, so that separate financial messages can be generated per process. |
|
POL-12595 |
Optimize the premium schedule lines and adjustment rules selection in online operations This enhancement optimizes the premium schedule lines and adjustment rules selection in online operations like quote integration point and sample invoice etc. |
|
NXT-18517 |
Mask the Operational Data This enhancement introduces the capability to mask the operational data within the application. The purpose of this enhancement is to create a representative operational test data for non-production environments. The user can specify which fields containing personally identifiable information (PII) as well as how the information is transformed. This feature is now available for on-premises deployments. It will be made available for cloud deployments in a future release. Documentation Links: |
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
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
35161735 |
3-32375480671 |
POL-12406 |
BP |
Policy calculation periods get deleted when there is no end date on the enrollment product and the last default time period |
Description: |
When there is no end date on the enrollment product and last default time period, then apply registrations process does not work as expected as no policy calculation periods are present (anymore). This end date is used to determine the period up until periods should be generated. And if the end date is not specified, no policy calculation periods are generated. |
|||
Resolution: |
When the end date of the enrollment product and last default period is not specified, the date up until is now filled using the following logic: 1. Add a year to either the end date of the last policy calculation period + 1 day or the look back date: whichever comes first. 2. Or add a year to the start date of the last default time period. Pick the latest date of the two. This ensures that the policy calculation periods are generated if applicable. |
|||
35268239 |
POL-12582 |
BP |
DynamicRecordSetup non-entity cache holds redundant FieldDetails objects |
|
Description: |
Too many redundant FieldDetails objects (which are already part of FlexCodeSetup non-entity cache) are cached in DynamicRecordSetup non-entity cache. This is causing memory issues. |
|||
Resolution: |
The memory utilization of non-entity cache DynamicRecordSetup is optimized |
|||
35164538 |
3-31623926471 |
POL-12412 |
BP |
Bulkupdate of enrollmentproduct with policy account failed on copyAndEndDateEnrollment |
Description: |
Bulkupdate of enrollmentproduct failed on copyAndEndDateEnrollment when the updated product has policy account, i.e when autoCreateAccount is set to true. |
|||
Resolution: |
Policy account creation was not happening when the enrollment product had the autoCreateAccount flag set to true. The policy account creation was taken care of during the execution of the DYLO (copyAndEndDateEnrollment) |
|||
35272323 |
3-32219601211 |
POL-12585 |
BP |
Add diagnostic MBean to investigate EclipseLink deadlock issues |
Description: |
Add diagnostic MBean to find the root cause of EclipseLink deadlock issues |
|||
Resolution: |
Added diagnostic MBean to investigate EclipseLink deadlock issues |
|||
35262642 |
3-32390599641 |
POL-12574 |
BP |
AsOf() function throws NullPointerException when it is applied on an empty dynamic field |
Description: |
The asOf() function can be used with two parameters on an entity: date and a sub-entity name. If there is no sub-entity on the entity present, it will throw a NullPointerException. |
|||
Resolution: |
The asOf() function when used with two parameters and if there is no sub-entity on the entity it now returns null instead of throwing NullPointerException, as expected. |
|||
35228683 |
3-32547903561 |
POL-12531 |
BP |
Username not displayed on group client event correctly when group client is submitted for approval. |
Description: |
When using predefined method addGroupClientEvent: the display name of the user is set. But in case of submit of a group client, this display name was set to Internal System User. This is because an activity is started and within activity processing, the user is always system. |
|||
Resolution: |
When submitting a group client for approval, the user that started the operation will be picked by deriving it from the "createdBy" attribute of the activity created. |
|||
35153678 |
3-32317309991 |
POL-12382 |
BP |
Automatic activity fail over sometimes results in duplicate child activities |
Description: |
When a JVM processing activity is restarted, the activity failover happens and the other JVM in the system re-submits that activity. This creates duplicate child activities upon rolling restart. This leads to reprocessing the data file that was already successfully processed before the JVM is restarted |
|||
Resolution: |
The unique Identifier issue is fixed by POL-12381 |
|||
35299085 |
3-32247856831 |
POL-12661 |
BP |
The number of items in shared Eclipselink caches is maximized |
Description: |
The shared Eclipselink caches could grow unlimited, which resulted in memory shortage. To prevent that, the number of items in such a cache is now limited using the system properties ohi.persistence.cache.size.default and ohi.persistence.cache.{0}.size. |
|||
Resolution: |
The number of items in shared caches is now limited using the system properties ohi.persistence.cache.size.default and ohi.persistence.cache.{0}.size. |