The records of tables extended from the Task table provide an efficient way of handling tasks, tracking the process through states and recording information via the Activity Feed.
In SimpleOne, the Task table is one of the basic tables of the system. It is not used on its own. The table provides a set of columns as a basis for child tables, i.e., tables extended from the Task table. The extended tables ( child tables ) inherit the fields and adjust them to the specific processes using column override.
SimpleOne provides the following set of child tables:
- ITSM Tasks (itsm_task)
- Incident (itsm_incident)
- Inquiries (itsm_inquiry)
- Requests (itsm_request)
- Problems (itsm_problem)
- Change Requests (itsm_change_request).
Usually, the Task table is not used on its own: tasks are created in its child tables. |
The scheme below illustrates the structure of ITSM table extensions:
Image Added
Panel |
---|
To learn how to create a task record, see the following articles: |
Note |
---|
Changes applied to the Task table will affect its child tables. Make sure that the changes do not cause malfunction in the child tables. Use column override to modify the parent and child tables. |
Records in the child tables of the Task table can be created in the following ways:
The table below lists the fields inherited by child tablesout-of-the-box Task table has the following fields:
Task table fields
ActiveTrue/False | Select this checkbox to make the table active or inactive. | Approval | Choice | Approval state. Available options: - Not Requested
- Requested
- Approved
- Denied
|
String | Task number. This field should have the TSKXXXXXXX format. It is filled in automatically. |
Caller | Reference | The originator of the task. |
Company | Reference | The company to which the task is related. |
Service | Reference | The service to which the task is related |
Assigned User | Reference | Responsible person to work on the task. |
Assignment Group | Reference | Responsible group to work on the task. |
Attention Required | True/False | This checkbox defines whether to notify the line manager of the assigned group/assigned user. |
Caller | Reference | The originator of the task. |
Comments | Text | A text field for storing comments regarding the task. |
Company | Reference | The company to which the task is related. |
Contact | List | A person from the users list to contact with. |
Description | Text | Detailed description of the task. |
Due date | Date/Time | Date and time by which the task should be completed. |
Followers List | List | Users list who follow the task for tracking updates. |
Number | String | Task number. This field should have the TSKXXXXXXX format. It is filled automatically. |
Assigned User | Reference | Responsible person to work on the task. |
State |
| This field displays the work state and progress. Available options: - Draft
- Registered
- Open
- In Progress
- Ready for deploy
- Ready for Test
- Closed Incomplete
- Closed Complete
- Cancelled.
|
Impact | Choice | The measure of effect caused by the issue impacts the business processes. Available options: - Low
- Medium
- High
- Very High.
|
Urgency | Choice |
The measure of Measure time until the issue impacts the business. Available options: - Low
- Medium
- High
- Very High.
|
Priority | Choice | The importance of the task. Available options: - Low
- Moderate
- High
- Critical.
Tip |
---|
You can configure the Priority Matrix for the system to populate this field automatically, based on the Impact and Urgency field values. |
|
Opened by | Reference |
The user User who initiated the task. |
ScreenshotShort Description | String | Image | Attached file. | Service | Reference | The service to which the task is related. |
Brief description of the task. |
SLA Due | Date/Time | Date and time by which the service level agreement should be reached. |
State | This field displays the work state and progress. Available options: - Draft
- Registered
- Open
- In Progress
- Ready for deploy
- Ready for Test
- Closed Incomplete
- Closed Complete
- Cancelled.
| Subject | Text | Brief description of the task. |
Additional Comments | Journal Input | |
some additional information about the task. Additional comments have the |
purple marking сomments are displayed comments are visible to the requestor on the portal |
|
page in task record. When a comment is added, the involved users (caller, assigned group/assigned user) receive a notification. |
Image Modified
|
Work Notes | Journal Input | |
the information about working on the issue. Work notes have the black marking. Info |
---|
Work notes are only available |
|
only for the responsible users in the agent interface. When a work note is added, the responsible users receive a notification. |
Image Modified
|
Active | True/False | Select this checkbox to make the record active or inactive. |
Approval | Choice | Approval state. Available options: - Not Requested
- Requested
- Approved
- Denied
|
Attention Required | True/False | This checkbox defines whether to notify the line manager of the assigned group/assigned user. |
Comments | Text | A text field for storing comments regarding the task. |
Contact | List | Contact person from the user list. |
Due date | Date/Time | Date and time by which the task should be completed. |
Followers List | List | User list who follow the task for tracking updates. |
Screenshot | Image | Attached file. |
Short Description | String | Brief description of the task. |
SLA Due | Date/Time | Date and time by which the service level agreement should be reached. |
Wf Executing Activity | Reference | Workflow activity, which initiated the creation of the task record. This field is populated automatically if the workflow inserts the current record. |
Info |
---|
Some fields above are not displayed on the record form of a newly created table by default. To configure the form, use the form layout settings. |
See the Column Types article to learn more.
You can create other tables extended from the Task table to meet your business needs. See the following articles to configure your own table extended from Task.