Esri / collector-integration

Multi Language repository that contains documentation and sample code for creating custom URL schemes in Collector for ArcGIS.
Apache License 2.0
18 stars 10 forks source link

Collector Callback #18

Closed bnadler closed 4 years ago

bnadler commented 7 years ago

I am able to launch Survey123 from Collector, but once the survey is completed, how do I configure the callback to return to Collector? Below is what I have tried per the documentation on the Survey123 side. once survey123 completes, it returns to the surveys screen, not to collector.

arcgis-survey123://?itemID=###&field:ASSETID={GLOBALID}&callback=arcgis-collector://

doug-m commented 7 years ago

@bnadler Collector doesn't currently support a callback mechanism like Navigator or Survey123. To this point Collector's workflow doesn't require a direct correlation between completing an edit and the completion of a given task. Can you share a bit more about why you are moving between Survey123 and Collector?

bnadler commented 7 years ago

Collector is used for offline mapping/feature updates. Survey123 is used for inspections on the features. The survey needs to be populated with the Pole ID to be related to the pole later.

The enhancement is a workflow design/UX consideration. I am not sure what “Direct Correlation” implies, but when a user launches a survey from Collector, they expect that when the survey is complete, that they are returned to Collector to continue on to the next pole (instead of having to “go back” manually). Without this “Callback” the user may skip this step and launch a new survey from the survey123 surveys menu that will NOT have the pole ID populated from the App Link dynamic value ( making the survey unusable)

Survey123 becomes a “dead end” for the user workflow and a liability for data collection… NOT ideal. Sincerely,

Ben Nadler | Esri Professional Services | Technical Analyst | Utilities, Telecom, & Energy

O: 303.449.7779 ext. 8278 | C: 303.884.9323 | E: bnadler@esri.commailto:bnadler@esri.com | esri.com/services<www.esri.com/services>

[ArcGIS Desktop Associate 10.1]https://urldefense.proofpoint.com/v2/url?u=https-3A__www.certmetrics.com_esri_public_badge.aspx-3Ft-3Dc-26d-3D2014-2D08-2D08-26i-3D14-26ci-3DESRI00109825&d=DQMGaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=2PIwAR_kAfcTQ3m7yzQ_wA&m=MTg50XiFwbuuxJPYWVEpKLMeCmEYjrGmk7iEt7Nk1ao&s=tONixqB4nuTFbokT_FXS01yAoJo27__NGx2ImUR8eg0&e=

[Enterprise Administration Associate 10.4]https://urldefense.proofpoint.com/v2/url?u=https-3A__www.certmetrics.com_esri_public_badge.aspx-3Ft-3Dc-26d-3D2016-2D06-2D16-26i-3D36-26ci-3DESRI00109825&d=DQMGaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=2PIwAR_kAfcTQ3m7yzQ_wA&m=MTg50XiFwbuuxJPYWVEpKLMeCmEYjrGmk7iEt7Nk1ao&s=gsAdSk03R1zXWPdraWdjsnZMRG6Y2qMskfSs3PpkLM4&e=

From: Doug Morgenthaler [mailto:notifications@github.com] Sent: Monday, March 6, 2017 8:10 AM To: Esri/collector-integration collector-integration@noreply.github.com Cc: Ben Nadler BNadler@esri.com; Mention mention@noreply.github.com Subject: Re: [Esri/collector-integration] Collector Callback (#18)

@bnadlerhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_bnadler&d=DwMFaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=2PIwAR_kAfcTQ3m7yzQ_wA&m=VQY9POtlo5KC5cM0LMDkw5hgtzOdD19_NXS0tyo5Edw&s=U4wAYQh5QJz4ayslr5Fhlrc8tvt5_6AquOUXQRrMLA0&e= Collector doesn't currently support a callback mechanism like Navigator or Survey123. To this point Collector's workflow doesn't require a direct correlation between completing an edit and the completion of a given task. Can you share a bit more about why you are moving between Survey123 and Collector?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Esri_collector-2Dintegration_issues_18-23issuecomment-2D284422687&d=DwMFaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=2PIwAR_kAfcTQ3m7yzQ_wA&m=VQY9POtlo5KC5cM0LMDkw5hgtzOdD19_NXS0tyo5Edw&s=8Yix1EA6elyVHqpOdtXIj5cSGA4cfK1jru8ghLMIn3E&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AHdKhq5AfivrT91luv3uagVp2zl-5FJZsmks5rjCHDgaJpZM4MMG6n&d=DwMFaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=2PIwAR_kAfcTQ3m7yzQ_wA&m=VQY9POtlo5KC5cM0LMDkw5hgtzOdD19_NXS0tyo5Edw&s=3sSUUMd-PAz2cFPzd8LQi2sjIMy9G4t7R_veoLdLH5M&e=.

scapararo commented 6 years ago

Hi Ben, I am running into the same problem with Collector / Survey123 integration that you describe here. Did you ever find a solution? Thanks Shawn

bnadler commented 6 years ago

Looks like the issue is still open. I was not able to find a solution other than end-user training. There was a dependency on Survey123 supporting the callback, then Collector responding to the call. Perhaps in a later release of Collector this will be resolved.

Check this thread on Geonet https://community.esri.com/thread/191106-app-link-callback-to-collector

murphy214 commented 5 years ago

Solved this by just hacking on uri, it works, maybe still relevant?

arcgis-survey123://itemID=youritemid&callbackprompt=yourappname&callback=app://

Someone should put that on Survey123's documentation page?

doug-m commented 5 years ago

@murphy214 we've added a similar callback to what is available in Navigator here: https://github.com/Esri/navigator-integration#enable-notifications-when-navigation-completes

This is currently available in our latest iOS beta if you're interested in trying it out.

doug-m commented 4 years ago

Available on iOS but not documented here - please use our doc site for current status.