Canceled
This outbound task attachment is used to let ERP systems know about the fact that the Field Worker has canceled the task. The Field Worker may have entered a reason for cancelling the task. The ERP system may decide to create a new task, depending on business requirements.
| 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 canceled | no | canceled |
| content | A note from the Field Worker regarding this cancelation | yes | Reconstruction is not finished yet |
| reference | The code of the Reason for Disruption | no | 12 |
| 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.
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.