Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
ANVABeheerder
Partner - Contributor
Partner - Contributor

Button to launch automation multi-tenant roll-out

We are rolling out a number of apps across multiple tenants. Inside one of our apps there's a button that triggers an automation. That works well on the tenant where the app has been developed.

When I deploy both the app and the automation on another tenant, the automations cannot be triggered because the automation has a different ID. Since we plan to roll out over tens of tenants, I am looking for a way to make this work (through a variable for example).

What I notice is that in Edit mode, the button displays the name of the automation on the original tenant. When I copy the app on another tenant, the id of that automation is displayed. I assuma that is because the automation does not exist with the same ID of the first tenant. So although it displays the automation's name in the development tenant, apparently it saves the automation's ID. I would need a way to look-up the name of the automation to find the automation's ID, for each site, and then put that in the button. All automated so it can be rolled out over all tenants.

Hope someone can help me here.

Labels (2)
2 Replies
AlexOmetis
Partner Ambassador
Partner Ambassador

The way we've achieved something similar is to use a web hook called by "Open a website or email" navigation option rather than the "Execute Automation" action on the Button. You can embed the variable value into the URL you use to call the Automation. More info at Working with webhooks | Qlik Cloud Help.

Qlik Partner Ambassador 2024
ANVABeheerder
Partner - Contributor
Partner - Contributor
Author

Thank you for your suggestion.

We have previously discarded this option since the execution-token is visible in the URL. With that in mind, this solution seems to work. How have you dealt with the visibility of the execution-token in the URL? 

The overall user-experience is lots better with the "Execute Automation" action. Is there a nicer way to display the Output to the user, rather than displaying JSON?