Home > WebEOC > Admin Guide > Dual Commit > Incident Mapping

Incident Mapping

Before data can be shared using Dual Commit, the way in which incidents are handled and synchronized must be configured on the target server. The target server can either automatically create a matching ad hoc incident for incoming Dual Commit entries or queue incoming entries until manually mapped to an existing incident. After an incident has been mapped, all queued dual commit entries automatically post to the mapped incident.

To set the incoming queuing option
  1. In the Admin window, go to Process: Dual Commit. The Dual Commit page opens.

  2. Click the Actions button, and then select Incoming Dual Commit Options. The Edit Incoming Dual Commit Options page opens.


  3. Do one of the following:

    • To create a new incident on the target system with the same name as the host server, select Queue all incoming dual commits until the incoming incident....

      Note: If you select this option when using remote boards, other WebEOC systems are not able to post messages or see those boards until their incidents have been mapped.

    • To create a new incident on the target server with the same name as the incident on the sending server, select Create incident if it does not exist.... Messages are posted under the newly created incident.

  4. Click Save.

Last modified



This page has no classifications.