Ideas to Prevent Users from Launching Groovy Rules When Approvals Are Preventing Editing
in Planning
Summary:
Follow up to my question posed here:
I've been able to prevent users from launching calc script rules based on approvals using this:
https://docs.oracle.com/en/cloud/saas/planning-budgeting-cloud/pfusa/about_runtime_prompts_and_approvals_security.html
However, several of the OOB labor rules use groovy script and not calc script. Is there any way to prevent users from launching groovy rules if they don't have access based on the approvals.
Thank you!
Content (please ensure you mask any confidential information):
Version (include the version you are using, if applicable):
0