ArcFM Desktop Developer Guide
Convert to Designer Objects
| ArcFM Desktop Overview > Designer Overview > Designer Objects > Convert to Designer Objects |
Use the ArcFM Solution Object Converter to convert your geodatabases to use Designer objects. The following fields will be added automatically to features in the geodatabase:
When these fields are created, the Object Converter also assigns the appropriate field model names to them.
You may choose to not create these fields by modifying their registry settings located in the Registry at the following location: HKEY_LOCAL_MACHINE\SOFTWARE\Miner and Miner\Designer8\Object Converter\. For any field you do not want to be created, modify its registry setting to be 0. Fields with a registry setting of 1 will be created. In the figure below, the DesignID, WorkFlowStatus, and WorkFunction fields will be created. The WorkLocationID and WorkRequestID fields will NOT be created.
NOTE: The WorkFunction field is REQUIRED. There is no registry key to omit this field.
Figure 1, Registry settings for Object Converter
Once your data is converted, Designer objects can be assigned automated behaviors that are triggered by create, update, and delete events during editing sessions. The Configuring ArcFM Solution online help in ArcCatalog offers more information about using the ArcFM Solution Object Converter.
In addition to creating new fields, executing the ArcFM Solution Object Converter also converts the existing GeoObjects to Designer custom GeoObjects. Only Designer custom GeoObjects may be used in the design environment. These GeoObjects are subclassed from Esri's standard GeoObjects and function as standard GeoObjects to ensure that no core ArcMap functionality is lost. Below are the Designer custom GeoObjects:
These objects are discussed further in the COM Library Reference section of the ArcFM Solution Developer Help.
This tool also creates and populates the following domains which are required by Designer:
