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 about types of point capture, see ArcGIS Tracker.

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 can not 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 timestamp variable only applies to fields of type date.

Some variables are automatically assigned to button fields that have a specific name. You may 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.

The following table lists variables that you can use with line and polygon layers:

The following tables list variables that you can use with point layers.

Device

Location

Travel

Photo

External GNSS

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.

A project user input variable is different from a button user input variable in the following ways:

• Only one project user input variable is 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.
• It is defined by the project author in Settings > Project user input.
• You cannot apply it to a text field that is configured with a range domain or coded value 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 dialog box 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.

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, select Project user input. You can apply project user input variables only to text fields without domains.

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 in the following ways:

• Many button user input variables can exist in one project.
• Values are entered by the user after pressing a button.
• Can be applied to only one field within the one button.
• Configured by the project author on the Data tab for each button.

Properties of the button user input variable are as follows:

• Label—Text that will appear as the title of the project user input dialog box in the app.
• Text field type—Can be single-line text or multiline text.
• Apply hint—Display hint text on the project user input dialog box 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.

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

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

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 via email or SMS, posting messages to social media, automatically writing records to a spreadsheet, and updating enterprise databases.

In QuickCapture, webhooks can be set up and activated when a record is submitted. For example, after a successful submission of information to the feature layer, the webhook could be called 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 Integromat, 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, Integromat 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, Integromat 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 Webhooks from the project Settings. When creating a new webhook, provide the following parameters:

• Name—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—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—Determines whether this webhook is enabled when the project is saved.

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 on 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 (BETA)

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 non-oblique imagery. Enabling oriented imagery on a project does not result in a change in the mobile user experience but does provide 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 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 sample app, use either of the following options in the QuickCapture designer.

• Click View on the confirmation dialog box after enabling oriented imagery on the layer.
• Go to Settings > Layers, open the menu for the layer and click View oriented imagery.