Rule for users to update application via button

[Felipe02]

Hello everyone, I created a rule below to only allow this user to update my application and not have permissions to edit folders or scripts.

However, I was unsuccessful. Has anyone experienced something similar?

The user has a professional license, and I need him to only be able to load this already published application via a button

because he selects a variable that is changed in the back end and changes the application's modeling

[howdash]

I wish I could help more, but I don't have access to my Qlik Sense servers at the moment.

I did find this video by Qlik and did a bit of research on the reload functionality. It's for Qlik Cloud and not for on-prem, but in that video they show that the default "Reload Data" action of a button doesn't work in a published app.

Qlik doesn't explicitly say it, but it looks like that button was designed to enable app reloads for non-published apps only. I might be wrong about that, but here's how I came to that conclusion.

A Qlik Sense app is essentially a container that holds data and visualizations. In a single app, all users see the same data and visualizations. Each user can interact with the objects without impacting what other users see, but all users see the same data.

So, if multiple users open the same, published app and one of the users initiates a reload, once the reload completes, the app will update and the rest of the users will see the newly loaded data.

So, if someone was looking at 2024 analysis and another user set the year to 2022 and reloaded the app, both users will see analysis for year 2022 once reload completes.

The user that was looking at 2024 data will be confused. He didn't reload the app but the data still switched from 2024 to 2022 because the other user reloaded the app with new data.

So the user that was looking at 2024 data will select year 2024 and reload the app which will reset the data for the user that was looking at 2022 data. Now the second user will be confused, will switch the year back to 2022, reload the app, and they'll be doing this constant reload of app, wondering why the app keeps switching years.

Because each app has only one data that it is displaying for all users, it would be problematic to introduce a button that users can use to reload a published app.

If loading data for all years into the app is not feasible, there's this thing that's called ODAG - On-Demand App Generation - which might work for you. Qlik put together a quick video demoing the ODAG functionality. It's essentially a way for you to create a "selections" app used for making selections and a "template" app that will be populated with selected data and copied to user's Work stream. It might work for you.