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
HREMP element Group
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:
25
Members:
0
Total:
25
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
Infor / Lawson Platforms
S3 Security
HREMP element Group
Please
login
to post a reply.
0 Replies
0
Subscribed to this topic
19 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Garry Ferwerda
New Member
Posts: 0
2/2/2015 7:09 PM
We have had our back office users on LS9 security for a while and we are now implememting EMS security. We also have multiple accounts, one for back office and one for EMS that we planning to combine (eliminate the back office login). We use the HREMP Element group to enforce record level security in the HR modules. We have discovered that for a certain subset of HR employees that they cannot access their own information in EMS once the EMS and back office roles are applied to a single login because the HREMP rule is blocking access. The Element Group rule is evaluated first and other rules are not evaluated if the Element Group rules come back ACCESS_DENIED (KB 5430934). Has anyone else been in this situation and is there a way around this without scrapping the HREMP rule?
Please
login
to post a reply.