Driver Workflow Integration

Last updated
Save as PDF

Overview

This site is for Omnitracs customers that are participating Driver Workflow integration. It is targeted to a technical audience that is involved in the actual web services integration.

Driver Workflow is a system of for communicating, performing, and collaborating around work performed by a driver. The major components are (a) the mobile Workflow engine, (b) the custom mobile Workflow template application, (c) the Workflow Magement Center (WMC) communication portal, and (d) customer system. This page addresses the WMC communications portal.

Since driver activities vary by line of business and company policy, Driver Workflow applications typically have some level of customization for each customer - similar to what you would experience with macros. As appropriate, examples are provided that are based off of the default Driver Workflow template application. This default application is a reference application that contains a majority of the functionality required by most companies. However, each customer may have additional forms in their applications, different workflow logic, and different message types, which will in turn create different forward and return messages that flow through the WMC communications portal. The mobile Workflow template application must match the message types that are being communicated by the customer system through the WMC communications portal.

Integration Documentation

Driver Workflow Web Service Integration Guide - A guide to the web service calls, security token, and authentication.

Driver Workflow Message Examples - Sample forward and return messages for the default Driver Workflow implementation.

Deprecated Interfaces

For customers who may have participated in the Driver Workflow Beta program, the older OmniView Driver Workflow (OVDW) interface documentation can be found here. Please note that these interfaces will only be available until November 30, 2011. Contact Omnitracs Technical Services if you need assistance switching your company workflow integration to use the newer interfaces.

After the service has been deprecated, invoking the service will return the following:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body>

<soap:Fault>

<faultcode>soap:Server</faultcode>

<faultstring>This method is deprecated</faultstring>

<detail/>

</soap:Fault>

</soap:Body>

</soap:Envelope>

All new development should be done on the current WMC interfaces only.

The basic workflow messaging strategies remain the same (data/datum pairs). Return messaging processing has been standardized around the Omnitracs Event Subscription Service and follows the integration pattern established for other Omnitracs applications.