Quick Capture Button User Input

[Montray Yadav]

Capturingdata with ArcGIS QuickCapture boils down to pushing a big fat button. If configured appropriately with device variables, you can also have additional attributes in your GIS feature be added automatically: direction and speed of travel, time-of-capture, horizontal accuracy and many others. That is the basic idea and the most common pattern of use for the app: push a QuickCapture button and the app does the rest.

User inputs are an advanced capability that lets field workers manually enter extra information for captured observations, without losing the fluent big button user experience of QuickCapture. In the animation below, as an example, a user input allows for a description of an event to be added after a field observation is collected.

User inputs can be easily authored from the QuickCapture designer. If you know how to map QuickCapture device variables to fields in your layer, configuring user inputs will not be difficult to you. User inputs, in fact, are conceptually very similar to device variables.

In the following animation, we select a single button in the project and configure it with a button user input so the end user can enter some comments. The value of the user input is persisted in the Notes attribute.

Button User Inputs will always honor the characteristics of the target field. For example, if you configure your Button User Input on top of a field of type text, the User Input will let you enter free text. If your field as a geodatabase domain defined, then your User Input will automatically display a list of values, etc.

Once a button user input dialog is defined, you can apply it to one or more buttons. Just be aware that you will need to associate your button user input one at a time. That is, you cannot select multiple buttons and then apply a button user input all at once. Additionally, you can only define one single button user input per button.

A Project User Input dialog is shown when the QuickCapture project opens. It lets end users enter a value which will be used when data is captured from the app. Project user input dialogs can also be optionally re-opened by the end user at any time while capturing data. The whole point about project user inputs, as opposed to button user inputs, is that the user enters a value upfront, and then than value is used when data is captured.

The configuration of a Project User Input is very similar to that of a Button User Input, except that you can configure up to three dialogs per project. The animation below shows how you can create a new dialog (Cost Center) and associate existing dialogs (District and Team) with a button.

When testing your Project User Inputs from the QuickCapture mobile app, you will notice that if you make them required, then you will not be able to start data capture unless you enter a value in the user input. Once you are capturing data, you can change the user input value at any moment.

E.g. "Comment" and then "Status" is backwards for how users want the button to work. Users what to define a "status" and then supplement the status with additional comment. I'm finding status values in the comments because the user wasn't expecting the distinct list question on the next screen.

This has been implemented in 1.19. In the QuickCapture designer there is a new option under the more (...) setting called Button user inputs. Here you can view existing button user inputs and drag to re-order them.

Capturing data with ArcGIS QuickCapture boils down to pushing a big fat button. Button pressed, field observation added to the map! If configured appropriately with device variables, you can also have additional attributes automatically calculated: direction and speed of travel, time-of-capture, horizontal accuracy and many others. That is the basic idea and the most common pattern of use for the app: push a QuickCapture button and the app does the rest.

Say you are using QuickCapture to do a quick inventory of fire hydrants in the city. Without button user inputs, you can easily collect the location, the type and take a photo. Configuring button user inputs you can also report, for example, its condition, model and a brief note. Many thanks to Andy Wells and all supporters of his ArcGIS Idea.

As Arnaud puts it in this ArcGIS Idea, this is a simple but essential enhancement. By default, QuickCapture shows button user input dialogs after a feature is collected. For example, if you are documenting a manhole, the button user input dialog appears after you tap the manhole button. That is all fine, except when collecting a line, or multiple lines at once. Waiting until the line is finished before you can populate its attributes can be problematic. With this update you can now present the user input dialog when the line starts, or when it finishes. If configuring multiple button user inputs, you can choose some to be shown a the start, and others at the end!

This release incorporates support for the GNS3 series from Esri Bronze Partner Juniper Systems. The GNS3S and GNS3M high accuracy GNSS receivers connect to ArcGIS QuickCapture via bluetooth. Once connected, not only you benefit from higher accuracy location data, but also from additional metadata describing the quality of data you are collecting. Like other compatible GNSS receivers, support is provided for iOS, Android and Windows devices.

