Request Forms: redirecting depending on variables

We have request forms with over 30 pages and complex questions, so i try to avoid duplicating the same questions on different pages. I'd like to ask the relevant major questions at the beginning of a form and gather more detailed information later. But If there are detail questions for more than one major options, I have to duplicate them to be able to redirect to different pages afterwards.

Being able to temporarily store variables (set by checkboxes, dropdows etc.) and use them later in the form to redirecet to certain pages would be very helpful!

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Cansu Yetisgin

Hi @Florian Kislich, thanks for posting your use case here! I've shared your feedback with our Product team 🙌🏼

Stacey Olsen

I second that!

Cansu Yetisgin

Thank you for supporting this suggestion @Stacey Olsen 👍🏼

Tiffany Sands

Yes please! I have wished for this multiple times now while building forms for our Organization!

Putting this context on both threads for the Wrike Team:

Specifically I will use our Creative Request Form as an Example. We need to know how the Creative will be billed and where time will be logged. We have retainers with different departments for each client. So first we have a question asking which department is making the request.

Then we have an action based on their answer here. For each department we created a DB that just list out all of the retainers for every client that has a retainer with them. So after the User chooses the Department they get a Single Answer question that pulls from this DB.

Then for each retainer we set an action to add it to a Parent Folder based on the Retainer chosen. We have well over one hundred Retainers and this needs to be updated every time a new retainer is signed or cancels. This then has to be done on every Internal Request Form we have. This is very time consuming. Being able to save this in one place and just edit it once to update across all forms would be amazing.

Basudha Sakshyarika

Thank you so much, @Tiffany Sands, for sharing your use case. 😊 That's a great example! I am forwarding this to our product team. 👍🏽