It's kind of unusual case: creating a task for non-published apps... What's the reason for that?
If you do not want other users to access this QVD-building application - just publish it in some stream that could be accessed by Admins only, for example...
This would be definitely a better process and will allow you to update your file independently.
Appreciate your reply.
I'm kinda new to Sense and actually trying to apply the best practices for everything
Considering your suggestion, we want to be able to edit the script anytime (unlike a final dashboard, where we would be dealing with objects mainly)
So these were the steps:
- From the hub: duplicate the app
- Edit the needed script/reload
- From qmc: publish and replace the existing app
- Delete the duplicated app
Would these be the correct steps?
These steps are correct.
Another option to consider: use external script file (for portions of the script you are modifying frequently).
In this case you will be using the same published app, which will load the script file from shared location...
You have to arrange a shared folder, worry about access rights for different people (if any), but it might be less complicated solution (do not need to handle publishing, do not need to worry about overwriting the published version accidently and have better source control).
You can even use different conditions to load different pieces of code in this case (using CASE: or IF options).
For example: load portion of your script from File_1 on Monday and from File_2 on Friday....