Answered
AIMS System Administrator
Seeing if someone out there knows the answer to this.. I hate experimenting.
I have a new version of an app that I am ready to roll out (currently saved in the main department). There is an existing (slightly different) version that still has some outstanding dispatches in play in another department. I do not want to change the name of the new app. I just want to share it with that same department as a replacement. If assigned users (to the old app) have dispatches in their queue, can I retire the existing with the dispatches still out there? I am hoping the (retired version) dispatches will stay in their queue and eventually once they are all completed the old app will just be retired and fade away.
0
Comments
Please sign in to leave a comment.
Howdy Keith,
Thanks for taking the time to reach out to us! Retiring an app will prevent new dispatches (or submissions) from being made.
However, any pending dispatches or submissions will remain in the user's queue until they are completed. Once all pending dispatches or submissions are completed, the retired app will no longer appear in the user's available apps.
I hope this helps!
Thanks Chip.
Sounds like what I am thinking will work. I am afraid I am going mess up the current dispatches that are already out there. I am just going to change it to retired and see what happens. If the dispatches are in the received status, I think as long as the user doesn't clear the data from their device all should be fine. The closer I get to April the less damage I can cause.
I plan to roll out the new version with new dispatches last week of March. If I don't retire the one with the same name before then, I think it will cause an issue with dispatch upload because it'll see two apps with the same name.