My Oracle Support Banner

Role Fields Are Not Saved On The First Time A Role Is Created (Doc ID 2494482.1)

Last updated on FEBRUARY 26, 2019

Applies to:

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


On : version, General

Role Fields are not saved on the first time a role is created

When creating a client in RoleScreen of a policy (ie New Client), none of the role fields are initially saved. The fields are created in the db but the values inserted/created/selected are not saved.

Although we currently use 11.2, it was also seen in


When a user enters value into a role field when in the process of creating a client, that value should be saved in the db.

The issue can be reproduced at will with the following steps:
1. First select a role that has fields (ie AsRoleFields). Then create a client in RoleScreen of a policy (ie New Client) and enter info in those role fields. Click Add. See that the role fields were not saved. See in db that AsRoleField didn't save vales.

Gives user the false impression of having entered information in fields. This could have serious impact downstream on policy activities for ex.


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

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