2020.4

This section contains the following for the latest version:

  • System requirements

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

Before upgrading your production environment, Trimble recommends that you read the system requirements and install the latest version in a test environment. If you have questions, please contact your Trimble customer representative.

Warnings

Forecaster Console update warning

As of V. 2018.3, the Forecaster Console in Inventory Services no longer uses Common Volumes to calculate order quantities. Now, it uses Trailer Compartments to maximize gallons and fit orders to specific trailer compartments. The V. 2018.3 update requires a simple setup process to forecast to trailer compartments. We have included a mass update tool in the ClientCenter download to ease this transition. Instructions on using the tool are provided in the Inventory Services 2018.3 release notes.

Social Security number encryption warning

Starting in version 2020.4, Social Security numbers you enter in the Driver profile are encrypted in the database by default.

Having encrypted Social Security numbers could interfere with third-party applications accessing the data. This happens because the data is encrypted when transferred. The third-party application would not have the ability to decrypt it.

You can set up the system so that the Social Security numbers you enter in the Driver profile are not encrypted in the database. To do so, set the DataEncryption General Info Table setting’s String1 field to N.

The Data Conversion Administration Utility allows you to encrypt/decrypt a group of Social Security numbers in your database. Contact your Professional Services representative to obtain the DataConversionAdministrationUtilityInstall.msi.

Access and usage of The Data Conversion Administration Utility should only be provided to a system administrator. That utility provides access to all highly sensitive data and should only be used in the explicit instance of needing to encrypt or decrypt the driver profile.

ALK warning

In very limited circumstances, your system could generate incorrect mileages when using PC*MILER version 32 with any of these products:

  • TMW Operations version 2018.2 or lower

  • TMW Back Office version 2018.2 or lower

  • Fuel Dispatch version 2018.2 or lower

  • TMWSuite version 2018.2.0.0275 or lower

This problem is associated only with systems that have one of these options set in their TTS50:

  • [MileageInterface]ExOptions[x]=I

  • [MileageInterface]ExOptions[x]=X

Having either of these options set will cause Practical mileage to be computed as Shortest, and Shortest mileage to be computed as Practical.

This will not affect mileages previously retrieved and stored in the mileage table.

The issue is fixed in the next general release, such as 2018.3 for TMW Operations.

A temporary workaround to bypass the incorrect code is to do any of the following:

  • Use an additional ExOption in conjunction with the I or X option.

  • Remove the I or X option entirely.

  • Install an earlier version of PC*MILER.

Requirements

  • TMWSuite®
    You must be using TMWSuite V. 2020.4.

  • Microsoft® .NET Framework
    Install or upgrade to the latest version of the Microsoft .NET Framework on your system. At a minimum, you should have V.4.6.2 installed.

    The framework must be installed on the FuelTMS applications server, client, and administrator systems before you install FuelTMS. If it is not present, the system displays an advisory message during the installation. Install the framework before running the application.

  • Microsoft® SQL Server®
    Microsoft SQL Server 2012 or later

    Note: SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019 are supported. Trimble Transportation recommends using the latest service pack of whichever version you use.

  • You must be logged into the system where you want to install the FuelTMS applications, and have administrator rights for that system.
    Like most applications, FuelTMS applications can be installed locally on a user’s system. It is also possible to install FuelTMS applications on a network drive. To do so, you must be logged into the system where the drive is physically located, and have administrator rights for that system.

  • SQL Server System Administrator rights are necessary.
    The installation of FuelTMS applications includes the manual application of a SQL script to the TMWSuite database. You must have a SQL Server administrator login and password to apply it.

Enhancements

Company Relations Profile

checkbox option added to prevent pre-populating freight rows in Call On Demand Order Entry (FS-202036)
In some cases when entering an order, a large number of freight rows would auto-populate due to the number of commodities tied to the company/consignee.
Now, for a non-forecasted site there is a Show All Commodities checkbox to allow or prevent auto-population of commodities in the freight row in Call On Demand Order Entry. This lets you enter commodities manually.
The checkbox is located in the Company Relations Profile window. To make it available, you must have [FuelDispatch]ShowAllCommoditiesCheckbox=Y in your INI file.

