17.50

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

Oil Field Order Entry

Working with the Meter Correction Factor (FS-200247)

In Oil Field Order Entry, the Meter Correction Factor is used when generating estimated barrels for metered tanks. The meter correction factor is stored in:

  • The Company Relations Profile window’s Tanks tab

  • The Oil Field Order Entry window’s Oil Field Readings grid

In previous versions, a factor did not accommodate more than four decimal places. It could be entered only in the Oil Field Readings grid. It was displayed only in the Company Relations Profile window.

Now, the factor can have up to six decimal places. It can be entered and viewed in:

  • The Company Relations Profile window’s Tanks tab

  • The Oil Field Order Entry window’s Oil Field Readings grid

  • The Inventory Services application’s Company Tank Setup window

Updating an order’s volume based on readings (FS-200084)

In Oil Field Order Entry, changes to the readings values can change the volume on the order. In previous versions, order volumes were not updated automatically.

Now, you can set up the system to recalculate the freight volume and the net volume when reading values change.

On-Demand Forecasting

Using On-Demand Forecasting for a store (FS-200205)

When you review a store’s pending forecasted orders in Call On Demand Order Entry or the Dispatch Dashboard, you can modify a commodity’s delivery volume and lock the order against further changes by the Forecaster.

To create better efficiency, you can now change the volume on a single order, and run the Forecaster to update delivery quantities for all of a store’s available orders in real time. The update affects a store’s forecasted orders ranging from a status of Available (AVL) to Started (STD).

When you change a delivery volume on a single order, you can set up the system to lock the volume on that order from any gallon change by the forecaster. The Retain and Runout times update according to the gallons specified on the order. The Forecaster adjusts the times for the rest of the store’s available orders.

This is a crucial and highly effective feature for Fuel Suppliers that service forecasted locations.

This feature allows you to perform the following actions in Call On Demand Order Entry and the Dispatch Dashboard:

  • Call On Demand Order Entry

    • Modify a commodity’s delivery volume or product mix for a single order, and run the Forecaster to update delivery quantities and dates for all of a store’s available orders

    • Select the new Forecaster tab to view forecasted order information for the store

    • Save the order to run the forecaster automatically, when there is a volume or product mix change

  • Dispatch Dashboard

    • Use the new Dynamic Forecasting Control grid to perform any of the following actions:

      • Change volume quantities

        Note: You cannot add quantities in the Dynamic Forecasting Control grid. You can only add products to an order in Call On Demand Order Entry.

      • Lock or unlock volume quantities

      • Run the Forecaster to view updates

      • Run the Forecaster and save the order

      • If you make a gallon change, the system locks the volume on the order automatically.

      • Undo your changes

Link to topic: : On-Demand Forecasting overview

Resolved issues

  • FS-99075
    When clicking the Print button on a Company Profile in the bottom right-hand corner to print the company’s directions, the text is scrunched together and illegible. The printed document also looks this way.

  • FS-100216
    When an update is made to a company (i.e., making it a supplier) through the Company Relations Profile or File Maintenance, you are unable to use the company in its new role until you completely close and reopen Fuel Dispatch. However, if you create a company from scratch, you can use the new company without needing to close and re-open the application.

  • FS-101504
    There currently exist multiple issues with the User Terminal Relations - Board Security functionality within Fuel Dispatch. The No Access column does not prevent access to the terminals listed in the Card Planner available trips list. You are unable to set up terminal restrictions without also using fleet restrictions (at the least adding the UNKNOWN fleet record).

  • FS-102814
    The GetSOPin stored procedure needs to be modified so that any reference to the cmp_id field being equal/set to 0 is wrapped in single quotes ('0'). The cmp_id field in the GGPINS table is defined as a VARCHAR data type, and up until recently this column did not contain any values that were not able to be implicitly casted as an integer value.

  • FS-103239
    When building an order in Call On Demand Order Entry, the Account Of field in the Tanks data grid will not populated unless the user tabs into the field. If the user clicks into this field it will only show the 'UNKNOWN' company record as an option in the drop down list.

  • FS-103962
    The [FuelDispatch]CheckAssetConflicts TTS50 setting does not appear to affect Call on Demand Order Entry in the same way it does Card Planner/Deadhead Trip Editor and Oil Field Order Entry. Users are able to assign and actualize/complete loads without a tractor and trailer in CP/DHTE and OFOE with this setting turned off, but receive errors preventing the save when trying to do the same in CODOE.

  • FS-104314
    When attempting to add or remove a delivery in Call On Demand Order Entry for certain orders you receive an error stating "An item with the same key has already been added".

  • FS-104722
    The Trl_Misc1 field is not displaying properly in the Cell Designer for some trailers.

  • FS-104844
    When there are multiple companies in the database that share the same alternate ID (cmp_altid) making a change and saving one of these companies via the Company Relations Profile will refresh the window loading an incorrect company (the first one returned by SQL).

  • FS-105400
    Passenger Profile — Delete button on top menu is not deleting the profile. It shows as deleting and clears on the screen. Close and open the profile window and look in the ID field and it is still there.

  • FS-105405
    Expiration enter during creation of Trailer profile is not saved

  • FS-200093
    Fuel Dispatch - Miscalculations of HTC in Dispatch Dashboard

  • FS-200115
    Order Cancel should increment job orders remaining.

  • FS-200116
    When a job order is maintained, disable the Job Ordered and Job Remaining fields in both OFOE and CODOE.

  • FS-200131
    Card Planner - Orders are duplicated across multiple drivers

  • FS-200132
    All the button clicks are not being logged into Application insight

  • FS-200136
    Tanks Tab Retaining Commodity Gallons after Reforecast

  • FS-200137
    Create unit test for RVP logic

  • FS-200138
    DAL Error thrown while running the Forecaster

  • FS-200157
    When an order is completed and non-editable, the scroll bar on the reference number pop up grids in CODOE is nonfunctional.

  • FS-200162
    Some fields when added to the Oil Field Order Entry window via the Quick Designer are not properly defaulted to 'UNKNOWN' and reset upon open of the window and creation of a new order.

  • FS-200172
    Fuel Dispatch Unconsolidation Logic remove orders from movement is stripping assets

  • FS-200173
    Fuel Dispatch consolidation logic is incorrectly unconsolidating orders from a consolidation

  • FS-200177
    When adding a manual pay detail from the Edit Pay Detail window, the paydetail.pyd_prorap is not populated correctly based on the drivers' accounting type.

  • FS-200180
    Second leg on split trip is getting updated with driver shift start time and causing time conflicts

  • FS-200192
    Fuel Dispatch inserting texts into tmsqlmessage in the wrong format

  • FS-200201
    Freight grid displaying wrong tank IDs after top offs

  • FS-200202
    Copying a copied order via Copy Move generates an error

  • FS-200216
    If a client is using the Tanks tab in Call on Demand Order Entry and a site has more than one tank of the same commodity, the application is not populating any Net Volume or freight information on the second tank for the commodity.

  • FS-200244
    COD OE Tanks Tab Duplicating Freight

  • FS-200249
    The Save Warnings window does not allow for the user to click "OK" after correcting time conflicts using the Conflict Corrections pop up window.