Trip Optimized
This attachment will be created by the domain when a trip has been optimized using either an API call or algorithm. It can also be uploaded by external systems such as the OMD Scheduler. It registers by whom and when the optimization was triggered, and whether it was succesful or not.
| Attribute | Description | Optional | Example |
|---|---|---|---|
| attachmentType | The type of this attachment. Needs to be 1, which means text | no | 1 |
| subType | The sub-type of this attachment, being tripOptimized | no | tripOptimized |
| content | The result of the optimization and a string containing additional information. In case of success (1), the string contains the name of the algorithm(s) used. In case of failure (0), the string contains the exception that occurred. Optimizations that executed without making any changes to the trip will be recorded as successful (1). | no | 1,optimize+oneopt |
| reference | The resource and day of the trip. | no | 1012,2019-09-05 |
| device | The name of the application that triggered the optimization. In case of the OMD domain service itself, this value will be null. The OMD Scheduler will set this value to OMDScheduler. | yes | OMDScheduler |
For this attachment to be generated, the createTripOptimizedAttachments and webPersistTrips preferences must have value true.