2021.3

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.

A PDF version of these release notes is available.

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. 2021.3.

  • 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

Cross Dump

Cross Dump notification (TTESUITE-42116)

In some cases, a driver may deliver the wrong product to the wrong tank. This can lead to major issues at the station.

Now, when a delivery is made the system will check that what was delivered matches, or is close to, the increases in the tank readings. It shows a warning that a possible cross dump has occurred in these windows:

  • Dispatch Dashboard

  • Forecast Order Review

  • Forecast Order Site Review

The [InventoryService]CrossDumpTolerance setting has been added. It specifies the tolerance used in detecting a Cross Dump at a destination, based on a reading increase in the tank.

Resolved issues

Application upgrade SQL

  • TTESUITE-42110
    When you upgraded to a newer version of Fuel Dispatch and ran the DBMod.sql upgrade script, it created a second trigger called dt_loadrequirement. This could cause poor performance in the application.

Call On Demand Order Entry

  • TTESUITE-41942
    The stop times on an order were displaying incorrectly. This happened when there was a record lock on an order and another Call On Demand Order Entry window was opened displaying the same order.

  • TTESUITE-42122
    If you changed the quantity on an order to zero (0) and tabbed out of the field, the quantity would change back to what it was originally. You had to repeat the process again for it to update.

Card Planner

  • TTESUITE-200078
    If you tried to cancel a TotalMail order from Card Planner, you would receive an error. You were still able to cancel the order in the TotalMail application.

  • TTESUITE-200487
    If you were using the Permitting feature, you could not plan loads with three or more stops/companies on the order. The system was ignoring permit weight values and displaying an error message. This meant you could not plan the order on any drivers.

  • TTESUITE-200619
    When you tried to assign a multi-job order to a driver, you got a Planning Cell error. This would happen due to a custom Card Planner view that does not have the VolumeRemaining field.

  • TTESUITE-41702
    When you tried to assign the first half of a split trip to a driver, a warning message appeared. It stated that the order was being assigned out of sequence based on retain/runout. The system would assign the second half of the split trip instead.

Company Profile

  • TTESUITE-200369, TTESUITE-200370
    If you opened an UNKNOWN company profile and selected the Load Requirements tab, it would cause a delay in loading the window. It should not look at the Load Requirements for an UNKNOWN company. This also caused performance issues when creating a new order in Call on Demand Order Entry.