Note |
---|
If the API changes in an incompatible manner this is listed explicitly in the "important release notes" section of each releases changelog. |
Provides the associations between users and tasks.
...
Name | Type | Info | |
id | int | GET only | |
entityVersion | int | PUT / POST only, optional, is compared against the tasks entity version | |
taskGuid | string | ||
userGuid | string | ||
login | string | GET only, set by server | |
surName | string | GET only, set by server | |
firstName | string | GET only, set by server | |
state | string | Valid values depend on the used workflow, for the default see the API usage in basic workflow description. | |
| string | DEPRECATED use workflowStepName instead! | |
workflowStepName | string | Valid values depend on the used workflow, for the default see | thethe API usage in basic workflow description. |
usedState | string | GET only, set by server | |
usedInternalSessionUniqId | string | GET only, set by server | |
isPmOverride | integer | GET only, set by server | |
staticAuthHash | string | GET only, set by server; Needed for single click authentication. Only readable for users with role "api". | |
deadlineDate | date | The date when the user should finish the assigned job. For each workflow and workflow step, can be defined how many days (excluding week-ends) the deadline should be in the future based on task order date. ex: In this config runtimeOptions.workflow.default.translation.defaultDeadlineDate, you can define the default deadline date for default workflow and translation step To use the defaultDeadline date config, set the deadlineDate with value "default" on post request. | |
assignmentDate | date | The date when the user is assigned to the job. (if the date is not set, it will be current date) | |
finishedDate | date | The date when the user finished the assigned job. |
...