Specify incident sharing

You can customize the default behavior of shared incidents. An incident is shared when it is responded to by multiple units, which cooperate in responding to the incident.

Note: You must have purchased FH Mobile Response Premium or Command Post to display and hide specific incident tabs. For information on upgrading from FH Mobile Response Basic to Premium, contact your FH sales representative.

  1. Choose Go → Config→ Options.

    The Options dialog box appears, displaying the Server tab.

  2. Click the Incident Share tab.

  3. Select or clear the following options as needed.

    ClosedAllow Changing Shared Fields

    If necessary, you can add customized fields to the Dispatch sub-tab that appears for each incident. These custom fields are shared with other units assigned to the incident.

    When you select Allow Changing Shared Fields, team members from other units can change the value in the shared fields as needed, and FH Mobile Response propagates the changed value to all the units.

    Note: Adding shared fields to the Dispatch tab is an advanced skill, requires specialized XML knowledge and understanding of values from the CAD system, and often needs assistance from technical support to implement. If you need assistance to add shared fields, contact your FH sales representative for more information.

    Clearing this option prevents modification of these fields.

    ClosedAllow Update Incident Resources

    Lets you choose whether or not to display or hide the Push Resource Changes to All Users button on the Resources sub-tab that appears for each incident.

    Note: The Allow Update Incident Resources option applies only to the Command Post version of FH Mobile Response.

    ClosedCan Update Incident Notes Field

    If necessary, you can add customized fields to the Dispatch sub-tab that appears for each incident. These custom fields can include a notes (incident narrative) field.

    Note: The ability to update a custom incident notes field on the Dispatch sub-tab depends on whether the integration between your CAD system and FH Mobile Response is one-way or two-way.

    If it is a one-way integration (such as with FH CAD Monitor), you are not able to change the incident data, even with a custom notes field on the Dispatch sub-tab.

    If it is a two-way integration (such as with CRIMES), if you have a custom notes field on the Dispatch sub-tab, and you select Can Update Incident Notes Field, other team members can update or add to the information in the notes field. The information is sent back to the CAD system, where it is then propagated out to the other units assigned to the incident.

    When you clear Can Update Incident Notes Field, other team members can not make changes to the notes field.

  4. Under Incident Location, do one of the following.

    ClosedSend updates to client computers sharing the incident
    1. Select Always Update to send updates to client computers sharing the incident if any information is changed with the incident.
    2. Select or clear Warn If Update Failed to indicate whether or not you receive an error messages if a change is made and attempts to update connected client computers fail.
    ClosedDo not send updates about the incident location

    1. Select Never.

      This ability is useful if you normally share incidents with other units, and you have an instance when you do not want to propagate a change.

      Example: You are conduction a training session with FH Mobile Response, and you do not want a changed location propagated to actual units in the field.

    2. Select or clear Warn If Update Failed to indicate whether or not you receive an error messages if a change is made and attempts to update connected client computers fail.

  5. Under Incident Name, do one of the following.

    ClosedSend updates about the incident location
    1. Select Always Update to send updates to client computers sharing the incident if any information is changed with the incident.
    2. Select or clear Warn If Update Failed to indicate whether or not you receive an error messages if a change is made and attempts to update connected client computers fail.
    ClosedDo not send updates about the incident location

    1. Select Never.

      This ability is useful if you normally share incidents with other units, and you have an instance when you do not want to propagate a change.

      Example: You are conduction a training session with FH Mobile Response, and you do not want a changed incident name propagated to actual units in the field.

    2. Select or clear Warn If Update Failed to indicate whether or not you receive an error messages if a change is made and attempts to update connected client computers fail.

  6. In Min Secs Between Weather Updates, type the minimum number of seconds allowed between weather updates within a shared incident.

    If an incident is configured to publish Internet or MET station weather, this value is the minimum elapsed time between weather updates to be published to the server.

    Note: This value overrides any other publishing frequency settings

    Example: If a MET station were configured to publish weather data every two seconds, the value in Min Secs Between Weather Updates takes precedence.

  7. Click OK.