My Oracle Support Banner

Oracle Public Sector Permits Cloud: How to Trigger Groovy Validation Depending on The User's Role? (Doc ID 2715932.1)

Last updated on SEPTEMBER 30, 2020

Applies to:

Oracle Public Sector Permits Cloud Service - Version 11.13.20.07.0 and later
Information in this document applies to any platform.

Goal

Expected:
Field level validation that depends on the user having the agency staff abstract role will get triggered consistently according to the logged in user's roles.

Actual:
Field level validation that depends on the user having the agency staff abstract role is triggered during application creation/submission, but after the permit is submitted, the logic is only triggered if the user is changing the field that the logic is written on.

Prerequisite: A permit has a field (xyz) that is required of an agency user and not of a public user. The field is validated by field-level groovy that depends upon the user having the role: ORA_PSC_AGENCY_STAFF_ABSTRACT.

Steps:
1. Log in as agency user and try to submit the permit application w/o completing the field xyz.
2. Get the groovy error.
3. Complete the field xyz and submit the permit application.

4. Log in as public registered public user and try to submit the permit application w/o completing the field xyz.
5. Validate that you were successful.

6. Log in as agency user again and open the permit application in Pending Payment (or Submitted) status that you created.
7. Go to the Application details, click Edit and remove the entry you made in field xyz and click Done.
8. Validate that you get the same groovy error as before.
9. Still as agency user, open the permit application in Pending Payment (or Submitted) status that the registered public user created.
10. Go to the Application details, click Edit and change some OTHER field. Do not touch field xyz. Click Done.
11. This is where it is expected that you get the same groovy error. As an agency user, the field validation should still run on the field even though you've done nothing to it.<--
12. Now, still as agency user, click Edit again if you have to, enter a value in field xyz on the permit submitted by the public user and click Done.
13. Click Edit again and remove the value you put in field xyz and click Done.
14. Validate that you get the same Groovy error.
 

Solution

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
Goal
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.