Rebook
This outbound task attachment is used when a Field Worker has refused the service object of the lead task in a task collection, while the task was already reported onSite. The Field Worker may have entered a reason for sending the service object back to the planner. A copy of the task might be created and the itemsPlanned and document attachments, related to the task, are re-booked onto the new task. The new task can become visible in the Unplanned box of the Scheduler. The planner then might reassign the task to another resource and day. This attachment type is relevant to ERP systems since it marks the lead task as not yet been processed in case of a Service Object-related process flow, or if re-booking was explicitly allowed for onSite tasks.
| Attribute | Description | Optional | Example |
|---|---|---|---|
| attachmentType | The type of this attachment. Needs to be 4, which means event | no | 4 |
| subType | The sub-type of this attachment, being rebook | no | rebook |
| content | A note from the Field Worker regarding this cancellation | yes | Not today |
| reference | The code of the Reason for Disruption | no | 2 |
| geocode | The best last known location at which this attachment was created | yes | 0_0_48.702344_10.165200 |
| format | In case, the related task is part of a collection, this field contains the id of the leading task. Otherwise, this attribute is empty. | yes | 2678290 |
| processFlow | If a service object was re-booked, this field contains its id. Otherwise, this attribute is empty. | yes | SO-852963-123 |
Note that the timestamp of this event can be retrieved by reading the createdOn column as described above.
The geocode stored along with this attachment is considered the location of the customer's site and may be used for further reference.
This attachment type is applicable to Reason For Disruptions of which the FollowOn type equals 4.
When using an external mobile application, this attachment must be provided to OMD by the Mobile App to update the task status. In this case, the attachment is an inbound attachment.