Following the support for the Digital Tachograph in WEBFLEET, we integrated the new data sources into our API, giving you access to driver state changes in real-time through the WEBFLEET.connect message queue. Anticipating the release of the Remote Link, we introduced a new working time report that now includes all the different working time data and combines the associated data that is currently distributed over 4 different reports. Everything you need on working times in one report.

Furthermore we added new functions which enables you to remove orders and text messages from the PND directly without the need for manual interference from the driver.

Besides the new additions and changes mentioned above, we have released some fixes, too:

• streamlined the process of creation and usage of a new user, by removing the need to have to login with the API user credentials before they could be used in API calls

• improved response times on showOrderReport and showTripSummaryReportExtern

• corrected the error message in deleteOrder(Extern) when parameter validation failed

• swapped latitude and longitude in the output of showEventReportExtern

• enabled use of filterstring in showObjectGroupObjectReport(Extern)

• corrected the calculation of average speed in showTripReport to match the WEBFLEET UI data

WEBFLEET.connect and webMethods

Take a look at the integration of Software AG's business process management software webMethods and TomTom WORK as shown on CeBIT 2010 on YouTube.

Note

Since we try to guarantee a continued support of existing integrations and to insure ample time for migration, the working time reports now made redundant by the release of showWorkingTimes were yet not removed from the WEFLEET.connect API (although they have disappeared from the documentation). New integrations should only be using the new working time report.

The updated documentation (1.62) is available in the download section.

• Kommunikation mittels Tom Tom Work - Dorner Electronic BRM

• Destiny, TomTom WORK and DMS have combined forces to create JobFlow PLUS

• Create WEBFLEET addresses directly from your Outlook Contacts

• Send your Outlook Appointments to your TomTom Work Go unit

• Adressen importeren in TomTom WEBFLEET (NL) and Adressimporter für TomTom WORK (DE)

Unfortunately, VB doesn't support MTOM encoding out of the box, so the file 'app.config' needs some tweaking after adding the service reference(s): find each occurence of the element textMessageEncoding and rename it to mtomMessageEncoding. Don't forget to reload the project after this change, otherwise VB won't recognise the changes.

The example is available in the download section.

• Drivers - a complete set of methods to manage drivers (insert, update, delete) and identify the vehicle the driver is currently signed on to.

• Events - added methods to acknowledge and reset events and extended the filter parameters

Other additions include support for address colors and editorial changes to the documentation (including message types for popQueueMessagesExtern and additions to the list of result codes).

The updated documentation is available in the download section.

• Higher level of detail and data that are easier to process. More location details that enable you to create custom location descriptions, separate status information as typed in on the TomTom (id and text). Depending on device support, current navigation destination, eta and distance to (order) destination are now available.

• Improved performance. Using message queues that store messages only until retrieval (up to 14 days) enables us to offer you a shorter response time to your requests and allows you to query data at a higher rate.

In addition, we have extended the data set returned from showObjectReportExtern to include details about the current navigation destination and the order that is currently worked on.

The message queue operations supersede the showMessageReportExtern operation that is no longer part of the API. It is therefore no longer listed in the documentation, but support for it is continued until end of this year (2008-12-31).

Please note that we have updated our network: the host name connect.webfleet.tomtomwork.com now resolves to the IP address 83.133.69.51 only. As long as you are using the host name to access WEBFLEET.connect, this change is transparent for you.

The updated documentation is available in the download section.

The updated documentation is available in the download section.

The Perl example package just got a new member: objects2rss.pl. Use the script to create a RSS feed with current positions of all objects.

In order to get you started without having to install Perl on your system, you can use the form below to download a RSS file. You could even add the URL shown after pressing 'submit' to Google Maps. Perl source code for the CGI module we use (and that can be run standalong, too) is available as part of the Perl example package in the download section.

Account * User name * Password * Show URL and RSS source Download RSS file

Documentation updated

The documentation has been updated to version 1.3.7, adding tripid-based replication to showTripReportExtern. Check out our download section.

The new rate limits differentiate between functional groups and are set to reasonable defaults for most use cases. So, from now on there is a much higher rate limit for order-related methods compared to the limit for access to raw messages. If you want to learn more about the new rate limits, check out the updated documentation.

