17.60

A PDF version of the complete 2017 release notes is available here.

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

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. 2017.17_01.0248 or later.

  • 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

  • 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

Introduction to Fuel Dispatch

Providing telemetry data to TMW (FS-200491)

To better serve you, TMW now offers you the option to provide application telemetry data. This data allows us to see near real-time information about the application and how you are using it. It logs:

  • User actions, such as opening windows, clicking icons and buttons, responses to errors

  • Performance information on saving and loading trips, window load times, and SQL view execution

  • Environment information, such as the application version, database SQL level, user name, TMW license values, machine statistics, and operating system version

    There is no performance overhead. Data is sent using the store-and-forward method when the machine has open cycles.

You can decide to share or stop sharing data at any time.

Link to topic: Providing telemetry data to TMW

Assigning resources and updating trips

Managing a retain date/time conflict between orders for the same commodity (FS-200505, FS-200515)

You use the Card Planner and Planning Worksheet to dispatch trips to fill a store’s need for a product. Most often, you dispatch them based on the order of their delivery dates. Dispatching them out of order may cause a retain date/time conflict between orders.

When another order for that commodity has a status of Planned, Started, or Dispatched, the system notifies you that a conflict exists. The notification includes the specified arrival date/time causing the conflict.

When a scheduling conflict occurs, you have two options:

  • Continue the asset assignment.

  • Cancel the assignment, and move the order back to the Available Orders grid.

Link to topic: Assigning resources to trips

Common Dispatch features

Route Scheduling (FS-200381)

The Route Scheduling features allow you to schedule fixed-route trips automatically. You can create a route template for trips that happen:

  • At the same stops or locations

  • On a set schedule, such as every day, every Monday, etc.

You can also assign resources in the template. The systems uses it to generate multiple, individual trips. This saves you the effort of creating them separately.

Oil Field Order Entry

Opening Oil Field Order Entry to view trip details (FS-200374)

When you plan trips in the Card Planner or the Planning Worksheet, you can double-click on an order to view its details. By default, the system opens the order in a separate, movable Oil Field Order Entry window. To return to the Card Planner or Planning Worksheet, you must close this window.

The administrator can change the default behavior and have Oil Field Order Entry open instead. To do this, have[FuelDispatch]CodoeDblClkAsTab=Y in your TTS50.

Link to topic: Opening Call On Demand Order Entry or Oil Field Order Entry to view trip details

Resolved issues

  • FS-82706
    When the client opens Fuel Dispatch they have numerous custom reports under the Custom Reports menu option. When a user opens say CODOE or Card Planner they lose some, or all, of those reports. PTS 70582 and 67402 were created for this, but were closed because the software was FAI as the menu just needed to be saved for those screens. However, upon trying to add these reports back to the Custom Report menu they are not able to be selected because they only exist as an option when no tabs are opened.

  • FS-89624
    Company Planner shows only one grid worth of mapped item data on the map. Meaning if you have three grids all with geo-data with one for driver, one for tractor and one for trailer it will show only the mapped location and allow mapped subscription functionality for one grid.

  • FS-101997
    Customer has long haul boards configured in the Fuel Dispatch - Card Planner window. When attempting to initially load one of the longhaul boards when first opening the Card Planner, no information is retrieved upon the refresh. When they refresh a second time, data will load without issue.

  • FS-105692
    During the shift, dispatchers are going into CODOE to update what the driver is scheduled to drop in each tank. When they key in the new values and place a zero in the tanks to move the volume to another tank, the UNIT changes from GAL to UNK. This was unknown to the user since the Unit field was not displayed on the screen.

    When the GAL value drops off the Unit field, and it defaluts back to UNK value. In the STOPS grid, open the LLD line and it can be seen that the Volume now jumps over to OrderedCount field. This prohibits the dropped gallons to be recorded against the sales. This will produce a zero in Inventory Services, Review Sales History, Delivered Tab.

  • FS-200286
    When clicking copy move in the dispatch menu on a master order with alphanumeric characters in the name, error Conversion from string TESTMASTER1 to type integer is not valid appears.

  • FS-200301
    When there are multiple tabs open in Fuel Dispatch an "ExecuteScalar" error occurs when adding new tanks in the Tank Model Maintenance Tab.

  • FS-200329
    When changing the Company ID for the live unload on a split trip, an index out of range error is thrown.

  • FS-200404
    Orders with multiple deliveries will have the incorrect freight pin code populated on the freight row where the parent freight is the first delivery. This then results in incorrect data to be populated on the Trip Summary report. Incorrect data populates the Driver’s Trip Summary report. Trip Summary report would need to be modified.

  • FS-200411
    Object Reference error is thrown when attempting to add a Deadhead stop on the Card Planner with no other trips planned to the driver.

  • FS-200412
    When TTS50 setting Misc.CompanyIDFormat is set to Numeric6Plus2, company id generation is supposed to function as specified on PTS 16911. However, the effective id is actually incrementing by two between sequential companies. Further, once the ID reaches 550000, a more serious issue appears that causes a totally invalid negative numeric id to be generated.

  • FS-200413
    If the client uses the Google Maps API in Company Planner they receive the following message and are redirected to a link for unsupported browsers.

    "You are using a browser that is not supported by the Google Maps JavaScript API. Consider changing your browser."

  • FS-200470
    An object reference error is thrown when opening the Quick Reading Entry application and then closing the window without having loaded a company. The window cannot be closed without loading a company first. The Quick Reading Entry window cannot be closed until a company is loaded.

  • FS-200493
    When using the LEG option for the BlockEditLevelAfterStl TTS50 INI setting, the entire movement is being locked for a split trip where the first leg segment is completed and pay details exist in Settlements. Dispatchers are unable to edit the second leg segment of a split trip when the first leg segment has pay details in Settlements.

  • FS-200494
    The Copy Extra Info check-box option is non-functional and does not prevent extra info data from being carried forward when an order is copied via the Copy Order/Trip window.

  • FS-200498
    Customer is reporting that the runout time for a delivery is not adjusting to reflect the runout of the tank. This appears to be effected by the Store Closed Window as the runout time is always one hour prior to the Window Start. A tank can already be at a critical level before a delivery is made due to the dispatch believing the runout time can be much later than it actually should be.