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
ESS Payment Modelling
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Chris Radcliffe
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
5187
People Online:
Visitors:
236
Members:
0
Total:
236
Online Now:
New Topics
S3 Customization/Development
Cobol - Extract Current Time
4/24/2024 7:21 PM
How do you extract just the Current System Time in
Lawson Landmark
LPL INSTR Functions
4/5/2024 8:32 PM
I'm writing a simple report using the Create R
Infor SCM
Translating 856 to get the ~ REF^CN^ field
4/3/2024 8:24 PM
We are trying to get the tracking number which is
IPA/ProcessFlow
Sample XML file create Flow
4/3/2024 3:43 PM
Hello everyone, I am new to creating XML files
Lawson S3 HR/Payroll/Benefits
bn105 error message
3/26/2024 6:40 PM
I need to change some of the set ups in our Life I
IPA/ProcessFlow
IPA executing Job
3/13/2024 7:08 PM
New to the IPA world and was wondering, can an IPA
Lawson S3 HR/Payroll/Benefits
Life Age Reduction on benefits plans
3/12/2024 7:15 PM
For our optional life we have an age based coverag
Lawson S3 HR/Payroll/Benefits
BN53.1 Add-In
3/7/2024 3:31 PM
We are migrating to Solstice. They require a
Lawson Business Intelligence/Reporting/Crystal
Domain Name Change
3/5/2024 7:45 PM
Our domain name needs to change and was hoping I c
S3 Customization/Development
Cobol calling Shell Script
2/29/2024 1:27 PM
Has anyone created or modified a Lawson Cobol prog
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
1351
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
ESS Payment Modelling
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
ALB
Veteran Member
Posts: 130
8/27/2013 3:50 PM
We have been having security violations with Payment Modelling in ESS. The rule is:
if(isElementGrpAccessible('COMPEMP', '', 'PR', form.EMP_COMPANY, form.EMP_EMPLOYEE))
'ALL_ACCESS,'
else
'NO_ACCESS,'
We have tried using lztrim and trim. So far, we have not had any success. We had to build an Element Group COMPEMP with company and employee.
I would appreciate any ideas.
Thanks!
BarbR
Veteran Member
Posts: 306
8/27/2013 4:07 PM
Do you have a Grant All on PR89 and this rule on PR89.1?
ALB
Veteran Member
Posts: 130
8/27/2013 4:51 PM
I have grant all access on the application PDL, PR, and PR89. I have conditional access on PR89.1 as originally posted so that an employee can only model his/her own information. There is also file access. We are not getting to the transaction.
Al
Basic Member
Posts: 17
8/27/2013 5:17 PM
This works for us on PR89.1:
if(user.getCompany()==form.EMP_COMPANY&&user.getEmployeeId()==form.EMP_EMPLOYEE)
'ALL_ACCESS,'
else
'NO_ACCESS,'
BarbR
Veteran Member
Posts: 306
8/27/2013 5:27 PM
AngelaC, your rule is identical to mine, and our Payment Modeling works fine.
ALB
Veteran Member
Posts: 130
8/27/2013 5:53 PM
I was trying to figure out if there is an issue with the element group. It looks like there is not much to it. I just has company and employee. Which profiles do you have COMPEMP defined?
Greg Moeller
Veteran Member
Posts: 1498
8/27/2013 6:05 PM
I think COMPEMP needs to be defined in the same profile that the rule to PR89.1 is in.
Karen Beyer Goode
Basic Member
Posts: 4
8/27/2013 6:19 PM
do you have a rule written on your element group?
This is the rule on our COMPEMP element group and its assigned to the same profile where access to ESS resides.
if(user.getCompany()==lztrim(COMPANY)&&user.getEmployeeId()==lztrim(EMPLOYEE))
'ALL_ACCESS,'
else
'NO_ACCESS,'
ALB
Veteran Member
Posts: 130
8/27/2013 7:13 PM
We have the rule on our group element.
After seeing the responses, I suspected it had to do with our identity. It appears to be due to putting leading zeros into the company on the identity for functionality for job reqs.
You are not authorized to post a reply.