Hi, I've created a multi-step webform.
Once submitted, this webform is to be reviewed by authorized people that are suppossed to fill in some private fields in the last step.
These users have to go through all pages to reach the last one and do theri job.

It would definitively more user-friendly if, during webform editing only, a user could be able to jump to a specific page by clicking on the corresponding label on the progress bar.

Could anyone help or give some directions on how to implement this modification?
Thanks in advance

Comments

quicksketch’s picture

TBarina’s picture

Thanks for your prompt reply.

Would it be possible to have at least a button "Jump to last page" during webform update operation only?

quicksketch’s picture

I think the best way to handle this would be to enable the feature you requested first (being able to jump to a specific page). Though jump to end would probably be easier to implement in the short-term, I think properly making the progress bar clickable would probably be more useful to both administrators and end-users. No matter which approach we use, we're going to run into weird scenarios where conditional logic would make certain pages skipped.

TBarina’s picture

You are right about wierd scenarios. That's why I was proposing to implement this only in update mode (i.e. when editing a submission record).
Surely this feature cannot be made available at the time of the first submission.
But right now I cannot imagine what could possibly went wrong when jumping while in update mode.

A button for jumping to last page only could be an interim solution (adding the button to the form and coding a proper callback function that could be reused later on by a clickable toolbar).

I could try and do something but I need some guidance.

quicksketch’s picture

But right now I cannot imagine what could possibly went wrong when jumping while in update mode.

On page 1, imagine you have option A and option B. Choosing option A skips the second page entirely and submits the form. Option B takes you to the second page which has a number of required fields on it. Now if a user edits a submission, changes option A to B, and then skips the rest of the form, the required fields on page 2 will never be filled out.

I know that's a complicated scenario, but either approach we use we're going to have some problems like this. Of course the easy way out is just disable the option to skip pages if any conditional logic is specified (or maybe if any multi-page logic is specified). I think these are good ideas, but it's going to take some work to implement.

TBarina’s picture

Many thanks.
Ideally, changing to option B should lead directly to show page 2 (or show conditional dependent items on the same page) and the choice to jump to last page would be taken after viewing the fields.
But of course we could build, on purpose or by chance, any complex scenario that would be trapped.

Probably the best way would be to make the feature available on the admin setting form and let the user/admin/programmer decide for which webform to enable or disable it. In that case it would all depend on the logic implemented for the single webform that, only in some extreme cases, could be incompatible with the feature.

In any case thanks a lot for your prompt replies and your contribution to this great webform module.

DanChadwick’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

Considering that this is too difficult:
#304353: IMCE doesn't show up, javascript error

I don't see this request being implemented either, although I'd be happy to review a comprehensive patch.

delacosta456’s picture

Hi
if i get correctly what you are looking for maybe Webform Steps module is what you are looking for !

hondaman900’s picture

Webform Steps only allows stepping one page ahead. Has anyone found a way to jump to any page in a multi-page form?

rpataca’s picture

Would love to see this feature

joecorall’s picture

I implemented a module that solves this problem: Webform Skip