Oh, that “Check LS” flag taunts us every time we administer one of our customers’ user accounts. We feel guilty when assigning a user to an LAUA security class, and when copying LAUA security class HRREP to HRREP+ and adding that one form for one person— knowing there is a better way. We understand that the move to the Lawson Security (LS) model is a notable shift, but the change is imminent and it doesn’t have to be painful if you’re backed by an experienced team.
As the upgrade to Infor 10x approaches, you have several options for implementing LS. Think of it like octane choices at the gas pump: 87, 89, and 93. For 87, you can migrate your existing LAUA security to LS, flip the flag and deal with it later. There is a tool, laua2ls, which assists with this process. For 89, you can implement a generic LS security setup based on best practices and tweak it as you go. For the 93, you start over; building security based on your organization’s current needs and knowing your LS model can be readily adapted for the future.
Choose any octane of security and the end result is the same: getting to Lawson Security. Make sure you understand the fundamentals behind it so you can easily complete those exception requests by saying, “There’s a role for that!”
Should you migrate to Infor 10x and upgrade security at the same time? Only you can make that decision. Our experience shows that many organizations find it difficult to learn a new security model and a new application version at the same time. No matter when security is implemented, users should test thoroughly. Velocity Zoom®
can provide visibility into how much testing is being done. And, once you’ve made sure everything works as expected, you’ll have the satisfaction of moving the Check LS flag to YES, and so will we..