A. When configuring your Triggers and Actions after re-configuring your codeREADr Services, you may find it easier to create new Zaps and turn off the old ones rather than editing Zaps. This is particularly important when testing the Catch Hook Trigger after you have scanned a value. If that’s test isn’t using the new service configuration, you may be able to proceed but the integration will fail.
B. Most administrators will use one codeREADr service to insert data into a validation database. However, you can also have multiple services inserting data into the same validation database.
- When creating your codeREADr services, each service must be associated to the same database in Step 1 (‘Type”) of the service creation wizard. Also, each service must have a unique Webhook created on Zapier and pasted into Postback URL form on the Advanced step, usually with a unique export template as well (see below).
- Assuming each service will change the response data after entering their answers, then each service will have their own uniques prompts for the app user to answer. This means you need to create a unique export template for each service. An example using this type of workflow would be process, asset or shipment tracking where at each step the app-user need to see the status of the previous step before taking an action. The app user will only see the answers submitted by the immediately prior user. And when they answer their prompts, the next app user will only see those answers and not any of the other answers prior to that.
- It’s also possible to share prompts for multiple services but be aware that the prompts will need to be answered each time or they will be blank for the next scan.
- When adding your prompts to a service on the Questions step, you generally should make one or all of them required (click the asterisk) so the app user must answer the question(s) before they can submit the record.