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

    Old conditions wizard: Spinner fields are not displayed in the action when a rule is set to Spinner field

    Asked by grade4pagasa on July 18, 2016 at 09:24 AM

    I created 2 spinner buttons and when I used the old platform to disable 1 spinner button, it won't give me that functionality (fig. 1).

    But when I edit the same form using the new platform, i can enable or disable the same spinner button (fig. 2). 

    And when I revert to the old platform (with the saved form using the new platform), i can see that the same command is saved successfully (fig. 3). But when i try to edit it and disable, there's no option to select the same spinner button. 

    * Please continue letting the users access the old platform.

    - Randy 

     

     

    fig. 1

     

     

     

    fig. 2

     

     

     

    fig. 3

     

    Bug Report platform in JotForm style uploads png
  • Profile Image
    JotForm Support

    Answered by Kiran on July 18, 2016 at 11:47 AM

    I see what you mean and am able to replicate the issue at my end. There have been several improvements made to the application that includes the Conditions wizard. We recommend you to use the new wizard only. The old wizard might be disabled once we have everything in place in the new wizard. Since the issue is with the old wizard itself, I'm not sure if this issue can be considered for a fix. However, let me forward the issue to our backend to see if it can be fixed. If we have any update in this regard, you'll be posted here.

    Thank you!