You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As a TO, we want to ensure that an end customer is close enough to an asset to prevent it from being opened remotely. Therefore, the MP must be able to transmit the position of the end customer to the TO when a request to open the asset is sent.
Urgency
Major (the TOMP API works as advertised but this is really neccessary to implement), because our process to open an asset depends on the user location
Additional context
Describe the solution you'd like
Transferring the position within the legEvent object.
As mentioned, we're going to have a look at this, but please remind that this adjustment has certain GDPR aspects. It cannot be applied without additional actions, like processing agreements and security precautions.
Is your feature request related to a problem? Please describe.
As a TO, we want to ensure that an end customer is close enough to an asset to prevent it from being opened remotely. Therefore, the MP must be able to transmit the position of the end customer to the TO when a request to open the asset is sent.
Urgency
Major (the TOMP API works as advertised but this is really neccessary to implement), because our process to open an asset depends on the user location
Additional context
Describe the solution you'd like
Transferring the position within the legEvent object.
Describe alternatives you've considered
Possible Implementation
POST: /legs/{id}/events]
{
"time": "string",
"event": "string",
"comment": "string",
"url": [
"string"
],
"asset": asset,
"userLocation": place
}
The text was updated successfully, but these errors were encountered: