The following configurations will need to be enabled for CoPilot to communicate with our web tools (FleetPortal, Content Tools, and RouteReporter).
| [Fleet Portal] | |
"Connected"=1 | Gives CoPilot permissions to communicate with our web tools |
"PostToFleetPortal"=1 | Used to enable/disable CoPilot's ability to post to our web tools |
"PartnerID"="ABC123" | Unique Partner identifier. Provided by Trimble MAPS |
"DeviceID"="12345" | Unique Device identifier. The Partner will create this for each of their customers' devices. |
"DriverID"="98765" | Unique Driver identifier. Used for filtering routes in RouteReporter by Driver. The Partner will create this. This configuration is optional. |
| [User Settings] | |
"AllowEnableCompliance"=1 | Used to enable/disable CoPilot's ability to post route information to RouteReporter. (Note: RouteReporter is a paid on license for CoPilot. Please consult your Business Development representative before enabling this configuration) |
We recommend setting these configurations through our integration APIs. Links to our API documentation can be found below.
CPIK libraries: https://developer.trimblemaps.com/copilot-navigation/v10-19/feature-guide/operating-features/configuration-options/#configuration-settings
SDK app: https://developer.trimblemaps.com/copilot-navigation/v10-19/sdk-app/api-functions/settings/#msg_configsetintval
Note: If needed, these configurations can also be hardcoded into a product.cfg which CoPilot can leverage on launch. However, being that some configurations will not remain static it is recommended to use our integration APIs.