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
Securing Report/Update Parameter?
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
NonnieBear1776
Past 24 Hours:
0
Prev. 24 Hours:
1
Overall:
5162
People Online:
Visitors:
379
Members:
1
Total:
380
Online Now:
Andy
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
Securing Report/Update Parameter?
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Dave Amen
Veteran Member
Posts: 75
4/16/2010 5:44 AM
For batch programs that have a Report-only mode and an Update mode (MM180, for example), is there a way using Lawson Security to restrict users to using only the Report mode? These users still need to change the other parameters, submit the job and view the report, but we'd like to lock down the Report/Update flag.
MattD
Veteran Member
Posts: 94
4/16/2010 12:10 PM
Greetings Dave,
You can write a rule based on that field. If it equals Update then deny access. I believe you need to write the rule on the form, but you may also be able to write the rule on the field itself as well. If you need further assistance let me know.
Matt
Dave Amen
Veteran Member
Posts: 75
4/17/2010 11:43 PM
That's it!
I went to the UPDATE_OPTION field on that form in the Security Administrator. When looking into the "Unconditional Access" options for that field, you're offered all of the values ACDIJMNPRSV (the standard batch program options). These are the same values that control access to the entire batch token.
But, you can edit the custom rule and code a rule to lock access to that field. Here's a simple one that works:
if(form.UPDATE_OPTION=='N')
'ALL_ACCESS,'
else
'NO_ACCESS,'
Any attempt to change the option to Y and click the "Change" button results in a security violation (and the system nicely puts the cursor on that field). This is exactly what we were hoping to accomplish.
Thanks Matt!
You are not authorized to post a reply.