Task management is similar to Approval Management in its basic setup. Like approvals, you can predefine tasks in Task Templates and Task Workflows and then automatically generate a set of Tasks to associate with a record based on the record type. However, there are differences in the sequencing options for task versus approval processes.

• With approvals, all approvals with the lowest step number must be completed before approvals with the next step number are triggered. You can have both parallel and sequential approvals, but in general approvals are automatically triggered based on the Status of the Approval records in the workflow. It's not possible to have separate branches of approvals operating independently, with flexible triggering options.
• Tasks, on the other hand, have flexible branching and triggering options. You can create prerequisite structures for completing tasks sequentially, and you can create branches of tasks that operate independently.  

The out-of-the-box system is currently set up to link Tasks to Contracts and Projects. However, it's possible to customize the setup to use Tasks with other modules. For more information, see Linking Tasks to Other Modules.

Creating and managing tasks involves records in four core tables: Task Templates, Task Steps, Task Workflows, and Tasks.

• Task Templates: A Task Template is a task in a Task Workflow. It's a reusable step that is used to generate a Task record that is linked to a specific type of record, like a Contract.
• Task Steps: Task Steps are subtasks in a Task Template. Each step can only be used in one template.
• Task Workflows: Task Workflows define a group of Task Templates to complete for each type of task. 
• Tasks: Tasks are system-generated instances of Task Templates or manually created records that contain the instructions, notes, and interactions that occur during the process.

The diagram below represents the default table relationships for task management.

The following list gives a high-level description of how the task process involves the tables in the diagram:

• Each Contract Type and Project Type can be linked to a predefined Task Workflow. But contract and project types can also be configured to allow users to dynamically select from a list of pre-defined tasks or create new ad hoc tasks.
• If you configure Contract Type and Project Type records to use a predefined Task Workflow, then that workflow is automatically assigned when a Contract or Project of that type is created.
• The Task Workflow includes a number of Task Templates or steps in the workflow.
• A Task Template can have subtasks defined as Task Steps.
• Clicking Create Tasks in the Contract or Project record generates Task records for each of the Task Templates in the workflow. The system links the new Task records to the parent record.
• In addition to assignment based on Contract Type, Tasks can also be assigned based on Clause Type.
• Tasks are automatically triggered to begin based on the assignment trigger configured in the template, or they are manually triggered by launching them from the parent record.

For details about each of the core task management tables, see the articles below.

• Tasks Table
• Task Workflows Table
• Task Templates Table
• Task Steps Table