Creating Personalizations for another Actor

Dr. Awesome

Does anyone out there have a process/policy where Personalizations to forms, lists, menus are created by someone with Configuration access for another actor?

Or, does anyone grant Personalization access to an actor temporarily for them to create their own personalizations and then access is later removed?

Infor is looking at a performance optimization to STOP checking for (and displaying) personalizations if the actor does not have Personalization access. The performance gain is fairly significant.

andy

I don't recall a scenario where we've created personalizations for users that don't have access to the configurable feature. There are some occasions were we modify existing personalizations for users, but those users have access to the configurable feature, i.e. they've created it and a change needs to be made they can't make through the UI, but it's a change we don't want to deploy for all users.

I suppose there could be a scenario where a global list customization exists, but a subset of users need a slightly different list, but that subset of users also doesn't have the configurable feature because we don't want them to be able to personalize other lists.

However, I don't recall encountering that scenario, because most of our users have access to that configurable feature.

Is there still a significant performance gain if a majority of users have the Limited List Personalization configurable feature?