Task steps Steps are used to define a multi-step process within a single task , as an alternative to rather than creating several tasks. This makes sense especially when the same person is performing all the steps, or when the steps are used as a reminder for actions that may or may not need to be done. Adding task steps to a task template can be simpler than creating multiple tasks in a task workflow, as the information is all in a single task. They are best used when you do not need an audit trail of when each step was done and by whom.and when there is no need to track the time it takes for each step to be completed. They can simplify workflows and reduce the overall number of tasks, while providing reminders about steps that should be done.
Individual task steps Individual task step records are linked to a specific task template and can only be used in that template. They Task Step records are very simple records with just a Step Number, Status, Title and a Sort Order. In a Task record created from the template, Task Steps appear as a set of checkboxes in the order defined by the sort order.
Screenshot image of a Task record showing the Task Steps set of checkboxes for items like Perform Backup, Stop all Services, and Reboot Server, Description and link to the Task Template.
Task steps are always created from within a task template, as described in the Task Templates section. They should not shown below, or they can be created directly , since without being linked to a task template, they will never appear anywhere. There with the task template specified. There is no automation on this table.
They appear within task template records as a related table ordered based on the Step Number.
When a task is created from the template, task steps are displayed as a list of items with checkboxes:
