Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.21.2.0.3
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.21.2.0.3.
Enhancements
ID | Summary | Description | Included in Patch |
---|---|---|---|
POL-8641 |
Additional Dynamic Fields on Registration |
Registration entity has been extended with additional Dynamic fields by increasing the horizontal storage from 5 to 20. |
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
Web Services
Ref | Action | Subject | Description |
---|---|---|---|
POL-8645 |
Modified |
personcoveredservices API |
Included x-oi-functional-key |
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
32945622 |
POL-8271 |
BP |
Business rule validation error occurs when updating dimension value using adjustmentrules API |
|
Description: |
The business rule violation error POL-ADJV-001 is returned from adjustmentrules API when doing a patch operation using a valid request that complies to the business rule. This happens, for example when changing the dimension value from from percentage to amount. |
|||
Resolution: |
The error POL-ADJV-001 is no longer returned for valid request and dimensions are updated as expected |
|||
33204871 |
POL-8598 |
BP |
BP - Incorrect column names shown in the advanced search field |
|
Description: |
While doing specific section for some of the pages the advance search shows different column names from that of the actual table columns for entities like premium tier, enrollment types, gender identities, address types, identifier types, collection methods, flexcode systems and product covered services |
|||
Resolution: |
Updated the confluence and removed unnecessary field. 3.For product covered services - Updated the code in advance search to render child resource label properly |
|||
33095867 |
POL-8602 |
BP |
Sometimes JET UI pages with large number of fields might cause a bad request error. |
|
Description: |
Sometimes JET UI pages with large number of fields might cause a bad request error due to a large request header like - "Request Header Or Cookie Too Large" thereby not rendering the page. In such a case the floorplan might need to be modified to reduce the number of fields and thereby reducing the accept header size. There is an enhancement planned in 3.21.3.0.0 to reduce the accept header size. |
|||
Resolution: |
Aliases have been applied to reference fields and child lists. In addition, all dynamic fields and child lists are expanded and not individually included in the fields parameter, thereby reducing the overall accept header length. |
|||
33105190 |
3-25346318151 |
POL-8627 |
BP |
Change event rules sometimes have the new values for the old entity |
Description: |
When, in combination with validation rules where changes on an entity are applied and a predefined method is used that flushes to the data base, the old entity attributes values were overwritten by the new entity values. This was causing the old entity as bind parameter for dynamic logic having wrong values. Steps to reproduce: 1. create a validation rule that changes something on the entity and call for instance the predefined method insurableEntity.getPolicies() (this method does a flush). 2. create another validation rule that changes (dynamic) attribute X on the entity 3. create a change event rule, update on attribute X with dynamic logic for effective date that compares the old and new value on attribute X: if different return a date value, if not, return null. Since effective date is mandatory it raises an IllegalArgumentException. This should not happen because attribute X has changed and the dynamic logic should return the date value. |
|||
Resolution: |
All changes of an entity are processed together, so old values will not be overwritten anymore. |
|||
33116287 |
3-26426116011 |
POL-8646 |
BP |
Functional key based PATCH on personcoveredservices sub resource using persons API fails with an error |
Description: |
PersonCoveredServices entity has an unique key on the combination of Person, Product, Service Option Service Code, Covered Service Type and Start Date. But functional key based PATCH on personcoveredservices sub resource using persons API fails with an error. Also, the metadata of persons API doesn’t show the attribute x-oi-composite-functional-key for personcoveredservices sub resource. |
|||
Resolution: |
Added composite functional key comprising of Person, Product, Service Option Service Code, Covered Service Type and Start Date on Person Covered Services |
|||
33117329 |
3-26378284121 |
POL-8649 |
BP |
If parameters are not specified in the sample invoice request and if the same is evaluated in the segmentation logic, exception is thrown |
Description: |
If parameters are not specified in the sample invoice request and if the same is evaluated in the segmentation logic, exception is thrown |
|||
Resolution: |
The 'parameter' now available (as an input binding variable) in the segmentation dynamic logic |
|||
33121120 |
POL-8658 |
Group client details page is not getting refreshed after performing submit operation |
||
Description: |
After user click on "submit" button in group client details page, confirmation pop up is displayed but still the page didn’t get refreshed and show the previous status itself. |
|||
Resolution: |
Group client details page is refreshed after performing submit operation and page shows Approved status |
|||
33144672 |
POL-8699 |
BP |
Group Account object navigation link, search fetches all group accounts in the system but not those group accounts in context of group client. |
|
Description: |
Group Account object navigation link, search fetches all group accounts in the system but not those group accounts in context of group client. |
|||
Resolution: |
Added an extra parameter 'doNotHandleCache' set to true. The issue was occurring because of changes in router component it was taking the cached query. After adding the parameter it will not do any caching. |
|||
33148972 |
3-26456481851 |
POL-8710 |
BP |
Exchange REST client operations sometimes failed with a JAVAX.CRYPTO.BADPADDINGEXCEPTION. |
Description: |
Sometimes the exchange REST client operations failed with JAVAX.CRYPTO.BADPADDINGEXCEPTION. This is caused by a bug in the JVM (https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8191002) that is only fixed in Java 9 onwards. WebLogic is certified to work with Java 8 in which this is not fixed. |
|||
Resolution: |
The system no longer calls the Java method that suffers from the bug. |
|||
33152434 |
3-26515153841 |
POL-8712 |
BP |
'Unknown Account Period NoPeriod' error message on Policy Accounts ADF Screen. |
Description: |
'Unknown Account Period NoPeriod' error is thrown on the Policy Accounts page when the policy has an Enrollment Product which is linked to the Account Definition with Account Period as 'NoPeriod' |
|||
Resolution: |
Policy Accounts page of the policy which has an Enrollment Product linked to the Account Definition with Account Period as 'NoPeriod' no more throws any error message and displays correct results. |
|||
33155088 |
3-26095438201 |
POL-8716 |
BP |
Run Calculation and Produce Invoice for a Group Account activity is stuck in 'InProcess' status if both fatal and informative message is attached to the activity |
Description: |
Run Calculation and Produce Invoice for a Group Account activity is stuck in 'InProcess' if one of the policies in the group account encounters both the informative message POL-FL-CAPR-018 and a fatal message POL-FL-CAPR-020. |
|||
Resolution: |
The Run Calculation and Produce Invoice for a Group Account activity is not stuck with 'InProcess' status any more. If a policy encounters both a fatal message (eg:POL-FL-CAPR-020) and an informative message (eg: POL-FL-CAPR-018), then only the fatal message is logged in the activity message. The informative message is logged only if the policy doesn’t encounter any fatal messages. |
|||
33188449 |
POL-8788 |
BP |
Add caching for static files |
|
Description: |
Stale copy of the static files were being served by the application |
|||
Resolution: |
Introduced ETag in the response headers to application’s static resources. This will ensure that the fresh copy of the resource is fetched whenever the resource is changed. If you are upgrading from a version lower than 3.21.2.0.3, make sure to clear the browser cache before accessing the application. If you are upgrading from 3.21.2.0.3 or above, clearing of browser cache is not needed. |