Request form conditional branching
Hi all,
Putting this out to the community in case others have tried to do the same. We are looking to combine a few of our current request forms into the one big form. There's a few reasons for this but mainly often a request includes a few different things and can mean people have to fill out multiple forms (design request etc). My issue is when asking requesters to select what their request is about if I make it multiple select I then can't branch out to different pages to collect the relevant info. I need to make it multiple select as often they need a few things however each request has a set of different questions.
Has anyone else tried to do this and found a work around? I tried doing follow up questions and mapping it this way however the form only redirects to one of the pages and not the others selected.
Would appreciate any tips!
Hi Amy Hunter,
unfortunately I also have not found any workaround other than creating specific form pages for all the necessary combinations, often repeating the same questions.
I preferred to divide into different forms and instruct the team to use the most correct form for the specific need and/or request the form to be filled out more than once.
I agree with Pietro, I haven't found a good work around for this either. I find on some forms it makes sense to just repeat questions, other times it makes sense to start a whole new form. For my organization, we have one branching "Master Form" for each department that contains all of the forms they use. So, at least they only have one link to go to for all forms, however if they need multiple things they have to fill it out more than once. This is not ideal, but it's the best I've been able to do so far.
Amy Hunter - I've done something similar to Pietro. I have a couple of branching forms. When creating these, I map the form out on paper before making anything. The map branches out (like a tree) the further down you go. I aim to collect the general info as high up the tree as possible, which minimizes duplicating questions.
Example - We initiate new process development projects with a request form. We have 5 separate divisions and 2-3 different project levels for each division. I start collecting general part information on the first page, then use the division to map to the next level data, where we collect division-specific information. Then map to project-level specific information. This duplicates the project-level questions, but since we have different templates in each division, this is necessary for us.
It doesn't prevent duplication but minimizes it. I do something similar for maintenance and employee feedback. Collecting general information before directing the requestor to a new page.
Thanks Pietro Poli Ali Moses and Mike Fank your suggestions are very helpful and I really appreciate it!