2018.1

A PDF version of the complete 2018 release notes, including resolved issues, is available here.

2018.1 SP1

Resolved issues

  • FS-201446
    The user disabled the load requirement for an order but still received a Prevent Save indicator when assigning the order to a driver.

  • FS-201472
    Company Notes disappear from the Call On Demand Order Entry Notes tab after saving the order.

2018.1

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. 2018.18_01.0192 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

Card Planner and Planning Worksheet layouts

Preventing non-admin users from modifying global default and group layouts (FS-200582 and FS-200583)

A system administrator has the ability to design different layouts appropriate for various user groups. As a user, you may be assigned one or more layouts and have access to multiple layouts.

Previously, the Grid Layout Permissions window allowed any user to overwrite window or grid layouts assigned to a group or identified as a global default. Now, your company can limit this functionality to administrators only.

This change applies to:

  • Planning Worksheet’s grid layouts

  • Card Planner’s drivers and trips layouts

  • Other Fuel Dispatch grid and window layouts

Introduction to Fuel Dispatch

Release naming convention changes (FS-20587)

TMW is standardizing the way we identify product releases. The new format is yyyy.r.x.zzzzz:

  • The first four digits (yyyy) represent the year of the release.

  • The fifth digit ® is the quarter in which the release is made available.

  • The sixth digit (x) is an internal identifier used by TMW.

  • The last five digits identify the build number.

You will see release numbers in this format:

  • On the ClientCenter download delivery page

  • In the version check message shown during installation

  • On the application login window

  • On the application Help About window

  • In the status bar at the bottom of the application window.

  • In Windows Control Panel’s Programs and Features list of applications.

Order Entry

Quick Copy now adds oil field reading rows to oil field orders (FS-200548)

When you create oil field orders, you include readings information that identifies the:

  • Company ID and Tank ID

  • Reading date

  • Order number and run ticket number

  • Commodity and commodity class

  • Amount of product removed from a tank

In previous versions, if you used the Quick Copy window to create oil field orders from a master order, blank readings rows were not included. This happened even if your system was set up to add them to oil field orders automatically.

Now, oil field orders created in the Quick Copy window include blank readings rows.

Quick entry functionality added to Call On Demand Order Entry’s Tanks tab (FS-200480)

The Tanks tab and the Freight tab now show the commodities carried at each store. Entering orders based on a store’s tanks eliminates the possibility of selecting the wrong commodity. The Tanks tab has been updated to:

  • Populate the store’s default shipper, supplier, and Account Of companies when a Tank Quantity is entered.

    Note: These fields are populated automatically when a product is added. This functionality is available in the Freight tab, as well as on the Tanks tab.

  • Use the default volume unit of measure specified in your TTS50 file, unless the commodity class specifies a default unit of measure.

  • ToolTips containing descriptions are now displayed over each Quantity field.

    Note: This functionality is available in the Freight tab, as well as on the Tanks tab.

  • Require an entry in the Tank Quantity field before you can make entries these fields:

    • Tank Volume (the delivered quantity)

    • Tank Net Volume (the quantity billed if the customer uses Net Volumes for billing)

You cannot edit the Tank Volume and Tank Net Volume fields for orders that are Available, Planned, or Dispatched. You cannot enter them for Master orders or Job orders. When these fields are locked for editing, ToolTips appear, stating why you cannot make an entry.

When an order is Started or Completed, the Tank Quantity field is locked. The other two fields are editable.

This functionality is also available on the Freight tab.

Tracking stores in critical need of product

Dispatch Dashboard shows stores' phone numbers (FS-200645)

In previous versions, the Dispatch Dashboard’s Stores List grid did not display each store’s phone number. Now, each store’s primary phone number appears in the grid.

Improved Reading Now accuracy (FS-200396)

In previous versions, the value shown for the Reading Now field could be inaccurate. This happened because the system compared a tank’s Reading Now value with the Shut Down volume recorded in its profile. If the Reading Now value was less than the Shut Down value, the system showed the Shut Down value.

Now, the system shows the actual Reading Now value, even if it is less than the Shut Down value.

The Reading Now field appears in these windows:

  • Dispatch Dashboard’s Stores List grid and the Tank Graph

  • Forecast Order Site Review window’s Tank Review/Reading grid, on the Day View tab and on the Order/Delivery Review grid’s Summary tab

  • Forecast Order Review window’s Stores List grid
    The grid appears just below the fields used to filter the stores to be retrieved.

  • The Site Snap Shot’s Tanks Graph shows the Reading Now value as the Now ToolTip. You access the Site Snap Shot from the Card Planner or Planning Worksheet.

Dispatch Dashboard warns when adding/removing freight (FS-200387)

When you edit a store’s order in the Dispatch Dashboard’s Store’s Orders grid, you can change the delivery volume of products on the order to adjust the delivery window.

You cannot add or remove products on the order. For example, suppose a store carries three commodities:

  • Unleaded 87

  • Unleaded 89

  • Unleaded 93

If an order shows quantities only for Unleaded 87 and Unleaded 93, you cannot enter a delivery volume for Unleaded 89. The system considers this as adding freight to the order.

If you change a commodity’s delivery volume to 0 (zero), the system considers this as removing freight from an order.

You can only add or remove freight in Call On Demand Order Entry.

In previous versions, adding freight made a message appeared. It stated, "Adding freight is not supported here. Please double-click and use Call On Demand Order Entry to add freight." No similar message appeared if you removed freight from an order.

Now, adding or removing freight makes a new message appear. It states, "Adding/deleting freight is not supported here. Please double-click and use Call On Demand Order Entry to add/delete freight."

Resolved issues

  • FS-200497
    When planning a job order to a driver using the Card Planner and dispatching the trip, the shift ID is not being populated on the legheader record if the trip is dispatched before clicking the Update button.

  • FS-200540
    Call On Demand Order Entry - Requirement Validation upon Save

  • FS-200549
    Company Planner Action OpenOrderEntryNew Not Working.

  • FS-200550
    User added controls are in an editable state when initially opening the floating Oil Field Order Entry form for an invoiced order.

  • FS-200558
    In Oil Field Order Entry, tabbing through to the Company ALT ID field resets the LUL location.

  • FS-200694
    Call On Demand Order Entry - Update fgt_DeliveryTank fields to key off of Actual Quantity field

  • FS-201950
    The Forecaster was modifying delivery times on orders that should have been locked. This happened when you had [InventoryService]ForecastPLNStatus=Locked and [InventoryService]ForecastDSPStatus=Locked in your TTS50. The system changed the order source status to Locked Volume (LCKVOL) instead of Forecast (FRCST) when you changed the volume on the order. Forecasted orders in Planned, Dispatched, or Started status were affected. Started orders are locked by default. Now when you change an order’s volume, the order source remains LCKVOL if your INI settings are set to the Locked option or when the order status is Started (STD).