Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Financial Management
Lawson S3 Financials
Process Level Restriction
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
51
Members:
0
Total:
51
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Financial Management
Lawson S3 Financials
Process Level Restriction
Please
login
to post a reply.
2 Replies
0
Subscribed to this topic
45 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Dee Hardy
New Member
Posts: 2
12/9/2014 3:14 PM
I'm not sure I's posting this problem in the right location. I wrote rules to restrict users by process levels, which works, but it doesn't allow for Drill Around access. For example, I can restrict a user to process level using the rule which looks at ProcessLevelControl and AccountingUnitControl in RMID, but no information is displayed when the users tries to use Drill Around. There should be a way to make this work. Does anyone have any experience with process level restriction and access to Drill Around? Any advice is very much appreciated? Thank you
John Henley
Posts: 3366
New Poster
Congrats on posting!
Engaged Reader
You are an engaged reader!
Avid Reader
Avid Reader art thou!
12/9/2014 5:44 PM
Split
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.
Dee Hardy
New Member
Posts: 2
12/9/2014 6:19 PM
Split
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,'
Please
login
to post a reply.