...
The next sections outline the important fields and options on each of the Task Template record layout tabs.
Template Details Tab
...
The automation on the Task Template table is almost all designed to handle the conversion into tasks when triggered from elsewhere, rather than to manage a process within the Task Template itself. It is described in the appendix.In general, there are "flag" fields in the task template that get set to Yes to trigger conversion for each of the different main record types, and linked fields to the source records so that the new tasks that are triggered can be linked to the correct service request, project, or change requestincludes rules to strip out any commas from the task title, a rule to update the sequence of task templates in relation to other templates for the same workflow, and the rule to unlink inactive task templates.
In addition, the system tracks all the service requests and projects for which a task template based on user selection has been generated so that users are prevented from generating the same task for the same parent record. Since change request tasks must be generated multiple times, one for each asset, we cannot block this in the same way.
...
Task workflows may be cloned and then modified, and when a task workflow is cloned, its task templates and any task steps are also cloned and linked to the new workflow.
Cloning reproduces all the elements of the original task template except any task steps. If task steps were involved in the task template, they will need to be recreated in the cloned template..