Page tree
Skip to end of metadata
Go to start of metadata

Tasks Table

The Tasks table is used within several other process tables to automate and track tasks. The Tasks table is a global process table that holds Task records, which can be linked to records in other tables. The Tasks table holds individual tasks. The Standard System Demo is currently set up to link tasks to Service Requests, Change Requests, Projects, and Assets, but they can also be created completely independent from other tables. Although the Task table only links to the four aforementioned tables by default, it is always possible to add or remove tables from this list.

Fields related to task generation and a related Tasks table, labeled Tasks, are shown in service requests and change requests for services that include tasks.

Tasks and the fields for generating them are also shown within Projects and Assets. Projects allow the same methods of task generation as service requests. Assets allow single tasks to be created and linked to the asset, and show all tasks that have been created from other records, such as change requests or service requests, that relate to that asset.

Layout

We'll begin with an overview of the important tabs, and some of their fields, of a Task record.

  • Task Details: Contains fields defining the nature of the task, such as Task Type, Task Summary, and the task Description. It also shows task Status, Assigned Team, Assigned Person, and the Date Due. The main task screen also includes an area for managing the related asset, if any. Tasks based on a template may be defined to have specific task steps, and if the task has such steps, they appear with checkboxes in the Working Notes section. There are no default rules enforcing that all checkboxes are checked before completing a task, but such a rule could be added. The user can add working notes at any time, and these will be added to the running history of all working notes: When working on an asset-related task, the technician can click one of the buttons shown above to update the Operational Status of the asset to reflect that it has been taken offline or brought back online.  
  • 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, tasks for which this task is a prerequisite. When a task has two prerequisites that are 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. The default Status for a task is Queued when it is created. When tasks are launched, any task without a prerequisite is automatically set to Assigned (see below for more details).
  • Related Info 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.

Use Case

Task records can be created by users in the Admin, Admin Import, Base ServiceDesk, Business Admin, Internal Customer, Marketing, Project Manager, Sales, and Service Managers groups. Although Tasks can be linked to one of several other tables, they are generally all created and processed in similar ways. When Task records are created, several automated actions occur. Task records are created:

  • By clicking the Generate Tasks button from the related record, such as a Project or Service Request record.
  • Manually by users in the Task table

When tasks are created using Generate Tasks, they are generated from Task Templates that have been created previously and defined to be used for the particular task. When a Task record is generated from a Task Template record, they are auto-assigned to the appropriate team or person thanks to the information contained within the Task Template record.

Users are prevented from creating tasks with a comma in the title, since this breaks some of the automation for prerequisite tasks. If a task is created with a comma, the comma is stripped out. Commas are also prevented in task template titles for the same reason.

The person assigned to a task can add working notes to it, refer to the linked Service Request, Project, or Change Request from it, and ultimately complete the task. There are several default statuses: Queued, Conditional, Assigned, Completed, Not Needed, Failed, and Waiting for Others.

  • When the user completes the task, they change the Status to Completed and save the record. If there is no value in the Date Done field, the system will put the current date/time into the Date Done field. Alternatively, the user may enter a time in the Date Done field directly. 
  • While working on the task, the user may enter any time spent on the task in the Time Spent and Time Description fields, then click Add Time to convert them to Time Entries.
  • When working on an asset, the Start Clock and End Clock buttons can be used to set the Actual Start Time and Actual End Time as needed. The user may also manually put values in these fields.
  • When a task record is saved a rule called Edit: All Edit Actions (API enabled) is run.
    • If the Status has changed to Completed, Failed, or Not Needed, the system updates the Dependent tasks by refreshing their Number of prerequisite tasks counts. If this was the last prerequisite, then that will trigger the next rule to assign the dependent tasks.
    • The rule also sets the Assigned Person, if it is blank, to the person who completed the task.
    • If the task is for a project, the project manager is notified of the task completion.
    • If the Working Notes field was updated, the text is copied into the Running Notes field and blanked out. And if the task is related to a change request, the notes are also updated into the change request's running Working Notes field.
    • If the status has just changed to Assigned (by launching the tasks from the main record or by the prerequisite tasks having been completed), the Date Due is set based on specified criteria. If the task was an auto-completing task, then it is marked as Completed and the assignee notified. Otherwise, the assigned person or assigned team is notified that the task is now assigned.
  • When a prerequisite task is completed, its dependent tasks are updated, and if all prerequisite tasks are now completed, then the rule called Edit: Assign tasks when number of completed prerequisites meets criteria (API) runs. This rule checks if the task was conditional, and if so, checks the condition to see if it is met. If the task is not conditional or its condition is met, then it sets the Status to Assigned. Otherwise, it sets the status to Not Needed.
  • When all tasks for a particular record are completed or marked as failed or not needed, the person / team assigned to the main request is notified that all tasks are done.

Measuring Time for a Task

In addition to time that is manually entered, the system tracks two kind of elapsed time. The Working Hours to Complete field is set to the difference between the Date Created and Date Done, excluding the non-working hours of the assigned team and also excluding the time during which the Status was Queued, Conditional, or Not Needed. The Actual Working Hours field measures the time between the Actual Start Time and Actual End Time, excluding the non-working hours of the assigned team.

These fields can be used in reports to see the average amounts of time tasks of specific types are taking. They can also be compared against the Template Number of Hours to Due Date value, which sets the expected working hours that should be needed for the task.

Workflow

There is a simple workflow for tasks that currently executes no actions:

Automation

The following is a summary of the rules and validations that run when new tasks are created, either manually or from templates:

  • When a task is created manually, if it is related to a Project whose status is Completed or Canceled, 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 performed by a rule called 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, such as the Change Manager or Project Manager, then the Assigned Team is set to that person's Primary Team. If no one was assigned due to a 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, and 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 then 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.

Disabled Time Based Rules

There are two time based rules that are set up but not running. These are:

  • TB: (DISABLED) Notify of upcoming task. It will notify the assigned person or team when the due date is one day away, once it is turned on. Currently it is disabled. There is a radio button at the bottom of the General tab in the table settings if this rule is desired. The schedule may need to be changed from every 10 years to something more useful.
  • TB: (DISABLED) Set alert color to red if overdue. This sets the alert color to red when the date due has passed, so that views that use row coloring can show to users that the task is overdue.


  • No labels