Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.21.3.0.5

This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.21.3.0.5.

Enhancements

No enhancements.

Configuration Properties

This section intentionally left blank.

Web Services

Ref Action Subject Description

POL-9539

Modified

AttachedPolicyData API

Customers are allowed to set property 'manual' during creation.

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

33568543

3-27562427001

POL-9540

BP

UI : Creating a policy from JET does not update the field 'manual' in attached data.

Description:

When creating a policy from the JET UI, the field 'manual' should be checked as yes. However, the field that is used to distinguish between manual and integration is set to false, indicating the policy was created through the integration.

Resolution:

The property 'manual' on attached policy data can now be set during creation.

33641635

3-27463122071

POL-9664

BP

Removing column URI from OHI_BOOKMARK_UK1

Description:

In 3.21.3.0.0 unique constraint OHI_BOOKMARK_UK1 was created on the combination of user preferences, alias and URI of the bookmark. The URI column should be removed from the constraint.

Resolution:

The attribute URI is removed from the Unique Key on Bookmarks

33657901

3-27944936671

POL-9678

BP

Updating an approved policy through 'POLICY IN DATA FILE SET IMPORT' fails when the policyholder person is matched on relation identifier instead of code

Description:

GEN-TMVL-011 is raised during policy import: The Policyholder with start date 10/01/2021 overlaps in time with a Policyholder that has start date 10/01/2021). This happens when: 1) policyholder is matched by relation identifier in the incoming payload. 2) policy loaded using file based policy import. 3) existing policy in system is APPROVED and the file contains new version of the policy.

Resolution:

The scenario described will no longer lead to the mentioned business rule failure.

Issues that were backported in previous Release / Patch

No backports.