Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.2
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.2.
| 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. |
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.templateand name itohi_install.cfg. -
Edit
ohi_install.cfgto 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 | Summary |
|---|---|---|---|
36376607 |
POL-14766 |
Connector config: spinner shown on create |
|
Description: |
Click on Create button in Connector configuration Page, Create page is not loaded with spinner shown for long time and there is a console error |
||
Resolution: |
User is able to view Create page on click of Create button in Connector configuration Page |
||
36325054 |
3-35475079541 |
POL-14637 |
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. |
||
36313847 |
3-35742239861 |
POL-14617 |
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 |
||
36352074 |
POL-14713 |
Dynamic field value is getting wiped off and not holding the data upon save and also title is not displayed |
|
Description: |
When a dynamic field is of string type, converted to Lov field and attached to Dynamic record and used as a detail page, the value selected is not retained on the page, also, when that field is used to display title of the page, the title is not displayed. |
||
Resolution: |
The selected value from LOV is retained and page is saved, also the selected value is displayed in title of the page |
||
36371685 |
3-35948698481 |
POL-14758 |
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 |
||
36502541 |
3-36334533791 |
POL-15012 |
Access mapping (relation links api) missing for organization/person page |
Description: |
Upon clicking the person in the policy enrollment, the member window opens but does not loads the person details |
||
Resolution: |
Person details are loaded on clicking the person in the policy enrollment and there is no error related to access |
||
36355929 |
POL-14718 |
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 |
||
36377401 |
POL-14768 |
Save and Cancel shortcuts aren’t working for create HRR pages |
|
Description: |
Save and Cancel shortcuts aren’t working for create HRR pages |
||
Resolution: |
Save and Cancel shortcuts will work for create HRR pages also now |
||
36353153 |
3-35011487731 |
POL-14714 |
Custom jet fields createdbyjet and lastupdatedbyjet are not working for tab configuration |
Description: |
The custom JET fields createdByJET and lastUpdatedByJET are not working in the below auditable resources in tab configuration in HRR page. createdByJET and lastUpdatedByJET should show user names |
||
Resolution: |
createdByJET and lastUpdatedByJET shows user names in tab configurations in HRR pages |
||
36366919 |
POL-14734 |
Preferred language field editable in persons details section though it is readonly |
|
Description: |
Preferred language field is nested property of Member field. It should not be editable in Policies page - person details section |
||
Resolution: |
Preferred language field is displayed as readonly nested property in persons details section as expected |
||
36350882 |
POL-14708 |
Ethinicity and race multivalue select box not working in create mode |
|
Description: |
Ethinicity and Race multivalue select box are behaving as a normal dropdown in create mode instead of multivalue. |
||
Resolution: |
Multiple values can be selected for Ethinicity and Race select box in Create mode as well |
||
36433105 |
3-36176430291 |
POL-14881 |
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 |
||
36462976 |
POL-14937 |
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 |
||
36453009 |
3-36224017471 |
POL-14927 |
Conversion Script For Floorplan Region Sets Changes |
Description: |
A data conversion was performed for all seeded floorplans that included the region in the payload. In the JSON payload for floorplans, the format "region → set1, set2, set3" was converted to an array format "set[]".However, the conversion script for customer floorplans (non-system specific) was not delivered as part of the major release. |
||
Resolution: |
The conversion script for customer floorplans (non-system specific) is delivered as part of this fix, that converts the customer floorplans (payload) having region components, with the format "region → set1, set2, set3" to an array format "set[]". It is also recommended to convert all the non system specific floorplans that are stored externally; this can either by done manually or by configuring the floorplans in the system before running the conversion script. |
||
36480308 |
3-31029430181 |
POL-14972 |
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 |
||
36355819 |
3-35475079541 |
POL-14715 |
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. |
||
36392137 |
POL-14785 |
Unable to invoke Macros when a macros template is attached to macro definition |
|
Description: |
Unable to invoke Macros when a macros template is attached to macro definition, there is a console error |
||
Resolution: |
It is possible to invoke macros without errors when a macros template is attached to macro definition |
||
36414244 |
3-35684326321 |
POL-14836 |
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. |
||
36350831 |
POL-14673 |
Preferred language, contact details and address details are not populating in person details section in create mode |
|
Description: |
Go to person details section and click on 'Add New?' deep link. Fill all the mandatory details, contact and address details and click on save button. Close the deeplink pop up. Observe Preferred language, contact details and address details are not populating in person details |
||
Resolution: |
Only the properties that are mentioned in Persons LOV floorplan will be displayed in create mode. Member Identifiers and Address List are moved to the same region as Members LOV |
||
36363652 |
POL-14729 |
Additional Fields at tab level is not retrieving the data. |
|
Description: |
The data of extensible fields under the more action drawer in a tab table is not showing up even after save. |
||
Resolution: |
The data of extensible fields under the more action drawer in a tab table is displayed properly after the save operation is performed. |
||
36264585 |
3-35378971011 |
POL-14532 |
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. |
||
36347910 |
POL-14683 |
Medicare details are auto populating in new record when there are multiple policy enrollment products |
|
Description: |
Medicare Details are auto populating (copied from previous enrollment product) in new records when there are multiple Policy Enrollment Products. Issue doesn’t exist when there are Medicare Details already created through API |
||
Resolution: |
Medicare details are not auto populated (from previous enrollment product) in new records when there are multiple policy enrollment products. It would be empty for the user to fill in the details |
||
36403711 |
POL-14805 |
Global activities: Business error shown on bulk update invoke |
|
Description: |
Invoke a new activity on the global activities page in the JET UI. Pick BULK_UPDATE as the activity type and populate the required fields. Populate the group account from the drop down list. On Invoking the activity, getting business error. |
||
Resolution: |
Invoke activity is successful without business error for Bulk update using Group Account |
||