I did appreciate your idea and implemented it in our environment to communicate users about our migration process. However, I have noticed that the new hub.css is updated in the client-side (Qlik Sense users machine) only I press CTRL + F5. That means that I need to force the browser cache to be updated to get the new version for that file.
Now comes my question. How did you make sure that all your Qlik Sense users had the updated version after you have been implemented the message?
Thank you very much for your time and consideration.
Thank you very much for your reply. Unfortunately, restarting the Proxy service is not enough.
Then I asked myself how Qlik does when a customer updates the QS version. They have the situation and need to guarantee that all Qlik Sense users will have the latest version once the upgrade is completed.
I investigated how it works in general (which are the techniques) and found out how Qlik does. In the following link, I shared my findings (check Step 2 in the documentation).