SubTask Flow
Tasks that create tasks, workflows that build themselves
SubTask Flow lets you create hierarchical relationships between GLPI task templates. Each parent template can have multiple children, and each child can be conditioned on a specific solution: for example, 'Yes' sends the flow down one path and 'No' down another.
LicensedGLPI 11 and 12
Features
When the technician records the solution in the ticket timeline, such as Yes or No, the module automatically creates the child tasks of the chosen path. If the template has no condition, the child tasks are created when the task is completed. Each child task inherits from its template the content, category, duration, privacy and the assigned technician and group.
The execution tracker records every parent-child relationship per ticket, with who triggered and who completed each step. When templates are linked, the module prevents linking a template to itself and warns when it finds a cycle between templates. Optionally, the technical group of each created subtask is added to the ticket as an observer.
How it works
Step 1
Configure solutions
Define the possible solution options (e.g. Yes, No, Partial) used as branching conditions.
Step 2
Create the flow in the template
Open a task template in GLPI and link the child templates, choosing which solution triggers each one.
Step 3
The flow runs by itself
In the timeline, the technician records the solution and the module creates the tasks of the chosen path. Without a condition, the child tasks are created when the task is completed.
Step 4
Track in the log
The Records tab shows each execution: ticket, parent task, child task, who triggered it, who completed it and the dates.
See it in action
A quick tour of what the plugin does in practice.
Video demo coming soon.
Image gallery
Screenshots for this section are coming soon.
Start using SubTask Flow
View available plans or read the full article about this module.