Allow Dispatcher Edits to Mobile Incidents

By default, a dispatcher cannot perform most edits to an incident that has been assigned to a mobile crew. The dispatcher may assign a restoration or switching order to a mobile incident (but not execute the operations) as well as edit non-critical data such as Remarks, Cause and the Time Restored Estimate.

The dispatcher can use the Take Control of Mobile Incident tool to add faults, location features and hazards. This tool temporarily removes the incident from the field to prevent a dispatcher and a field editor from simultaneously editing the same incident and causing conflicts.

Alternately, you can perform the customization discussed on this page to allow the dispatcher to make edits to a mobile incident without using the Take Control of Mobile Incident tool. Be very careful doing this, however. It is possible to create a scenario in which the field editor and the dispatcher simultaneously edit the same incident. This will cause conflicts that Responder Mobile cannot resolve.

If you choose to implement this optional configuration, you MUST establish a work or business process that prevents conflicts. This optional configuration makes it possible to create conflicts between the field and the Enterprise. These conflicts may be resolved only by using one user's edits and dismissing the other's edits.

For example, if a dispatcher edits a device and the field user edits the same device, one user's edits will be saved and the other user's changes will be lost.

Conflicts may not even generate an error message.

To allow the dispatcher the ability to edit and add devices remove the MobileFieldUpdate attribute from specific tables in the DatabaseSchemaConfig.xml file. Note that this creates the possibility for conflicts. Review the note box above before continuing.

Open DatabaseSchemaConfig.xml for editing. By default, this file is installed here: C:\Program Files (x86)\Miner and Miner\Responder\Server.
The MobileFieldUpdate attribute has been set by default on the following tables. Remove this attribute and its value (MobileFieldUpdate="PreventUpdates") on any table you want the dispatcher to be able to edit for mobile incidents.

Table	Description
RX_INCIDENT_DEVICES	Remove MobileFieldUpdate setting to allow the dispatcher to add and edit fault devices on mobile incidents.
RX_INCIDENT_FEATURES	Remove MobileFieldUpdate setting to allow the dispatcher to add and edit location devices on mobile incidents.
RX_HAZARDS	Remove MobileFieldUpdate setting to allow the dispatcher to add and edit hazards on mobile incidents.

Save and close DatabaseSchemaConfig.xml.

You may use the Prevent Field Edits page to remove some editing capability from field editors and possibly avoid some editing conflicts.