[STATUS: LAUNCHED! 🚀] Request Form

100% yes!

As more and more teams in my company come on board to the Wrike way, my forms are growing exponentially and people are becoming confused - which form for what?

I suggested this be sort of a form-chain where one form could branch to other forms that way you could keep things modular and teams can still manage their own requests/forms but we can have an overall general form to steer people in the right direction.

Yes, yes, yes please! We have large projects that require multiple deliverables and each one is now a separate request. It would be nice to be able to be able to request all the associated deliverables on the same request form. Either branching or daisy chaining would work, or be able to associate/refer back to an existing request and have the projects automatically tie them all together.

Yes this would be very helpful.  We have projects that span multiple departments and to have a form that could generate a task for each with it's own workflow and parent folder would be very helpful.

Yes! I was looking for this today. I would like the ability to create multiple projects from a single form as well. It would keep team members less grumpy when multiple projects with redundant information are needed at one time. 

Totally agree with Charlene on this! Forms absolutely should have the ability to create multiple tasks. This way, the submitter does not need to sit there create 10 task requests just for 1 project. I really thought this was a capability for Wrike and was crossing my fingers this would be the solution to my team's Excel tracking woes. 

Do we have any update on this @Wrike Team?

@Everyone Hey, thanks for bringing this up and adding your comments and use-cases. For now I can't share an update, but I'll get back to you when I have news.

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

I accidentally started my own thread for this, but to repeat as others are following:

I would see extreme value in a request form that not only creates a Project but also lets you create tasks from the selection of checkboxes/questions.This is for when a project has multiple deliverables but can vary project by project, so a template is inefficient to use.

In my head the request form would allow you to 

1) generate the project name based off a question

2) saves the new project in the correct folder

3) enables a prefix to be applied

4) the checkboxes options are entered 

5) A task is created for each checkbox selection. And the task name is [prefix] "option 1", [prefix] "option 2" etc.

6) scheduling would be more difficult but an end date and duration option could be of use, then it is up to the designer to complete all tasks in the time frame. 

In our case when we are purchasing a property and the design team is requested to create various documents. Sometimes they are required to create 6 documents, other times only 2, so having the checkbox create a task for each deliverable would save us so much time and very clearly show what is required from the request form. 

@Claire, hey again, thanks for posting 🙂 Do you mind if I delete your standalone post on this, so that all the related feedback is in one place? Allso, please make sure to upvote this original post by @Devon Marie 👍

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

This would be so amazing! We have issues where there is a campaign request that involves the building of landing pages, sending of emails, creating digital ads, making brochures and so on! 

Currently our Sales team just puts a request in and dumps all of these deliverables into one project and we are left sorting all the different pieces out. It's a time suck. 

I agree on this request.  It would be hugely beneficial.

Just wondering if there has been any update on this topic not followed up on this thread? This would be very valuable for our team as well. 

Hi! I am interested in an update as well - I accidentally made the same post and 67 people have upvoted that post, combined with the interest shown here looks like people really want this

Claire Castle Hi! We have a huge need for this as well.
I can't find your other request though to upvote it, can you send me the link please?
Have a great day :)

Soraya Jung Claire Castle Nich Adam Julie Watt Jagoda Auger Devon Marie Valastro Annie Phan Elijah Rubin Doug Clift Charlene Chang Melissa Kolbe

New updates to the request form logic now allow you to create conditional subtasks and subprojects from one form minimizing the number of intake forms your customers need to submit. See the section on conditional subprojects/substasks. Hope this helps.

https://help.wrike.com/hc/en-us/articles/115003404345-Dynamic-Request-Forms#subprojects

@... Hello! 

Thank you for informing us of that update. 
Can you give us an example though of how this allows us to create multiple tasks from one request form? For example, our Customer Care dept has asked me to make them a request form for hotel & taxi bookings. 

Page 1: We ask for the client details. A dropdown asks them to select whether they want to book a hotel, taxi, or both. The selection of that dropdown bumps the client to pages 2, 3, or 4 accordingly. 

Page 2 - only has fields for the hotel booking, then the form is submitted.
Page 3 - only has fields for the taxi booking, then the form is submitted.
Page 4 - has fields for the hotel booking, then it bumps them to Page 2 for the taxi booking; then the form is submitted.

It would be amazing if we could choose for each page to create its own task.

How does this currently work with the current dynamic request forms? 

Thanks!

Hello everyone - I think this issue is solved, as it is possible to create subtasks from blueprints dynamically from a request form: https://help.wrike.com/hc/en-us/articles/1500005219582-Conditional-Subtasks-and-Subprojects-in-Request-Forms

Hi Lisa, if you agree, you could mark this thread as "Completed", too.

Dear Cansu and Lisa,

I'm impressed of your perfect teamwork! 😁

Florian

Thank you Florian Kislich, we try our best! 😊

Hi @..., Lisa! Just jumping back into this topic because no one was ever able to answer my question...
It seems that Florian's team uses request forms different than we do (not a surprise, there are so many diverse companies using Wrike).

I'm curious if the original author of this post, Devon Marie Valastro finds the conditional subtasks blueprint logic actually solved her problem. Or if, like us, the request forms are still extremely limited in terms of having multiple tasks created by one form (and with the client's responses mapped separately into each of the appropriate new tasks). That was how I understood Devon's original request.

We're getting to a point where we have to hire a developer to get around the limitations...

Ps. Just realized I created a product request on this topic back in 2019. Will keep an eye on the topic there ;) https://help.wrike.com/hc/en-us/community/posts/360037721213-Include-Subtask-Details-with-Dynamic-Request-Forms

Hi Soraya Jung, thanks for posting and sharing the link to your request. All members who support this suggestion - please upvote Soraya's post 🙌🏼

Definite upvote on this request - this would be a very helpful feature for our team's use as well.