Craig -
This came up while planning for a field exercise this week.
I can understand the challenge of keeping things simple in the user interface but after working with a number of stakeholders, they've agreed they want a way to do this as a dispatcher.
Here is one comment:
"That seems really inefficient. What if you make a mistake on one of your dispatches, now you have junk stuff in there you can't get rid of. I can see them wanting to have a permanent record of dispatched but there should be some sort of archive. That is just clunky".
Potential Solution
What about a field in the assignment feature layer called "Archive"? When the end user selects assignments they want archive, they select "Archive" from a dropdown and get prompted "are you sure?". This just changes the entry under "Archive" to "Yes". The app or (feature layer view used in the app) has a filter to just not show the Archive = Yes features? This is similar to the vetting function in the now deprecated Crowdsource Story Map.
I am sure you've thought of many possibilities, but this seems like a logical approach and would benefit the end user greatly without losing any backend data.
- Paul