Add and configure Create Field Maps Task

Available with Workflow Manager license.

In ArcGIS Workflow Manager the Create Field Maps Task step allows you to create a task to help manage and track field work associated with your job using ArcGIS Field Maps. The tasks capability in Field Maps is designed to help you manage and track work efficiently in the field. In a task-enabled feature service, each feature shows up as a task item on an interactive list in the Field Maps mobile app.

When the Create Field Maps Task step is run, Workflow Manager automatically creates a new task in your task-enabled feature service. The step also automatically updates the task properties with values specified in the Step Details panel.

A job must have a defined location for the Create Field Maps Task step to run. Each task has a point, polyline, or polygon geometry, which it inherits from the job location. If the task location is a point and the job location is a polyline or polygon, the centroid of the job location becomes the task location. If the task location is a polyline or polygon, the job location must be the same geometry type.

Optionally, Workflow Manager can place a webhook dependency on the job, which is automatically released when the task status meets conditions specified in the Step Details panel. To do this, the Create Field Maps Task step requires a webhook connection to be created with the task-enabled feature service. This allows Workflow Manager to receive updates on the task status. A webhook dependency is automatically added to the step that follows the Create Field Maps Task step.

To use webhook dependencies in the Create Field Maps Task step, you must enable the ArcGIS Workflow Management organization extension.

Tip:

The webhook dependency can be viewed on the Holds tab, in the Dependencies section.

Configure the step

Complete these steps to configure the Create Field Maps Task step:

1. Create or edit a workflow diagram to access the Step Library panel.
2. Drag Create Field Maps Task from the Step Library panel to a connection arrow of a step on the workflow canvas.

   Learn more about adding steps to a workflow diagram.

   The Step Details panel appears.

3. Provide a name for the step in the Step Name text box.
4. Choose a feature service from the Feature Service drop-down menu.
5. If you don't have a feature service associated with the workflow diagram, add a feature service data reference.
   1. Click Add data reference from the drop-down menu.

      The Add data reference dialog box appears.

   2. Add a data reference by doing one of the following:
   • Browse for item—Browse and choose from a list of items on the current portal.

     Tip:

     You can refine results by applying filters and tags.

   • Enter item ID manually—Provide the item ID and reference name in the Item ID and Reference Name text boxes. The item is automatically validated by Workflow Manager, and the data reference type is set.

   If the data reference cannot be validated, you must provide the item ID to a valid data reference that matches the set data reference type.

   Learn more about managing data references

6. Click the Layer Name drop-down arrow and choose the task-enabled layer where you want to create the task.

   Caution:

   • A job must have a defined location for the Create Field Maps Task step to run. If the task location is a polyline or polygon, the job location must be the same geometry type.
   • The feature service must contain at least one task-enabled layer to be configured with the Create Field Maps Task step.
7. Click the Change Input Type drop-down arrow and choose an input type for the Task Type combo box.
   • Selection—Choose a task type that corresponds with the type of task you want to create from the Task Type drop-down menu.
   • Arcade—Provide an ArcGIS Arcade expression to reference a domain code for a task type configured in your task-enabled layer.
8. Optionally, configure a task property for the step to update when the task is created.
   1. Click Add Task Property.
   2. Click Show default value to define the default value for the property.
   3. Choose one of the following options:
      • Value—Provide a static value.
      • Arcade Expression—Provide a dynamic value using an Arcade expression.
   4. Provide a default value for the property in the Value or Arcade Expression text box.
   5. Optionally, click Add Task Property and repeat the steps to add more properties.

      Tip:

      To delete a task property, hover over it and click Delete Property.

   6. Optionally, hover over a property, click Reorder Property, and drag it to the desired location to reorder properties.
9. Optionally, add a webhook dependency to the step.

   License:

   This functionality requires a license for the ArcGIS Workflow Manager Server Advanced role.

   1. Check the Add Webhook Dependency check box.
   2. Choose a webhook connection from the Webhook Connection drop-down menu.

      Note:

      To add a webhook dependency, at least one webhook connection must be configured with the feature service selected in step 4.

   3. Under Release Condition, define the criteria that the task status must meet for the dependency hold to be released.

      The release condition should be a status that indicates the field work has concluded. For example, Task Status = Completed.

      Tip:

      Multiple combinations of release conditions can be managed using the AND and OR logic operators. For example, if two release conditions are configured and the OR logic operator is used, the dependency hold is released when the task status matches either value. If the AND logic operator is used, the dependency hold is only released when the task status matches both values.

   4. Click Add Release Condition to add more release conditions.

Return value

When the step is completed, its return value is stored to indicate the result of the step. The return value can be immediately evaluated using paths to determine the next steps in the workflow. You can also retrieve the return value for completed steps throughout the workflow using Arcade expressions.

The following table lists the step's return values:

Return value	Description
S000001	The step completed successfully.
F000001	The step failed.

Output value

When the step is completed, its output value is stored and can be used to determine the path the workflow follows or can be used as inputs for other steps throughout the workflow. The following table lists the step's output values:

Output	Description
taskObjectId	Returns the Object ID for the task created using the Create Field Maps Task step
taskType	Returns the coded value for the task type for the task created using the Create Field Maps Task step
taskGlobalId	Returns the Global ID for the task created using the Create Field Maps Task step