Grid Filters

To customize these filters, you’ll modify the XML for the dockable window in ControlStylesConfig.xml using VB Script. You’ll need to know which dockable window you’re modifying. Below are the dockable windows with grid filters that may be customized. These names are as they appear in ControlStylesConfig.xml. The name in parentheses corresponds to the name of the window in the user interface.

IncidentGrid (Incident grid for user’s regions)
IncidentGridAllRegions (Incident grid for all regions)
AlertsGrid (Alerts)
Pending EditsGrid (Pending Operations)

Create a Custom Filter

This topic walks through an example of adding a filter that displays all of the crews associated with a particular company. This filter resides on the Alerts (AlertsGrid) dockable window in Responder Explorer.

Open ControlStylesConfig.xml. By default, this file is installed here: C:\Program Files (x86)\Miner and Miner\Responder\Server.
Search for the control (dockable window) that holds the filter you want to customize (e.g., IncidentGrid, IncidentGridAllRegions).
Each control has tables associated with it. Filters must be associated with the first table under the control. The list below shows the control followed by the initial table.
- IncidentGrid: RX_INCIDENTS
- IncidentGridAllREgions: RX_INCIDENTS
- AlertsGrid: Alerts (not in geodatabase)
- PendingEditsGrid: PendingEdits (not in geodatabase)

The tables referenced by the AlertsGrid (Alerts) and PendingEditsGrid (PendingEdits) controls do not correspond to tables in the geodatabase. Instead, their columns are listed in ControlStylesConfig.xml. For example:

<Table Represents="PendingEdits" Editable="false">
 <Columns Key="">
  <Column Represents="TimeStarted" IsSortColumn="true" />
  <Column Represents="OperationID" Visible="false" />
  <Column Represents="Substation" Visible="false" />
  <Column Represents="Feeder" Visible="false" />
 </Columns>

Use these columns to create your filter.

Create your filter using the available columns (either in the geodatabase table or in the <columns> section). Be sure to place the <FilterFinders> tag immediately after the </Appearances> tag. Below is an example filter that displays all incidents in the Ithaca substation.

<FilterFinders>
 <FilterFinder Key="IncidentDevices_Substation" FilterFinderType="Both">
  <Evaluator>Vbs:[Substation] = 'ITHACA'</Evaluator>
  <Caption>Ithaca Substation</Caption>
  <Description>All incident devices on the Ithaca Substation</Description>
 </FilterFinder>
</FilterFinders>

Note that VB Script is case-sensitive. The casing in the example above is correct. The following casing will fail:

<Evaluator>VBS:[Substation] = "ITHACA"</Evaluator>

Figure 1, Sample filter in the user interface

Attributes

Key: This is a unique value that identifies the filter.
FilterFinderType: This is the type of filter and determines where in the user interface it appears. This attribute is set to "Filter" for basic filters. It can be set to "Finder" to appear in the Search dialogs. Use "Both" if you want your custom filter to appear in both places.
IsDefault: This attribute identifies whether the filter is the one displayed by default.
Evaluator: This is the criteria used by the filter. See the Evaluators section on this page.
Caption: The text displayed in the user interface.
Description: A brief description of the filter. This text is not displayed in the user interface.