Designer Field Editors

The Customize ArcFM section discussed custom field editors for use in ArcFM. This section focuses on creating custom field editors for use with Configuration Editors and Extended Data, both of which are specific to Designer.

Items in a design might have ancillary data that does not affect the state of the design environment. This data might be important where the WMS is concerned, but is only considered as extended data by Designer. Extended data can be passed back and forth between the WMS and Designer via the design XML. Once in the design tree, custom editors can manipulate the data and the changes can be saved back to the WMS.

In the design environment, it is possible for a geographic feature to represent multiple Compatible Units (CUs). While Designer supports the assignment of multiple CUs to features using the existing user interface and drag/drop functionality, custom Configuration Editors can provide special functionality specific to the needs of the implementation. Configuration editors provide an alternative user interface on ArcFM/Designer’s Attribute Editor where the user can assign multiple CUs to a GIS unit.

A Custom Field Editor can come in one of two forms: a Metadata Editor or a Configuration Editor. These two types of custom field editors are implemented and are integrated with the ArcFM Attribute Editor in the same way, but perform different tasks.

This section discusses extended data, CU configurations, and the custom field editors that can be written to allow the user to edit these items.