Streaming points

A project author can configure a point button to capture continuously, similar to how line and polygon buttons operate. Streaming point capture is useful when you want to record GNSS metadata and other data such as speed for every vertex along a path. Each vertex of the path is represented by a point and can be continuously automatically sent to ArcGIS.

If a button user input is applied to a point button, streaming mode cannot be enabled on that button. If streaming mode has already been selected for a point button, a button user input cannot applied to that button.

Streaming point capture is not designed to actively track the location of mobile workers.

To learn more, see Location sharing.

Show map after capture

A project author can configure a point button to display the map after capture. On this map, the mobile worker can visually confirm the location that was captured, and also pan the map to capture a more accurate location.

When the map is enabled, the project author can also customize the map title or the map hint, to provide guidance or instruction to the mobile worker.

Fixed values

You can apply fixed values to fields when a button is pressed. This fixed text is defined by the author and constrained by the field type and length. For example, an integer field cannot accept a decimal or text value.

Device variables

Device variables are used to automatically populate QuickCapture fields with common GIS attributes. Not all variables can be applied to all types of fields. For example, the time stamp variables only apply to fields of type date.

Some variables are automatically assigned to button fields that have a specific name. You can choose to manually create these named fields in your feature layer, or optionally, select Capture GPS receiver information when creating a feature layer in ArcGIS Online or creating a feature layer in ArcGIS Enterprise.

Device information

User information

Location

Travel

Photo

The variables in the following table are typically available only when connected directly to an external GNSS receiver, however, the variables marked with * are also available on Android when an external receiver is connected through a mock location provider.

GNSS

Offline map

By default, the map extent of an online map is cached for ongoing use when the device is taken offline. As long as the project is not closed, the map extent that was visible while online will remain visible when offline.

If the app user opens a project while the device is offline and no offline map has been configured by the project author, the Esri default offline map will be visible. This default offline map is a lightweight simplified basemap of the world, designed to provide basic geographic context to local data.

There are two ways that custom offline maps can be configured for use by the app: an offline map can be associated with the project in the web designer by the author, or the Esri default offline map on the device can be replaced by the app user.

In the web designer, any of the following can be selected as the project map:

• Online basemap
• Online web map
• Offline .tpk, .vtpk, or .mmpk files.

The Esri default offline map is a .vtpk file that is copied to the device during installation. This file—esri_default.vtpk—can be replaced with your own file of the same name, of any of the supported offline file types: .tpk, .vtpk, or .mmpk. Once replaced, the map will be viewable in any project opened while the device is offline. This file is located in the maps folder on the device in the following places:

• Windows—C:\Users\<username>\ArcGIS\QuickCapture\resources\maps
• Android—Internal Storage/Android/data/com.esri.quickcapture/files/ArcGIS/QuickCapture/resources/maps
• iOS— QuickCapture/ArcGIS/ArcGIS QuickCapture/resources/maps

If the app is reinstalled, any replaced files will be deleted and the Esri default offline map reinstated.

Exclusivity groups

An exclusivity group is used to ensure only one button within the group is active at any time. Consider capturing a series of lines that represent the changing condition of a footpath. As you travel along the path, the condition may be excellent, good, or poor. Tap the excellent button to start capturing a line representing an excellent section of footpath. When the condition changes, tap the poor button immediately. Capture of the excellent line stops, and capture of the poor line starts.

Exclusivity groups are typically applied to polyline and polygon buttons, but you can also add point buttons that are streaming mode enabled. You can include buttons from different template groups in a single exclusivity group, and you can apply multiple exclusivity groups to a project.

Project user input variable

The project user input variable value is populated by the app user, and you can apply it to one or more buttons in a project. The app user enters the value; however, the project author must define the buttons and fields to which the variable will apply.

The following apply to a project user input:

• Up to three project user input variables can be defined per project.
• Its value is entered by the user before pressing a button. If the user input is set as required, the user is prompted to enter this value when starting the project but can edit the value at any time.
• You can apply its value to any text fields in any buttons.
• You can apply its value to a text or integer field that is configured with a coded value domain.
• You cannot apply its value to a text field that is configured with a range domain.

Properties of the project user input variable are as follows:

• Label—Text that will appear as the title of the project user input page in the app.
• Input type—Can be single-line text, multiline text, or choice list. You can add, delete, and reorder choices. Optionally, you can allow free text entry with choice lists.
• Apply hint—Display hint text on the project user input page in the app.
• Apply an input mask—Define the format for data entry by using characters and symbols to define an input mask.
• Required—Specifies whether the mobile app user must provide the user input value before they can press any button. When not required, the user can optionally enter a user input value by selecting the edit button (next to the user input value displayed at the top of the screen) and typing a value.

  Note:

  When applying a user input value to a feature layer with required fields, ensure that its required property is set to true to avoid submission errors.

