Mobile Client Workflows
The Mobile Client subtab, or workflow family, is the home of client-side workflows specific to the Mobile application. Some examples are the Approve, Open, and Reject workflows. Think of these client-side workflows as actions an individual might take on their individual mobile device while working with the application.
The default markup workflow contains a Field Assignment for the Mobile user followed by an Enterprise Assignment for the desktop GIS editor. An Approval assignment type is provided with the product, but not included in the default markup job workflow.
Available Tools
The functions, tools, and subtabs are largely the same between the Studio and Default Workflow Studio tabs. However, the Studio tab provides a few additional tools on its subtabs. Refer to the Studio topic in the ArcFM Solution Center Implementation Guide to learn about the additional tools.
The following buttons are available on all subtabs in Default Workflow Studio:
Revision history of a workflow is recorded and can be helpful to track changes made to different versions of workflows over time. Refer to the Default Workflow Studio topic to read more about revision history records.
Below is an example of a Mobile Client workflow, the Approval – Approve workflow.
Workflow Properties
| Property | Definition |
|---|---|
|
Name |
The title of your workflow. |
|
Minimum Client Version |
The minimum version of Editor required to execute this workflow. This field applies to autoupdater workflows on the ArcGIS Server subtab, and workflows on the Editor Client subtab. Drop-down values on the ArcGIS Server subtab begin with 2024 C1. Drop-down values on the Editor Client subtab begin with 2025 C1. We recommend leaving this field blank on all other types of workflows. |
|
Workflow Status |
Published — the workflow is published and represents the latest version of the workflow. Draft — the workflow is in draft form and not published. Retired — the workflow has been replaced by a newer version and this version is retired and no longer published. Example — this is a workflow example that is useful for copying and pasting into a new workflow as a template or starting point. |
|
Workflow Metadata Id |
The unique identifier on each version of a workflow that allows you to call a particular version. |
|
Workflow Ancestral Id |
This identifier designates the starting point of a workflow’s history, after which all versions maintain that Ancestral Id. |
|
Version |
The version number of the workflow. Useful in tracking the evolution of workflows as administrators make changes. |
|
Updated By |
The user name of the last person to modify the workflow. The OOTB workflows provided by Schneider Electric say Updated By Schneider Electric Team, or sometimes say none. |
|
Updated On |
The date the last workflow modifications were made. |
|
Expression Language |
The coding language that is used within the workflow. |


