Work Location (wl) Key

The work location (wl) key places a work location graphic on the map and zooms to it at the given coordinates. It can optionally include a label, be associated with specific markup types, and be associated with an existing as-builting job. Multiple work locations can be included in a single URI command.

Parameter	Description	Important Considerations
`lat` and `long`	These parameters specify the position of a work location (`wl`) on the map.	The `lat` and `long` parameters are required if the work location key (`wl`) is used.
`label`	When provided, the given label is placed next to the work location graphic on the map.	The `label` parameter is optional. This parameter may not contain semicolons. The `label` parameter should not be used with the `wr` parameter.
`markupTypeID`	One or more `markupTypeID` parameters may be included for any one `wl` key, but each must have a number associated with it (e.g. `markupTypeId1`, `markupTypeId2`, etc.). Each `markupTypeID` parameter given should equal an existing markup type globally unique identifier (GUID) in your tenant. You can view each markup type's GUID in the Mobile plugin in the Solution Center.	The `markupTypeID` parameter is optional. This parameter is supported on iPad only. IMPORTANT: Once you migrate markup types to dynamic workflows and begin using assignment types, this parameter is no longer valid.
`wr`	This allows you to associate a work location with an existing as-builting job. This parameter must equal the GUID of an existing work request that is associated with an as-builting job for the user. This parameter does NOT automatically open the as-builting job, rather it places a work location graphic in the map. The user can then tap it to open the as-builting job directly from the map.	The `wr` parameter is optional. This parameter is supported on iPad only. The `label` parameter should not be used with this parameter as the work location is automatically given a label that is the name of the work request.