• Show barcode scanner—Use barcode scanner on the input dialog box for text field entry.

  Note:

  The following formats are supported: QR CODE, UPC A, UPC E, EAN 8, EAN 13, CODE 39, and CODE 128.

A project user input is created and configured by the project author either on the Data tab for each field or in the Project user input menu item.

To assign a project user input variable to a capture field of a button, on the Data tab, from the drop-down menu of the capture field, choose Project user input.

In the mobile app, the user is prevented from entering text that exceeds the length of the data field.

Button user input variable

A button user input variable value is populated by the app user after a button is pressed in a project. The app user enters the value; however, the project author must define the buttons and fields to which button variables will apply.

A button user input variable is different from a project user input variable, as values are entered by the user after pressing a button. Up to three button user inputs can be applied to each project button, with each updating a specified field.

Properties of the button user input variable are as follows:

• Label—Text that will appear as the title of the project user input page in the app.
• Input type—Can be single-line text, multiline text, date time or choice list. You can add, delete, and reorder choices. Optionally, you can allow free text entry with choice lists. You can specify a default value and date range with the date time input type.
• Apply hint—Display hint text on the project user input page in the app. This is not applicable when configured with a range or coded value domain.
• Apply an input mask—Define the format for data entry using characters and symbols to define an input mask.
• Required—Specifies whether the mobile app user must provide the user input value after a button is pressed.

  Note:

  When applying a user input to a feature layer with required fields, ensure that its required property is set to true to avoid submission errors.

• Show barcode scanner—Use barcode scanner on the input dialog box for text field entry.

  Note:

  The following formats are supported: QR CODE, UPC A, UPC E, EAN 8, EAN 13, CODE 39, and CODE 128.

• Show user input dialog box—Specifies whether the button user input is shown at the start or end of data capture. This applies to buttons that capture line and polygon features; it does not apply to point buttons.

Depending on field type, different user input variable parameters are available:

• String—User input label, display as multiline single line or choice list, hint, input mask, required.
• Integer—User input label, required.
• Double—User input label, required.
• Date—User input label, required.

A button user input can be configured by the project author on the Data tab for each button. To assign a button user input variable to a capture field of a button, on the Data tab, from the drop-down menu of the capture field, select Button user input and select Create new.

If you create a button user input for a field that has a domain (either coded value or range), the choices are presented to the user as a single choice list. Free text cannot be entered when a coded value domain is present. When a range domain is present, data entry is limited by the range.

Input masks

An input mask defines the format for data entry using characters and symbols as part of a project or button user input variable. When you apply an input mask to a user input variable, values entered by the user must follow the specific pattern defined by the input mask.

To apply an input mask to your user input variable, define the mask in the userInputs.domain.inputMask property.

The following table lists the characters and symbols that you can use in an input mask:

The mask consists of a string of characters and separators, optionally followed by a semicolon and the character used for blanks. The blank characters are always removed from the text after editing. The following table lists example masks:

Webhooks

Webhooks are a widely supported method used to allow multiple applications to interact with each other, using HTTP POST requests to pass callbacks between them. For more information, see Wikipedia's page on webhooks. Common uses for webhooks include sending notifications by email or SMS, posting messages to social media, automatically writing records to a spreadsheet, and updating enterprise databases.

In QuickCapture, you can set up and activate webhooks when a record is submitted. For example, after a successful submission of information to the feature layer, you can call the webhook and trigger another action, such as sending a notification email, appending the record to a spreadsheet, and sending an alert.

Your workplace may have its own webhook provider, but a wide variety of third-party workflow services are available, such as Make, Microsoft Power Automate, Zapier, and tray.io. You can use all of these to incorporate QuickCapture as a trigger for a greater automated process. In particular, Make has a QuickCapture module, allowing you to integrate QuickCapture into your webhook workflow with minimum difficulty, and without the need to configure the webhook in the QuickCapture designer or to input a payload URL.

There are many ways you can use QuickCapture as a trigger in your workflows. To get started, Make has templates that you can use to include attachments in your email notifications, add records to spreadsheets, and create calendar items. To learn more, see Automate workflows with Integromat.

You can configure a webhook in the QuickCapture designer by choosing the Webhooks menu item . When creating a webhook, provide the following parameters:

