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. When making task A dependent on task B, task B must be on the same template and above or to the left of task A in the plan view. The “Set Dependency Across Templates in GUIDEcx” recipe enables the ability for a task to be dependent on another task regardless of which templates the two tasks are on.
For example: When the task “Configure Server for Customer” (on template 1) is marked Done by a user…
…we want the task “Set up Training” (on template 2) to go live:
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 for this integration:
Add a “Gate Task” directly above the task “Set up Training”. We recommend naming this gate task the same as the destination task, with “(Gate Task)” added as a suffix (e.g. “Set up Training (Gate Task)”)
Make the destination task (e.g. “Set up Training”) dependent on the gate task.
Now that you've added that task to your template you're ready for the next step.
Within Recipe Builder:
Open the recipe
Enter Edit mode
Click on the trigger step.
Add the source task(s) to the trigger conditions. Multiple source tasks can be entered simultaneously by separating them with an “or” operator.
Include one “Add items to Source Task / Gating Task Pairs list” step in the recipe for each source task / gate-task task pair. For example here is the step for specifying that when “Configure Server for Customer” is marked Done by a user we want the recipe to automatically mark “Set up Training (Gate Task)” to Done:
Start the recipe. The integration is now live.
This single recipe will work across all projects, simultaneously; if a task matching a source task name is marked Done by a user, across any project, the integration will update the matching gating task (on the same project) to Done.
Recipe Testing
Follow these steps to test the recipe:
Create a project with your two templates
Mark source tasks as Done
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).
Celebrate because now your dependency logic is even more powerful!
NOTE: You can add any number of task pairs to the recipe. But if another group at your company would like to define their own inter-template dependencies, it may be easier to maintain if they have their own copy of the recipe. To do this simply clone the recipe and edit it using the same steps as described above.