---
sourceDocument: Xanadu Finance and Supply Chain
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/source-to-pay-operations

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Finance and Supply Chain

ft:clusterId :

    - stpop

bundleId :

    - stpop

workflow :

    - Creator


---

# Configure due dates for tasks

# Configure due dates for tasks {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure due dates for different task types so that the Due date field is auto-populated when you create tasks for internal users and suppliers.

## Before you begin

Role required: sn_slm.admin

## About this task

Although the Due date field is auto-populated for a task type, you can always update this field as required.

## Procedure

1. Navigate to AllSupplier Lifecycle OperationsAdministrationDefault Due Dates for Tasks.  
   The Decision Builder opens and displays the Decision table for configuring the default due dates.  
   {#configure-task-due-date__table_wbc_wbv_tyb__entry__2}

   | Task type | Default due date |
   |-|-|
   | Mark complete | 3 |
   | View link | 3 |
   | Play video | 3 |
   | Upload documents | 3 |
   | Complete a form | 3 |
   | Sign document | 3 |
   | Complete checklist | 3 |
   | Complete survey | 3 |
   [ ]

   {#configure-task-due-date__table_wbc_wbv_tyb}
2. Under the Default due date column, select a row next to the task type row and enter a positive number.  
   The number that you enter for a task type is auto-populated in the Due date field the next time you create a task of that task type.

   For example, let's say that you enter 3 as the due
   date for the task type Mark complete. If you create a Mark complete task on September 12, the due date will be in three days from this date; that is, September 15.
3. Select Save.

*[\>]: and then