Skip to main content

IMPORTANT - Product End of Life Statement - IMPORTANT

Request RE, Survey, and Calendar 1.5 Support Ending December 31, 2020
Contact Kinetic Data Support with Questions
Kinetic Community

6 Tricks with Subtrees




This presentation covers what a subtree is, how to use subtrees, and six tricks to get the most out of your trees in Kinetic Task.




  • What is a subtree?
  • 6 Tricks
    • Build reusable subprocesses
    • Break up large trees
    • Simplify task parameters
    • Reduce task parameters
    • Use subtrees for updates
    • Use subtrees to repeat
  • Recap and discussion


Subtrees are Kinetic Task trees that can be called by other trees.  They can be used to increase reuse and decrease complexity.  Subtrees are created and cloned like a tree, and configured and used like a task handler.  There are two types of subtrees: shared subtrees and local subtrees.  Shared subtrees are categorized like handlers and can be used by any tree throughout the system.  Local subtrees are displayed in the special Local Subtree builder task category, and are only available in trees that share the same source root / source group categorization.

Subtrees can be used build reusable subprocesses, which can then be leveraged in other trees to avoid duplication of effort and to simplify the master process.  Common examples of reusable subprocesses include approvals, reminders, and SLA logic.  Subtrees can also be used to break up large trees, thereby improving maintainability of your processes.  By wrapping handlers with complex parameters in a subtree, it is possible to simplify task parameters and to reduce task parameters.  Simplifying and reducing task parameters, such as wrapping a send email handler to build an email template subtree, is another way of decreasing complexity.  By using subtrees for updates, it is possible to implement even more advanced processes to be run whenever a deferred task is updated.  Lastly, it is possible to use subtrees to repeat a process an unknown number of times by having a subtree call itself!