Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Security
Get RMID from UserName
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jessica
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5164
People Online:
Visitors:
236
Members:
0
Total:
236
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Security
Get RMID from UserName
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
ErikSmith
New Member
Posts: 3
4/10/2007 11:29 PM
We are attempting to write a rule in Lawson Security to allow users access to jobs defined by other users in the same group. When using the function isMemberOf(group,lookup) using the UserName element in GEN, we fail because that UserName is a windows NT identity (NT00001). I cannot find a way to translate that UserName into the RMID that is required for isMemberOf(). Can anyone offer suggestions on how we can accomplish this. We are a new Lawson install and trained on 9.0 and Lawson Security, and are unsure how much Lawson Security takes from LAUA.
John Henley
Senior Member
Posts: 3348
4/11/2007 1:03 AM
You should be able to use the user.getRDId() function to get the user's RMID.
ErikSmith
New Member
Posts: 3
4/11/2007 1:49 AM
I know I can do that for the logged in user. Our issue is that we are using the UserName Element from GEN. Our thinking is that we can test the users to see if they are in the specified group and limit what users are available when prompting the user box on a batch program form (ie PR160). What we are trying to accomplish is to have a "generic" user in each application area (prjobuser) that "owns" the job and other users can access that job and submit it. We want to use the "prjobuser" to create the job, have the functional users have access to INQUIRE, CHANGE, and SUBMIT the job, but via Lawson Security lock the functional users out of some of the parameter fields (particularly file name parameters on PR160 and AP161) so that we have consistent output file placement. This also helps with reporting services as the link in RS to publish back office reports is JOB USER and JOB NAME, when we have staff leave we dont lose the link to RS, as all the published reports would be run under the generic user, but submitted by the functional user.
If there is a way to use the Environment Groups in LAUA, with users controlled by Lawson Security, I would love to know how.
You are not authorized to post a reply.