---
title: "Tasks Table"
canonical: "https://help.agiloft.com/space/SDA2512/218107168/Tasks+Table"
format: markdown
---
The Tasks table stores all of the tasks that are associated with specific Contracts or Sourcing Events. Task records contain the instructions, notes, and interactions that occur during the process of working on tasks.

# Record Creation

By default, users in the following groups can create Task records: admin, Admin Import, Business Admin, Contract Manager, Internal Supplier Manager, Legal, Project Manager, Response Evaluator, and Sourcing Event Manager.

Tasks are typically created from Contract records. When and how they're created depends on the task generation method defined for the [Contract Type](https://agiloft-public.atlassian.net/wiki/spaces/SDA2512/pages/218109121).

- When the task generation method for the contract or project type is **Predefined Task Workflow**, users select a [Task Workflow](https://agiloft-public.atlassian.net/wiki/spaces/SDA2512/pages/218110043) in the Contract or Project record. Clicking Generate Tasks triggers the creation of Task records from the [Task Templates](https://agiloft-public.atlassian.net/wiki/spaces/SDA2512/pages/218109826) in the workflow. This includes Recurring Tasks, which get created automatically at selected intervals, and Obligations, which get created based on the Contract Type or [Clause Types](https://agiloft-public.atlassian.net/wiki/spaces/SDA2512/pages/218109599) in the contract.
- When the generation method is **User Selected Tasks**, users select tasks from a checklist of Task Templates in the Contract or Project record. Clicking Generate Tasks generates Task records for the selected Task Templates. This also includes Recurring Tasks and Obligations.
- When the generation method is **User Generated Ad Hoc Tasks**, users click the Add Ad Hoc Task button in a Contract or Project record and manually configure a Task record. Recurring tasks and Obligations can also be configured ad hoc.

## Ad Hoc Tasks

When Tasks records are generated from a predefined workflow or user selected tasks, the Task Template configuration is mapped to the Task. This section describes the important fields to complete when creating Tasks manually from a Contract or Project record.

In the common area, the Related To field is set to the appropriate table based on the type of record you created the Task from. In the Task Summary field, write a descriptive title for the task. Do not use commas in the value.

### Task Details

On the Task Details tab, configure the assignees, assignment trigger, and task recurrence.

- **Assigned Team** and **Assigned Person**: 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.
- **Assignment Trigger**: This field defines when to assign the task. The Date and Status options are only available for Contracts:
  - **Date**: Select this option to set a specific trigger date or a date relative to a date from the Contract record.
  - **Status**: Select this option to choose which contract status should trigger the assignment.
  - **Creation / No Open Prerequisites**: Select this option to assign the task as soon as it's created, as long as there aren't prerequisite tasks. If there are prerequisites, the system will assign this task once those tasks are completed.
- **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 End On Date to end the recurrence.
    - **Number of Occurrences**: Select this option to set the number of times the task should recur in the End After Number of Occurrences field.

### Related Tasks

The Related Tasks tab shows any existing prerequisite tasks for the same parent record. It also shows any dependent tasks, which are tasks for which this task is a prerequisite. If prerequisite tasks are disabled, you can enable them by setting Enable Prerequisite Tasks to Yes. Then you can add and existing tasks as prerequisites.

### Related Info

The Related Info tab shows details about the record linked to the task.

### Process & Time

The Process & Time tab contains attachments, overdue reminder settings, and a timer where the assignee can record the time spent on the task. Time Entries are stored in the Time Entries table.

## Completing Tasks

When a task is assigned, the assignee can add working notes, refer to the linked Contract or Project, and ultimately complete the task.

- When the user completes the task, they click the Mark as Completed/Approved button and save the record. If the Date Done field is empty, the system enters the current date and time in the field.
- While working on the task, the assignee can 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. In addition, the Start Clock and End Clock buttons can be used to set the Actual Start Time and Actual End Time as needed.
- When a prerequisite task is completed, its dependent tasks are updated.
- When all tasks for a particular record are completed or marked as failed or not needed, the person or team assigned to the parent record is notified that all tasks are done.

### Measuring Time for a Task

In addition to time that is manually entered, 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 also the time when 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. You can use these fields in reports to see the average time to complete tasks of specific types.

# Views

The Default View for the out-of-the-box Tasks table shows the Edit icon, status indicator, ID, Related To, Task Summary, Task Type, Status, and Assigned Team fields.

![Default View for the Tasks table](media://b9cf39f3-c3a5-4af3-a352-78aa9af5eefc)

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.
- **P: Assigned Person = user's name and Status != done**: Finds all tasks where you are the assigned person and the Status is anything other than Completed/Approved.

# 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 created from AI-extracted obligations, segmented by subtopic.
- **Assignee's tasks in the past month, segmented by type**: Bar chart that shows the number of tasks segmented by type that were created or updated in the past month for each assigned person.
- **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 Type.
- **Obligations by Responsible Party**: Reports on the number of open obligations by responsible party. Open obligations have a Status of Conditional, Queued, Assigned, or Waiting for Others.
  - The bar chart shows the number of obligations each Responsible Party has open.
  - The report shows the number of open obligations by Responsible Party and lists each obligation.
- **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 Team**: Reports on the number of open obligations by assigned team.
  - The bar chart shows the number of open obligations for each team, segmented by the Overdue value.
  - The report shows the number of open obligations per team and lists the obligations grouped by the Overdue value
- **Obligations by Type**: Reports on the number of open obligations by type.
  - The ring chart shows the number of open obligations by type.
  - The report lists the open obligations grouped by type.
- **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 type.
- **Tasks by Opportunity Company**: Bar chart that shows the number of tasks by Opportunity Company.

# 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 Tasks table includes the following fields.

| **Field Label** | **Data Type** | **Description** |
| --- | --- | --- |
| Actual End Time | Date/Time | The date and time recorded when the user clicks End Clock on the Process & Time tab. |
| Actual Start Time | Date/Time | The date and time recorded when the user clicks Start Clock on the Process & Time tab. |
| 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:<br>- Default
- Red
- Yellow | The colors to use by actions that set colors in the table view for identifying records that are overdue or failed. |
| All Time Spent | Calculation on Multiple Linked Records: Time Entries | The total number of hours spent on the task according to Time Entry records. |
| Assign When Contract Changes Status to | Choice:<br>- Draft
- Pending Review
- With Counterparty
- Pending Approval
- Approved
- Pending Signature
- Signed
- Active
- Renewed
- Expired
- Canceled
- Terminated | When Related To is Contracts and Assignment Trigger is Status, this field specifies which Contract Status triggers the assignment of the task. |
| 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. |
| Assigned To Variable ID  
Replacement Variable Label  
Assigned to Variable | Link to selected fields from other table: Replacement Variables | Identifies the role the task is assigned to. |
| Assignment Trigger | Choice:<br>- Date
- Status
- Creation / No Open Prerequisites | Defines when to trigger the assignment of the task.<br>- Date is only available for Contracts. When selected, you set a specific trigger date or a date relative to a date from the Contract record.
- Status is only available for Contracts. When selected, you choose which contract status should trigger the assignment.
- Creation / No Open Prerequisites is available for Contracts and Projects. When selected, the task is assigned when it's created, as long as any configured conditions are met and there aren't prerequisite tasks. |
| Assignment Trigger for Conversion | Choice:<br>- Date
- Status
- Creation / No Open Prerequisites | System-managed field used when generating recurring tasks. |
| Attached Files | File with Versioning | Stores any supporting documents for the task. This field does not support file versioning or OCR. |
| Auto-Complete? | Choice:<br>- 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. |
| Before or After Contract Date | Choice:<br>- Before
- After | When Assignment Trigger is Date and Date Assignment Type is Relative, this field defines whether to trigger the task before or after the chosen Date from Contract. |
| Button: Add Time | Action button | Creates a Time Entry record with the values in Time Spent and Time Description. |
| Button: Add to Prerequisites | Action button | If Enable Prerequisite Tasks is Yes, this button can be used to add as a prerequisite the task selected in the Add Tasks to Prerequisites field. |
| Button: End Clock | Action button | Records in the Actual End Time field the date and time the task was completed. |
| Button: Mark as Assigned | Action button | If the Status is Queued, Conditional, or Waiting for Others, this button can be used to change the Status to Assigned. |
| Button: Mark as Completed/Approved | Action button | If the Status is Queued, Assigned, or Waiting for Others, this button can be used to change the Status to Completed/Approved. |
| Button: Mark as Failed/Rejected | Action button | When Status is Queued, Assigned, or Waiting for Others, this button can be used to change the Status to Failed/Rejected. Requires comments to be added in the Working Notes field. |
| Button: Remove from Prerequisites | Action button | When Enable Prerequisite Tasks is Yes, this button can be used to remove as a prerequisite the task selected in the Remove Task from Prerequisites field. |
| Button: Start Clock | Action button | Records in the Actual Start Time field the date and time the task was started. |
| ButtonAB: Reassign Task | Action button | Used in an action bar for inactive tasks. Changes the status of the selected tasks to Assigned. |
| ButtonAB: Remove | Action button | Used in the default action bar for the Tasks related table in Project records. Changes the status of the selected tasks to Not Needed and removes them from the related table. |
| Cancel Further Recurrence | Choice:<br>- True
- False | When a task is Queued, this field can be used to stop the task from recurring after the current iteration is complete. Defaults to False. |
| Cell Phone  
Company Name  
Direct Phone  
Email  
Contact Name | Link to selected fields from other table: People | These fields aren't included in the layout by default. They could be used to select a contact person for the task. |
| 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 Related To is Contracts, these field identify the Contract this task is for. |
| Converted to Recurring Task | Choice:<br>- Yes
- No | System-managed flag that tracks if a recurring task was generated for this task. |
| Date Assignment Type | Choice:<br>- Fixed
- Relative | When Assignment Trigger is Date, this field defines how the trigger date is determined.<br>- When Fixed, set a specific trigger date in the Date to be Assigned field. Choosing a fixed date may require you to update the task template in the future.
- When Relative, additional options are displayed for configuring the trigger date relative to a date from the Contract record. |
| 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 Field RV ID  
Contract Date Field for Assignment  
Date Variable | Link to selected fields from other table: Replacement Variables | When Assignment Trigger is Date and Date Assignment Type is Relative, these fields define which date from the Contract to use for calculating the trigger date. |
| Date of Next Assignment | Date | For recurring tasks, this system-managed field stores the date when the next iteration of the task should be assigned. |
| Date to be Assigned | Date | When Date Assignment Type is Fixed, this field defines the trigger date. |
| Dependent Tasks | Related Table: Tasks | When Enable Prerequisite Tasks is Yes, this field lists the tasks that are dependent on the current task. Used to determine the next tasks to trigger when a prerequisite task is completed. |
| Description | Text | A description of the task. |
| Diagram | Relationship Diagram Field | Shows a diagram of the tasks related to the current one. |
| Enable Prerequisite Tasks | Choice:<br>- Yes
- No | Indicates whether this task can have prerequisite tasks and controls the visibility of the prerequisite task related fields on the Related Tasks tab. |
| 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:<br>- 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 Type is Obligation, this field denotes the financial impact of not meeting the obligation. |
| Financial Impact Color | Choice:<br>- 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:<br>- Yes
- No | System-managed flag used to manage recurring tasks. |
| Highest Sequence Prerequisite Task ID  
Highest Sequence | Link to selected fields from other table: Tasks | System-managed fields used for task sequencing. |
| Hours to Complete | Floating Point | Legacy field that is not used. |
| Include Obligation Management  
Obligation Function ID | Link to selected fields from other table: Functions | System-managed flag that indicates whether the Obligation Management function is enabled. |
| Latest Contract Attachment | File with Versioning | Allows you to attach the latest version of the contract. |
| 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:<br>- 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:<br>- Yes
- No | This field is not included in the layout by default. |
| Number of Completed Prerequisite Tasks | Calculation on Multiple Linked Records | System-managed field that counts the number of completed prerequisite tasks. |
| Number of Days before or after Contract Date Field | Integer | When Assignment Trigger is Date and Date Assignment Type is Relative, this field defines the number of days before or after the "Contract Date Field for Assignment" to trigger the task. |
| Number of Dependent Tasks | Calculation on Multiple Linked Records: Tasks | Lists the number of dependent tasks for this task. |
| Number of Prerequisite Tasks | Calculation on Multiple Linked Records | When prerequisite tasks are enabled, this field counts the number of prerequisite tasks. |
| Number of Selected Task Steps | Calculation on Multiple Linked Records | System-managed field that counts the number of selected Task Steps. |
| Obligation Clause Text  
Source Contract Clause ID | Link to selected fields from other table: Contract Clauses | For obligations generated due to Clause Types included in the contract, this field stores the text of the clause. |
| Obligation Company  
Obligation Company ID | Link to selected fields from other table: Companies | The company from the contract the obligation is for. |
| Obligation Source | Choice:<br>- Contract Type
- Contract Clause
- Ad Hoc | If the Task Type 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 Type | Choice:<br>- Audit
- Delivery
- Document
- Hold Private
- Notification
- Payment
- Report
- Other | If the Task Type is Obligation, this field defines which type of obligation the task is. |
| 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:<br>- Pending
- Overdue | System-managed flag to track whether the task is overdue. Used in reporting. |
| Person Assigned to Task | Link to single field from other table: People | Background field that gets its value from the Assigned Person field. It's a legacy field that was replaced by Assigned Person but is still used in some reports, searches, and rules so remains in the system. |
| Preceding Recurring Task ID  
Preceding Recurring Task | Link to selected fields from other table: Tasks | Links the current task to the preceding recurring task. |
| Prerequisite Task to Add ID  
Add Task to Prerequisites | Link to selected fields from other table: Tasks | Filtered to Tasks linked to the same parent record and that are not already listed in the prerequisite tasks.  Used to choose a prerequisite task to add to the list. |
| Prerequisite Tasks | Link to selected fields from other table: Tasks | Set by a rule on creation from a template to the ones whose IDs are included in the Source Template Prerequisite Task IDs. |
| Project ID  
Project ID Text  
Project Manager Team  
Project Category  
Project Manager  
Project Name  
Project Task Generation Method  
Type of Project  
Project Status  
Project Company | Link to selected fields from other table: Projects | When Related To is Project, these field identify the Project this task is for. |
| 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:<br>- Parent
- Child | System-managed field that specifies whether the recurring task is a parent or child task. |
| Recurrence Unit | Choice:<br>- 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:<br>- Yes
- No | Indicates whether the task recurs. |
| Related To | Choice:<br>- Project
- Contracts
- Contract Requests
- Opportunity
- Contact
- Sourcing Events
- Supplier Profile | Defines which process table can use this task and controls visibility of fields on the form. |
| Remove from Prerequisite Task ID  
Remove Task from Prerequisites | Link to selected fields from other table: Tasks | When Enable Prerequisite Tasks is Yes, this field can be used to select a task to remove from the list of prerequisites. |
| Responsible Party | Choice:<br>- 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. |
| Sequence | Floating Point | Defines the approximate order of this task in the workflow. The sequence gives a general idea of the order but isn't definitive and doesn't control any of the processing. You can enter a decimal value to insert the task between two existing tasks without having to renumber other tasks. Defaults to 1. |
| 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 Contract Type ID | Link to selected fields from other table: Clause Types | System-managed field that stores the Contract Type for obligations generated because of the Clause Types included in the contract. |
| Source Last Trigger Date | Date | Unused legacy field. |
| Source Task Checklist ID  
Number of Active Steps | Link to selected fields from other table: Task Templates | Linked set to Task Templates to display Task Step Numbers; visible if Template Task Checklist = Yes. |
| Status | Choice:<br>- Queued
- Conditional
- Assigned
- Completed/Approved
- Failed/Rejected
- Waiting for Others
- Not Needed | The state of the task. |
| Task Launched | Choice:<br>- 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:<br>- Task Template
- User Created | System-managed flag that indicates whether this task was generated from a Task Template or created by a user. |
| Task Steps | Link to single field from other table: Task Steps | Lists any active Task Steps for the task. |
| Task Summary | Short Text | Required field that specifies the name of the task. Do not include commas. |
| Task Type | Choice:<br>- Task
- Approval
- Milestone
- Obligation
- Notification | Specifies the type of task this is and controls the visibility of other fields on the screen. |
| Template Assign Based On  
Template Assign When Contract Changes Status to  
Template Assignment Trigger  
Template Condition  
Template Date Assignment Type  
Source Template ID  
Template Number of Hours to Due Date  
Prerequisite Task Template IDs  
Template Task Generation Type  
Task Template Usage  
Workflow ID to be Triggered  
Template Use Task Checklist | Link to selected fields from other table: Task Templates | If the task was generated from a Task Template, these field identify the template. |
| Template Triggering Task | Choice:<br>- Yes
- No | Unused legacy field. |
| Time Description | Text | Description of the time spent on the task. Used when creating a Time Entry record. |
| Time Entries | Related Table: Time Entries | Lists any Time Entry records for the task. |
| Time Related to | Choice:<br>- Project
- Task | Unused legacy field. |
| Time Spent | Elapsed Time | User-entered hours and minutes spent on the task. Used when creating a Time Entry record. |
| Trigger Condition | Choice:<br>- When all tasks are completed
- When any task is completed | When Enable Prerequisite Tasks is Yes, this field controls how many prerequisite tasks must be completed before this task is triggered.<br>- When set to When all tasks are completed, all prerequisite tasks must be completed before this task is triggered. This is the default value.
- When set to When any task is completed, this task can be triggered if at least one prerequisite task is completed. |
| 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 Queued, Conditional, or Not Needed. |
| Working Notes | Text | Stores comments from the assignee while working on the task. |

# Automation

This section describes the 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: All create validations (web)**: This rule runs when a Task is created manually. It validates that the Due Date is not in the past. In addition, if the task is related to a Project, it validates that the Project is not Completed or Canceled. If either validation fails, the user is warned and prevented from saving the record.
- **Create: All Creation Actions for Non-Contract Tasks (web, API, email)**: This rule runs when a Task is created. It performs several actions based on the type of record the task is related to. If task template usage is Conditional, it sets the Status to Conditional. Otherwise, the Status is Queued.
- **Create: All Contract Task Create Actions (web, API)**: This rule runs when a Task is created. It performs the following actions for tasks related to contracts:
  - Sets the appropriate assignee and prerequisite tasks based on the task template configuration.
  - If task template usage is Conditional, it sets Status to Conditional. If the condition is met, it sets the Status to Assigned. If it's not met, it sets the Status to Not Needed.
  - Sets the date to be assigned according to the Assignment Trigger. If the assignment trigger is met, it assigns the task.
  - Removes any commas from Task Summary.
  - If Task Type is Obligation and the source is not a template, it sets the source to Contract Clause. Otherwise, it sets the source to Contract Type.
  - If it's a recurring task and there's a preceding recurring task, it flags the current task as a child and updates the recurrence counter.
  - Sets the next reminder date to notify the assignee.
- **Edit: Assign tasks when number of completed prerequisites meets criteria (web, API)**: This rule runs when a Task is edited. It finds records with prerequisite tasks that were just completed and performs the following actions:
  - If the task is not conditional, it changes the Status to Assigned.
  - If the template is conditional, it evaluates the condition and changes the Status to Assigned or Not Needed depending on result.
  - Sets the next reminder date to notify the assignee.
- **Create/Edit: Update Sequence based on Highest Sequence (web, API)**: This rule runs when records are created or edited. For records where the highest sequence number is set, it increments the Sequence as needed.
- **TB: Notify of upcoming task**: This time-based rule runs every day at 2:00 am. It finds records where the due date is less than 24 hours away and notifies the assignees of the due date.
- **Edit: All Edit Actions (API enabled) (web, API)**: This rule runs when records are edited. It handles Status and due date updates as well as notifications.
  - If the Status changed to Completed, Failed/Rejected, or Not Needed, it updates the dependent tasks by refreshing their number of prerequisite tasks counts. If this was the last prerequisite, it triggers the assignment of the next task.
  - If Assigned Person is blank, it sets it 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.
  - If the Status changed to Assigned, it sets the appropriate due date and notifies the assignees.
- **TB Demo Data Update: Update date fields by one month each month so reports have data**: This time-based rule runs on the 10th day of each month at 8:30 pm to update date fields for Demo Data records so they stay current. It also deletes the History associated with updating the demo fields.
- **TB: Set alert color to red if overdue**: This time-based rule runs every day at 3:00 am. It sets the alert color to red when the due date has passed so views with row coloring highlight overdue tasks.
- **Edit: If task title has a comma, strip it out (web, API)**: This rule runs when tasks are edited. It removes any commas from the Task Summary field.
- **TB: Assign Task if Date to be Assigned is Today**: This time-based rule runs every day at 3:00 am. It finds Conditional and Queued tasks where the date to be assigned is the current day or earlier. It evaluates any conditions and prerequisite tasks and updates the Status appropriately.
- **TB: Send Overdue Reminders**: This time-based rule runs every day at 6:00 am. It finds Assigned tasks where a reminder is due, notifies the assignees, and resets the reminder date.
- **Edit: Handle Recurring Task (web, API)**: This rule runs when records are edited. It finds recurring tasks and handles the recurrence cycle. If the conditions to end recurrence aren't met, it creates the next task in the sequence.
- **Edit: Run Assignment Actions Bundle if Status Changes to Assigned (web, API)**: This rule runs when tasks are edited. It finds tasks where the Status changed to Assigned and performs the following actions:
  - If Auto-Complete is Yes, sets the Status to Completed/Approved and notifies the contract owner and assignees if the task is configured to do so.
  - Updates the due date if appropriate.
  - Handles recurrence related updates as needed.
- **Create/Edit: Set Financial Impact Color (web, API)**: This rule runs when records are created or edited. For obligations, it sets the Financial Impact Color to the appropriate value.

# 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 Queued. 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://b5e81460-84b9-48ac-ae4e-11d303e3674f)

- **Queued**: Tasks are launched but the Assignment Trigger isn't met.
- **Conditional**: If the task was generated from a Task Template with Conditional usage, the status is set to Conditional.
- **Assigned**: When the Assignment Trigger is met or a user clicks the Mark as Assigned action button, the task is set to Assigned.
- **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.
- **Waiting for Others**: An assignee can change the Status to Waiting for Others if they are blocked.
- **Not Needed**: If the configured condition is not met, the task is set to Not Needed.

# Ownership

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.