Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.20.3.0.5

Enhancements

No enhancements.

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 of ohi_install.cfg.template and name it ohi_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:
1. Open a command window and browse to <OHI_ROOT>/util/install.
2. 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

This section intentionally left blank.

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.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB	SR	Internal	BP	Summary
32493249	3-24415907166	POL-7365	BP	Error while adding Adjustments in Enrollment Products screen
Description:	When an adjustment having amount type schedule dimension is added to the existing adjustments of the enrollment product, the page gets navigated to previous screen while saving the record
Resolution:	Adjustment can be selected and saved successfully in Enrollment Products screen.
32557686	3-25277596251	POL-7541	BP	Incidents raised from activity are not stored in data files table if ohi.incident.target is set to datafileset
Description:	If the property ohi.incident.target is set to datafileset and when a technical/unexpected error (eg: IndexOutOfBoundsException) occurs when executing the activity, the incident is not written to the data files table.
Resolution:	The incident is now correctly written into data files table when the property ohi.incident.target is set to datafileset
32572229	3-25277596251	POL-7578	BP	java.util.NoSuchElementException if policy holder start date is after policy enrollment product start date
Description:	java.util.NoSuchElementException is raised if policy holder start date is after policy enrollment product start date in case of policy based premium. If there is no policy holder as of the reference date, the premium should be calculated for the oldest enrolled person on the policy.
Resolution:	java.util.NoSuchElementException is no longer raised and premium is calculated for the oldest enrolled person on the policy.
32616451	3-25407851131	POL-7686	BP	Titles are not getting saved in Persons page
Description:	In Persons page, 'Titles' field was not getting updated after Save.
Resolution:	Titles are now updated after Save.
32572286	3-25277596251	POL-7580	BP	java.lang.IndexOutOfBoundsException is raised from APPLY_REGISTRATIONS activity when multiple registrations (including refund) present with the same payDate
Description:	java.lang.IndexOutOfBoundsException is raised from APPLY_REGISTRATIONS activity when multiple registrations (including refund) present with the same payDate. This happens when: - an exact payment was sent in and applied - the daily premium was diminished - a refund was sent in - and when the refund is processed and applied, a new payment was sent in with the same payDate (as the original payment and the refund) and process and apply registrations process was run
Resolution:	java.lang.IndexOutOfBoundsException is no longer raised from APPLY_REGISTRATIONS activity
32584314		POL-7624		In policy view-edit page : group account tab show busy state icon and UI page stop responding.
Description:	In policy view and edit page, when user clicks on Group account tab, it shows the busy state icon and stops responding.
Resolution:	Now user can successfully navigate to group account tab in policy view-edit page.
32592074	3-25196339551	POL-7649	BP	Adjustment result amount is incorrect in the last split PCP if the adjustment with a lower sequence is not applicable in the last split PCP
Description:	If two adjustments (scoped on TotalPremium) are defined with different sequence, in the last split PCP, the result amount for the adjustment with a higher sequence is incorrect if the adjustment with a lower sequence is not applicable (for example, if the adjustment with a lower sequence ends one day before the start date of the last split PCP).
Resolution:	The adjustment result amount is now correct in the last split PCP if the adjustment with a lower sequence is not applicable in the last split PCP

BugDB

Internal

Summary

32493249

3-24415907166

POL-7365

Error while adding Adjustments in Enrollment Products screen

Description:

When an adjustment having amount type schedule dimension is added to the existing adjustments of the enrollment product, the page gets navigated to previous screen while saving the record

Resolution:

Adjustment can be selected and saved successfully in Enrollment Products screen.

32557686

3-25277596251

POL-7541

Incidents raised from activity are not stored in data files table if ohi.incident.target is set to datafileset

Description:

If the property ohi.incident.target is set to datafileset and when a technical/unexpected error (eg: IndexOutOfBoundsException) occurs when executing the activity, the incident is not written to the data files table.

Resolution:

The incident is now correctly written into data files table when the property ohi.incident.target is set to datafileset

32572229

3-25277596251

POL-7578

java.util.NoSuchElementException if policy holder start date is after policy enrollment product start date

Description:

java.util.NoSuchElementException is raised if policy holder start date is after policy enrollment product start date in case of policy based premium. If there is no policy holder as of the reference date, the premium should be calculated for the oldest enrolled person on the policy.

Resolution:

java.util.NoSuchElementException is no longer raised and premium is calculated for the oldest enrolled person on the policy.

32616451

3-25407851131

POL-7686

Titles are not getting saved in Persons page

Description:

In Persons page, 'Titles' field was not getting updated after Save.

Resolution:

Titles are now updated after Save.

32572286

3-25277596251

POL-7580

java.lang.IndexOutOfBoundsException is raised from APPLY_REGISTRATIONS activity when multiple registrations (including refund) present with the same payDate

Description:

java.lang.IndexOutOfBoundsException is raised from APPLY_REGISTRATIONS activity when multiple registrations (including refund) present with the same payDate. This happens when: - an exact payment was sent in and applied
- the daily premium was diminished
- a refund was sent in
- and when the refund is processed and applied, a new payment was sent in with the same payDate (as the original payment and the refund) and process and apply registrations process was run

Resolution:

java.lang.IndexOutOfBoundsException is no longer raised from APPLY_REGISTRATIONS activity

32584314

POL-7624

In policy view-edit page : group account tab show busy state icon and UI page stop responding.

Description:

In policy view and edit page, when user clicks on Group account tab, it shows the busy state icon and stops responding.

Resolution:

Now user can successfully navigate to group account tab in policy view-edit page.

32592074

3-25196339551

POL-7649

Adjustment result amount is incorrect in the last split PCP if the adjustment with a lower sequence is not applicable in the last split PCP

Description:

If two adjustments (scoped on TotalPremium) are defined with different sequence, in the last split PCP, the result amount for the adjustment with a higher sequence is incorrect if the adjustment with a lower sequence is not applicable (for example, if the adjustment with a lower sequence ends one day before the start date of the last split PCP).

Resolution:

The adjustment result amount is now correct in the last split PCP if the adjustment with a lower sequence is not applicable in the last split PCP

Issues that were backported in previous Release / Patch

No backports.