What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.
We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.
Unique field data triggers even on "Incomplete Payments"Asked by ASRA on April 28, 2013 at 04:14 AM
If a form contains a field that is limited to unique entries, and a user creates an incomplete submission, the unique value in that field in the incomplete submission cannot be entered again by anybody.
Example: Imagine a form where users must enter a unique membership # to identify themselves. They enter that into a form that contains a payment option but the payment fails for some reason. Now they are unable to make a new submission because their unique membership # was used up by the incomplete submission. In addition, malicious users can prevent others from making submissions by using their membership # to create an incomplete submission.
Shouldn't the field value only be "used up" once the sbmission is complete instead of when it is submitted?
I think that needs a little manual job for now. There may sometimes be a case regarding on the "incomplete payments" that they can pay you manually instead "online". So therefore you need to mark incomplete submissions as complete, otherwise delete them. This will also removed the unique data restriction.
I would suggest to enable receiving submissions notification even on incomplete payments so you will be aware of every "incomplete payments".
I will also submit this to our development team so they can consider this as an enhancement of the the unique field feature. We will inform you here once this changes will be implemented.
I think I see the problem. If the unique field only got triggered upon completion of the submission it would allow duplicate values, because once a payment has gone through (to PayPal etc) it is too late to block somebody's submission on the basis that it wasn't unique.
Your comments will help our developers to find the best solution for this, there is a ticket already forwarded to them so hopefully you'll get an update sooner than later
Apologies for the very late update, but I'd like to let you know that I have released a fix for this problem.
Unique field data check can now be bypassed if the pending submission is older than 24 hours (time allowance for payments that are not reflected right away).
Please do inform us if you have follow-up questions, if you are experiencing issues that are related to this topic.