General Patch for Responder - Patch #5941 for 9.3.1 SP1

 

This patch is intended for installation on top of Responder Client, Server, and Web machines running 9.3.1 SP1 (build 5881) and replaces previously released patches #5929, #5897, and #5884.

Functionality Included: This patch prevents SCADA incidents from rolling up downstream non-outage calls as well as a number of other enhancements. Please see the list of bug fixes below for more details on these changes.

Recommended Users: Clients who use Responder on 9.3.1 SP1 would benefit from this patch.

The following files are included in the patch and will replace existing files:

• Miner.Responder.Desktop.dll
• Miner.Responder.Framework.dll
• Miner.Responder.Model.dll
• Miner.Responder.Model.Switching.dll
• Miner.Responder.Presentation.Wpf.dll
• Miner.Responder.Presentation.Wpf.Switching.dll
• Miner.Responder.Processors.dll
• Miner.Responder.Explorer.exe
• Miner.Responder.Shared.dll
• Miner.Responder.Switching.InteropModule.dll
• Miner.Responder.Switching.InfrastructureModule.dll
• Miner.Responder.Switching.BaseTasksModule.dll
• SwitchingOrderArchiveReport.xslt
• SwitchingOrderReport.xslt

Installation instructions:

1. Download the patch installer Patch_931SP1_5941.exe to any location on your desktop machine.
2. Double-click the file to launch the installation.
3. At the installer dialog, review the readme information if desired. Then click 'Install Patch'.
4. When the installer dialog displays 'Completed', click the 'Close' button.

Required Configuration Updates for Patch #5929

If you have previously installed patch #5929 you can skip the following extra configuration steps.

Patch 5929 contains a change that adds to the database schema. In order to properly apply the changes, please use the appropriate scripts below (they are included in the zip file with the patch):

If you are running Oracle, please run the following upgrade scripts:

• QFE42168_Active_History_Tables_Oracle.sql
• QFE42168_Archive_Oracle.sql

If you are running SQL Server, please run the following upgrade scripts:

• QFE42168_Active_History_Tables_Mssql.sql
• QFE42168_Archive_Mssql.sql

Patch 5929 requires a couple of configuration changes; please apply the changes specified below:

On all Responder server machines, please open DatabaseSchemaConfig.xml and find the section that defines the RX_OPERATIONS table and then find following line:

<Column Name="SUMMARY" Caption="Summary" Length="200" Represents="Summary" />
          

Below that line, add the following line:

<Column Name="CONTEXT" Caption="Context" Length="200" Represents="Context" />
          

Next, find the section that defines the RX_OPERATIONS_HISTORY table and make the same edit as you did in the previous steps.

Next, open the ArchiveSchemaConfig.xml and make the same change as described above for the RX_OPERATIONS_ARCHIVE table.

On all Responder server machines, please open ExplorerRulesConfig.xml and find the line below:

<b:RuleClass Key="ValidateTagForInsert" Type="Miner.Responder.Explorer.ValidationRules.ValidateTagForInsert,Miner.Responder.Explorer" />
          

Below that line, add the following line:

<b:RuleClass Key="ValidateIncidentCauseChange" Type="Miner.Responder.Explorer.ValidationRules.ValidateIncidentCauseChange,Miner.Responder.Explorer" />
          

Optional Configuration Updates for Patch #5929

A new localizable warning message has been added for QFE41743. If you wish to localize this warning message, please follow the steps below on all Responder server machines:

Open your localized version of Miner.Responder.Explorer.Properties.Resources.rex and find the </root> tag. Just above that tag, add the lines below (localized as you need):

<data name="MsgCallTroubleTypeWillBeChanged" xml:space="preserve">

    <value>There are {0} calls with {1} = '{2}' assigned to this incident. Changing the incident's {3} to '{4}' will result in the {1} field being reset to '{5}' for these calls.</value>

</data>
          

If you already applied Patch 5897, then you can skip the following configuration steps:

Patch 5897 introduces a configuration point which lets you determine what should happen when you run the Update Population tool to count your customers by feeder AND you have a circuit which is multi-fed. If you would like to have the customer count set to 0 for each of these feeders then you don't need to make any configuration changes. If you would like to have customers fully counted on any feeder which has a multi-feed (i.e. customers will get counted once per feeder, increasing your customer count) then you can do the following:

• Edit the Miner.Responder.DataServices.exe.config file and search for the string

  <add key="useSwitchingOrderApprovals" value="true" />

• Add the following key below the one you just found:

  <add key="MultiFeedOptions" value="LogMultipleFeedPathsReturnAll" />

Patch #5941 contains the following bug fixes:

• QFE42838 - Responder - Incident Management -- SCADA incidents rollup downstream non-outage calls when they should not (#5941)
• QFE41546 - Need to be able to better support create fault, create switching operation, change fault and update population tools with multi-feeds (#5929)
• QFE41627 - Error in SO Simulation with Nested Incident (#5929)
• QFE41743 - Two issues with submitting multiple calls per customer and then changing the incident cause or device status (#5929)
• QFE42167 - Some tasks show the device in the summary field, rather than the task itself (#5929)
• QFE42168 - Switching task titles should be editable as in previous versions (#5929)
• QFE42169 - Should be able to send SO to approvals once assigned to incident (#5929)
• QFE42185 - Incident cause is not set to Planned when created from a switch order (#5929)
• QFE42186 - Using "View on Map" does not display correctly when some steps are placed on conductors (#5929)
• QFE42187 - Grouped steps show up with incorrect step numbers on Switch Order Report (#5929)
• QFE42173 - Feeder Manager Initialization parameters should be cached to improve performance (#5929)
• QFE41237 - Doing a phase correction when an incident is probable results in the incident being confirmed (#5897)
• QFE41294 - If you have a multifeed in your network, the count should not show 0 when running update population tool (#5897)
• QFE41114 - Invalid date/time fields entered on Switch Order still allow step execution (#5884)
• QFE41115 - If you have a multifeed in your network, the Update Population Information tool will stop (#5884)

Internationalization updates:
None.

For ArcGIS and ArcSDE issues, please seek assistance from ESRI Technical Support.