ArcFM Desktop > Mobile - Desktop > Advanced Redliner > OPTIONAL: Create Login Database > Create or Import Graphic Favorites |
If your Mobile users will be placing redline graphics in the field, then you will need to populate the login or backdrop database with graphic favorites before sending it to the field machines. There are a few ways to do this.
Sample Graphics: The login database provided with the ArcFM sample data contains sample graphic favorites. You may choose to use these. No further configuration is required.
Create Graphics: Open the backdrop or login database in ArcMap and use the Graphics tab to create graphics. With an edit session started, select a graphic on the map, right-click the Graphics tab and select Create Graphic Favorite.
Import Graphics: You can use the ArcFM System Favorites tool in ArcCatalog to export graphics from an existing geodatabase and import that XML into your backdrop or login database. Note that the Graphics tab in the ArcFM System Favorites Manager does not display the graphic favorites in the database. Also, if you import graphic favorites into a database that already has graphic favorites (such as the Login database provided with the sample data), all existing graphic favorites will be overwritten.
When using either Basic and Advanced Redliner, your stored display must contain at least one valid layer on which your license allows an edit session. Your license determines the rules around whether your ArcFM Annotation feature class can reside in the same dataset as a geometric network, and whether that dataset can contain relationships:
Valid layers are required because both Redliner and Inspector must start edit sessions. To begin an edit session, your map must include at least one editable layer. This is true even for Basic Redliner, even though it cannot edit any features.
If all the layers in your stored display come from a single geodatabase, the order of the layers does not matter because ArcFM automatically uses valid layers to start the edit session. The layer rules for multiple geodatabases depend on which product you use: