The exchange of the task information is realised via the table “Tasks” which contains the type and sequence of the used tasks and the table “Task parameters” which contains the corresponding task parameters, see chapter Data export and import / CSV export and import / The table "Task parameters". Tasks are implicitly brought into a corresponding order already by their line-by-line arrangement in the table. Furthermore, it is possible to substructure the tasks by indicating corresponding “Parent tasks”.
# |
Column name |
Purpose |
---|---|---|
0 |
Task ID |
An integer for clear identification of the task within the data scheme. Each task ID may only occur once. Consecutive numbering is not absolutely necessary. |
1 |
Parent ID |
An integer defining the superordinate task. The ID refers to the column 0 (task ID) of the table “tasks”. If no value is indicated, the respective task is located at the top level. In the current version, tasks may only be arranged below tasks of the type “tHumanTaskGroup”. A group as task to be subordinated must not contain a group, but only individual tasks. Parent tasks must be necessarily defined prior to their respective “Child tasks”! |
2 |
Object ID |
An integer defining the assigned object (human model). The object ID refers to the column 0 (object ID) of the table “Objects”. |
3 |
Type |
A character string of an internal type identifier. It is used for identification of the task type. |
4 |
Description |
A character string for user-defined designation of a task. |
5 |
Time-relevant |
A decision field used to mark a task as “time-relevant” (if the field is empty, the respective task is considered as “not time-relevant”). Tasks which are not time-relevant are ignored when determining the total process time. |