Process Level Restriction

Dee, when you say " I wrote rules to restrict users by process levels, which works ", are you referring to form/token rules? For update, add, inquire, etc.? If so, did you also create rules that govern table access? That is used for securing drillaround.

Thank you for your response! Because the user needs to be restricted to specific process levels, for example, process level 50, on AP and GL forms, I wrote the rules below. I've used inquiry/view only security classes, and I've also created a custom security class that grants ALL_INQUIRIES access to, for example, GL90.1. I use the file access security classes, APFAFileAccess, GLFAFileAccess, etc. delivered with the Accelerator set up that a consultant brought before go live. The restriction works - the user can only see and choose from process level 50 and process level 50 accounting units, which are identified in the AccountingUnitControl and ProcessLevelControl fields in the user's RMID. However, when the user tries to Drill Around, no records are returned. When the process level restriction security classes are removed, Drill Around returns records as it is supposed to. Thank you!

Rule written on PROCLEVEL element group – Security class = PRCLVLAUC

if((user.attributeContains('AccountingUnitControl',trim(PROCESS_LEVEL))||(PROCESS_LEVEL=='LP')))
'ALL_INQUIRES,'
else
'NO_ACCESS,'

********************************

Rule written on PROCLEVEL element group – Security class = PRCLVLPLC

if((user.attributeContains('ProcessLevelControl',trim(PROCESS_LEVEL))||(PROCESS_LEVEL=='LP')))
'ALL_INQUIRES,'
else
'NO_ACCESS,'