Add New (Client) Relationship - Unable To Add/Search For Configured/Eligible Secondary Client Type
(Doc ID 2824233.1)
Last updated on NOVEMBER 29, 2021
Applies to:Oracle Insurance Policy Administration J2EE - Version 184.108.40.206 and later
Information in this document applies to any platform.
On : 220.127.116.11 version, General
User unable to manually Add New (Client) Relationship due to inability to search and select the targeted Secondary Client based on its type.
The respective Client types allowed for Primary and Secondary Clients are configured for each defined Relationship.
Individual Relationships limit the Primary Client to “Individual” only, while allowing the Secondary Client type to vary in alignment with the nature/type of the Relationship.
Most of the associated Secondary Relationships are configured for “Individual” client type (e.g. Spouse, Child, Sibling, etc.).
A handful are for “Corporate” Client type (Estate, Trust, etc.).
When adding a new Client Relationship manually the user first selects the Primary Relationship type and then the applicable Secondary Relationship type.
The next step is to either search for an existing or add a new Client as the secondary Client in the Relationship.
The list of available existing clients or addition of a new one is limited to the available type(s) configured for the selected Secondary Relationship type as per above.
The system should refresh the client search parameters to target the applicable Client types each time one of the available Secondary Relationship type values is selected from the list.
This worked as designed in v10, however in v11 the Client search parameters are not being refreshed.
Instead the Client type(s) associated with the default/initial Secondary Client type value displayed when the screen loads remains in effect regardless of how many or which selections are made.
In this case the default is “Administrator” which is limited to “Individual” Client type and thus prevents searching/adding a trust Client that is “Corporate” type.
Available Client type should be filtered according to configuration for each Secondary Client type and refresh when user makes different selection.
Workaround is alter/liberalize configuration to allow all Client types for every Secondary Relationship types available for a given primary relationship type - requires additional procedural consideration/monitoring to ensure users only select intended client type from all offered.
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