Require Cancel Reason

You can configure Responder Explorer to display a prompt requiring a reason for cancellation when you cancel an incident, device, hazard, or feature. To enable the prompt:

Configure the Responder Data Services configuration file (Miner.Responder.DataServices.exe.config) for any server machine that accesses Responder. This file is located in the Miner and Miner\Responder\Server folder. You may edit the file by opening it in an XML application (such as XML Spy) or by opening it in a simple text editing program (such as Notepad).

Do not edit XML files using a word processing program such as WordPad or Microsoft Word as it may corrupt your configuration file.

On the server machine, browse to and open Miner.Responder.DataServices.exe.config.

Look for the following XML:

	Copy Code
<appSettings> <add key="TelemetryService.Address" value="localhost:36745" />

Insert any or all of the following <add key> lines into the <appSettings> section:

	Copy Code
<add key="RequireCancelReasonIncident" value="true" /> <add key="RequireCancelReasonDevice" value="true" /> <add key="RequireCancelReasonHazard" value="true" /> <add key="RequireCancelReasonFeature" value="true" />

Copy Code

<add key="RequireCancelReasonIncident" value="true" />
<add key="RequireCancelReasonDevice" value="true" />
<add key="RequireCancelReasonHazard" value="true" />
<add key="RequireCancelReasonFeature" value="true" />

Set the value to true on the items you wish to prompt the user for a cancellation reason.

Save and close Miner.Responder.DataServices.exe.config. You may need to restart services to see this change.

In Responder, when they receive the prompt, users must select a reason for cancellation, and confirm the action.

If the incident has associated calls, the cancellation prompt is still required.

You may have this functionality configured from a previous release (prior to 10.2.2) by setting the CANCEL_REASON field to Visible=true on RX_INCIDENTS in the DatabaseSchemaConfig.xml file. This previous method resulted in an empty Cancel Reason column that appeared in Responder Explorer for every incident.

Instead, we recommend setting the CANCEL_REASON visibility to false in DatabaseSchemaConfig and utilizing the steps above to prompt users for a cancellation reason. This eliminates extra columns in Responder Explorer.

You can have both methods enabled, without issues, in Responder Explorer. Only one prompt for cancellation appears for each incident.