Beta:
While you can prepare and configure tasks in the Field Maps Designer web app to manage and track work efficiently in the field, the tasks capability is in beta in the Field Maps mobile app. See How do I access tasks in the Field Maps mobile app for more information.
Tasks in Field Maps are highly customizable, allowing you to create task management workflows that support your specific field operations, enhancing accountability and improving overall project management.
You can configure tasks in the following ways:
- Configure the form
- Customize task symbology
- Configure task actions and layouts
- Manage filters for to-do lists
Configure the form
Forms in feature layers provide a structured method to input and manage detailed information for features.
Tasks are features. When you create a new feature in your task-enabled layer, the form allows you to enter all the necessary information about that task. You define and configure the information for your tasks using the Forms tab in Field Maps Designer.
When you create a new task-enabled layer, the following form elements are added to the form by default:
- Task type—Type of task.
- Assignee—Person assigned to the task.
- Status—Status of the task (for example, In progress, Complete, etc.).
- Priority—Priority of the task (for example, Low, High, Critical, etc.).
- Due date—Due date of the task.
- Description—Description of the task.
- Notes—Notes taken while completing the task.
Task type, Assignee, and Status are required fields and control the display of to-do lists in the Field Maps mobile app.
You cannot remove required fields from your new task-enabled layer. You can change the display name of required fields but you cannot change the field name. If you choose to enable tasks on an existing layer, build the following required fields into your form with the correct field names:
You can remove or keep and configure any of the other default fields that are provided when you create a new task-enabled layer. Additionally, you can add and configure your own custom fields to the form to ensure your task layer accurately supports your project needs.
Note:
To configure the tasks form, you must have access to the web map and associated layers. See Data access and editing.
Task type field
The required Task type field allows you to define the types of tasks suitable for your specific field workflows in the map. You must configure at least one task type for task functionality to work in Field Maps.
To configure the Task type field values (coded value domain), complete the following steps:
- Select the tasks layer in your map in Field Maps Designer and click the Tasks tab.
- Click Task Settings.
- Click Edit
next to Type in the Task Values section.The List of values window opens, where you can add the different types of tasks associated with the feature layer. A placeholder Task Type 1 is listed by default.
The Label is the value displayed in the form, and the Code is the value stored in the layer.
- Add task types to the list and click Done.
Note:
Task types can also be edited from the Forms tab. In the Forms tab, you can drag a CSV of values into the window to upload the coded value domain list.
Assignee field
The required Assignee field is essential for specifying which workers can be assigned tasks in the map. Configuring this field allows you to assign tasks to specific workers or let them view and pick up unassigned tasks. You can use the Assignee field to track who is working on specific tasks and who has completed them—promoting accountability, efficiency, and maintaining a historical record of task assignments in your field operations. You must add at least one worker into the Assignee field values for tasks to work.
To configure the Assignee field from the task settings, complete the following steps:
- Select the tasks layer in your map in Field Maps Designer and click the Tasks tab.
- Click Task Settings.
- Click Edit next to Assignees in the Task assignee section.
The List of values: Assignee window appears, where you can add the workers on your team who can be assigned a task. There are three ways to add assignees:
- Add the assignees into the fields by typing them in one at a time.
- Click Select from organization to add users directly from your organization or from partnered organizations.
The Label value can be any name and the Code value must be an ArcGIS username. This ensures that, when a task is assigned to a mobile worker, it appears on their personal to-do list in Field Maps.
- After you have added your workers, click Done.
Note:
You can also configure the Assignee field in the tasks form. However, the option to add users directly from your organization is not an option in the form area.
Tip:
Create a group in your organization for mobile workers that will be working on the project. You can quickly add all those associates into the Assignee field from the Select from organization option under Task Settings.
Status field
The required Status field records the progress of each task, such as whether it is unassigned, assigned, in progress, or completed. This field is important for tracking the current state of tasks, ensuring that mobile workers and managers can easily monitor task progress and manage workloads effectively.
You can immediately get started using tasks with the Status field default values, or you can add your own custom status values to better meet the specifics of your field workflows.
When you create a new task-enabled layer in Field Maps, the following default values are provided in the Status field:
| Status Label | Status Code |
|---|---|
Unassigned | 0 |
Assigned | 1 |
In Progress | 2 |
Completed | 3 |
Some examples of status customization in a utility inspection workflow scenario could include:
- Unassigned—The task is created but not yet assigned to a worker.
- Assigned—The task is assigned to a specific worker.
- In Progress—The worker is actively performing the inspection.
- Paused—The inspection is temporarily halted, perhaps due to weather conditions or waiting for additional resources.
- Review—The inspection is completed, and the task is moved to a QA reviewer for approval.
- Completed—The QA reviewer has approved the inspection, and the task is marked as finished.
Note:
You can configure the Status field in the form or on the Task tab in the Task Values section under Task Settings.
Status code values (in the esritask_status field) are used to configure the expressions that control:
- The actions the mobile worker can perform as they work with a task.
- The filters that determine which to-do lists a mobile worker can see.
If you change any status codes in the Status field, you must modify any Arcade expressions that reference the status field values and ensure they are referencing your updated codes for your workflows operate correctly.
For example, if you change the Completed status code from 3 to 4, update the Arcade expression in the In Progress task action layout to reference the new value. This ensures that when a mobile worker taps the Finish button, the status updates to Completed.
By understanding and configuring task actions and layouts, you can create flexible and efficient workflows customized for your field operations.
Note:
For more details on the required fields, see Understand the tasks information model.
Adding and configuring custom fields
You can add and configure custom fields in the tasks form in Field Maps, just like you do with data collection forms. This flexibility allows you to customize the tasks form to meet your specific workflow needs, ensuring all necessary information is captured when a new task is created.
For example, you might include fields like Estimated Time to Complete for scheduling and resource allocation, or Materials Needed to ensure workers have everything required to complete the task.
Forms vs. pop-ups in tasks
In the feature layer, pop-ups and forms serve distinct purposes. Understanding these differences will help you to design the task creation and task completion experiences for your projects.
Forms—The form is used for entering and managing data. Forms are editable and allow for data entry and updates.
Pop-ups—The pop-up displays read-only information about a feature in the map. Pop-ups are used to present data without allowing modifications.
Forms and pop-ups show up in tasks in the following ways:
Forms—In the tasks model, forms are used to create or update tasks. Task forms can be built and configured in Field Maps Designer or Map Viewer. You can customize the form for your specific workflow needs, adding and configuring fields to ensure all necessary information is captured when a task is created or updated.
For more information about the tasks form and default fields, see Configure the form.
You can create and update tasks for your mobile workers in multiple ways. To learn more, see Create and manage tasks.
Pop-ups—In the tasks model, the primary role of the pop-up is to display task information to the mobile worker. When a mobile worker opens a task in the Field Maps mobile app, the information presented to them about the task is the information that was provided and designed in the task layer’s pop-up.
When you create a new task-enabled layer in Field Maps Designer, the following default configuration for your task pop-up is provided:
Pop-up title—Task type
Pop-up fields—Status, Priority, Assignee, Notes, Due date, and Date completed
Pop-ups are designed and managed in the web map using Map Viewer. You can customize the content and layout of the pop-up to ensure it provides all necessary task information to the mobile worker. For more information on designing pop-ups, see Configure pop-ups.
Customize task symbology
When you create a new task-enabled layer in Field Maps Designer, you start with a set of default fields, values, and symbology. This symbology includes visual indicators unique to each task status, helping you quickly identify the status of tasks on the map.
If you want to change or customize task symbology, you can do so in Map Viewer. For detailed instructions on how to create and manage symbology for features, see Use style options.
A feature template for the unassigned task type is included by default. If you want to create new tasks with other status types, you can create additional templates for any other statuses that your workflow may require.
To learn more about changes to consider when configuring feature templates, see Considerations for feature templates.
Configure task actions and layouts
Task actions and layouts are essential components within the tasks functionality which allow you to design the task completion process for mobile workers.
Task actions—Actions are interactive buttons or menu items that enable mobile workers to perform specific tasks, such as changing the task status, taking notes, getting directions, or attaching photos.
When mobile workers open a task in the Field Maps mobile app, they see these actions as buttons or menu items in the pop-up. The app can display up to four action buttons at a time, with additional actions accessible through an overflow menu. Map authors can reorder actions within the layout to prioritize the most important ones. You can indicate which action is a primary action and it will be highlighted in blue for the mobile worker.
- Task layouts—Layouts are groupings of task actions, organized based on the stages of your task workflows. Layouts determine how and when actions are displayed to mobile workers. Each layout can be customized to include different actions depending on the task's status or other factors.
Caution:
You must have at least one task layout defined in order for tasks to work.
Default actions and layouts
Default actions and layouts based on your default task statuses are shown when you create a new task-enabled layer in Field Maps Designer.
For example, in the default Unassigned task status layout, default actions are provided, including Pick up, Directions, and Compass. The default actions differ depending on the task's status.
You can get started by using the default configurations or you can customize task actions and layouts to meet your workflow needs.
Configuring task actions and layouts
Both task actions and layouts are configured in the Tasks tab in Field Maps Designer. Building task actions and layouts is similar to building forms. You drag and drop actions into the Task Layout canvas and configure each action to customize the task completion experience and ensure your mobile workers have all the tools they need to efficiently complete their tasks.
Work with task layouts
A layout is a grouping, or container, for actions available during each stage of the task workflow.
The following are questions to consider when building or editing layouts for tasks:
- What actions are essential for each task status? Determine which actions are necessary for mobile workers to complete tasks efficiently at each stage (for example, Pick up, Directions, and Complete).
- How should the layout change based on task status? Consider how the visibility and arrangement of actions should adapt as the task progresses through different statuses (for example, Unassigned, In Progress, and Completed).
- What information do mobile workers need at each stage? Ensure that the layout provides all the necessary information and tools for mobile workers to perform their tasks effectively at each stage.
- Are there any specific conditions that should control layout visibility? Identify any additional factors, beyond task status, that should influence when and how layouts are displayed (for example, task priority and location).
- How can I streamline the task completion process? Look for ways to simplify the layout and reduce the number of steps required for mobile workers to complete tasks, enhancing overall efficiency.
To configure layouts, complete the following steps:
- On the Forms page, click the Tasks tab to see the All layouts view.
- To edit a layout, click on the layout to open it in the layout builder, where you can add, modify, or delete actions.
The layout builder includes a center canvas showing how actions will appear in Field Maps and a Layout properties pane for renaming the layout and controlling its visibility with Arcade expressions.
Each layout has a default visibility expression controlled by the task status field. For example, the Unassigned layout visibility expression makes it so the layout only appears if the task status field value is unassigned. The expression is DomainName($feature, “esritask_status”) == “Unassigned”.
The same pattern is applied to the other default layouts. However, you can customize when layouts are visible by editing the Arcade expressions. This is helpful if you have other factors that should determine layout visibility aside from the status of the task.
To edit Arcade expressions, complete the following steps:
- Click the Expressions button
next to the Visible check box. - Click the overflow menu next to the selected expression and click Edit.
The Expression builder window appears. The builder allows you to write an expression and preview it in Arcade before saving it.
- If you want to edit the Arcade syntax directly, click Launch Arcade editor.
- Once you’re finished editing, click Done.
Work with actions
Configuring task actions involves setting up interactive buttons or menu items that enable mobile workers to perform specific actions in their tasks in the Field Maps mobile app.
The actions mobile workers need are configured inside of the individual task layouts as follows:
- Add new actions—Drag and drop new actions from the Layout elements pane onto the canvas. For example, you can add a Take photo action to allow mobile workers to capture images of tasks. The actions will display in the mobile experience hierarchically; four buttons and an overflow menu. You can drag an action to re-order it. You can also indicate which action is the primary action for the mobile worker, which will be highlighted in blue in Field Maps.
- Duplicate or remove actions—When you hover over an action on the canvas, duplicate and delete options appear.
- Configure actions—On the layout canvas area, click on an action (for example, Pick up) to configure its properties, such as Display name, Icon, and Primary action. You can also manage which fields are updated automatically and manually when the action is used.
Supported task actions
Field Maps includes the following task actions:
| Name | Description |
|---|---|
Attach | A group of actions that includes Choose file, Choose media, Record audio, Take photo, and Take video. |
Assign | Assign a task to someone and update the task status to assigned. |
Choose file* | Attach a document to the task feature. |
Choose media* | Attach a photo, video, or audio file to the task feature. |
Collect here* | Collect a new point feature at the location of the task. |
Compass* | Get oriented toward the location of the task. |
Delete* | Delete the task feature. |
Directions* | Get directions to the location of the task using a navigation app on your device. |
Divider | Add a visual separator between actions. |
Edit field | Update fields automatically or prompt users to update fields manually. See Edit field action. |
Edit form* | Edit the form associated with the task feature layer. |
Favorite* | Add the task location to your favorites list. |
Finish | Update the task status to complete. |
Integration | Link to another app, such as Survey123. |
Menu | Group actions within a single menu. |
Pick up | Self-assign the work and update the task status to assigned. |
Record audio* | Record audio and attach it to the task feature. |
Related records* | If the task layer has a related table, view and modify related records. |
Start | Update the task status to in progress. |
Status | Update the task status. |
Take photo* | Take a photo and attach it to the task feature. |
Take video* | Take a video and attach it to the task feature. |
Note:
Actions in the table marked with an asterisk * are system actions, meaning their name and icon properties cannot be changed.
Task action examples
Edit field
The Edit field action allows mobile workers to update individual task fields. This can be applied to any field you want mobile workers to have access to edit.
For example, if you want mobile workers to add their own notes to a task, you can include a Notes field as an editable action in the task layout.
Note:
A Notes field is included by default when you create a new task-enabled layer. You can see how the Notes field is configured under the Action properties in the default In Progress layout.
Include a Notes field in the task layout by completing the following steps:
- Click the Tasks tab for the task layer and open the layout where you want to add a Notes field for mobile workers to edit.
- In the Layout builder panel, locate the Edit field element. Drag it onto the layout canvas.
- Change the field Display name to Notes, choose the update type (for example, text), and select the corresponding field from the task layer.
Mobile workers are prompted to add or update their notes directly within the task in the Field Maps mobile app. Any formatting and expressions built in the form for that field will be honored while editing.
Integration
The Integration action is a powerful tool that allows you to link to any app using deep links, directing mobile workers to other apps and even specific locations within an app. This enables seamless transitions between the Field Maps mobile app and other applications.
For example, mobile workers could tap on an integration action to open a specific form in ArcGIS Survey123, pre-populate information in a Microsoft Teams message to discuss a certain task, or access a work order in a customer relationship management (CRM) system.
You can also use integration actions to allow mobile workers to add and update features or add related features directly in the Field Maps mobile app.
Link to an app
You can use the Link property of the Integration action to add a link.
For example, you can link to a Survey123 survey by entering the link in the following format:
arcgis-survey123://?itemID=565e3b97e3a34215930
Tip:
You can rename an integration action to match the link destination, for example, Open survey.
Create dynamic links
You can link to other apps dynamically by creating calculated expressions. For example, you may want to add conditional logic so a different survey opens depending on the task type—or you may want to use multiple expressions to build the link itself.
To create a calculated expression, do the following:
- On the Forms page, click the Tasks tab to see the All layouts view.
- To edit a layout, click on the layout to open it in the layout builder, where you can add, modify, or delete actions.
- Drag an Integration action onto the canvas.
- Specify a display name for the action.
- In the Link section, type: arcgis-survey123://?itemID=
- Click the Expressions button next to the Links section.
The Expressions pop-up appears, displaying expressions used elsewhere in the tasks configuration.
- Click + New expression.
- Write your expression in the Arcade editor.
For example, you can create an expression that uses the task type to return a Survey123 item ID to link to a specific survey:
if (DomainName($feature, "esritask_type")== "Inspect tree"){ return "565e3b97e3a342159303d14a9fefc783" } else if (DomainName($feature, "esritask_type")== "Remove tree"){ return "37627a597a7140d8bebdfa471039595b" } else { return "e7ee0dd366024ba5a727df5a82bbacde" } - Click Done.
You can now append the expression to the itemID parameter of the app link, for example:
arcgis-survye123://?itemID=expr/survey-type
The expression is added to the text in the Link property. When a mobile worker taps the action in Field Maps, the survey linked to the task type is opened.
Add and update features or add related features
When completing tasks, you can update or add features to a layer (in the same map or a different one) using the Integration action. For example, if you notice a hazard while completing an inspection task, you can use a configured integration action to capture the hazard in a separate layer. You can also use a configured integration action to record the inspection information in a related table.
Integration actions are powered by URLs. You can configure the integration action with an app link. By customizing the link, you can control what app and map the action links out to, the layer and feature that can be updated, the action that can be taken (either adding or updating a feature), and the attributes that are passed via the link.
Before you begin configuring the action, create the app link using one of the following formats:
Add a feature
https://fieldmaps.arcgis.app?referenceContext=<action>&itemID=<ID>&featureSourceURL=<URL>
Add a related features
https://fieldmaps.arcgis.app?referenceContext=<action>&itemID=<ID>&featureSourceURL=<URL>&foreignKeyField=<fieldname>
Update a feature
https://fieldmaps.arcgis.app?referenceContext=<action>&itemID=<ID>&featureSourceURL=<URL>&featureID=<ID>
The following parameters are required for app links that add and update features:
- referenceContext—The reference context parameter determines the action taken when the map and layer are open. For tasks, you can either set this equal to addFeature , addRelatedFeature, or updateFeature depending on whether you want the action to initiate adding or updating a feature in the layer.
- itemID—The item ID parameter determines the map that the link should open. This should be equal to the item ID for the map containing the layer you want to update. The item ID for the map is displayed in the URL of the map’s item details page and when the map is open in Field Maps Designer.
- featureSourceURL—The feature source URL parameter should be equal to the URL of the layer being updated. This can be found on the item details page for the layer.
- featureID (updateFeature and addRelatedFeature)—The feature ID parameter should match the GlobalD field of the feature being updated.
- foreignKeyField (addRelatedFeature only) —The parent record field you want to pass through to the foreign key in the related (child) record.
There are additional parameters you can add to further customize the app link, such as defining the location where a new feature is added (if not defined, current location is used by default), high accuracy settings, adding to and updating related tables, and whether certain fields are automatically filled in when creating a new feature. To learn more about all the parameters you can use to create these links, see Initiate capturing a feature, Initiate updating a feature, and Add a related feature.
Build an app link with Arcade
You can use Arcade expressions to build a custom link with the Integration action.
For example, in a tree inspection workflow, you could use an Arcade expression to open a tree inspection form (related record) right from the task in the Field Maps mobile app.
Manage filters for to-do lists
Filters in Field Maps allow mobile workers to view tasks based on specific criteria that you define. Each filter is defined by an expression that determines which tasks will appear in the Field Maps mobile app. You can create your own filters or use the default filters. There must be at least one task filter defined in the map or tasks to-do lists will not display in Field Maps.
Configure task filters
To configure task filters, navigate to the Tasks tab in Field Maps Designer and click on Task settings. The Task settings pane will display the default task filters.
Here, you can manage filters in the following ways:
- Reorder filters—Click and drag to reorder filters. The first filter in the list will be automatically presented when the map is opened in the Field Maps mobile app.
- Duplicate or remove filters—Click the Overflow button to duplicate or remove filters.
- Edit filter expressions—Click the Filter button to manage the expression that define the filter.
- Add new filters—Click + New filter to add a new task filter.
Note:
Field Maps uses filters to manage the display of the task to-do list. You cannot add separate filtering in the Layer Filters section under App Settings in Field Maps Designer.
Work with the default task filters
When you create a new task-enabled layer, the default filters Assigned to me, Unassigned, and Completed are available. You can customize or remove these filters.
Assigned to me
The Assigned to me default filter gives the mobile worker a list of the outstanding tasks that have been assigned to them. To do this, it uses the following conditions:
esritask_assignee = ‘CURRENT_USER’ AND NOT(esritask_status = 3), where:
- esritask_assignee = 'CURRENT_USER' filters tasks assigned to the signed-in user.
- NOT(esritask_status = 3) ensures that tasks with a status of Complete (default code value = 3) do not appear.
Note:
'CURRENT_USER' is unique syntax for task configuration and is replaced with the username of the signed-in user in the Field Maps mobile app.
Completed
The Completed default filter gives the mobile worker access to a list of the completed tasks that they have done. To do this, it uses a similar expression to the Assigned to me default filter above without the NOT condition, so only tasks with the Complete appear:
esritask_assignee = ‘CURRENT_USER’ AND esritask_status = 3
Unassigned
The Unassigned default filter gives the mobile worker access to a list of tasks that have not been assigned to anyone. This is helpful for workflows where mobile workers should be able to pick up unassigned work. This filter uses one condition to display tasks that have not been assigned:
esritask_status = 0
Create additional task filters
You can create your own task filters in Field Maps to customize which tasks appear in to-do lists in the mobile app, ensuring that the right tasks are visible to the right people at the right time.
To create a new task filter, do the following:
- Click + New filter.
- Enter a label and definition expression.
- Click Done.
- Click Save to save the map in Field Maps Designer.
- Reload the map in the Field Maps mobile app to see the new filter.
Tips for creating filters:
- Include esritask_assignee = 'CURRENT_USER' to ensure tasks only appear if they are assigned to the signed-in user. Omit this condition to view tasks assigned to everyone in your organization.
- Filter expressions are written in SQL. For more information on SQL syntax, see SQL reference for query expressions used in ArcGIS.
- Always save the map after creating a new filter and reload it in Field Maps to apply the changes.
Example filter expressions:
High priority tasks
esritask_assignee = 'CURRENT_USER' AND ((esritask_priority = 3) OR (esritask_priority = 4))
Unassigned tasks for a specific crew
esritask_status = 0 AND crew = 'truck2'
Tasks due between specific dates
esritask_duedate BETWEEN DATE '2024-04-03' AND DATE '2024-04-04'
High priority unassigned tasks
esritask_status = 0 AND ((esritask_priority = 3) OR (esritask_priority = 4))