With this feature, you have the flexibility to collect as much data as you want with a workflow that best suits your needs. For example, you could specify the flow of custom questions based on context or answer trees within your script.
You can format questions in specific ways (date, zip code, phone number, etc.). Also, you can check if an answer fits an expected profile. You can ask one question or many questions with each Custom Question. The core value is that the app user’s answer (or answers) for each Custom Question is saved as part of the official scan record.
To add custom questions, you can use the API or the web UI located on the Questions page and Questions tab when creating a Service. There are two options: URL and HTML. Clearly, the most flexible is the URL option. However, the HTML option is valuable if collecting data offline or if you don’t want to use your own servers.
Here’s an example of a Custom Question script that auto inserts the device’s date so the app-user doesn’t have to enter a date. Here’s an example script where the app-user can enter any date from a drop-down menu, thus making date entries formatted, quicker to enter, and more accurate. And here’s an example script where the app-user is presented with dependent questions with multiple answers recorded with each scan record. And here’s an example of multiple answers with a form field when a specific answer is selected. Email support if you need a text file of the example scripts for inserting into the Custom Question field.
In addition to the standard no-coding options for conditional questions, we offer programmers the option to create ‘On-the-Fly’ questions when using our Postback URL feature. You only need to show the app-user these questions when you choose to based on the context. Whereas, with a Custom Question the app user always sees the option to answer a question after a scan.
An On-the-Fly question works like this:
- The scan record is posted in real-time to your server
- Your server will see the barcode value scanned and any answers to questions made by the app-user before submitting the scan.
- Your script can process that information and present the app-user with more questions to answer. Also, you can choose to not present any questions.
- When the app-user answers those questions, they submit it. Then, you can ask more questions. If satisfied, allow the app-user to move on to the next scan.
For instructions, please see our documentation.