Unable To Provide Securities For Error Fields For A Transaction Residing At Customer Plan Level
(Doc ID 2665857.1)
Last updated on MAY 04, 2020
Applies to:Oracle Insurance Policy Administration J2EE - Version 188.8.131.52 and later
Information in this document applies to any platform.
On : 184.108.40.206 version, General
Unable to provide securities for Error fields for a transaction residing at Customer Plan level. There are two different transactions at two different levels, plan level and customer plan level and both has Error field which needs to be provisioned with security to Override Not allowed. At plan level, providing security will disable error Override for a specific set of security groups. However the same is not working as expected for a transaction residing at Customer plan level. In case of an error (Check Tolerance Limit) when a user processes activities like BTAdminPayment and PremiumPaymentExpected. For one set of security groups, error message should not be overriden and another set of groups the users should be able to override the error message.
Providing security for specified groups should blocks users belonging to that security groups to not override an error.
The issue can be reproduced at will with the following steps:
1. Under any security group
2. Go to Customer plan transactions
3. Any transaction which has Overridable Errors
4. Change it to Override Not Allowed for selected security group
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