Privacy Policy

The Trimble Privacy Policy link added (FS-202027)
The Trimble Privacy link has been added to the Fuel Dispatch login window. When you click the link, the Privacy Policy page opens in a web browser.

Resolved issues

Call On Demand Order Entry

  • FS-201870
    When you created a new order, the default volume unit was not pulling values from the tank or the weight recorded for the commodity class. It had used the values set in the TTS50 setting [FuelDispatch]DefaultWgtVolCount.

  • FS-201951
    When you used the Add Freight Record button to add a new commodity to an order, an additional live load (LLD) stop was added in the Stops grid. This happened even if the same shipper was used.

  • FS-201963
    You could not make changes to an Available order. This happened when you opened it in the same window where you had opened a settled order.

  • FS-202020
    Previously, when you used the Retain/Redirect feature you could enter a retain quantity that could exceed the volume on the order. Now, a pop-up message informs you that the quantity should be less than or equal to the original quantity.

  • FS-202063
    When using a Job Order by volume, you could exceed the total volume remaining on the order. Now, a pop-up message informs you that there is no volume remaining on the selected order.

  • FS-202078
    If you set the quantity and volume to 0 (zero) on a Started or Dispatched order and saved it, the order became corrupted. This caused errors in the Planning Worksheet and Card Planner.

Card Planner

  • FS-202079
    An error occurred with the Multi-Job Remaining field. It was not correctly updated when you assigned all remaining Job orders in the Card Planner or Planning Worksheet. The jobs remained in the list. This happened whether the setting [FuelDispatch]RecurringJobOrders=Y or N.

  • FS-201507
    When you selected TotalMail > Cancel Workflow from the shortcut menu, you did not get a message if the order had completed trips. Now, a notification message appears.

  • FS-201607
    If you had [FuelDispatch]CardPlannerCustomDriverField set to a date field, that column in the Card Planner did not display data. That happened if you used Cell Designer to change the column to a custom name for the date field.

  • FS-201982
    When searching for drivers by date using a long haul board in Card Planner, returned no results. This was specific to drivers that did not have trips assigned to them. Now, searching by date returns results for all drivers.

  • FS-202029
    Attempting to assign a Job order in Card Planner resulted in a system error.

  • FS-202046
    If you used the Show Filter Row in the data grid and you double-clicked a column, an error occurred.

Dispatch Dashboard

  • FS-202031
    When you clicked the "X" to exit the Fuel Dispatch application while in Dispatch Dashboard, an error message occurred and the application would not respond. This happened if data was loaded in Dispatch Dashboard.

  • FS-201947
    The HTC (Hours to Critical) column was not displaying the correct value for critical hours. This happened if you used a site that had multiple tanks with the same commodity.

Driver Calendar

  • FS-202041
    If you tried to view data for more than 45 days in the Driver Calendar window, an error would occur. Now, a pop-up message notifies you when you exceed the 31 days limit.

Oil Field Order Entry

  • FS-201952
    Previously, the field size in the Oil Field Readings tab would only allow 14 characters in the fields MeterStart, MeterEnd, DeliveryStartMeter, and DeliveryEndMeter. Now, the fields allow 16 characters that includes the decimal places.

Order Scrolls

  • FS-201983
    When you used the New Search button in Order Scrolls, the grid layout would reset to the default if you were using a custom layout. Now, the custom layout is retained.

Planning Worksheet

  • FS-202044
    When you tried to load the Planning Worksheet an error occurred. This happened if an active tractor and trailer had the same ID.

Systemwide

  • FS-201991
    The system was processing the same consolidated move record multiple times. This caused performance issues.

Trailer Profile

  • FS-202019
    The Set Compartments to Trailers list did not show trailers without compartments. This prevented you from mass assigning trailer compartments. The list appears on the Trailer Profile’s Compartments tab.

  • FS-202040
    When you attempted to view trailer compartments through the Set Compartments to Trailers grid, an error occurred. This prevented you from assigning compartments to trailers.