Use device variables to automatically populate GIS attributes. Speed, horizontal accuracy, device model or data collection time are some common ones. QuickCapture supports more than 50! Check the complete list here. Now you have one more: SessionId.

Here is an example: Say you are configuring QuickCapture to combat poaching in an African National Park. You set your project to require location sharing. By having the session_id be stored with every observation, you can later in the office tell which observations are linked to which track.

Create a new project user from a field with a domain and QuickCapture will automatically show all the domain values as a list to the end user. In fact, if you change the domain values, QuickCapture will update the list accordingly. Many thanks to Todd Turner and all supporters of his ArcGIS Idea.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse suscipit sapien ac sapien malesuada fringilla. Fusce venenatis, mauris id sagittis dapibus, mauris velit sollicitudin ante, a pulvinar leo orci vel erat. Nam mattis erat augue, at luctus ex dignissim et. Donec suscipit, dui at efficitur tristique, nulla nisi ornare lorem, vel dictum lectus eros nec felis.

ArcGIS QuickCapture allows users to capture locations, field conditions, and photos, with quick access to the camera icon on the top-left corner of each button in a project. However, in some instances, the camera icon does not display on some of the buttons, as demonstrated in the image below.

For the take photo option to be enabled in the ArcGIS QuickCapture project, the hosted feature layer of the project must be editable. Log in to ArcGIS Online with the same credentials used in ArcGIS QuickCapture, and check the Enable editing. check box in the hosted feature layer settings. Refer to ArcGIS Online: Allow others to edit for steps to do this.

Arcade expressions can be written to calculate fields in records captured with ArcGIS QuickCapture. When the user taps a button in the project, a feature is captured and the app subsequently uses the Arcade expression to populate the value of one of the fields. Then the feature is sent to the underlying ArcGIS service. It is best practice to handle casting within the script for full control of casting behavior to Number, Date, or Text return types.

I created an app that has tasks/to-do's, I would like to implement a button thats called "submit". I would like it to have a function where when the user clicks submit it will capture their name/email and if possible the time it was clicked (the time portion isnt important if its not possible) mainly just name and email is the important part. I want this to be captured onto my sharepoint, I have created 3 coloumns as plain text that say manager, manager email, accepted time. How do i go about making this? any help would be appreciated. Thank You!

Looks like you have a mandatory field 'Title' in your SP list. I believe it's automatically created and can't be deleted. If it's unimportant to you, just include it in your Patch() with the other fields and put some filler data there to remove this error.

Based on signed in user is perfect and exactly what i was looking for. In my gallery i have a drop down where its defaulted to "incomplete" they will then change it to "complete" and click submit, from there their signed in info (name/emailed tied to their email account) get put into my sharepoint list columns under manager, manager email, accepted time.

I see what you're saying! One thing you could try is using the Patch function. This will allow you to save this info, based on the signed in user's information- they won't even have to enter it anywhere.

I have a Form (microsoft form) already where the manager will fill out and that info gets put into my SP and then filtered into my app. Do i still need to create a Edit Form in this case? For preference i did not add those criteria in the form as i want to make sure the managers dont delegate their tasks to others so i want to document who clicks on that submit button.

I have a page with two buttons. One is a element and the other is a . The buttons appear on the page in that order. If I'm in a text field anywhere in the form and press , the button element's click event is triggered. I assume that's because the button element sits first.

I can't find anything that looks like a reliable way of setting the default button, nor do I necessarily want to at this point. In the absence of anything better, I've captured a keypress anywhere on the form and, if it was the key that was pressed, I'm just negating it:

The reason is because a button inside a form has its type implicitly set to submit. As zzzzBoz says, the Spec says that the first button or input with type="submit" is what is triggered in this situation. If you specifically set type="button", then it's removed from consideration by the browser.

3a8082e126