---
title: "Tasks Table"
canonical: "https://help.agiloft.com/space/SDA2603/521276365/Tasks+Table"
format: markdown
---
The Tasks table stores a record for each task that’s been created in the system. Task records describe the action that needs to be taken and contain details about the assignees, when the task should become active, when it’s due, and if should automatically recur. Tasks also contain running notes and several action buttons that allow assignees to transition a task through its lifecycle.

# Related Tables

Out-of-the-box, the Tasks table is linked to [Contracts](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521274901) and [Obligations](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521277281), and you can create tasks directly from Contract and Obligation records. You can also create standalone tasks that aren’t linked to another type of record. The diagram below shows the default out-of-the-box relationships.

![Default table relationships for the Tasks table](media://5f0b07b5-13f6-4b98-a25e-66bc9b620cdc)

You can create tasks that are related to sourcing events or supplier profiles, but there isn’t a direct link to those tables in the out-of-the-box system.

# Record Creation

Tasks are typically created from [Contract](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521274901) or [Obligation](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521277281) records. You can also create tasks by clicking New in the Tasks table view and manually linking the new record to another parent record or leaving it separate as a standalone task. 

By default, users in these groups can create tasks: admin, Admin Import, Business Admin, Contract Admin, Contract Manager, Internal Supplier Manager, Legal, Project Manager, Response Evaluator, Sourcing Event Manager, and Tasks Management.

Task records are owned by the user who's assigned to complete the task. For more information on record ownership, see [Record Ownership](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718158) in the Help Guide.

# Record Layout

This section gives a high-level overview of the out-of-the-box power user record layout. Each tab is listed below, with descriptions of the main features, action buttons, and fields included in the layout by default. For information on working with record layouts, see [Layouts](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43715914) in the Help Guide.

## Common Area

In the common area, the Source Table, Task Category and Task Type fields are populated based on the type of record you created the Task from.

- **Source Table**: This field specifies which process table this task relates to and controls visibility of tabs and fields on the screen. Standalone tasks can also be created.
- **Task Category**: This field categorizes the task and also and controls the visibility of other fields on screen.
- **Task Type**: This field links to the [Task Types Table](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521279258), which defines the type of task and controls the default values for certain fields in the Task record.

Below the fields are several action buttons for changing the task status. The buttons that appear depend on the current status of the record:

- **Mark as Pending**: If Status is Prepared or Blocked, this button can be used to change the status to Pending. When the status is changed to Pending, the task [activation actions](https://agiloft-public.atlassian.net/wiki/spaces/SDA2603/pages/521276365/Tasks+Table#edit_activation_actions) are triggered
- **Mark as In Progress**: If Status is Prepared, Pending, or Blocked, this button can be used to change the status to In Progress, indicating the assignee is actively working on the task.
- **Mark as Blocked**: If Status is In Progress, Prepared, or Pending, this button can be used to change the status to Blocked. The action validates that the user is on the assigned team and have entered Working Notes.
- **Mark as Completed/Approved**: If Status is Prepared, Pending, In Progress, or Blocked, this button can be used to change the status to Completed/Approved. The action validates that the user is on the assigned team. If the Date Done field on the Process tab is empty, the system enters the current date and time in the field.
- **Mark as Failed/Rejected**: If Status is Prepared, Pending, In Progress, or Blocked, this button can be used to change the status to Failed/Rejected. The action validates that the user is on the assigned team and have entered Working Notes.
- **Mark as Canceled/Not Needed**: If Status is In Progress, Blocked, Prepared, or Pending, this button can be used to change the status to Canceled/Not Needed.

## Task Details

The Task Details tab defines the assignees, activation trigger, and task recurrence settings.

- **Assigned Team** and **Assigned Person**: Defines the assignees. In the Assigned Team field, select the team to assign the task to. If you want to select a person from the team to become the assignee, select the user in the Assigned Person field. Otherwise, any member of the team can update the task.
- **Date Due**: If there’s a specific date the task needs to be done, you can select a date. Leave the field blank if you want to set a relative due date based on dates in the parent record or based on the time it takes to complete the task.
- **Task Summary**: In the Task Summary field, write a descriptive title for the task. Do not use commas in the value.
- **Activation Trigger**: This field defines when to trigger the task so the assignee can start working on it.
  - **Creation**: Select this option to activate the task as soon as it's created.
  - **Date**: Select this option to set a specific trigger date or a date relative to a date from the parent record.
  - **Status**: Select this option to choose which contract status should trigger the assignment.
- **Recurring Task**: When you want to configure the task to recur automatically at selected intervals, set this field to Yes and configure the fields that appear:
  - **Recur Every**: Specify the number of days, weeks, months, or years to recur. The unit of time is selected in the Recurrence Unit field.
  - **Recurrence Unit**: Select the unit of time for the Recur Every value.
  - **End Recurrence Based On**: Choose how to determine the end of the cycle:
    - **Date**: Select this option to set a specific date to end the recurrence on.
    - **Number of Occurrences**: Select this option to set the number of times the task should recur.

## Related Info

If Source Table is Contracts or Obligations, the Related Info tab is displayed and shows details about the parent record the task is related to.

## Process

The Process tab contains attachments, overdue reminder settings, and a timer where the assignee can record the time spent on the task.

### Measuring Time for a Task

The system tracks two kinds 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 the time when the Status was Prepared, Conditional, or Canceled/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. You can use these fields in reports to see the average time to complete tasks of specific types.

## Emails

The Emails tab lists any email communications related to the task, such as notification emails sent to assignees by automation rules.

# Views

In addition to Default View and other [standard views](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718574), the Tasks table includes other views for displaying tasks in related records and dashboards:

- **All Obligations View**: This is the default view for the All Assigned Obligations widget in the Obligation Management Dashboard.
- **Detail View**: This view presents details that include the same columns as the Default View plus the Person Assigned to Task, Date Due, and Date Created fields.
- **Obligations in Contracts**: This is the default view of the All Contract Obligations related table in Contract records.
- **Recurring Task View**: This is the default view for the Manage Task/Obligation Recurrence related table in Contract records.
- **View in Contract**: This is the default view of the Tasks related table in Contract and Project records.

# Saved Searches

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

- **My Assigned Tasks**: Finds tasks where the Status is Assigned and you are the assigned person or are on the assigned team.
- **My Open Tasks**: Finds tasks where the Status is Assigned and you are the assigned person.
- **My Queued Tasks**: Finds tasks where the Status is Queued and you are the assigned person or are on the assigned team.

# Charts/Reports

In the out-of-the-box system, the Tasks table includes the following charts and reports:

- **All Tasks, segmented by assignee**: Bar chart that shows the number of tasks each person has assigned to them.
- **Assigned Tasks linked to Obligations**: Reports on the number of tasks linked from active Obligation records, grouped by subtopic.
- **Assignee's tasks in the past month, segmented by type**: Bar chart that shows the number of tasks that were created or updated in the past month for each assigned person, segmented by Task Category.
- **Average Time to Close Tasks by Assignee**: Reports on the average number of working hours it took for each assignee to close tasks.
  - The bar chart shows the average number of hours by person.
  - The report shows the average number of hours by person and lists each completed task.
- **Closed Tasks, by assignee**: Bar chart that shows the number of tasks each assignee closed.
- **Non-Obligation Assigned Tasks**: Reports on the number of tasks that are not obligations, grouped by Task Category.
- **Obligations by Person**: Reports on the number of open obligations by assigned person.
  - The bar chart shows the number of open obligations for each assigned person, segmented by the Overdue value.
  - The report shows the number of open obligations per person and lists the obligations grouped by the Overdue value.
- **Obligations by Responsible Party**: Reports on the number of open obligation- or contract-related tasks by responsible party. Tasks are considered open if they have a Status of Pending or Blocked.
  - The bar chart shows the number of tasks each Responsible Party has open.
  - The report shows the number of open tasks by Responsible Party and lists each task.
- **Obligations by Team**: Reports on the number of open obligation- or contract-related tasks by assigned team. Tasks are considered open if they have a Status of Pending or Blocked.
  - The bar chart shows the number of open tasks for each team, segmented by the Overdue value.
  - The report shows the number of open tasks per team and lists the tasks grouped by the Overdue value
- **Open Tasks, by assignee**: Bar chart that shows the number of open tasks for each assignee. Open tasks have any Status except for Completed/Approved.
- **Outstanding Contract Tasks by Month**: Reports on the number of pending contract tasks per month.
  - The bar chart shows the number of pending contract-related tasks per month segmented by type of task.
  - The report shows the tasks by due date and grouped by task category.

# Fields

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

| **Field Label** | **Data Type** | **Description** |
| --- | --- | --- |
| Activate when Contract changes Status to | Choice: The list of choices for Status in Contract records | When Activation Trigger is Status, this field specifies which contract status should trigger the task. |
| Activation Date | Date | When Activation Trigger is Date and Activation Date Type is Fixed, you set the trigger date in this field. When this field is blank or Activation Date Type is Relative, the system sets this field. |
| Activation Date Before or After | Choice: Before, After | When Activation Date Type is Relative, this field indicates whether the offset is before or after the date. |
| Activation Date from Source Field ID  
Activation Date from Source Field  
Activation Date Variable | Link to selected fields from other table: Replacement Variable | When Activation Date Type is Relative, these fields store date-related variables used in the Activation Date calculation. |
| Activation Date Number | Integer | When Activation Date Type is Relative, this field specifies the number of Activation Date Units to offset the date by. |
| Activation Date Type | Choice: Fixed, Relative | Defines how the activation date is determined, whether it’s a specific, fixed date or a relative date. |
| Activation Date Units | Choice: Hours, Days, Weeks, Months, Quarters, Years | The unit of time to offset the activation date by. |
| Activation Trigger | Choice: Date, Status, Creation | Defines when to trigger the task.<br>- When set to Date, you can configure the task to trigger on a specific date or a date relative to a date from the contract.
- When Status, you choose which contract status should trigger the task.
- When Creation, the task is triggered as soon as the record is saved. |
| Actual Working Hours | Elapsed Time | If the Status is Completed/Approved or Failed/Rejected, this field displays the difference between the Actual Start Time and Actual End Time, including only the working hours of the assigned team. |
| Alert Color | Choice: Default, Red, Yellow | The colors to use by actions that set colors in the table view for identifying records that are overdue or failed. |
| Amount - Fixed | Floating Point | For obligation-related tasks, this field shows the fixed amount from the obligation, if there is one. |
| Amount - Percentage | Floating Point | For obligation-related tasks, this field shows the percentage amount from the obligation, if there is one. |
| Amount Type | Choice: Fixed, Relative | For obligation-related tasks, this field shows the type of amount from the obligation. |
| Assigned Person  
Assigned Person ID  
Assignee Primary Team | Link to selected fields from other table: People | These fields identify the person assigned to complete the task. It's filtered to show people on the team selected in the Assigned Team field. |
| Assigned Team  
Assigned Team ID | Link to selected fields from other table: Teams | These fields identify the team assigned to the task. |
| Attached Files | File with Versioning | Stores any supporting documents for the task. This field does not support file versioning or OCR. |
| Auto-Complete? | Choice: Yes, No | Indicates whether to mark the task complete as soon as it's assigned. This option is useful when the Task Type is Notification. That way the task is automatically set to Completed/Approved when the notification goes out. |
| Button: Mark as Blocked | Action button | Changes the task status to Blocked. Requires the user to add comments to Working Notes. |
| Button: Mark as Canceled/Not Needed | Action button | Changes the task status to Canceled/Not Needed. Requires the user to add comments to Working Notes. |
| Button: Mark as Completed/Approved | Action button | Changes the task status to Completed/Approved. |
| Button: Mark as Failed/Rejected | Action button | Changes the task status to Failed/Rejected. Requires the user to add comments to Working Notes. |
| Button: Mark as In Progress | Action button | Changes the task status to In Progress. |
| Button: Mark as Pending | Action button | Changes the task status to Pending. |
| Cancel Further Recurrence | Choice: True, False | Can be used to stop the task from recurring after the current iteration is complete. Defaults to False. |
| Child Recurring Tasks | Related Table: Tasks | Lists any recurrences of this task that have been generated. |
| Contract Company  
Contract is Confidential  
Contract Manager  
Contract Manager ID  
Contract Title  
Contract ID  
People who can view Contract  
Contract Requester ID  
Contract Requester Name  
Roles that can view Contract  
Contract Status | Link to selected fields from other table: Contracts | When Source Table is Contracts, these field identify the Contract this task is for. |
| Converted to Recurring Task | Choice: Yes, No | System-managed flag that tracks if a recurring task was generated for this task. |
| Date Done | Date/Time | The system sets this field to the date and time the Status first changed to Completed/Approved or Failed/Rejected. |
| Date Due | Date/Time | The due date for the task. |
| Date of Next Occurrence | Date | For recurring tasks, this system-managed field stores the date when the next iteration of the task should occur. |
| Description | Text | A description of the task. |
| Diagram | Relationship Diagram Field | Shows a diagram of the tasks related to the current one. |
| End After Number of Occurrences | Integer | When Recurring Task is Yes and Recurrence Task Type is Parent, this field lists the number of times the task should recur. |
| End On Date | Date | When End Recurrence Based On is Date, this field specifies the end date. |
| End Recurrence Based On | Choice: Date, Number of Occurrences | When Recurring Task is Yes and Recurrence Task Type is Parent, this field defines how to determine when to stop the task from recurring.<br>- When Date, you set a specific End On Date to end the recurrence.
- When Number of Occurrences, you set the number of times the task should recur in the End After Number of Occurrences field. |
| Financial Impact | Currency | When Task Category is Obligation, this field lists the cost of failing to meet the obligation. |
| Financial Impact Color | Choice: Low Financial Impact, Medium Financial Impact, High Financial Impact | This background field is used to set the color of the notification icon in views. |
| Handle Recurring Task | Choice: Yes, No | System-managed flag used to manage recurring tasks. |
| Hours to Complete | Floating Point | Legacy field that is not used. |
| Next Reminder Date | Date | System-managed field that is set based on the values in the Date Due and Send Overdue Reminder Every X Days fields. |
| Notification Email Body | Text | When Task Type is Notification, this field stores the body of the notification email. |
| Notification Email Subject | Text | When Task Type is Notification, this field stores the subject line of the email. |
| Notify Contract Manager on Completion? | Choice: Yes, No | When Related To is Contracts, this field controls whether to notify the Contract Manager when the task is completed. Defaults to No. |
| Notify for Auto-Completion? | Choice: Yes, No | This field is not included in the layout by default. |
| Obligation Company  
Obligation Company ID | Link to selected fields from other table: Companies | The company from the contract the obligation is for. |
| Obligation ID  
Pinpoint Citation  
Obligation Subtopic  
Obligation Topic | Link to selected fields from other table: Obligation | For obligation-related tasks, these fields list details about the obligation. |
| Obligation Source | Choice: Contract Type, Contract Clause, Ad Hoc | If the Task Category is Obligation, this field defines the source of the obligation.<br>- Contract Type means this obligation relates to the type of contract.
- Contract Clause means this obligation relates to the presence of certain clauses in the contract document.
- Ad Hoc means this obligation was generated on the fly. |
| Obligation Trigger ID  
Obligation Trigger | Link to selected fields from other table: Replacement Variable | For obligation-related tasks, these fields list the obligation trigger from the obligation. |
| Occurrence Number | Integer | When Recurring Task is Yes, this field lists which occurrence number this task is. Defaults to 1. |
| Occurrences Generated | Calculation on Multiple Linked Records: Tasks | System-managed field that stores the max occurrence number of all child tasks. |
| Overdue? | Choice: Pending, Overdue | System-managed flag to track whether the task is overdue. Used in reporting. |
| Percentage Basis ID  
Percentage Basis | Link to selected fields from other table: Replacement Variable | For obligation-related tasks, these fields list the percentage basis from the obligation. |
| Preceding Recurring Task ID  
Preceding Recurring Task | Link to selected fields from other table: Tasks | Links the current task to the preceding recurring task. |
| Recur Every | Integer | When Recurring Task is Yes, this required field specifies the number of days, weeks, months, or years to recur. The unit of time is selected in the Recurrence Unit field. |
| Recurrence Task Type | Choice: Parent, Child | System-managed field that specifies whether the recurring task is a parent or child task. |
| Recurrence Unit | Choice: Days, Weeks, Months, Years | When Recurring Task is Yes, this required field specifies the unit of time used to calculate when the task recurs. |
| Recurring Task | Choice: Yes, No | Indicates whether the task recurs. |
| Responsible Party | Choice: Customer, Internal, Customer and Internal, Partner, External | When Task Type is Obligation, this field lists the party responsible for the task. |
| Roles that can view Task | Link to single field from other table: Roles | For confidential contracts, this system-managed field stores a list of roles that can view the task. |
| Running Working Notes | Append Only Text | Captures a running list of the Working Notes added to the task. |
| Send Overdue Reminder Every X Days | Integer | The number of days past the due date to remind the assignee to complete the task. |
| Source Cancel Further Recurrence  
Source End After Number of Occurrences  
Source End On Date  
Source End Recurrence Based On  
Source Recurring Task ID  
Source Occurrence Number  
Source Task Recurrence | Link to selected fields from other table: Tasks | System-managed fields involved in managing recurring tasks. |
| Source Table | Choice: Standalone, Contracts, Obligations | Defines which process table this task relates to and controls visibility of fields on the form. |
| Status | Choice: The list of states in the workflow | The state of the task. |
| Task Category | Choice: Action, Approval, Obligation, Notification | Specifies the type of task this is and controls the visibility of other fields on the screen. |
| Task Launched | Choice: Yes, No | System-managed flag that's set to Yes when tasks are launched from the main record. It's used to prevent Queued tasks from being set to Assigned when earlier tasks in the sequences are marked as Not Needed. |
| Task Recurrence | Text | Summary note describing the task recurrence in natural language |
| Task Source | Choice: Task Template, User Created | System-managed flag that indicates whether this task was generated from a Task Template or created by a user. |
| Task Summary | Short Text | Required field that specifies the name of the task. Do not include commas. |
| Task Type Default Person ID Fixed  
Task Type Default Person Variable  
Task Type Default Team ID Fixed  
Task Type Default Team Variable  
Task Type Default Time to Complete  
Task Type Default Time to Complete Units  
Task Type ID  
Task Type | Link to selected fields from other table: Task Types | These fields store details from the related Task Type record for this task. |
| Time to Complete | Integer | If you can’t set a fixed Due Date, use can use this field to enter how much time the task should take as a number of hours, days, weeks, etc. You choose the unit of time in the Time to Complete Units field. The system uses this value to calculate the Due Date once the task is activated. |
| Time to Complete Units | Choice: Hours, Days, Weeks, Months, Quarters, Years | The unit of time to calculate the due date by. |
| Working Hours to Complete | Elapsed Time | System-managed field that calculates the difference between Date Created and Date Completed according to the working hours of the assigned team. Excludes the time when the Status was Prepared, Conditional, or Canceled/Not Needed. |
| Working Notes | Text | Stores comments from the assignee while working on the task. |

# Automation

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

- **Create: Simplified Task Creation actions (email, web, API)**: This rule runs when a Task is created. It performs the following actions to update date fields and the record status:
  - If the Activation Trigger is set to Creation, it sets the Activation Date to today.
  - If Activation Trigger is Creation and Status is Prepared, it sets the Status to Pending.
  - If Activation Trigger is Status and Contract Status equals the value in the “When contract changes status to” field, it sets the Status to Pending.
  - If Activation Trigger is Date and Activation Date Type is Relative, it sets the Relative Activation Date.
  - If Activation Trigger is Date and the Activation Date is less than or equal to today, it sets the Status to Pending.
  - If Date Due and Activation Date are blank and Time to Complete is greater than 0, it sets the Date Due based on the time to complete value.
  - If Date Due and “Send Overdue Reminder Every X Days” are set, it sets the Next Reminder Date.
- **Edit: Simplified Task Edit Actions (web, API)**: This rule runs when a Task is edited. It performs the following actions:
  - If the Activation Trigger is set to Date and Activation Date is less than or equal to today, it sets Status to Pending.
  - If Activation Trigger is Date, Activation Date Type is Relative, and relative date fields were changed in the last modification, it sets the Relative Activation Date.
  - If Activation Trigger is Status and Contract Status equals the value in the “When contract changes status to” field, it sets the Status to Pending.
  - If Status changed to Canceled/Not Needed, Completed/Approved, or Failed/Rejected:
    - If Assigned Person is blank, it sets it to the person who last updated the record.
    - If Alert Color is Red, it sets Alert Color to Default.
    - If Status is not Canceled/Not Needed and Notify Contract Manager on Completion? is Yes, it emails the Contract Manager to notify them the task is complete.
  - If Working Notes has a value, it appends the value to the Running Notes or All Task Notes field in the parent record.
  - If Activation Date changed in the last user modification, and Date Due is blank or earlier than the Activation Date, it recalculates the due date.
  - If any recurrence-related values changed, it recalculates the Date of Next Occurrence.
  - If it’s a recurring task and the next occurrence isn’t created, it queues the next occurrence.
- > Macro (anchor)

**Edit: Simplified Task Activation Actions (web, API)**: This rule runs when a Task is edited. It finds records where the Status changed to Pending and performs the following actions:
  - If Auto-Complete is Yes, it changes the status to completed and sends out the appropriate notifications.
  - If Auto-Complete is No, it notifies the assignees of the new task.
  - If Activation Date is blank, it sets the date to today.
  - If Date Due is blank and Time to Complete is greater than 0, it sets the appropriate due date. If Time to Complete is not greater than 0, it sets Date Due to two days from now.
  - If it’s a recurring task, it sets the Date of Next Occurrence.
- **Edit: Simplified Handle Recurring Task (web, API)**: This rule runs when a Task is edited. It finds recurring tasks and handles recurrence-related updates as needed. If the conditions to end recurrence aren't met, it creates the next task in the sequence.
- **Edit: Remove Commas from Task Summary (web, API)**: This rule runs when tasks are edited. It removes any commas from the Task Summary field.

# Workflow

This section describes the out-of-the-box workflow for the Tasks table. For information on configuring workflows, see [Workflows](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718058) in the Help Guide.

By default, new records have a Status of Prepared. Transitions to subsequent states are handled automatically by rules or manually with action buttons. The list below describes each of the states.

![Default Workflow for the Tasks table](media://198913a3-9182-4de9-b05c-36a3b12b8818)

- **Prepared**: The Task is created but the activation trigger isn't met.
- **Pending**: The Task is active and ready to be worked on.
- **In Progress**: The assignee clicked the Mark as In Progress button and is working on the task.
- **Blocked**: The assignee clicked the Mark as Blocked button to set the Status to Blocked.
- **Completed/Approved**: When the assignee finishes the task, they mark the record as Completed/Approved.
- **Failed/Rejected**: If the assignee declines a task, they mark the record as Failed/Rejected.
- **Canceled/Not Needed**: A user canceled the task.
- **Conditional**: If the task is triggered only when certain conditions are met, the status is set to Conditional.