Submit Rules

Responder uses submit rules to control the logical flow of the application. For example, a user is required to enter a time and user name when restoring an electric device. A submit rule enforces this requirement by keeping the OK button disabled until the required information is supplied.

While most submit rules are necessary, Responder does provide several submit rules that may be enabled or disabled. You may enable/disable ONLY the submit rules listed below. Do not disable any other submit rules. The following rules may be enabled or disabled in the SubmitRulesConfig.xml file which is installed here: Program Files\Miner and Miner\Responder\Server\. To enable a submit rule, simply remove the characters that comment it out of the XML (). To disable, comment it out.

Submit Rule	Description	Default Setting	OK to Modify?
ArchiveIncidentHistoryRule	This rule is enabled by default and has two properties: ArchiveCanceledIncidents: Copies cancelled incidents to the appropriate Archive tables. Set to "false" by default (incidents are NOT copied to the Archive tables). DeleteHistory: Use this property to delete an incident from the History tables when it is added to the Archive Tables. By default this value is set to "false" (incidents are retained in the History tables).	Both properties are set to False	Yes
PopulateUserCreated	Populates the User_Created field in all tables.	Enabled	Yes
PopulateUserUpdated	Populates the User_Updated field in all tables.	Enabled	Yes
PreventUpdatesToMobileCrewTasks	Prevents a dispatcher from editing an incident that has been sent to a crew in the field. Warning: If you disable this submit rule, you MUST establish a work or business process that prevents conflicts. Disabling this rule makes it possible to create conflicts between the field and the Enterprise. *Telvent recommends against disabling this submit rule.	Enabled	Yes *Read warning in Description column first
RemoveTagsPlacedViaSwitchingOrderWhenCanceled	Removes tags that have been placed as part of a switching order when that switching order is cancelled.	Enabled	Yes
SecureDownstreamHazards	When all affected phases are open, this submit rule identifies downstream hazards on the open phases and designates them as clear or safe to work on.	Disabled	Yes
UpdateHazardWhenCrewWorking	Secures a hazard when the crew is working.	Disabled	Yes
UpdateLeadCrewAssignmentAdded	Updates the Lead Crew field based on crews added.	Enabled	Yes
UpdateLeadCrewAssignmentModified	Updates the Lead Crew field based on crews edited.	Enabled	Yes
UpdateLeadCrewAssignmentDeleted	Updates the Lead Crew field based on crews deleted.	Enabled	Yes
ValidateCrewAssignability	Prevents a crew from being dispatched to multiple incidents at the same time. The crew must complete an incident before being dispatched to another. It can have a Dispatched or Working status on only one incident at a time. Disable this rule to be able to dispatch a single crew to multiple incidents.	Enabled	Yes
ValidateIncidentDeviceTimeOpChange	This rule determines the circumstances under which the Time of Operation field may be edited. The Time of Operation field may be edited only in the following situations: On an unconfirmed incident, you may edit the Time of Operation value either forward or backward (in time). If an incident is confirmed and has a single device with no operations, you may edit the Time of Operation value either forward or backward (in time). If an incident is confirmed and has a single device with operations, you can edit the Time of Operation, but you MUST also update the phasing. If the phasing is updated, the Time of Operation can be edited provided it is greater than or equal to the existing time of operation. If an incident is confirmed and has multiple devices, you may edit the Time of Operation on either device. However, you MUST also update phasing. If phasing is updated, the Time of Operation must be greater than or equal to the existing Time of Operation for any device on the incident. If you wish to change this rule (disable it or modify the parameter), it must be modified in SubmitRulesConfig.xml and ExplorerRulesConfig.xml. Warning: If this submit rule is disabled, there are particular scenarios with backdating that may cause issues with load point outage and restoration times.	Enabled	Yes *Read warning in Description column first
ValidateIncidentDeviceTimeOpOnStatusChange	This rule impacts the Time of Operation for incident devices that are undergoing a phase change or devices that are added to an existing incident. This rule prevents these devices from having a Time of Operation that is earlier than the Time of Operation for any existing device on that incident. This rule has a parameter called ApplyToConfirmedOnly. When set to True, this rule applies only to confirmed incidents. When set to False, this rule applies to all incidents. Default=True. If you wish to change this rule (disable it or modify the parameter), it must be modified in SubmitRulesConfig.xml and ExplorerRulesConfig.xml. Warning: If this submit rule is disabled, there are particular scenarios with backdating that may cause issues with load point outage and restoration times.	Enabled	Yes *Read warning in Description column first
VerifyTagsAllowIncidentCancelation	Throws an error if cancelling or deleting an incident device will cause the device will violate a tag as it returns to a normal state.	Enabled	Yes
VTextOutageAlert	With proper configuration, this submit rule enables sending a text message based on configurable parameters. Note: In addition to enabling this rule, edit the vtext.txt file which is installed here: Program Files\Miner and Miner\Responder\Server\ with the appropriate sender, receiver, and subject information.	Disabled	Yes