Services Portal 2.8 Release Notes

These release notes describe the new features and enhancements for Services Portal applications (QTRACS, Performance Monitoring, Trailer Tracks, Fleet Mapping, GeoServices, and Administration) in Services Portal 2.8, which released in the U.S. spring of 2016.

For previous release notes, click here.

System Requirements and Upgrade Information

Supported browsers

QTRACS, Performance Monitoring, Trailer Tracks, Fleet Mapping, GeoServices, and Administration are supported fully on Internet Explorer versions 8-11, Edge, Firefox, and Chrome. You may experience minor display issues in IE 8.

No other internet browsers are tested or supported.

Although Omnitracs endeavors to provide uniform support for modern browsers across all applications in the future, at this time all other applications not listed above (such as Hours of Service, Media Manager, Critical Event Reporting, etc.), may have different browser support. Please refer to this browser compatibility matrix for specific browser support information for each application.

Ensure your browser loads the newest version of the Services Portal

It is highly recommended that you clear temporary Internet files before you log in for the first time after the upgrade. Press Ctrl+Shift+Delete to open your browser’s history control panel then check the box for temporary internet files or caches. Click delete or clear to confirm your choice then close and reopen your browser. This will ensure your browser is loading the newest version of the Services Portal pages. For more information about this process, including browser specific instructions, see Omnitracs’ quick reference card on the subject.

Trailer Tracks Portal Changes

Services Portal 2.8 includes support for the TT150, a new Trailer Tracks product being developed as a low cost alternative to the TT200/210 line. The TT150 focuses primarily on trailer tracking and trip reporting and will be managed and configured through the same Trailer Tracks portal interface. This necessitated several updates of the Trailer Tracks Portal in order to better identify devices and their applicable features and parameters.

UI Changes

  • The Company Settings – Trailer Tracks page was reorganized to indicate which settings apply to which devices (TT100, TT150, or TT200/210) and to create separate sections for battery thresholds, trailer mileage reporting, and field installation
  • The more options filter on the trailer list was updated to allow for filtering by specific device type instead of only being able to filter by tethered or untethered mobile types
  • The trailer list now indicates the speed and direction of travel of the trailer if that information is available
  • The Trailer List CSV received several updates:
    • Mobile Unit Type was renamed Device Type and the previous values of tethered or untethered were replaced with the more specific device types (tethered TT100, untethered TT150, untethered TT200, untethered TT210, and none)
    • The Status Report Interval column was adjusted to support two intervals due to the TT150 providing powered and unpowered intervals. Only one interval is shown for other devices
    • A new TT150 LEDs column was added to the CSV to indicate if Communication and GPS LEDs are enabled or disabled for the TT150. N/A is shown for other device types
    • N/A or blank is shown for columns that do not apply to trailers equipped with devices that do not support the features in that column
  • Several changes were made to Settings section of the trailer details page:
    • The Mobile Unit tab was split into the Reporting and about Device tabs
    • The About Device tab displays information about the trailer tracks device such as its serial number, type of device, battery information, device part number, and any field installation notes. Sections are only shown if applicable to the trailer’s equipped device
    • The Reporting tab shows detailed information about the device status reporting intervals, wakeup intervals, additional sensors installed, trip status, external power, and in-cab device interface. Sections are only shown if applicable to the trailer’s equipped device
  • The UTT Status Report event on the History section of the trailer details page has been renamed to just Status Report
  • The dashboard was minimally updated to rename Terminal Health to Device Health and to replace MSN (mobile serial number) with serial number in the Find Trailer Box
  • The Setup – Monitoring Plans received the following updates:
    • The tethered and untethered tabs have been renamed and expanded to contain tabs with appropriate settings for the specific devices (TT100, TT150, and TT200/210)
    • Tabs are only shown for the device types in your fleet; i.e. if your fleet only contains TT210 devices you will only see the TT200/210 tabs and not the TT100 and TT150 tabs

Integration

The ESS mobileType element values were updated to provide more device specificity and support the TT150. Previously Trailer Tracks devices could return one of two possible values (10 or 11) to indicate if it was an untethered or tethered device. In Services Portal 2.8 these values have been updated to provide more specificity as follows:

  • 10 = TT200/210
  • 11 = TT100
  • 12 = TT150

