How does Qlik Cloud define the "Executed by" user when an Automation is triggered from an app?

[Adfc_NZ]

Hi,

I have a simple Automation being triggered by a Button in an app. Both App and Automation are owned by my user.

However, I was expecting that when another user triggers the automation via the app, that the "Executed by" field in the Automation's History would show that user (the user logged into the app at the moment of the "triggering") and not myself which is what is happening.

Any ideas if this is standard behaviour or if it isn't if I can do something to the Automation or the trigger (Button) to show who was the user that triggered the automation?

Thank you.

[Vegar]

@Adfc_NZ 

I believe that you cannot change who's executing the automation, but I believe there is a way to catch who ran it

You should be able to create a variable with information about the user. Try adding SubField(OSUser(), '=', -1) or GetUserAttr('userEmail') into such a variable.

See even Get user Name/ID in Qlik Saas cloud while running automation through button 

If you try this successfully then please report back and mark this question as solved.

[Adfc_NZ]

Hi Vegar,

Thank you very much for your reply, but that's not what I'm after. What I'm referring to, is the "Executed by" field:

What is the Qlik rule to populates this field? Because my experience with an apps triggering an automation shows 2 different behaviours: in one case it populates it with the person clicking the button in the corresponding app, the other case populates the it with the owner of the corresponding app and/or automation (I own both in this case).

And I'd like this particular automation to populate with the user "pushing the button" (i.e. the person working in the app), not with my name just because I'm the owner of both the app and the automation.

[Dave_Channon · Accepted solution]

There are two ways to run automations via the button object:

1. With `run mode: triggered` checked - this generates an execution token for the automation meaning other users call the automation with a credential generated by the owner of the automation. This will always show it as having been run by the owner.
2. With `run mode: triggered` unchecked - this requires other users who might press the button to have `Can edit` role in the shared space the automation resides in. They won't be able to edit the automation (confusingly, only owners can do this), but they will be able to execute it via the button, and the executions list will show it running as their user rather than the owner.

Hope that helps!