Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Related Tasks tab shows the prerequisite tasks, if any, and allows the current task to be related to prerequisite tasks within in the same parent record. It also shows any dependent tasks (, that is, those for which this task is a prerequisite):

Sample Task recordImage Modified

In the above example, we see a task that has two prerequisites already defined. The Trigger Condition defines whether this task will be set to Assigned only when both prerequisites are done, or as soon as any of them are done. Additional tasks associated with the same Service Request can be added to the prerequisites by selecting the task and clicking the Add to Prerequisites button. Either of these two tasks could be removed by selecting it in the Remove Task from Prerequisites field and clicking the Remove from Prerequisites button.

...

This tab shows details about the record linked to the task, which will typically be either a project, service request, or change request. It provides hyperlinks to get to the source request to see more information.

Related Info tab of a Task recordImage Modified

Other Tabs

The Time tab allows time to be entered and shows all time entered for the task. Note that any time entered for the task will also be included in the request to which the task is linked.

...

  • When a task is created manually, if it is related to a Project whose status is Completed or Cancelled, the user is prevented from saving the task.
  • If the Date Due is in the past when the task is created, the user is warned but allowed to correct or save the task. These actions are done by the rule: Create: All create validations.
  • Next a rule called Create: All Creation Actions runs, and it performs several actions based on the record the task is related to. If the task template usage is Conditional, then the Status of the task is set to Conditional. Otherwise the default status is Queued.
  • If the task was assigned to an individual from the related record (i.e. , for instance the Change Manager or Project Manager), then the Assigned Team is set to that person's Primary Team. If no one was assigned at all due to some failure of the template, then the Assigned Team is set to the 1st Level Support Team.
  • If the task is created in a Status of Assigned, then if the Assigned Person is not the creator and there is an assigned person, that person is emailed, otherwise the assigned team is emailed.
  • If the task is for a change request and was generated as a single task, its sequence value is set to 1.
  • If the task source is a task template that had prerequisite templates, then the corresponding tasks are set to be prerequisites. The prerequisites are then sorted and the one with the highest sequence value is set in another linked field called Highest Sequence.
  • A rule called Create/Edit: Update Sequence based on Highest Sequence than runs to set the new task's sequence value to the highest sequence plus 1.
  • Note that the Sequence field is purely informational. No automation is triggered based on the sequence, but it is there to provide a general idea of the order in which tasks will be triggered and completed.

...