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.


  • Profile Image

    Is it possible to make a form too complicated?

    Asked by iondjp on April 06, 2017 at 01:45 PM

    I am really starting to appreciate the power of JotForm builder and tools. I have built systems similar to this years ago and I fully appreciate the complexity and the time. Well done ladies and gentlemen.

    You can skip to the bottom of my message to get straight to the point, but here's the background.

    I want to create a series of forms that will contain a client's details, quote notes and details, job details, and invoice details.

    Each section would be entered by a different person. For example, the receptionist enters the call details, then the estimator opens the half finished submission to enter quote details, then the project manager opens to add more info, etc.

    Each section will use complex hide/show conditions and required/unrequired conditions to make the form as specific as possible to the individual using the form. I don't have any issues building that form. All is good so far.

    If I was building a relational database (as in the olden days of my youth) I would have created three different forms (eg.: contact info, quote info, invoice info) and then pulled the data from database tables. However, I am not sure if I can (or even want to) dust off my rusty PHP or JavaScript skills to figure out how to pull data from one form's submissions to pre-populate the second and third form, and so on, and so on.

    Therefore, I was going to create a single form by using the JotForm builder and some custom HTML text areas to do all the 'heavy lifting'. Doing it all in one form means that there will likely be several dozen fields, a number of apps incorporated (like address verification) to provide functionality, and numerous conditions created.

    This leads me to my questions:

    1) Is it possible that I may make my form so complicated that it is too slow?

    2) With all the background scripts that are going to be created and referenced in my form, will it make my form prone to crashes or freeze ups?

    3) Is there a better way to do this without getting into complicated custom scripting to pull data from various form submission tables?

    Forgive me if I was too verbose ;-)

     

  • Profile Image
    JotForm Support

    Answered by david on April 06, 2017 at 03:02 PM

    You can create a sort of workflow process by using emails and include submission edits links.  The following thread has an example of how to do so:

    https://www.jotform.com/answers/853147

    It is indeed possible to make a form use enough resources that it would start to bog down the browser and potentially even crash it.  This usually starts to happen around 4-500 fields or when a couple hundred conditions are used. 

    This depends on the complexity of the conditions and how many fields are checked.  When using multi-page forms, all conditions are checked when navigating to another page and when the most strain is placed on the browser. 

    The continue forms later option also is not recommended when creating larger forms.  By larger forms I mean in excess of a couple hundred fields. 

    As for scripting in the form, we do not allow for adding scripts to the forms.  You can get the full source code of your form and manipulate that code in your page:

    https://www.jotform.com/help/104-How-to-get-the-Full-Source-Code-of-your-Form

    But the scripts cannot be added directly in JotForm.