Hi all,
I’m looking for guidance on designing a workflow using Survey123.
I’ve been asked to create a survey that allows individuals to check in to a job site at the start of their day and check out at the end. Due to licensing constraints, the survey will need to be public. We’re currently using Enterprise 11.3, and Survey123 is not installed on the server, so we’re limited in accessing the latest features.
Here’s what I’ve implemented so far:
- A check-in survey that generates a unique (UUID) check-out code and emails it to the user.
- A check-out survey where users enter their code to complete the check-out process.
To support validation, I created a hosted feature layer view from the private survey to use as a lookup table. However, I’m running into issues: Attachments in the view layer are still visible (which I’d prefer to restrict). And The check-out survey is not reliably validating or retrieving the correct UUID from the lookup.
What would be the best approach to:
- Securely validate the check-out code in a public survey.
- Properly configure the lookup so the UUID is recognized and matched correctly?
- Prevent exposure of attachments or sensitive data in the view layer?
Any recommendations, best practices, or alternative workflows would be greatly appreciated.
Thanks in advance!
