Page Break: Make it possible for "Auto Next" to work on widgets as its trigger point

  • Profile Image
    Asked on August 01, 2016 at 02:08 PM

    I'm struggling with conditional logic to get user to transition to different pages. I have tried to repurpose the 'submit' button to go to a different page. I have also added some radio buttons and conditional logic with both the text of the button and "value" of the options which I've just assumed is "1" and "2". Can you please tell me what the best way to do this is. Thanks

    This is a re-post of a comment on How to Skip Pages Using Conditional Logic

  • Profile Image
    Answered on August 01, 2016 at 03:57 PM

    We would be more than happy to help assist you with getting your form conditions up and running.

    First off, may we know which form you are having this trouble on so we can take a look?

    Is it this one here ****link removed***** which seems to be your latest form but please let us know which if not?

  • Profile Image
    Answered on August 01, 2016 at 10:49 PM

    I can see when you select an option from the first page, it won't take you anywhere, because the next button is hidden, simply make it visible:

    Let us know if you need more help, we will be glad to assist you.

  • Profile Image
    Answered on August 01, 2016 at 11:45 PM

    Hi BDavid,

    I don't understand why you can't hide the "next" button and "auto next"
    like you can with the other features.

    This seems like a lazy response to a bug.

    Please explain.


  • Profile Image
    Answered on August 02, 2016 at 12:17 AM

    Could you please also remove the link to my form as it's still under development.



  • Profile Image
    Answered on August 02, 2016 at 04:17 AM

    Hi Jo,

    I made this thread private. Any information posted here is now safe for public views.

    With regards to the issue, I see that you have enabled "Auto Next" on page break buttons. FYI, this feature was implemented recently about a week ago and will only work on regular radio and dropdown fields for now as its trigger point and they must be the last field on every page. All widgets like Button Radios aren't yet supported.

    Here's an example using a cloned version of your form. I replaced the button radios widget on the first page using a regular radio button field. Feel free to test so you can see how it works.

    *****link removed*****

    So for now, if you want to continue using the button radios widgets, we suggest to show the next and back buttons in your page break field so your users can navigate through the pages using these buttons. Otherwise, if you want the "Auto Next" to work in your form, replace the button radios widgets with a regular radio button field.

    I will also escalate this to our developers as an enhancement request for the "Auto Next" feature.

    Thank you!

  • Profile Image
    Answered on August 02, 2016 at 04:45 AM
    Thanks for the detailed explanation.
    That all makes sense.
    I would be great if you could update me on this feature, but understand if
    you guys don't have a system to do that.
    Also, would prefer that you remove both links as I have seen other message
    where support staff have said the message has been moved to private and
    clearly this sometimes doesn't work.
    Also, this is really good info for others. So happy to make it public with
    both links removed.
    Thanks again,
  • Profile Image
    Answered on August 02, 2016 at 05:26 AM

    Yes, we will let you know via this thread once auto next will work on widgets.

    I have now removed the links and set this thread back to public.


  • Profile Image
    Answered on August 08, 2016 at 03:39 PM

    Any chance I could be notified once this is live?
    Exactly what I am looking for!!!
  • Profile Image
    Answered on August 08, 2016 at 04:11 PM

    @ BAGtheapp

    I created the separate thread for you here

    You will get notification there for any update on the status.