In Perspective how do I close an “Access Denied” screen and return to the app?
Is there a solution to this? View permissions are effectively useless because there is no way of returning from the access denied page.
Please provide steps to reproduce the problem. (For example, is this a problem with Designer or running a Perspective app in Designer or in the browser?
- Configure a view with permissions
- Access the page without the required permissions
- The access denied page is shown
5. No way to leave this page. Restarting workstation is required.
6.
Why are they able / allowed to navigate to the page if it's not accessible? Enable / disable the navigation based on permissions. Don't present enabled options to the user that they can't use.
So in order to configure access to a view, I need to:
- Configure view permissions on the view itself to prevent direct access
- Configure a script that prevents the navigation action (that now needs to be a script so it can be bypassed) from firing based on permissions.
- Configure bindings on the enabled property of any button that accesses the page.
I don't think that is the best from a development perspective.
The access denied page is expected to be seen by the user, it shouldn't break the program.
Docks are still visible even if the user doesn't have "primary view" view permissions. It seems you don't have any docks; how are you doing your navigation?
However I share the same views as @Transistor; if something isn't viewable to a user, disable the button and give them an icon (e.g. security badge) to tell them why. Don't make them click on the button to find out
I am recreating some hmi views that have different nav options based on the screen that is active. So I don't necessarily have a fixed navigation area to use as a dock. I was hoping to avoid a docked view but I have implemented it now, so operators are just going to have to deal with it.
I generally agree, but this is a valid function of the program, so it should probably be recoverable from this point. If I were to add a restriction to anything that navigates to this screen, I would need to update the permissions in multiple places. It just seems like poor practice in terms of having maintainable code. Especially if someone who isn't me wants to change the permissions, they now need to find every instance of something navigating to that page to update it with new permissions.
I've gotten around this somewhat in the past by defining custom session properties as user groups, but I was hoping to avoid that. I don't see why perspective can't check if it is able to access a page before navigating. At the very least it could have a return button if there is a valid url to return to.
Fair, a back button would be a good idea 
would be a good one for the ideas site