---
title: "Task Workflows Table"
canonical: "https://help.agiloft.com/space/SDA2512/218110043/Task+Workflows+Table"
format: markdown
---
The Task Workflows table stores records that predefine a set of tasks to complete based on the type of record being worked on. In the out-of-the-box system, Contracts and Projects are configured to use task workflows. Task Workflow records control which type of process table can use the workflow and the [Task Templates](https://agiloft-public.atlassian.net/wiki/spaces/SDA2512/pages/218109826) to include. 

# Use Case

Out-of-the-box, Task Workflows are used to predefine the tasks to complete for a contract or project based on the [Contract Type](https://agiloft-public.atlassian.net/wiki/spaces/SDA2512/pages/218109121) or [Project Type](https://agiloft-public.atlassian.net/wiki/spaces/SDA2512/pages/218112609). When the Task Generation Method is Predefined Task Workflow, users can select a workflow to generate tasks from when they create certain types of Contracts and Projects. 

By default, members of the admin, Admin Import, Business Admin, and Contract Admin groups can create and edit Task Workflows. You can create Task Workflow records the following ways:

- From the Available Workflows related table in Contract Type records
- From the Predefined Workflows table in Project Type records
- By opening an existing workflow and clicking Clone Workflow. Cloning a workflow also clones any related Task Templates, so cloning is ideal when you need to create a similar workflow.
- By clicking New in the Task Workflows table's action bar

Each Task Workflow record defines which process table the workflow relates to and which tasks to complete.

In the common area, you're required to select which table can use the workflow and give the workflow a unique title. You also have the option to clone the workflow. The Related To field defines which process table can use the workflow. If you create a workflow from a Contract Type or Project Type record, Related To is automatically set to the appropriate related table. By default, all workflows are created with an Active Status.

![Task Workflow record related to Contracts](media://c66878a6-f9a4-4c48-822f-bc66398617c2)

## Workflow

The Workflow tab describes the workflow and defines the tasks to include. In Workflow Details, add a description for the workflow. You also have the option to add notes. If Related To is Contracts, select which Contract Types can use this workflow in the Available for Contract Types field.

The All Task Templates section lists any existing Task Templates in the workflow and provides the option to create a new template. Once the first template is created, if the Enable Prerequisite Tasks field is set to Yes in the workflow, then additional templates are able to define earlier ones as prerequisites.

### Prerequisite Task Handling

Workflows can have multiple threads of dependent tasks with different prerequisites, and the threads can proceed independently. They can also have many independent tasks that proceed in parallel or a single thread of dependent tasks where each task must be completed sequentially. The ability to choose exactly which tasks must be finished before another task is assigned provides a flexible model for complex task workflows.

When tasks are launched from the main Contract or Project record, the Status of tasks is set to Assigned based on the following logic:

- The task status was Queued or Conditional.
- The task has no prerequisites and is either not conditional or its condition is met.
- The task has some prerequisites, but their status is Not Needed or Completed.

If the condition is not met for a conditional template, that doesn't prevent dependent templates from being assigned. If dependent tasks should also be skipped when the prerequisite task is Not Needed, assign the same condition to the dependent tasks.

Below is an example task workflow for processing contract types based on the start date.

![List of Task Templates for a workflow](media://4a1de5be-b7a5-40ae-8972-b33882f3d4bb)

There are three tasks without prerequisites, ID 328, 325, and 380, that are assigned as soon as their Assignment Trigger is reached. The tasks with a Sequence value of 2 are assigned once their prerequisite tasks are completed and their Assignment Trigger is met. Since task ID 327 is Conditional, it won't be assigned unless the condition is met.

# Views

The Default View for the out-of-the-box Task Workflows table shows the Edit icon, ID, Related To, Workflow Title, Status, and Number of Tasks fields.

![Default View for the Task Workflows table](media://f15835ef-fc6f-4988-93df-cc695d49b282)

In addition to Default View and other [standard views](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718574), the table includes a View in Contract Type view for viewing the Task Workflows related table in Contract Type records.

# Saved Searches

The out-of-the-box Task Workflows table includes several saved searches that are used by rules. The following saved searches are available in the menu by default:

- **Active Workflows**: Finds all records with a Status of Active.
- **Demo Records**: Finds records where the Demo Data field is set to Yes.

# Fields

In addition to the [standard fields](https://agiloft-public.atlassian.net/wiki/spaces/SDA2512/pages/218104402/Table+Concepts#standard_fields), the out-of-the-box Task Workflows table includes the following fields.

| **Field Label** | **Data Type** | **Description** |
| --- | --- | --- |
| Available for Contract Types | Link to single field from other table: Contract Types | For workflows related to Contracts, this field defines which Contract Types can use the workflow. Select each type from the lookup field. |
| Button: Clone Workflow | Action button | Creates a copy of this workflow and all of its Task Templates. |
| Button: Create New Task Template | Action button | Creates a new Task Template and links it to this workflow. |
| Description | Text | Required field that describes the purpose of the workflow. |
| Enable Prerequisite Tasks | Choice:<br>- Yes
- No | Required field that indicates to enable prerequisite tasks for the workflow. This field controls visibility of the prerequisite task related fields in Task Template records. |
| Has Task Templates | Choice:<br>- Yes
- No | Indicates whether the workflow has task templates associated with it. |
| Notes | Append Only Text | Notes about the workflow. |
| Number of Tasks | Calculation on Multiple Linked Records: Task Templates | Counts the number of task templates in the workflow. |
| Related To | Choice:<br>- Project
- Contracts
- Contract Requests
- Opportunity
- Contact
- Sourcing Events
- Supplier Profile | Defines the type of process this workflow can be used for. |
| Source Workflow ID  
Source Workflow Title | Link to selected fields from other table: Task Workflows | If this workflow was created by cloning another workflow, these fields identify the source workflow. |
| Status | Choice:<br>- Active
- Inactive | The status of the workflow.<br>- When Active, the workflow is available for use. This is the default value.
- When Inactive, the workflow is not available for use. |
| Task Generated from a Workflow for Conversion | Choice:<br>- Yes
- No | System-managed field that maps to task templates and is used to restrict the Task Generation Type to Predefined Task Workflow. |
| Task Generation Type Default for Conversion | Choice:<br>- Predefined Task Workflow
- User Selected Tasks
- User Generated Ad Hoc Tasks | System-managed field that maps the Task Generation Type when a user creates a new task template from the workflow. |
| Task Templates | Related Table: Task Templates | Lists the active task templates in this workflow. |
| Workflow Title | Short Text | Required field that defines a unique title for the workflow. |

# Automation

This section describes the rules that are implemented for the out-of-the-box Task Workflows table. For details about rule configuration options, see [Rules](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43714473) in the Help Guide.

- **Create: Trigger task template conversion for cloned workflow (web, API)**: This rule runs when Task Workflow records are created. It finds cloned workflows that include task templates and creates the cloned template records.
- **Create: All Create Actions (web, API)**: This rule run when records are created. It finds cloned records and sets the appropriate Workflow Title.
- **Edit: refresh task template prerequisites as number of tasks changes for cloned (web, API)**: This rule runs when records are created or edited. It finds cloned workflows where the Number of Tasks value changed and refreshes the list of prerequisite task templates.

# Ownership

Task Workflow records are owned by the user who creates them. Specifically, Creator Login is set to the Login of the user who creates the record. For more information on record ownership, see [Record Ownership](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718158) in the Help Guide.