Close popover
Jon Garfunkel (JonnyGar)
BNY Mellon
Vice President, BPM CoE
BNY Mellon
JonnyGar Member since 2009 91 posts
BNY Mellon
Posted: April 29, 2015
Last activity: July 17, 2017

Operator with multiple accessgroups pointing to same application

When Pega introduced application-based acessgroup, a new warning was introduced on the Operator ID record when saving with multiple accessgroups pointing to same location:

"Each access group must list a unique application name"

Why must? Really, what is the consequence?

This warning makes sense in a production environment, but not pre-production where users (developers) have multiple roles.

The only consequence I'm aware of is a UI decision that's tricky to override -- the "Switch Application" dropdown actually switches accessgroups. These used to display accessgroups, but I think in v5 or v6 this was updated to display Application name, which was presumed to be more useful for the user. But, clearly, for developers, the accessgroup name is more useful.

Obviously, this should be an overridable switch/preference per user. Or otherwise this should just solely display the accessgroup in the developer dashboard list.

(I'm planning on overriding this for us v6 & v7. One of these days)

***Updated by moderator: Lochan to add Categories***

***Updated by moderator: Marissa to close post***

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

System Administration User Experience
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.