Move
Whenever a task is moved within the planning, this outbound attachment will be added to the task, indicating the details of the move. The following moves can occur:
- Same Resource - other Day
- Other Resource - other Day
- Other Resource - same Day
- Planned - Unplanned
- Unplanned - Planned
During the lifecycle of a task, it is possible that a task is moved across several trips. Each move in the planning will be logged separately. The timestamps of the moves can be retrieved by reading the createdOn column as described above.
| Attribute | Description | Optional | Example |
|---|---|---|---|
| attachmentType | The type of this attachment. Needs to be 1, which means text | no | 1 |
| subType | The sub-type of this attachment, being move | no | move |
| content | The new day and resource. An empty value indicates that the task is now unplanned. Optionally the duration of the task, in minutes, and an indication, whether the task has a fixed date, can be appended. | no | 2014-10-16,1013,60.0,false |
| reference | The old day and resource. An empty value indicates that the task was formerly unplanned. | no | 2014-10-17,1012 |
| processFlow | The status into which the Task has been changed. | no | IP |
| format | alternativeId of the task, if available | yes | 124374 |
| extra | The account number of the customer. | yes | 395001 |
By default, moves within the same trip, possibly changing the order of the stop, are not stored as a move attachment. See here for more details.
For this attachment to be generated, the createMoveAttachments preference must have value true.