Create Task
Create a Task or Catalog Task in ServiceNow.
The input fields on this card are dynamically generated based on your ServiceNow instance. The input fields include the default fields provided by ServiceNow. For example, Active, Approval history, Description, Time worked, and any custom fields you've added to your Task or Catalog Task tables. This topic describes some of the common input fields.
Options
| Field | Definition | Type | Required |
|---|---|---|---|
|
Task Type |
Choose one of the Task types to create:
|
Dropdown |
TRUE |
Input
| Field | Definition | Type | Required |
|---|---|---|---|
|
Task |
|||
|
Number |
An identifying number for each task record. This field is the display value for the Task table. The system generates this number when the task is created. |
Text |
FALSE |
|
Description |
A long description of the work to be done. |
Text |
FALSE |
|
Short description |
A short description of the task. This description is used as a title for the record. |
Text |
FALSE |
|
Additional comments |
Comments about the task record. Each comment is inserted into the Activity field. |
Text |
FALSE |
|
Opened |
The date and time when a human opened the task record for the first time. |
Date & Time |
FALSE |
|
Approval history |
History of approvals for the record. |
Text |
FALSE |
|
Watch list |
Specifies the users that receive email and SMS notifications when the record is updated. By default, only the Incident, Change, and Service Catalog applications notify users listed in this field. For other Task-based applications, you must create and send custom email notifications to these users. |
Text |
FALSE |
|
Priority |
Specifies how high a priority the task should be for the assignee. By default, the calculatePrioritybusiness rule calculates this value based on the Impact and Urgency values. Record lists then color-code each task by degree of priority. |
Number |
FALSE |
|
Work notes list |
Specifies the users that receive email and SMS notifications when work notes are added to the record. By default, only the Change, Problem, and Service Catalog applications notify users listed in this field. For other Task-based applications, you must create and send custom email notifications to these users. |
Text |
FALSE |
|
Assigned to |
Specifies the user assigned to complete the task. By default, this field uses a reference qualifier to only display users with the itil role. Some applications override the parent reference qualifier to display relevant users. For example, the Service Order and Project Task tables filter users based on their skills. |
Text |
FALSE |
|
Active |
Specifies whether work is still being done on a task or whether the work for the task is complete. By default, only application-specific business rules set the value of this field. For example, the incident autoclose business rule closes resolved incidents that haven't been updated for one day. |
True/False |
FALSE |
|
State |
Status of the task. Values include the following:
Applications typically use dictionary overrides to display application-specific states. |
Number |
FALSE |
|
Time worked |
Displays a timer that measures how long a record is open in the form view. |
Text |
FALSE |
|
Work notes |
Displays and allows the entry of comments viewable only by ITIL users. Each comment is inserted into the Activity field. See Journal field type. |
Text |
FALSE |
Output
| Field | Definition | Type |
|---|---|---|
|
Response |
||
|
System ID |
The unique record identifier (sys_id) for the task. |
Text |
|
Task Number |
An identifying number for each task record. This field is the display value for the Task table. The system generates this number when the task is created. |
Text |
|
Status Code |
Result of the operation. The connector returns an HTTP status code that indicates whether the action taken by the card succeeded or failed. For example:
For a full list of possible status codes, see HTTP status codes. |
Number |