[Status: Not planned] Modular Questions or Nested Forms for Creating Request Forms
Being able to pull questions from a pool of modules for a request form (or nesting other forms) would be a huge help in creating/updating custom forms.
Our company has 40+ spaces, one for each department and collaborative effort. Currently, the only way for a form to place a project/task in the correct space is by creating a dropdown with each of those spaces as an option. If a new space is added, the new option has to be added into the dropdown on every form.
If it was possible to create one question as a module or separate form that could be nested into a new form, the question would only need to be updated in one location.
In addition to assigning spaces, this kind of option could be related to users, owners, folder locations and adding tasks. IMHO, modules and/or nesting could hugely impact the usefulness of request forms.
An awesome idea, this would be super useful!
Hi @Patrick, thanks for posting your idea!
I checked with the Product team, and for now the suggestion is not planned. It doesn't mean it will never be released! I personally really like the idea and I can see how it can be useful. I'll get back to you here if there's an update.
@Ben Thanks for adding a comment here :)
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Hi everyone, a quick update; this is not planned as of this moment. I'll let you know if there are any updates.
This is a huge pain point for me as I try to build out complex automation with request forms and blueprints.
Here's my use case:
We have a request form for one-off emails. It includes required fields so I can pass along all the information our team needs to do.
We also have a request form for complete campaigns, which almost always include emails. I would love to be able to check a box that indicates that this campaign will contain an email. That box would trigger a subsequent request form on the next page (the one-off email form). That way I only have to build out the email request form once.
Thanks so much for sharing your use-case Anna Wallace, passing it on to the team right now 👍
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Hi Lisa and Wrike team,
Do we have any update on this one ?
Hi everyone! I've checked with our team responsible for request forms, and they don't have this idea on the roadmap at the moment. If anything changes in the future, we'll let you know.
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Added an upvote for nested forms. We have a form covering requests across five topics. The landing and submission pages are common for each topic. Each topic contains a series of unique questions and multiple pages within the form. As we're undergoing a redesign effort, we thought it would be easier to design each topic's form independently for two reasons. One, managing the pages and questions becomes easier from a UI perspective. And two, there are topics that relate to some groups and not others and an independent form would allow those groups to provide references (links) directly to that form. It becomes challenging with the common landing and submission pages, but the primary UI challenge is managing the topic's form pages within the larger comprehensive form. Anyway, just a few thoughts since this came up recently in my team's discussions.
Hey Gretchen Linder, thanks for taking the time to share this detail with us here. It's really useful and we've passed it on to the Product team 👍
Elaine Community Team at Wrike Wrike Product Manager Learn about Wrike’s killer features and best practices with our Online Training Webinars
Elaine Wrike Team member Learn about Wrike’s killer features and best practices with our Online Training Webinars
+1 for nested forms.
We have multiple request forms where nesting would be very beneficial and would actually save time. Example: we have a request form like 'Assign a standalone task' where people can assign standalone tasks by team or by type of tasks (whatever user prefers).
If the user wants to assign task by team and selects 'IT team' then I'm asking a follow-up question to make sure if the requestor actually wants to assign a task to IT team or is looking for help and therefore should make an IT helpdesk ticket. We have a separate form for IT helpdesk tickets which I would gladly nest when the requestor actually wants to make an IT helpdesk ticket and not assign a task to IT team. Right now I have duplicated relevant pages for helpdesk tickets in this 'assign a standalone task' form to make experience seamless for my users.
Same for Procurement team. I'm making sure if a user really wants to assign a task to procurement team or just make a purchase order. We have separate form for purchase orders, but I have also duplicated relevant pages in above request form so the user can continue in the form he just started.
Hi Łukasz Marek 👋 Thank you for the upvote and for providing such a detailed explanation of how this feature could benefit your organization. If there’s any progress on this suggestion in the coming months, I’ll make sure to keep you updated.
Rohan V Community Team at Wrike Wrike Product Manager Learn about Wrike’s killer features and best practices with our Online Training Webinars
Rohan V Wrike Team member Learn about Wrike’s killer features and best practices with our Online Training Webinars