Relocate
This in- and outbound task attachment is used to report the change of the geocode of a task. It can be initiated in OMD Mobile, by the mobile worker. If a task attachment of this subType is uploaded to the OMD Cloud, the geocode of the task is updated, if its status is not closed, plus the related customer's geocode is aligned. Task attachments of this subType are reported to the ERP.
| Attribute | Description | Optional | Example |
|---|---|---|---|
| attachmentType | The type of this attachment is 1 |
no | 1 |
| subType | The sub-type of this attachment is relocate |
no | relocate |
| geocode | The new location of the task in the usual OMD-Mobile format | no | 0_0_8.831159_49.837775 |
| extra | The extra can contain an XML with all locations that paticipated in the search for the new location | yes | (see below) |
<Data>
<Location provider="manual" latitude="49.83777464912724" longitude="8.831159099936485" match="4" name="resourceIdXyz" geocode="0_0_8831159_49837775 4"/>
<Location provider="network" latitude="49.837110578672366" longitude="8.82896639406681" match="0" name="imei1234" geocode="0_0_8828966_49837111 0"/>
<Location provider="task" latitude="49.836839844629324" longitude="8.829377107322216" match="4" name="taskIdAbc" geocode="0_0_8829377_49836840 4"/>
</Data>
The extra contains an XML with several locations and their coordinates, identified by the provider attribute. For the manually selected location the provider is manual. The location of the device during relocation is either gps, network or passive. In case the device location could not be determined, this element is missing. If the task had a geocode before, its location is added with the provider task. Otherwise this element is missing, too.