Our use case:
We have a Wrike request form that allows staff to request help from our IT team. This form allows the submitter to select from a list of topics, one of which allows them to request a replacement ID/access badge.
If the reason for this replacement request is that the badge was lost or stolen, we also need to open a Security Incident task (where the task/subtasks are pre-defined as a template task that needs to be copied).
- The reason for badge replacement is recorded in a task-level custom field called Badge Reason. This information is populated by the request form.
- A second custom text field called Wrike Integrate allows us to identify new tasks vs. updated tasks. This field is always blank for new tasks created by the request form.
- A Wrike Integrate recipe triggers on New/Updated tasks in the folder where badge replacement requests are created by the request form, where the Badge Reason field is either Lost or Stolen, and the Wrike Integrate field is empty. This recipe copies a Security Incident template task (with a number of ordered subtasks) into a different team's space, then updates the badge replacement task that triggered the recipe to add text to the Wrike Integrate custom field (so additional changes to the badge replacement IT task don't trigger the recipe again).
The challenge... when Wrike Integrate loops through the subtasks, it apparently does so in reverse order, so the subtasks on the copied task initially appeared in reverse order and had to be manually re-organized.
We revised our recipe to solve this problem, so the subtask order on the new Security Incident task matches the subtask order on the template task.
Example Wrike Integrate recipe:
If anyone else needs to accomplish something similar, here's a community recipe we shared that shows how to copy the task then loop through and copy the subtasks in the correct order. (This example recipe doesn't include any trigger conditions or actions that rely on custom fields, since those are unique to our Wrike Integrate account.)