The deployment of this rate limits has already started for new users; existing users are currently not affected and only migrated on request.

If you are looking for applications that have built-in support for WEBFLEET.connect readily available, this is the place to browse.

For existing WEBFLEET.connect integrations, we offer the opportunity to be listed in our solutions catalog - a great way to promote your product to TomTom WORK customers, dealers and everybody else looking for applications that work with WEBFLEET.

If you would like to have your solution listed here, please use the contact form to drop us a note.

• showOrderMessageReportExtern - download or replicate order-related messages. This function makes available the history for an order including status changes, additional input given by the driver when sending custom order status messages and addresses matching the position of the order status message.

• reassignOrderExtern - assign a new object to an existing order and send a 'cancel order' message to the previous object.

The new functions are available to all WEBFLEET.connect-enabled accounts; the updated documentation is available in the download section.

So, please search your configuration for the old DNS name new.webfleet.de and replace this with the new one. You should notice the immediate improvement. The new domain name comes in conjunction with a new SSL certificate, so check your security settings too. The old system will be taken out of service by end of August. Make sure that you have applied the change by then.

We have also updated the documentation in some places, in particular, the description of showMessageReportExtern has been extended.

In order to get you started without having to install Perl on your system, you can use the form below to download a day's trip as a KML file. You could even add the URL shown after pressing 'submit' as a Network Link to Google Maps My Places. Perl source code for the CGI module we use is available as part of the Perl example package in the download section.

Account * User name * Password * Object Number * Date (dd/mm/yyyy) * Show URL and KML source Download KML file

Update: KML file example

If you do not have access to an WEBFLEET account with WEBFLEET.connect enabled, you can download a sample KML file here.

Update: Demo video

This makes it easy to store historic information on your disk and make it available to your back office applications. That way, your applications can benefit from Connected Navigation without the need to bind them directly to WEBFLEET.

Prerequisites

• You must have a valid WEBFLEET account with WEBFLEET.connect enabled.

• You need access to a database engine (PostgreSQL, MySQL, Oracle, ...) with privileges to create a new table.

• You must have a DBI driver module for your database within the Perl library path.

Using the example

• Create a new table messages in your database, that has the same columns as the response from showMessageReportExtern.

• Use your operating system's scheduling facility to execute the example periodically (say, every 2 or 5 minutes).

After messages start to show up in the messages table, access these with your own back office application as you like.

Learn more details about this application from the documentation included in the example file as Perl POD.

• new geocodeAddressExtern - adds geocoding to WEBFLEET.connect as a separate function

• updated showObjectReportExtern - now returns the most recent position for every object in addition to the object data.

Geocoding

Instead of integrating geocoding in multiple functions we provide a new function that returns all possible matches (if any) for the given location details. This is necessary as there might be multiple matches caused by typographic errors in the address data or an incomplete parameter set. You are responsible to make the decision on whether you just use the first row returned or let you users make the decision on which result to use.

In order to save some processing steps, geographic coordinates are returned formatted for user display as well as in a representation suitable for use with other WEBFLEET.connect functions that require geographic coordinates.

The updated documentation is available in the download section.

Function WFCobjects(Account As String, UserName As String, Password As String) _
    As String
    Dim Action As String
    Dim ReqUrl As String
    Dim Req As WinHttpRequest
    
    Action = "showObjectReportExtern"
    ReqUrl = "https://connect.webfleet.tomtomwork.com/extern?lang=en"
    
    ReqUrl = ReqUrl & "&" & "account=" & Account
    ReqUrl = ReqUrl & "&" & "username=" & UserName
    ReqUrl = ReqUrl & "&" & "password=" & Password
    ReqUrl = ReqUrl & "&" & "action=" & Action
    
    Set Req = New WinHttpRequest
    Req.Open "GET", ReqUrl
    Req.Send
    WFCobjects = Req.ResponseText
End Function
      

The complete example is available in the download section.

• A list of changes that were or a will be included in API updates

• Official announcements or updates

• Techniques for using the API, including discussion of examples

• Interesting solutions that integrate with WEBFLEET.connect