Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello, Qlik experts.
I work with a multitenant subscription and have an application with a button that execute an automation.
I can successfully copy the app and the automation to a different (recipient) tenant via another automation.
I use a variable with a corresponding value of AutomationID, as on a recipient tenant the automation after copying has a different ID. The issue is that I can't get it working. I have an error "You are not authorized to run the automation".
To fix this issue I have to open the button properties and recheck "Run Mode: triggered".
It looks like the execution token for automation is linked only after a certain manual action.
Is there a way to get the automation working without extra manual steps, because you have to apply the same actions on every app deployment/copying to a recipient tenant?
Hi @Elena_Z
This is a limitation in the way the button object captures the execution token from the automation, which we have on our backlog to look at. Please feel free to raise this as an a request on Qlik Ideation also.
Looking into next year, we are implementing a more manageable way of triggering automation runs with the upcoming shared automations capability. This is currently under development, and will allow you to land an automation in a shared space, meaning any user with rights in that space can execute it. This removes the requirement for a fixed execution token too.
As an aside, make sure you're storing automation connections into shared spaces already, as that'll make management much easier across more than 1 user and unlock using the new pattern when it arrives.
Hi @Elena_Z
This is a limitation in the way the button object captures the execution token from the automation, which we have on our backlog to look at. Please feel free to raise this as an a request on Qlik Ideation also.
Looking into next year, we are implementing a more manageable way of triggering automation runs with the upcoming shared automations capability. This is currently under development, and will allow you to land an automation in a shared space, meaning any user with rights in that space can execute it. This removes the requirement for a fixed execution token too.
As an aside, make sure you're storing automation connections into shared spaces already, as that'll make management much easier across more than 1 user and unlock using the new pattern when it arrives.