• Name—Set the name of the webhook (unique within the project).
• Target feature layer—Select a single feature layer. The payload is sent to the configured webhook URL each time a record is submitted to this layer.
• Webhook URL—Specify where the project information is sent. An external webhook provider must provide this.
• Event data—Choose what information is included in the payload, including project details, information of the user, portal and submitted record, and response from the server.
• Status—Determine whether this webhook is enabled when the project is saved.

For an example of a webhook payload, see FAQ for project authors.

Project validation

Analysis is performed to help validate data and diagnose your project configuration when you open, save, or share the project. Guidance is provided to help fix errors or warnings in the Messages pane. Click the error or warning message to locate the issue.

You can save the project with warnings. However, you cannot save it until all the errors are resolved. Issues that may prevent saving include the following:

• Invalid data sources—Feature layers and map that have been deleted or unshared.
• Empty required fields—Fields marked as required must have a device variable, user input, or fixed value defined. When assigning a user input to a required field, ensure the user input variable is also marked as required.
• Invalid project settings—Incompatible values for recommended and required horizontal accuracy, settings marked as required must have valid input, invalid webhook configuration, or a project without any buttons configured.

Oriented imagery

You can configure QuickCapture to automatically capture photo metadata that enables the use of Oriented Imagery in ArcGIS. Enabling a QuickCapture project with oriented imagery allows you to better manage and visualize your nonoblique imagery. Enabling oriented imagery on a project does not result in a change in the mobile user experience but does provide ArcGIS users with the following capabilities:

• Select a location or asset and see which photos cover it.
• Select a photo and see its footprint.
• See a correlation between ground features (on the map) and image features.

To enable oriented imagery in the designer, you need a QuickCapture project that is configured to take photos. Follow these steps to enable oriented imagery:

To visualize and exploit the photos with the Oriented Imagery app, click the Manage project layers menu item , open the menu for the layer and click View oriented imagery.

Location sharing

Location sharing is an organization-wide capability that allows you to record where mobile workers are and where they have been. When you enable location sharing, licensed users in your organization can use the QuickCapture mobile app to upload their locations to the location sharing layer. The tracks are secure in the location sharing layer—mobile workers only see their own tracks, and additional permissions are required to view the tracks of others. Once location sharing is enabled, administrators can use the Track Viewer web app to share the last known location and track data with other users in the organization by creating track views.

To learn more about enabling location sharing in your organization, see Enable location sharing in ArcGIS Online and Enable location sharing in ArcGIS Enterprise, or see the Deploy a Location Sharing Solution with QuickCapture implementation guide.

To enable location sharing in your project, choose the Location sharing menu item . When you enable location sharing, you can choose the following:

• Required—When tracking is required, mobile workers cannot disable tracking.
• Last known location update interval—The interval of the single location that represents the last known location reported by the mobile app. You can choose 1 minute, 15 minutes, or 1 hour. The default is 1 minute.
• Last known location category—The value that will be written to the category field of the last known location layer. It can be the project name, a fixed value, or a project user input. The default is the project name.
• Tracks upload interval—The interval at which locations are uploaded to the track layer. The default is off (disabled). When off, only the last known location will be uploaded. To enable track upload, set this interval to 10 minutes.
• Tracks category—The value that will be written to the category field of the tracks layer. It can be the project name, a fixed value, or a project user input. The default is the project name.

To learn more, see FAQ for project authors and FAQ for mobile workers.

Arcade expressions

ArcGIS Arcade can be used to calculate fields in records captured with QuickCapture. A project author can write an expression that uses Arcade functions, operators, input values from other fields in the target layer, or values from other layers in the QuickCapture project web map. The following are example use cases that can be constructed as an Arcade expression:

• Calculate a value from values coming from another field
• Do a point in polygon query to return an attribute value
• Use a function to calculate the time duration of a captured polyline

The QuickCapture designer includes an expression builder to help authors write expressions and uses the QuickCapture profile. Similar to how user inputs are defined once and usable in more than one button, once an Arcade expression is saved in the designer, it can be assigned to more than one button.

Arcade expressions can be configured by the project author on the Data tab for each field. To assign an Arcade expression to a capture field of a button, on the Data tab, from the drop-down menu of the capture field, choose Arcade expression and select Create new.

Fields that are managed by ArcGIS, such as OBJECTID, GlobalID, CreationDate, Creator, EditDate, and Editor, should not be used in an expression because their values are not known until after a record is submitted. If an expression requires a value for a username or record capture date, the expression should reference a field that has been populated with a device variable.