One of my operators was unable to click a button in a low-code app that has an automation script attached to it, getting the following error: "Not allowed." After checking the permissions of an operator in the Users / Groups in the cube, I was able to confirm that they did have the permission to Execute Automation but no permission for "UI available." After adding the "UI available" they were able to execute the script. I'm wondering why the UI available was required here. Is it because the automation script uses UIBuilder to create a dialog prompt? I wasn't able to fully understand what this permission allows for reading through the documentation. Is it just a necessary dependency to allow users execute automation scripts? Moving forward, if I want to give permissions to a user for a single specific aspect of a module, is the UI available also always required?
I see that
- For many permissions, it makes no sense to grant them unless you grant the corresponding UI Available permission as well.
How do I determine what these permissions are that depend on UI available?
We were able to replicate the same behavior. I believe we can compare this to launching scripts from a Visual Overview. There it doesn't require the 'UI available' flag to execute a script, so I believe we're applying security too strictly in Low-Code Apps. We'll create a task and report back here once it has been resolved.
Thanks for reporting!