Hi, I've seen a somewhat related posting to this, but not quite. I've got a Survey123 form with submissions made entirely over the web. Is there a work flow where after the web hook notification the submission can viewed on the web for "final approval/submission"? I'm thinking some sort of 2-stage submission process, but I'm struggling to wrap my head around an easy solution using one hosted feature class. Thanks.
We actually do something very much like this, but a bit more complex. A simple two-step process is easy to achieve, especially if you use layer views. So let's say you have a layer of "Form Submissions", here's what you do:
There are many ways to accomplish the final step. Our approving users wanted something very straightforward, so we brought the view layer into a dashboard list. Selection in the list filtered the Details element and the Embedded Content.
The embedded content is a very bare-bones Survey123 form, which only exposes the Approved field for change. We've been using this for over a year now, with virtually no issues. Hope it helps you!
Hello,
I have a similar need for approvals but for daily accomplishments over a 2 week time period.
So the approver needs to do a batch approval rather than review each entry and approve one at a time. I understand there is a widget for batch attribute changes but as far as I can tell requires a mapped based selection for editing attributes. I would need a query based selection for a specific user and date range for the supervisor to then approve in bulk. Supervisor could review individual entries if need be, but I foresee them scanning these and wanting to do a bulk approval (attribute change).
Any ideas on we might accomplish this since the data isn't mapped just a flat table of entries?
Steve Harouff
WVDOF GIS Manager