My Oracle Support Banner

Role Field Values Not Committed To DB When Saving Role/client/address Together (Doc ID 2463377.1)

Last updated on OCTOBER 22, 2018

Applies to:

Oracle Insurance Policy Administration J2EE - Version 11.1.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.0.0 version, General

ACTUAL BEHAVIOR
---------------
From the policy role screen, when adding a new client to a new role on the policy, after entering client, address, & role information, clicking "Add" commits all entered values to the DB except for the dynamic role fields. the values must be reentered and resaved in order for them to be committed.

EXPECTED BEHAVIOR
-----------------------
Dynamic role field values, in addition to values for the core role/client/address tables and dynamic client/address fields are committed to the DB.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Navigate to an existing policy
2. Navigate to its role screen
3. Click the "New Client" button
4. Choose a role type with dynamic fields defined
5. Enter the client, address, and role fields
6. Click the "Add" button
7. View the role details

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, Users are required to enter client and address info first and click save before entering role field values and clicking save again.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.