I use GoCanvas for vehicle inspections, and I have a problem with different users inspecting the same vehicle because they don't realize someone else has already gotten it. I update the reference file daily to indicate "Already Inspected" on those vehicles, but that is too slow.
We always start with a definite list of specific vehicles that need inspecting (it's not a random sampling). Is there a feature that could tell a user automatically if they are about to do a duplicate submission?
0
Comments
Please sign in to leave a comment.
Hi PDC PE's
That is a great question. There may be a few options, some are more elegant than others but may be worth exploring with your Account Manager and our Professional Services team.
1. The most elegant solution would be Dynamic Reference Data. This integration would recognize when new information is added to the form and update the reference data and vice versa, automatically. So if a vehicle gets inspected, that submission would send the information to SQL database and update the reference data so that the next person accessing that form would see the vehicle is inspected or not available on the list. Although elegant, this is the most costly option and would require a custom integration.
2. The second is to set up a Zapier connection with Google Sheets and GoCanvas. Either Professional Services could do that for you or you could do it on your own, making this option a little less involved than full blown Dynamic Reference Data.
3. You could use Dispatch and Assignments to assign inspections to your team. This would require that all inspections for the day are prepared in advance but then everyone would be able to see the list of vehicles that need inspecting that day. If an inspection is claimed, no one else would be able to fill out that form.
4. The least elegant option, but perhaps the simplest, is to simply email everyone the submission when an inspection is complete. An identifying feature of the vehicle, like VIN or make/model, can be placed in the email subject so everyone can see which vehicles have been completed in their email inbox at a glance.
Let's see if our other Community members have ideas to chime in too! Thanks for your question!
Lauren :
I think the simplest solution is for goCanvas to develop a backend database by itself so we have a history of all the submissions and then we can define which fields should be unique.
Isn't that the most elegant solution?
The main deficiency for GoCanvas is that it's a front and form, but it does not have a backend database to hold the data.
Hi Lifeng Wu
Thanks for joining the conversation! Unfortunately, that is not the simplest solution, although I wish it was. In order to have our own backend database, the setup costs and costs that would be passed to our customers would not be financially sound. The backend systems we use are the industry standard and best available. Our goal is to always provide the best service for a price that is feasible for our core customer base.