This page outlines what's new in the current release. If you are upgrading from more than one release prior, it is important to review all What's New pages for each release between your original release and the release to which you are upgrading. You do not need to install each release between, only follow the upgrade steps and review the What's New pages. The current release installer will provide all functionality enhancements since your original version.
This page outlines the upgrade steps for various ArcFM Solution applications. These are basic required upgrades and do not include configuration for new tools. If you are skipping release versions (e.g., upgrading from 9.3.1 to 10.0.1), note the following:
- DO NOT install each release in between. Only install the version to which you're upgrading.
- DO review the upgrade steps for each release in between the original version and the one to which you're upgrading. Perform any additional upgrade steps outlined on these pages (e.g., recommended Esri patches, Responder upgrade steps, Process Framework database upgrades, etc.).
- DO run the Create/Update ArcFM Solution System Tables tool only once. There's no need to run it multiple times.
- DO run the Upgrade ArcFM Solution Database tool only once. There's no need to run it multiple times.
- DO review the What's New page for each release in between. These pages will outline the new functionality available to you.
- DO review the Migration pages for each release in between. These pages will let you know if you need to compile custom code.
This section provides a list of API changes for 10.0.2. Be sure to review the API changes and perform any migration steps for releases between your original version and the one to which you are upgrading.
- Ensure that your hardware and software meet the ArcGIS system requirements. These requirements are available at http://support.esri.com/.
- Ensure that your hardware and software meet the ArcFM system requirements defined at the ArcFM Solution Supported Versions web page.
What's New in Responder?
- Performance Enhancements: Responder has improved data throughput as well as end-user performance by changes to Responder Explorer grid and tree data management, server-side caching, Web Prediction settings, and Message Router.
- Previous releases used the Length attribute in the schema configuration to set the length of the field. With the release of 10.0.2, each field length in the schema matches the field length in the database, and this attribute is no longer needed. The Configuration Batch Script will remove this attribute. However, if it exists in the configuration file, it won't impact anything.
- The Responder team collaborated with Microsoft to identify ways to optimize geodatabase performance on a SQL Server geodatabase. One result of this collaboration is a tool that generates a SQL script that changes NUMERIC data types to INT data types on columns in Responder tables. This optional tool (SqlNumericColumnsUpdateScriptGenerator.exe) may be run along with the 10.0.2 Responder upgrade scripts to improve performance.
- A new Change Normal State tool has been added for users with the Senior Dispatcher role. This tool allows the user to change the Expected State in Responder to match the current conditions in the Geodatabase and to accept these conditions as the new "Normal" state.
- Responder Line Display now implements as a separate service. Configuring and enabling this service allows you to include the display of de-energized, multifed and backfed lines on the map. In addition, you can configure Responder Line Display to change visibility based on scale and to exclude the display on certain feature classes. This display now performs asynchronously after the completion of incident operations in Responder Explorer. This service also includes a new tool to manually re-process line displays for incidents in Responder Explorer.
- New reports and domains are now available in Responder based on RUS Bulletin 1730A-119. You can now track the type of equipment and voltage on an incident. With the CAUSE_RUS and WEATHER_RUS domains, you can also select from more Causes and Weather options based on RUS standards, when creating or editing incidents.
- You can run three new reliability reports (SAIDI by Cause Code, SAIDI by Cause Code - Summary, and Outage and Minute Count by Cause Code) from Responder Archive Explorer.
- Custom filters and finders no longer support VB Script. The Filters section of the Responder Customization Guide provides detail on how to upgrade your existing tree filters to use Data View Filter (DVF) instead of VB Script. This section also outlines how to create custom tree and grid filters. If you have custom filters on grids (e.g., Incidents grid), no upgrade is required.
What's New in ArcFM Desktop?
- The Attribute Autoupdater developer sample received a new class. This class provides an Auto Phase Assign autoupdater that compares the Phase Designation values of a feature and its connected feature. If the Phase Designation values do not match, the AU presents a dialog that asks the user to choose the phase to assign to both features.
- A new class was added to the Special Autoupdater developer sample. This class provides an autoupdater that creates TransformerUnit related objects based on the PhaseDesignation field of a newly placed Transformer feature.
- The Next Upstream Protective Device Trace finds the nearest upstream protective device to any edge location you choose. This trace provides visual indications of places from which you previously traced. That lets you keep track of where you’ve been and plan where you’re going.
- The Isolation Protective Device Trace locates both the nearest upstream and downstream protective devices. This trace also clearly displays features you've already located so you can isolate protective devices of interest.
- Whether you’re using directional or non-directional tracing, you can now trace all or any subset of fibers in a cable, or choose exactly which fiber objects to trace. This also relates to tracing any group or subset of children to a traceable object (e.g., channels within a fiber path).
- For directional linear tracing, there’s an easy two-click method for selecting a line and its trace direction. For directional point tracing, you can now choose different trace directions for multiple objects at once—in the simple context of other objects’ locations.
- You now have the option to disable connection deletion warnings that display when disconnecting items in Connection Manager.
- New in the Fiber Settings menu is the option to create default attenuation values for connection types.
- Fiber System Settings are now available in ArcCatalog. This dialog allows an Administrator to set the default settings for all users. Fiber User Settings, when modified, will override Fiber System Settings.
- The Fiber Trace Report was overhauled for far better readability. Now it’s easy to interpret reports and gather accurate data on length and loss values of objects in your fiber network.
- The Connection Manager has improved performance.
- The Special Autoupdater developer sample received a new class. It now includes the Sample Update Fiber Object autoupdater that may be used with Fiber Manager. This autoupdater maintains a text field that indicates the connectable object's availability based on its status in the Connection Manager.
- The Open Design functionality has improved performance. Opening a design may now take significantly less time.
What's New in ArcFM Server?
- ArcFM Server returns ArcFM field order and visibility by subtype.
- Complex edges are displayed in trace results.