This patch is intended for installation on top of Responder 9.1.2 SP1 (build 3597). This patch fully replaces previously issued patch #3608.
Functionality Included: This patch provides several changes and bug corrections.
Recommended Users: This patch would benefit all clients using Responder.
Notes: There are three separate files required for this patch, one each for Responder Client, Responder Web, and Responder Server.
When the user edits the Actual Status of a fault device (without returning it to Normal Status) using the Edit Fault tool, the behavior regarding the associated load points differs based on the fault device's confirmation status. Returning all phases to Normal Status results in a restoration, regardless of confirmation status.
Confirmed Fault: When the Actual Status on a confirmed fault is edited, the affected load points are restored. The restoration is reflected in the incident's history and, ultimately, the archive (assuming the incident is eventually closed). Any calls associated with restored load points are processed and callbacks created if requested.
Unconfirmed Fault: When the Actual Status on an unconfirmed fault is edited, the affected load points are corrected. A correction is not reflected in the incident's history or in the archive. If any customer calls are associated with the corrected load points, the calls will be re-submitted and corresponding single-premise incidents created. If you wish to restore a particular phase on an unconfirmed incident, it must first be confirmed. If the Actual Status and Confirmed fields are changed at the same time, the phase change is treated as a correction.
CNG25480 - Resubmit a call if the incident it is assigned to is restored with a time of operation before the call time.
Responder allows the dispatcher to enter a restoration time in the past. For example if the fault was restored at 6pm and the restoration logged in Responder at 7pm, the dispatcher can enter a restoration time of 6pm. In this case, if a customer call associated with that device is received later than 6pm (e.g. 6:30pm), a single-premise incident will be generated and the call associated with it. This ensures that calls received after a device is restored are addressed.
When configuring Responder Prediction Services (Miner.Responder.PredictionServices.exe.config), consider carefully before setting the attribute. The following describes how this attribute impacts the scenario described in CNG25480.
The attribute will impact incidents when a fault is restored with a past time of restoration and customer calls have been received since the time of restoration. For example, a three-phase transformer has its A phase restored in Responder Explorer at 7pm, but its time of restoration is 6pm (its B and C phases are still confirmed out). Between 6:14pm and 6:36pm, three calls are received from load points downstream of the transformer on its A phase. When the transformer is restored, these calls are re-submitted and single-premise incidents created. If this value is set to True, the transformer may be predicted out as soon as it is restored. If this value is set to False, prediction will skip over the confirmed fault device (the transformer) and look for the next unconfirmed device upstream.
MM25906 - Unconfirmed non-outage single premise incidents may now get subsumed into larger incidents. If the incident is restored with a backdated time, any calls (non-outage or outage) that came in after the restore time will be resubmitted. Non-outage calls that have been subsumed into outages will get a restore time if they were submitted before the time of restoration of the controlling incident device, just as outage calls are treated.
The following files are included in the patch and will replace existing files:
Extract installation executables:
Run the installation executables:
Responder Incident Device Management Enhancements Patch #3615 contains the following bug fixes:
For ArcGIS and ArcSDE issues, please seek assistance from.