Set Multi-Task Dependency in GUIDEcx Recipe

Learn how to set up multiple task dependencies for one task!

Elan Maynez avatar
Written by Elan Maynez
Updated over a week ago

Recipe Overview

Built into GUIDEcx is the ability to make a task dependent on another task, a task group, a milestone, or the completion of an earlier template. The “Set Multi-Task Dependency in GUIDEcx” recipe enables the ability for a task to be dependent on several other tasks regardless of which templates/milestones/task-groups the tasks are in.

For example: You would like the task “Grant Access” to go live when all of the following dependency tasks are completed: “Conduct Internal Planning”, “Verify Customer Setup”, and “Widget Settings”.

You can now do this! All you need to do is follow the steps found below:


Integration Setup

Installing the Recipe

Prerequisites: An Admin license in GUIDEcx

Follow the steps outlined in the video below to install the recipe:

Get Your Template Ready:

  1. Add a “Gate Task” directly above the task “Grant Access”. We recommend naming this gate task the same as the destination task, with “(Gate Task)” added as a suffix (e.g. “Grant Access (Gate Task)”.)

  2. Designate the destination task (e.g. “Grant Access”) to be dependent on the gate task. It’s also a good idea to make the gate task have a visibility of internal hidden.

Now that you've added that task to your template you're ready for the next step.

Within Recipe Builder:

  1. Open the recipe

  2. Enter Edit mode

  3. Click on the trigger step.

  4. Edit the trigger condition to include all of the dependency tasks. Multiple dependency tasks can be entered simultaneously by separating them with an “or” operator.

  5. Edit the “Create Dependency Tasks List” step to include all of the source tasks.

  6. Edit the “Create variables Gate Task” step to designate the name of the gate task.

  7. Start the recipe. The integration is now live.

This single recipe will work across all projects, simultaneously; if all tasks matching the dependency task names are marked Done by users, across any project, the integration will update the matching gating task (on the same project) to Done. That will make the destination task go live.


Recipe Testing

Follow these steps to test the recipe:

  1. Create a project with your template

  2. Mark all of the source tasks Done

  3. You should see the integration will automatically mark the gate task done. You will also see that the destination task goes live (the red dot on the dependency icon will turn green, and the start/due dates will change from a light gray font to dark black).

  4. Celebrate because now your dependency logic is even more powerful!

NOTE: To create another multi-task dependency, simply close the recipe and edit it using the same steps as described above.

Did this answer your question?