is there anything in particular that I have to keep in mind when I want to add a button to an app - that will be viewed in the browser - with the trigger to reload the script?
(the thing is that we cannot schedule it inflexibly because someone has to manually export the base_data_lists from a customer_tool and save them on our servers and only then can my code run)
I did something with a button which started an EDX-Trigger to start the reload-task. Unfortunately I didn't get any information when the reload-task ended, so I had to wait an amount of time and reloaded the app in my browserwindow.
thanks! That is a possibility to keep in mind. We'll have to talk about this. I don't know yet how that is to be done - there is a chance that the person who will have to manually export those lists will be someone with access to the QMC. In that case, reloading an app is only one click. We should not, however, give that duty to just one person - else, whenever this person goes on holiday, there won't be anything going on ...
If you have a Publisher, the Document Administrators feature can be used to accomplish both requirements:
There can be many doc admins for a single document, and while they can access the QMC this access is restricted to specific tabs with just their tasks and documents listed, nothing else.
Since doc admins can access the QMC to view the status of their tasks, they'll know when a task has finished. No more arbitrary waiting periods to make sure that the job has finished...
See chapter 9.3 in the Server Reference and the QMC Help.
