Move
If a task is moved from one trip to another, i.e. from one route of a mobile worker to another day or from one mobile worker to another mobile worker, a move attachment will be created if the preference createMoveAttachments is set. This allows external systems to synchronize the planning of a task with the OMD planning.
| createMoveAttachments | ||
|---|---|---|
| Type | Default Value | Example |
| Boolean | false | true |
By default, move attachments contain the date and resource to which task is assigned. To include the timestamp rather than the date, set the createMoveAttachmentsWithTime to true.
| createMoveAttachmentsWithTime | ||
|---|---|---|
| Type | Default Value | Example |
| Boolean | false | true |
By default, the move attachment is created if the task is moved across trip boundaries. This behaviour can be adapted to reflect the following scenarios:
all: any move, also within the same tripallExceptToday: any move, also within the same trip, but not within a today's triptripChange(default): all moves across trip boundaries, i.e. from one day to another day or from one resource to another resource or from unplanned to planned or from planned to unplanned.
| createMoveAttachmentsType | ||
|---|---|---|
| Type | Default Value | Example |
| Boolean | tripChange | allExceptToday |
External systems may require the estimated duration of the task.
| createMoveAttachmentsWithEstimatedDuration | ||
|---|---|---|
| Type | Default Value | Example |
| Boolean | false | true |
External systems may require an indication, whether a moved task has a fixed date or not.
| createMoveAttachmentsWithFixedFlag | ||
|---|---|---|
| Type | Default Value | Example |
| Boolean | false | true |