Back to Planner
This outbound task attachment is used to when a Field Worker has refused a task. The Field Worker may have entered a reason for sending the task back to the planner. The task will become visible in the Unplanned box of the Scheduler. The planner can then reassign the task to another resource and/or day. This attachment type is usually not relevant for ERP systems.
| 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 backToPlanner | no | backToPlanner |
| content | A note from the Field Worker regarding this cancellation | yes | Not today |
| reference | The code of the Reason for Disruption | no | 1 |
| geocode | The best last known location at which this attachment was created | yes | 0_0_48.702344_10.165200 |
| format | In case of collective task it will contain the id of the leading task of the collection. | yes | 2678290 |
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 3.
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.