• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Human Capital Management Lawson S3 HR/Payroll/Benefits

ESS Benefit Enrollment - BN31.1 Security

 6 Replies
 0 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
Bob Canham
Veteran Member Send Private Message
Posts: 217
Veteran Member
1/26/2012 1:38 PM
We are currently working on bringing up Benefit Enrollment through ESS to allow for Life Event and New Hire enrollment.  We would like to do these as immediate updates, but have concerns with the security.  From what I have been able to find, the update is done on the BN31.1.  However, the BN31.1 doesn't allow to secure by the Employee field on the form.  Has anyone else secured the BN31.1 so that the employee logged in can only change their own data?
Karen Sheridan
Veteran Member Send Private Message
Posts: 142
Veteran Member
1/26/2012 5:12 PM
We aren't using Life Events right now but we are using New Hire Enrollment pending. BN31.2 is securable by employee number. But, if BN31.1 is being used, you should still have the benefits table secured by employee and that would stop any rogue attempts to update someone elses record.

HTH,
Karen
Bob Canham
Veteran Member Send Private Message
Posts: 217
Veteran Member
1/26/2012 5:20 PM
We actually have our BENEFIT table secured as you recommend, and while they can't view what is in it for someone else, it still lets the entry on BN31.1 happen.
Lee Wall
Basic Member Send Private Message
Posts: 4
Basic Member
2/1/2012 12:39 PM
I added this just yesterday- Are you using Lawson Security? Here is how I secured the BN31:

BN31 - grant full access
BN31.1 - grant full access

Under BN31.1, expand DT0 and locate BEN-EMPLOYEE.
Add the conditional rule access to BEN-EMPLOYEE

if(form.BEN_EMPLOYEE == lztrim(user.getEmployeeId())) 'ALL_ACCESS' else 'NO_ACCESS'

When the user tries to add a benefit with different employee ID, they'll get a security violation. I'm not sure how to do this in laua, but I imagine it can be done. Email me if you would like to discuss further.
Bob Canham
Veteran Member Send Private Message
Posts: 217
Veteran Member
2/1/2012 12:56 PM
Thanks for that recommendation. I didn't think of trying to do it that way and will give it a try.
Bob Canham
Veteran Member Send Private Message
Posts: 217
Veteran Member
2/1/2012 2:03 PM
I just tried out what you said and it worked great. Thanks again!
Lee Wall
Basic Member Send Private Message
Posts: 4
Basic Member
2/1/2012 2:34 PM
Great- you're welcome!