2018.4
A PDF version of the complete 2018 release notes, including resolved issues, is available here.
2018.4 SP13
Resolved issues
-
FS-201557
Fixed the issue where the Card Planner and Planning Worksheet showed an incorrect trip Retain Date and Runout Date for split trips. -
FS-201567
Fixed the issue where you were unable to dispatch a splash blend load that included a Certificate of Analysis. -
FS-201591
Adjusted the Inventory Services forecast logic to compare the compartments on a loading configuration instead of checking the Trailer ID, when assigning an order to an asset in the Fuel Dispatch Card Planner and Planning Worksheet. -
FS-201613
Fixed the issue where creating an order for a splash blend product and a Certificate of Analysis in Call On Demand Order Entry caused an error.
2018.4 SP12
Resolved issue
-
FS-201525
When using the Optimize Source feature to change the shipper on orders in the Card Planner’s Avl. Orders grid, and one or more orders included a Certificate of Analysis (CofA), the system provided no indication that the CofAs had to be deleted before changing the orders. Now a pop-up window opens and identifies the orders from which certificates must be deleted.
2018.4 SP11
Enhancements
Order entry
Certificate of Analysis (FS-201481)
Previously, when creating a Certificate of Analysis on a splash blend product the user had to select one of the child splash blend commodities. When they opened the Certificate of Analysis Creation window, the Customer Specification information pertained to the child commodity rather than the parent splash blend commodity. Now, the requirements and Certificate of Analysis for the product being delivered pertain to the parent rather than the child splash blend commodities.
Resolved issues
-
FS-201425
Fixed the issue that caused a GEH error to occur when a user created a Certificate of Analysis, saved the order, changed the consignee, and then saved the order. -
FS-201494
Adding a splash-blend commodity and a shipper to a freight record with a COA in the Freight grid, removed the COA text from the COA button. This issue is now fixed. -
FS-201520
Fixed the issue where the Count, Count Unit, Weight, and Weight Unit fields are not retained in a window layout when the window is re-opened.
2018.4 SP10
Resolved issues
-
FS-201462
In Call On Demand Order Entry, the Account Of field did not restrict the list of company IDs to those specified in the AccountOf tab in the Company Relations Profile. This issue was fixed. -
FS-201475
Fixed the performance issues in the Dispatch Dashboard. The following changes were made:-
The Mode field specifies the quantity of data retrieved for a specified duration. It includes these options:
-
LegacyResult
Shows data gathered within 14 days forward and 20 plus days back -
ShortResult (default)
Shows data gathered within 7 days forward and typically, 2 weeks back
-
-
Additional columns are available to show in the Stores List grid. The columns are similar to those in the Forecast Order Review window.
-
2018.4 SP9
Resolved issue
-
FS-201831
In addition to the Shipper tank Id (which is already locked down and displays a ToolTip warning), the Shipper and the Commodity Code fields are read-only while a Certificate of Analysis exists. If a user attempts to change any of these fields, a new warning opens. It tells the user that they must first delete the Certificate of Analysis to make those fields editable. The ToolTip that already exists for the Shipper Tank Id now applies to the Shipper and Commodity fields.
2018.4 SP8
Resolved issue
-
FS-201344
When entering a new order in Call On Demand Order Entry and changing the commodity code on the first freight line of the order, the commodity code in the drop-down menu matched the commodity code of the last freight line on the order. Now the proper commodities show for each line item in the Freight grid.
2018.4 SP7
Resolved issue
-
FS-201320
A reading of Zero (0) appears in the import file that is being inserted into a client’s database. Some files have a zero for the reading due to an error or something occurring at the site level that caused the zero to populate instead of the actual reading. Now when a zero shows for a valid tank, the entire site is ignored.
2018.4 SP2
Enhancement
TruETA
Viewing TruETA data (FS-201118)
TruETA is a trip planning and execution tool that calculates estimated time of arrival (ETA) for each stop along a truck’s route. It is a cloud-based solution that automates the calculation of ETAs based on current vehicle position, driver Hours-of-Service (HOS) and real-time and predictive traffic patterns.
TruETA is an add-on module that is sold separately. For details, contact Trimble Transportation Sales. |
Now, you can view TruETA information in Fuel Dispatch, using the TruETA Company Planner board. This board lists trips for which TruETA calculations have been run. The system displays trip information, including the TruETA status, such as Early, Late, or At Risk. When you click a trip in the list, a map of the trip is shown.
2018.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. 2018.4.0.0004 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
Driver schedules
Starting at a different start company (FS-200471)
In the Edit Driver Schedule window, if you change the Start Company for a day, the End Company for the previous day is changed.
For drivers that float between multiple start companies, a new INI setting enables you to change the driver Start Company for the current day without affecting the previous day.
Link to topic: Changing a driver’s generated schedule
Order entry
Set maximum full-trailer amount for manual order entry (FS-200253)
For non-forecasted sites, it is possible to overload a trailer when entering an order in the Call On Demand Order Entry window Freight tab.
A new INI setting enables you to set the maximum full-trailer amount to help avoid overloads. When configured, the system displays a message if a given quantity is greater than the allowable limit.
Link to topic: Recording commodity information on the Freight tab
Oil Field Order Entry
Viewing a lease’s order history (FS-201044)
When manually creating orders in Oil Field Order Entry, it can be helpful to reference the shipper’s (lease) previous orders. Leases often produce only enough oil to justify pickups a set number of times per day or week. Customers may call in the order multiple times. Being able to quickly view existing order can ensure you do not create duplicate orders. Currently, to view existing orders you must use the Order Scroll or Card Planner. Now, you can set up the system to show the lease’s orders on the Oil Field Order Entry window’s Order History tab. You can show up to 50 orders on the tab.
Link to topic: Viewing a lease’s order history
Basic company profile setup
OtherTypes2-4 added to Company profiles (FS-201001)
In previous versions, your company could set up the system for you to make entries in company profiles using the OtherTypes1-2 fields.
Now, the OtherTypes3-4 fields have been added to company profiles.
The name and options for these fields are user-defined. Entries in the Other Type 1 - 4 labels determine the options you see. |
Retrieving records in scroll windows
Improved access to scrolls and profiles (FS-200996)
In previous versions, accessing scroll windows from the Tools menu required that you scroll through the menu to find the one that you wanted. Direct access to profiles from the Tools menu did not exist.
Now, the Tools menu has been updated to group scroll windows for easier access. The menu also provides direct access to profile windows from the Profiles grouping.
Resolved issues
-
FS-200914
Planning Worksheet does not create Freight_By_Compartment records from JOB orders -
FS-200975
Call On Demand Order Entry: Able to modify orders that are completed and paid -
FS-201022
Dispatch Dashboard: TOH Volume incorrect for Manifolded tanks -
FS-201049
Forecast Order Review: Forecast Order Review produces an Index Out of Range error when selecting the Reviewed box for multiple companies. Open the window and select the Reviewed checkbox for one company, then click another company’s row and save and repeat this process two more times. On the third attempt, the error appears. -
FS-201070
Call On Demand Order Entry: When more than one fgt_shipperTankID is on a freight record, loading an order always shows zero. -
FS-201071
TMW GO Driver: When attempt to send a load from Fuel Dispatch and do not have SystemsLink Fuel installed, an error occurs. The error message states "Update Error with action http://tempuri.org/ITMWGoHostSercie2/SaveOffer cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher…." -
FS-201072
Forecaster: Including completed (Locked) orders, which can cause single delivery orders to exceed a tank’s safe fill. -
FS-201958
When you changed the volume and assigned a driver at the same time, the Source field value showed Locked Volume (LCKVOL). This occurred even when you had[InventoryService]ForecastPLNStatus=Locked
in your TTS50. In addition, all Freight grid volumes reset to 0 (zero) when you planned stops and assigned a driver in the Stops grid.