{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":39933,"path":"platform-administration/table-administration-and-data-management/r_ImportantTaskTableFields.md","title":"Important Task table fields","bundle":null,"doc_type":null,"release":"australia","body":"\n# Important Task table fields\n\nThe Task table is a base class that provides fields for the core ITSM applications such as Incident, Problem, and Change Management. All applications that extend the Task table share these fields in common.\n\n<table id=\"table_phh_g11_tp\"><thead><tr><th>\n\nLabel\n\n</th><th>\n\nName\n\n</th><th>\n\nType\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nActive\n\n</td><td>\n\nactive\n\n</td><td>\n\nboolean\n\n</td><td>\n\nSpecifies 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 have not been updated for one day.\n\n</td></tr><tr><td>\n\nAdditional comments\n\n</td><td>\n\ncomments\n\n</td><td>\n\njournal\\_input\n\n</td><td>\n\nDisplays and allows the entry of comments about the task record. Each comment is inserted into the **Activity** field. For more information, see [Journal field type](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/c_JournalFields.md).\n\n</td></tr><tr><td>\n\nApproval History\n\n</td><td>\n\napproval\\_history\n\n</td><td>\n\njournal\n\n</td><td>\n\nDisplays the history of approvals for the record. For more information, see [Tools for completing tasks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/table-administration-and-data-management/c_TaskTable.md).\n\n</td></tr><tr><td>\n\nAssigned To\n\n</td><td>\n\nassigned\\_to\n\n</td><td>\n\nreference\n\n</td><td>\n\nSpecifies the user assigned to complete the task. By default, this field uses a [Reference qualifiers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/c_ReferenceQualifiers.md) to only display users with the itil role.\n\n 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.\n\n</td></tr><tr><td>\n\nCreated\n\n</td><td>\n\nsys\\_created\\_on\n\n</td><td>\n\nglide\\_date\\_time\n\n</td><td>\n\nDisplays the date and time when the task record was created.\n\n</td></tr><tr><td>\n\nDescription\n\n</td><td>\n\ndescription\n\n</td><td>\n\nstring\n\n</td><td>\n\nDisplays and allows the entry of a multi-line description of the work to be done.\n\n</td></tr><tr><td>\n\nEscalation\n\n</td><td>\n\nescalation\n\n</td><td>\n\ninteger\n\n</td><td>\n\nIndicates how long the task has been open. Escalations are dynamically populated using service level agreements, which specify how long a task remains in each escalation state. Escalation states go from **Normal** to **Moderate** to **High**, and finally to **Overdue**. Record lists color code each task by escalation state.\n\n</td></tr><tr><td>\n\nNumber\n\n</td><td>\n\nnumber\n\n</td><td>\n\nstring\n\n</td><td>\n\nDisplays 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.\n\n To manage number generation, see [Record numbering](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/c_ManagingRecordNumbering.md).\n\n</td></tr><tr><td>\n\nOpened\n\n</td><td>\n\nopened\\_at\n\n</td><td>\n\nglide\\_date\\_time\n\n</td><td>\n\nDisplays the date and time when a human opened the task record for the first time.\n\n</td></tr><tr><td>\n\nPriority\n\n</td><td>\n\npriority\n\n</td><td>\n\ninteger\n\n</td><td>\n\nSpecifies how high a priority the task should be for the assignee. By default, the **calculatePriority**business rule calculates this value based on the **Impact** and **Urgency** values. Record lists color code each task by degree of priority.\n\n</td></tr><tr><td>\n\nShort Description\n\n</td><td>\n\nshort\\_description\n\n</td><td>\n\nString\n\n</td><td>\n\nDisplays and allows the entry of a short description of the task, which is a human-readable title for the record.\n\n</td></tr><tr><td>\n\nState\n\n</td><td>\n\nstate\n\n</td><td>\n\nInteger\n\n</td><td>\n\nDisplays a choice list for status of the task:\n\n-   Pending\n-   Open\n-   Work in Progress\n-   Closed Complete\n-   Closed Incomplete\n-   Closed Skipped\n\n Applications typically use [Dictionary overrides](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/table-administration-and-data-management/c_DictionaryOverrides.md) to display application-specific states.\n\n</td></tr><tr><td>\n\nSys ID\n\n</td><td>\n\nsys\\_id\n\n</td><td>\n\nGUID\n\n</td><td>\n\nDisplays the [Unique record identifier \\(sys\\_id\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/c_UniqueRecordIdentifier.md).\n\n</td></tr><tr><td>\n\nTask Type\n\n</td><td>\n\nsys\\_class\\_name\n\n</td><td>\n\nsys\\_class\\_name\n\n</td><td>\n\nSpecifies the type of task, which corresponds to the child class. The system populates this value when a record is created on a child table.\n\n</td></tr><tr><td>\n\nTime Worked\n\n</td><td>\n\ntime\\_worked\n\n</td><td>\n\ntimer\n\n</td><td>\n\nDisplay a timer which measures how long a record is open in the form view.\n\n</td></tr><tr><td>\n\nWatch list\n\n</td><td>\n\nwatch\\_list\n\n</td><td>\n\nglide\\_list\n\n</td><td>\n\nSpecifies users who receive [Email and SMS notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/c_EmailNotifications.md) 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 custom email notifications sent to the users listed in this field. For information about addming more users to the watch list, see [Add users to a watch list](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/t_UseAWatchList.md).\n\n</td></tr><tr><td>\n\nWork notes\n\n</td><td>\n\nwork\\_notes\n\n</td><td>\n\njournal\\_input\n\n</td><td>\n\nDisplays and allows the entry of comments viewable only by ITIL users. Each comment is inserted into the **Activity** field. For more information, see [Journal field type](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/c_JournalFields.md).\n\n</td></tr><tr><td>\n\nWork notes list\n\n</td><td>\n\nwork\\_notes\\_list\n\n</td><td>\n\nglide\\_list\n\n</td><td>\n\nSpecifies users who receive [Email and SMS notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/c_EmailNotifications.md) 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 custom email notifications sent to the users listed in this field.\n\n</td></tr></tbody>\n</table>**Parent Topic:**[Task table structure](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/table-administration-and-data-management/task-table-structure.md)\n\n"}}