Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.21.1.0.1
UI Changes
Ref | Action | Subject | Description |
---|---|---|---|
POL-7232 |
Modified |
policy enrollment page |
The person’s address list is visible on the policy enrollments floorplan. |
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
32541746 |
3-24941428911 |
POL-7503 |
BP |
Not able to display person address list in the policy enrollment floorplan |
Description: |
Not able to display person address list in the policy enrollment floorplan. Two level of references from any resource are supported. User should be able to customize any floorplan for the same. |
|||
Resolution: |
The person’s address list is visible on the policy enrollments floorplan. |
|||
32557659 |
3-25277596251 |
POL-7540 |
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 |
|||
32572036 |
3-25277596251 |
POL-7577 |
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. |
|||
32572272 |
3-25277596251 |
POL-7579 |
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 |
|||
Resolution: |
java.lang.IndexOutOfBoundsException is no longer raised from APPLY_REGISTRATIONS activity |
|||
32592059 |
3-25196339551 |
POL-7648 |
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 |
|||
32616425 |
3-25407851131 |
POL-7683 |
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. |
|||
32643729 |
POL-7687 |
Optimistic lock failure on attached policy data when running process and apply registrations |
||
Description: |
This occurred when an exact payment was sent in and the policy had outstanding policy events as well. |
|||
Resolution: |
The optimistic lock failure no longer occurs when running process and apply registrations integration point. |