A complete list of ESS changes can be viewed on the Services Portal Integration Developer’s wiki at https://intinfo.omnitracs.com/display/iWebInt/changes+scheduled+for+3-19-16+deployment

Several error strings have been updated for the following Trailer Tracks Web Services:

Web Service Previous Behavior New Behavior
setTrailerGeofence Error string "039 Tethered Trailers are not geofence capable" was returned when referencing a trailer equipped with a TT100. A more generic error string "039 Device type does not support mobile geofences" is returned when referencing a trailer equipped with a TT100, TT150, or no device.

enableDataSharing

disableDataSharing

checkDataSharing

No error string (a blank response) was returned when referencing a trailer equipped with a TT100. A new error string "008 Data sharing not supported" is returned when referencing a trailer equipped with a TT100, TT150, or no device.
getScheduledReeferMonitoring No error string (a zero/null response) was returned when referencing a trailer equipped with a TT100. A new error string "007 A reefer trailer with the specified SCAC/ID does not exist" is returned when referencing a trailer equipped with a TT100, TT150, or no device.

getMileageCounter

setMileageCounter

getTrailerMileageThreshold

setTrailerMileageThreshold

Error string "008 Trailer SCAC/Trailer ID invalid" was returned when referencing a trailer equipped with no device.

If the trailer mileage reporting feature is not enabled for the customer, then existing error string "005 Trailer mileage reporting not enabled" is returned for trailers equipped with no device.

If the trailer mileage reporting feature is enabled for the customer, then existing error string "006 Trailer mileage reporting not supported" is returned for trailers equipped with no device.

For more information visit the Web Services Trailer Management page on the Services Portal Integration Developer’s wiki at https://intinfo.omnitracs.com/display/iWebInt/Trailer+Management

Arrival/Departure Notification

Integration customers who subscribe to the GeoServices Event Notifications transaction (T.5.01) receive ESS arrival/departure notifications every time a vehicle arrives at or departs from specified landmarks.

An option to republish an updated ESS arrival/departure notifications was added several releases ago but was hidden and could only be enabled by Omnitracs personnel. The option for customers to turn this feature on or off has been added to the Company Settings - QTRACS page of the Services Portal in this release. Turning this feature on may require updates to existing integration.

Updated Performance Monitoring Charts

Previously the charts in Performance Monitoring used Google’s Image Charts API. However, Google has deprecated that API and may discontinue service at any time. Performance Monitoring now uses the Highcharts API.

This change means that Performance Monitoring charts and graphs may appear a little different that you were previously used to. However, all the same information is still being displayed and the new API provides some additional functionality that the previous charts and graphs lacked. This new functionality includes:

  • Hovering over a data point in a graph or chart will show a popup with more detailed information about that data point
  • You can hide or turn off a data element in a graph or chart by clicking on its associated item in the legend below the graph or chart

Fixes/Minor Enhancements

The following fixes and minor enhancements were included in the Services Portal 2.8 release.

Browser Support

  • Services Portal release 2.8 and its associated applications (QTRACS, Performance Monitoring, Trailer Tracks, Fleet Mapping, GeoServices, and Administration) is now considered compatible with Microsoft Edge, Microsoft’s newest browser in Windows 10.

Performance Monitoring

  • The first user-created Vehicle Type is now set to the default type instead of the Rsv type.
  • Fleetwide overrange parameters are now automatically sent to a mobile device whenever the Vehicle Type Parameters are sent or resent.

QTRACS

  • Fixed an issue with the message export feature where the wrong message was sometimes exported when two messages existed with the same source, destination, and creation time.
  • Fixed an issue that sometimes prevented the Message Export from printing correctly if the message contained special characters.

Trailer Tracks

  • Corrected the Event History CSV to show the proper values of Engine Off or Engine On for the Reefer Engine State.
  • A new MonitoringPlan2 object has been created that is returned by the getMonitoringPlanDetails2() and getMonitoringPlanList2() web services. This new object supports the following parameters:
    • <enableTrailerSpecXmit>
    • <mileageThreshold>
    • <lastChangeTime>

    This new object is an improvement over the previous getMonitoringPlanDetails() and getMonitoringPlanList() web services that did not support those parameters. The previous monitoring plan object and its associated web services have been deprecated but remain usable.

Previous Releases