Community

Welcome 🖖

Hi there! 🙂 Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome 🖖 Have you checked out this week's Release Notes yet?

Hey! 👋 Curious about something? Visit How To to search and ask the Community for answers.

Welcome! 👋 Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.

What can we help you with?

e.g. Gantt chart, Creating tasks, Sharing folders...

Cascading/Conditional Fields In Request Forms

6 comments

  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Laura Boylan

    Stephanie Townsend - If you haven't seen the similar request at https://help.wrike.com/hc/en-us/community/posts/115004517529, you might want to add your vote there.

    I've mentioned this elsewhere, but will repeat in case it helps anyone else... We currently use Formstack + Wrike Integrate for our more advanced forms, due to the more advanced functionality Formstack offers, and the easy integration via webhook. We'd prefer to keep all our forms within Wrike but need more options for formatting and dynamic/conditional questions before we can bring all our forms back into Wrike.

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Elaine

    Hi Stephanie Townsend, thanks for the suggestion! 🙂

    As Laura Boylan mentioned, it would be great if you could add your vote to the above request in our Product Feedback forum. That way, it'll be one step closer to receiving a status. You can read more about the Product Feedback process here.

    We really appreciate and encourage feedback and suggestions here on the Community, and we'll share any updates as soon as we receive them 👍

    Elaine Community Team at Wrike 🌎Discover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Joel Gold

    (Edited )

    @Elaine & @Laura, the use of Formstack is a great workaround, it would be even better if folder/project/task descriptions could display proper HTML buttons.

    For example, imagine you have this important Formstack form that your users are constantly using, it would be awesome to have buttons for those forms displayed directly in the project description of the Wrike project using the form. You could even have the hyperlink behind the button land to different versions of the same Formstack form, where part of the questions are already answered, like this users are not made to answer questions like: “which Wrike project is this for?”

    Essentially you could have the description of each project/folder/task have a unique “launch Formstack” button that you already know what folder/project/task the form is being launched from.

    Please see my post about this here:
    https://help.wrike.com/hc/en-us/community/posts/360037534433-Buttons-Interactive-Objects-full-HTML-in-Task-Descriptions

    This would make use of Formstack (or other similar products) seamlessly integrated in Wrike for our users, as opposed to having to leave the Wrike workspace manually to another system to launch these dynamic forms.

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Lisa

    Hi Joel Gold, thank you for weighing in and also for posting your related suggestion 🙂 Our Product team are looking at automation generally, so this feedback should be very interesting to them. 

    Lisa Community Team at Wrike 🌎Discover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Stephanie Townsend

    Thank you, everyone. I have added my comments to the other open questions.

    We are hoping to use Wrike's built-in reporting/viewing features and are not currently connecting Wrike to another database for reporting where relationships can be built. Using the recommended workaround by creating an independent custom field for all the variations is creating limitations in reporting, request forms and making maintaining the systems difficult.

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Hugh

    Hi Stephanie Townsend, thank you for all of your input and feedback. As soon as I have any updates for you, we'll let you know. If you have any other questions or feedback, let me know! It helps our Product team in discussions about possible future updates 😊

    Hugh Community Team at Wrike 🌎Discover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 0
    Comment actions Permalink

Please sign in to leave a comment.

Folllowing List for Post: Cascading/Conditional Fields In Request Forms
[this list is visible for admins and agents only]

Community

Welcome 🖖

Hi there! 🙂 Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome 🖖 Have you checked out this week's Release Notes yet?

Hey! 👋 Curious about something? Visit How To to search and ask the Community for answers.

Welcome! 👋 Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.