How is application scope selected for non-admin users?

[Max Nowak]

Hi,

I currently have a weird problem where a UI Action generates an error, but only if the user who's clicking on the button is in an application scope different than Global. Meaning that, if I select "Global" in the application picker, everything works fine, if I select any custom application scope, it doesn't work.

Now, normal users don't see the application picker, so my question would be how the current application is determined for non-admin users. Are they just always in global scope, or does the application change based on what lists or forms they open? For example, if a non-admin user opens a table from a custom application, does the scope automatically change to that custom application in the background?

Thanks in advance,

Max

[Community Alums]

HI @Max Nowak ,

There is nothing to do with non-admin users.

Application picker is not available for them, as they don't do any Platform admin related activities.

These users are primarily uses the platform for a specific job for that they have been assigned to a particular module with a role.

Rets they should not either access or visibility.

[Max Nowak]

I know that the application picker is not available to them, but my question was, is their application scope automatically changed in the background, or do they always stay in global?

Take my example, I have a UI Action that works when I select global in the application picker, and it does not work when I select a custom application. When a non-admin user, who doesn't have access to the application picker, executes that UI action, what will happen? Will they always be in global, so there will be no problems, or are there any scenarios in which a user's application scope gets automatically changed?

[hydu9535]

Hi

While creating the UI action you need to select available to all application