Markup Considerations
The customer-managed Markup Service option is only available for existing ArcFM Mobile implementations already using this option. Refer to the Customer-Managed Markup Service topic for more information.
-
ArcFM requires configuration of the Markup Service. Refer to the Configure Markup Service for more information. For system requirements, refer to GIS – Supported Versions – ArcFM Mobile Services, Portal, and Tools on myArcFM.
-
Markups require a dataset with a storage type of ST_GEOMETRY or SDO_GEOMETRY for Oracle databases or GEOMETRY for SQL Server databases. If your geodatabase uses either SDELOB or SDEBINARY, you must either enable a new configuration keyword on your geodatabase, or you will need to migrate your storage type. For more information about configuration keywords, refer to Esri’s Configuration Keywords for Enterprise Geodatabases article.
-
Will you use the default markup palette provided with ArcFM? If so, refer to ArcFM Markup Sample Data on myArcFM for installation steps.
-
If you create custom markup palettes, palette design and configuration are required. Refer to the Configure the Markup Service topic for more information.
-
If your markup map service operates over HTTPS, you may need to install the correct certificate on all Mobile client machines for markups to function properly. Cloud services deployment also requires HTTPS, so ensure that you have it set up before considering this type of deployment.