Create Task activity
Summarize
Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
Summary of Create Task activity
The Create Task activity allows users to generate a task record using previously gathered or generated data within the ServiceNow Process Automation Designer. It is available for users with admin, pdadmin, or pdauthor roles to incorporate into playbooks.
Show less
Key Features
- Inputs: Configure activity properties including:
- Label: Title displayed on activity and playbook card.
- Description: Information regarding activity usage or outcome.
- Run condition: Conditions for running the activity, utilizing data from prior activities.
- Start Rule: Determines when the activity starts based on playbook or stage triggers.
- Assigned To: Reference to the user responsible for task completion.
- Wait for user input: Option to pause until the end user completes or skips the activity.
- Advanced Inputs: Additional configurable options, including assignment groups and specific user assignments for task access.
- Task Table: Name of the task table extension where the task will be created.
- Wait for Task completion: Pause the playbook until the created task record is completed.
Key Outcomes
By configuring the Create Task activity, customers can streamline task management within their playbooks, ensuring that tasks are effectively assigned, tracked, and completed based on predefined conditions. This enhances automation and improves overall process efficiency in ServiceNow.
Create a task record from previously gathered or generated data.
Roles and availability
This activity is available as a common activity. Users with the admin, pd_admin, or pd_author role can add this activity to a playbook.
Inputs
Open the activity properties panel and configure your activity to add values for the following inputs. If the input value varies, use the pill-picker to show where to get the
value. To learn more about the pill-picker, see Dot-walking examples.
| Input | Type | Description |
|---|---|---|
| Label | String | Title to display as activity and playbook card. |
| Description | String | Information to display about activity usage or outcome. |
| Run condition | Condition Builder | Conditions that must be met to run an activity or stage. You can use data from prior activities to build conditions. Note: Show additional options to see this field. |
| Start Rule | Choice | Under , select a start rule for when your stage should start running:
|
| Start with delay | True/False | Option to wait for a duration of time before running an activity or stage. When enabled, this input displays the Start with delay input properties. Note: Show additional options to see this field. |
| Assigned To | Reference.User [sys_user] | User responsible for completing the task associated with the activity. Note: Show additional options to see this field. |
| Short Description | String | Summary of the task to complete. |
| Wait for user input | Choice | Option to pause the playbook until the end user manually completes or skips the activity. Only users with the pd_admin role can edit this field. By default, the activity waits for user action or data before it completes. |
Advanced inputs
After configuring the required inputs for your activity, you can also choose to configure additional inputs. In the side panel, select Show additional
options to display these advanced inputs. For more information, see Activity experience.
| Input | Type | Description |
|---|---|---|
| Assignment Group for this Process Step | Reference.Group [sys_user_group] | Assignment group allowed to perform this playbook activity. If you don't set any values for Assignment Group or Assigned To, any user can read and edit the collected
data. The Assignment group and Assigned to fields limit who has access to do so. To specify only individual users, use the Assigned To field. The same users do not need to be specified in both
fields. Note: By default, these fields are mapped to the Assignment Group and Assigned To fields of the trigger record. This means that users assigned to work on the
parent record have access to submit, view and edit the collected data by default. |
| Assigned to this Process Step | Reference.User [sys_user] | User allowed to perform this playbook activity. If you don't set any values for Assignment Group or Assigned To, any user can read and edit the collected data. The
Assignment group and Assigned to fields limit who has access to do so. To specify only individual users, use the Assigned To field. The same users do not need to be specified in both
fields. Note: By default, these fields are mapped to the Assignment Group and Assigned To fields of the trigger record. This means that users assigned to work on the
parent record have access to submit, view and edit the collected data by default. |
| Task Table | Table Name | Name of the task table extension in which you want to create a task. |
| Add Field | Template Value | Field values to assign when creating the task record. |
| Fields to show after creation | String | Comma-separated list of fields to display for a created record. |
| Wait for Task completion | True/False | Pause the playbook until the created Task record is complete. |
Outputs
These outputs can provide data to other activities in your playbook. You can access this data as activity inputs when you configure your activity:
| Output | Type | Description |
|---|---|---|
| Table | Table Name | Table containing new record. |
| Record | Reference.Task[task] | Reference to record created. |