QuickCapture: Linked Button to Survey123 "Rules"

[pjdohertygis]

Should some waypoints force the end-user to open Survey123? For example, waypoints that would default to needing follow-up? Should these force open Survey123, partially filled out with the project user input (Team, Squad, etc) --> Favorites and the waypoint type? This might reduce confusion around when to use QuickCapture vs Survey123?

I'll put together a quick example....

Link: https://arcg.is/1bfW8i

[pjdohertygis]

From OH-TF1

Some initial thoughts on the linked button concept…

It seems to work well, except I had one issue where the second time I used a linked button, it took me to the empty Drafts part of Survey123. After trying to recreate the problem while screen recording, I was unable to make it happen again.

In the big picture, where everything is centered on QC, we need to be able to encode the project inputs into the hyperlink so that the Team, Squad, and Search Type don’t need to be entered in or pasted from favorites. This will probably require some work on Esri’s end, but would eliminate the need to do any project setup at all in 123. See https://github.com/pjdohertygis/WideAreaSearchTemplates/issues/136

For practicality, if we’re going to take the user into a more detailed survey for a point that needs more information, each of those surveys needs to have a required field beyond what you have to do on QC. So if all we’re doing in 123 is filling project fields and clicking submit, we probably don’t need to link to it in 123. But let’s not create the need to use 123, but instead adapt to the need when it occurs. I understand we’re testing the process, so don’t take any of it as “we don’t need this”.

A cool way to make this better would be conditional linking, where if you’re doing a recon or hasty, the buttons work as buttons on QC, but if you’re in a primary or secondary, some buttons take you to 123. Again, more work for Esri, but would be more applicable to our op-tempo.

[pjdohertygis]

Once consideration is - what if you forgot to sign-in and download the survey before leaving? If we only provide a linked button, then you are stuck. How do we address this? (From Jared)

[pjdohertygis]

This is a capability we can leverage on specific incidents in conjunction with Field Data Rules of Engagement, but it is difficult to "templatize" not knowing all scenarios that could come up (mass fatality incident, teams that did not download Survey123).

[pjdohertygis]

Team - " "

Harris FL-TF2 recommended we make Lifeline Report a button that always opens up Survey123 because it requires more details.

I've implemented this now as a test in the Sandbox: https://arcg.is/14fK4

This brings back the question, for what other buttons should we require Survey123 input and what happends if they don't have it installed? We need input from the Cadre on this to move forward.

Furthermore - @IsmaelInRedlands @xiao8579 If QuickCapture eventually allows for two button user inputs, that might reduce the need to using both apps. Here is another user from the same exercise feedback - at the time we only allowed them to choose a "Lifeline Category" for button user input, but they wanted to also add comments.

" "