Best Practice to "reset" Emergency Management Operations Solution but Retain Data

[COSPNWGuy]

Hello. I'm new to the Emergency Management Operations Solution. It looks very powerful. Could someone explain how the industry at large handles "resetting" this solution between events but still retain data? 

For some events, it might not be necessary to retain the data and layers could just be wiped, but for large scale things, data might be needed for later documentation processes (i.e. FEMA).  I would hope the answer is not to deploy the solution for each event that comes, as I know we will spend significant time configuring the solution for our needs. Thanks.

[JeremiahLindemann · Accepted solution]

Hi,

Yes, the solution is intended to be implemented and handle multiple incidents over the course of time without the need to redeploy for each incident.

Many of the layers have an "Active Incident" field (see attached).  By setting this to No will apply a filter so it isn't visible on the Emergency Information Manager or Dashboard. Some layers such as Critical Infrastructure or Shelters don't have this as you can manage the status of Open/Closed.

Recently batch editing just came to Experience Builder so it is on our roadmap in a future update to include this so you can select several features at once and set their Active Status to No- you could also extend the solution now using this new functionality.