If an automation script is called from a low-code application (a button) which, for example, sets a parameter of an element, which user rights apply? Those of the user who is using the low-code app?
So if a user is allowed to use a low-code app but doesn't actually have the right to change a parameter of an element, but the script wants to set the parameter, is that possible? Because that would be very dangerous.
Is there a way in the script to check the user rights of the current user for a specific parameter of the element before setting it?
Hi Peter,
When a user clicks a button in a LCA which executes an Automation Script, it will be executed in the security context of that user. Any SLNet message sent within this script will be executed under this user. If the parameter set is sent using a message, and the user clicking the button has no permission for the element, the set won't be completed, and an error will be returned.