Ability to test Request forms in Draft mode
It's great that we have the ability to create drafts for Request Forms.
It would be very useful to have the ability to test the updates that are applied to the form before they get published. It could be done through a temporary short link.
We currently need to duplicate the form to test any modifications and apply them again to the original form after they have been tested.
Hey Roxane Carrier, thank you for submitting this idea!
When you mention testing the updates, do you mean the actual projects or tasks and their attributes that are created after the form is submitted?
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,
yes, we would like to still have the actual tasks/projects and attributes created. We typically use Test in the name of the projects/tasks that we are creating, when testing to make it clear to the team. Our challenge here is to be able to test updates on live request forms without publishing them right away.
Let me know if you need more info
Thanks for clarifying Roxane Carrier 🙌 I'm passing your feedback to the team 👍
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 is a great idea.
Currently, my workaround is to use a duplicated version of the blueprint that only has job roles assigned to prevent unnecessary notifications going out and cluttering inboxes with test tasks. But there's still a bunch of test tasks that need to get deleted.
Thanks for sharing this workaround and for adding your feedback here Jessie Stith, it's much appreciated 👍
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
Hi, I'm wondering if there has been an update to allow testing form set up before publishing.
Hi Diana Vicens, welcome to the Community 👋
No updates for this suggestion at the moment; please be sure to upvote the original post above if you haven't yet - the votes help our team gauge the popularity of different ideas in this forum. Once the post reaches the 60 votes threshold, we'll add one of the statuses here.
Please let me know if you have any questions or need help with anything else 🙂
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
Upvote here. We are planning an update to a 10+ page form. We prefer to create a brand new request form. However, the URL associated with the current form is referenced on countless SharePoint sites and user email signatures, and managing communications and changes for hundreds of users is not an approach leadership prefers. Our experience with the request form requires extensive testing to ensure we checked all the right boxes, applied the right custom fields and branches correctly, and flows well for the end user; "code review" (aka a second eye on the setup) is not the only testing method we can employ with confidence in the end result. Without the ability to test a draft copy of the request form, we must build a new form (now at 18 pages) to get client approval. Then we must rebuild the existing form to the approved design to maintain the URL. The new build of the form must be done off-hours (on the weekend) to thoroughly test because it must be published and is, therefore, "live" to the end users.
Thank you for sharing detailed feedback Gretchen Linder, I'll be happy to pass it on to the Request forms team 👍
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