- TableauxAsked on July 18, 2016 at 03:44 PM
I am building a multi-page form. Is there a way to show how many pages are left? Something like the "Progress Bar" widget but for pages not fields.
- JotForm SupportMike_GAnswered on July 18, 2016 at 05:12 PM
You can use Text fields on your form to show pages and remaining page left like, "Page 1 of 4".
Here's a sample form: https://form.jotform.com/61996858693986
I hope this helps. If you have any other questions or concerns, please feel free to contact us anytime. Thank you.
- TableauxAnswered on July 19, 2016 at 10:35 AM
This won't work for my needs.
I need the pages left to change dynamically based on field entries/conditions. Depending on how a person answers a specific field, they may have 3 pages left or 2 or 4.
- CharlieAnswered on July 19, 2016 at 12:16 PM
Unfortunately, we do not have this kind of widget. I presume you are skipping pages is that correct? Which means you want to only count the number of pages remaining if they are somehow "required"? The problem I'm seeing is that pages do not have that kind of setup in our end, the conditional logic "Skip to page" simply skips the user to another page, but that doesn't make the page "inactive" or "unrequired", with that limitation, it is quite hard to actually count the remaining pages. So far, the only widget that can track the progress on a form is the Progress Bar widget, but it is field specific and not on pages.
Another problem I see on this feature is that pages dynamically change as you have mentioned, I believe it is somehow a confusing way to tell the user the real progress of what he/she is filling out.
1. I'm on page 1 and fill out all the fields there, a feature tells me that I am 1 out of 14 pages or 13 pages left.
2. Now on page 2, I fill out some fields AND based on conditions I will be skipping some pages, a feature then tells me that I am 2 out of 10 pages or 8 pages left.
This is where the confusion starts, it informs be that I should be filling out 14 pages or at least 13 pages when I was on page 1, however in page 2 it then changed. An actual limit of pages should be static, which means it is already should be defined to be used as a basis of progress completion.
I might be missing something here, if you could provide us more information on how the function should work correctly, then I could try forwarding it as a feature request to our developers.