2021.2

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

Social Security number encryption warning

Starting in version 2020.2, Social Security numbers you enter in the Driver profile are encrypted in the database by default.
However, 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 lets you encrypt/decrypt a group of Social Security numbers in your database. Contact your Professional Services representative to obtain the DataConversionAdministrationUtilityInstall.msi.

Only a system administrator should have access to the utility. Users without sys admin rights should not use it. The utility provides access to all highly sensitive data. It should be used only in the explicit instance of needing to encrypt or decrypt the driver profile.

Cancel order/trip feature warning

Starting in version 2020.1, the user interface for the cancel order/trip functionality has changed. Several enhancements were made to make the process easier and more intuitive. Also, the same Cancel Trip/Order window is now used in both Order Entry and in the Trip Folder.
For more information, see Canceling an order in version 2020.1 and later.

User level record security

Starting with TMW Operations version 2019.1, there is a functional change that will affect customers using custom views on Company Planner, Brokerage, or Covering boards that rely on User Level Record Security. Affected customers may need to contact Support for assistance before upgrading. See the User level record security resolved issue for details.

Minimum technical requirements for 17.50 or higher warning

To upgrade from a build lower than 17.50 to 17.50 or higher, you must follow these steps.

  1. Notify your Support team that you will upgrade. (As noted in Step 4, they will need to work with you to complete the installation process.)

  2. Verify that your environment adheres to these minimum technical requirements:

    • Microsoft .NET Framework version 4.6.2 must be installed.

    • Client operating systems must be at Windows 7 SP1 or higher.

    • Server operating systems must be at Windows Server 2012 or higher.

    • In addition, verify that your system adheres to the additional requirements listed in the General requirements section for the build you are upgrading to.

  3. Run the TMW Operations installation program.

  4. Before any users attempt to use TMW Operations, call your Support representative to have them update your Planning Worksheet boards.

Trimble Transportation has added columns to the system default Planning Worksheet views to enhance the inline editing feature. These columns also must be added to all custom views. Support will perform this step for you at no cost.

Case sensitive passwords warning

Starting with V.17.50, the system treats all passwords as case sensitive. This includes existing passwords.

This change affects how you log in with an existing password:

  • If your password was created with [Misc]CaseSensitivePasswords=OFF in your TTS50, you must enter that password in all upper case characters.

  • If your password was created with [Misc]CaseSensitivePasswords=ON in your TTS50, you can enter that password as you originally recorded it (case sensitive).

Requirements

Before you begin installing TMW Operations version 2021.2, check that these requirements are met:

  • TMWSuite®
    You must be using TMWSuite V. 2021.2.

  • TMW Back Office
    If you are using TMW Back Office, your version of TMW Operations must be the same as your version of TMW Back Office.

  • Microsoft® .NET Framework
    .NET Framework 4.6.2 or later (full package not client)

    The framework must be installed on the TMW Operations server, client, and administrator systems before you install TMW Operations. If it is not present, the system displays an advisory message during the installation. Install the framework before running the application.

  • Internet Information Services (IIS) for Microsoft Windows Server®
    IIS Microsoft Windows Server 2008 R2 or later

  • Microsoft SQL Server®

    • Microsoft SQL Server 2012 or later

      Note: SQL Server 2014, SQL Server 2016, SQL Server 2017, and SQL Server 2019 are certified for use with this application. 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 TMW Operations, and have administrator rights for that system.
    Like most applications, TMW Operations can be installed locally on a user’s system. It is also possible to install TMW Operations 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 TMW Operations 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.

  • TruETA Preplanning
    You must have these Trimble Web Products and modules installed:

Enhancements

Brokerage

Viewing the Load Information window in the Planning Worksheet (209914)

You can set up the system to show the Carrier Load Information for Order(s) window when you open the Planning Worksheet. To do so, you must have [Dispatch]AutoShowPopLoadInfo=Y in your TTS50. This setting now applies to TMW Operations.

Copying orders

Invalid BillTo warning added (NSUITE-210272)

You can set up the system to require that an order have a valid Bill To company. Sometimes a company flagged as a Bill To will have that flag removed. The system did not show a warning when you copied an order for a company that was no longer a valid BillTo . Now, the system shows a warning that the order’s Bill To company is not valid. Clicking Cancel in the message cancels copying the order.

Notes feature

Note security added (NSUITE-210605)

TMW Operations now uses the [Misc] EnableNoteSecurity INI setting. You use the setting to activate group-level notes security. This security limits the type of note a user assigned to a group can create, modify, or delete. You set up note security in the Note Group Maintenance window. The window is in the System Administration application. Go to Edit>Note Group Maintenance to open it.

Profit and Loss

Currency change/recompute charges message added (NSUITE-210682)

When you change an order’s Bill To company, the system updates the order header currency.
A new message warns you to re-compute the charges.
The message states, "Order header currency will be changed. Upon save LH currency will be changed to match the order header currency. Existing charges need to be re-computed."

Tractor profiles

Hiding the map on the Tracking tab (NSUITE-211190)

You can set up your system to show the Tracking tab in the Trailer Profile window. When you do, the tab shows Trimble Maps by default. If you are not using Trimble Maps, you can turn off the map. To do so, set [TWMapping] MappingInstalled=N in your TTS50.

Resolved issues

Advances/Misc Labor

  • TSI-674
    When issuing an Advance for a Comdata carrier card, the card number for the pay type Comdata Interactive Advance did not load. This happened on the Advance tab.

Asset Assignment

  • NSUITE-211162
    The trailer for BMT/DMT events on an order became unassigned when:

    • A tractor’s previous trip ends in an LUL event and you assign the tractor on a new trip that starts with an HPL event.

    • You have the setting [Dispatch] TrailerOption=Y in your TTS50.

Brokerage

  • NSUITE-211117
    Clicking Cover on the Brokerage board’s Available or Covered panes caused a GEH error.

Canceling orders

  • NSUITE-210835
    When attempting to cancel a trip, you got conflicting messages. This happened when you tried to cancel a split trip that had a completed empty segment.

  • NSUITE-210595
    When you canceled an order using the Split Trip option, the canceled order retained the original leg number. A new leg number was assigned to the new Split Empty segment. This was confusing to users because the trip was started using the original leg number but completed using a different number.

Card Planner

  • NSUITE-210897
    If you attempted to retrieve drivers on or after the date of 03-09-2021, they would not display. This was due to a Board Date parameter that was set within SQL.

Company Planner

  • NSUITE-211293
    When the parameters that are passed in exceeded the 1000 character length, the carrier_search stored procedure caused a GEH error. This happened when you clicked Cover on the Company Planner’s Covering board.

Company profiles

  • NSUITE-210586
    The system was incorrectly converting and saving Lat/Long values with multiple decimal places.

Consolidation Manager

  • NSUITE-210422
    Schedule/reschedule reason codes were not enabled when you consolidated orders. This happened if you changed the Earliest/Latest times. The system required a reason code only for the original order. It ignored the other orders.

  • NSUITE-211204
    In the Consolidation Manager window, when you changed times for a consolidated trip, it caused a GEH error. Closing the Trip Folder without saving changes also caused the error.

Copying orders

  • NSUITE-210236
    The Copy Order feature copied the rate mileage table, even when the Copy Rates checkbox was cleared.

  • NSUITE-210809
    When you have [Order] ShowCopyNoInvoice=Y in your TTS50, the Copy Order/Trip window includes the Do Not Invoice checkbox. It is selected by default. When you copy an order, the copy should show Do Not Invoice in the InvStatus field. If you copied a Multi-Order Job in the window, the system would ignore the selected checkbox. The copy would show Pending in the InvStatus field.

Custom layouts

  • NSUITE-211346
    The Accidents tab is available in these profile windows:

    • Carrier

    • Tractor

    • Trailer

    • Driver

    Using a custom layout for the tab could affect how long it took to load data in the window.
    Warning: This fix may affect your Accident tab custom layouts. You may need to use Quick Designer to recreate them.

eManifest

  • TSI-849, TSI-851
    For a multi-crossing ACE trip, all consignee companies appeared on the Company tab. This error happened if the origin and final stop were at the same location or in the same country.

  • TSI-854
    When you opened an order in ACE eManifest that had a province code of QC, an error would occur. QC is the province code for Quebec. This also happened in the ACI eManifest.

Hub Miles

  • NSUITE-211165
    Two issues existed for hub miles:

    • When you consolidated orders, hub miles from a previous tractor remained on the events after that tractor was removed from the trip.

    • When a tractor was removed from a consolidated trip, its hub miles were removed only from the first order. The remaining events retained hub miles that no longer applied.

      When a trip is completed, the hub miles update the tractor profile. Because the system did not correctly remove hub miles from consolidated orders, a tractor’s profile could show the hub miles for a different tractor.

Interface Settings

  • NSUITE-207066
    When you tried to create and save a new Company record in the Company Profile window, an error occurred. This happened in the DX Configuration window on the Trading Partners tab.

Load Requirements

  • NSUITE-210846
    You can record default load requirements for companies and commodities. When you assign assets to a trip with default requirements, the system verifies they meet the requirements. It was not showing a warning when the assigned assets did not meet the default requirements on the trip.

Manage Mileage Table

  • NSUITE-207797
    Clicking Insert in the Route Editor window caused a GEH error.

Order Entry and Trip Folder

  • NSUITE-204170
    The CancelReasonCode was not available to use for all orders. Now, when you cancel an order it is available. Click in the Cancel Reason field to select the appropriate code.

Performance Improvements

Carrier profile

  • NSUITE-211254
    Now, the Carrier Profile window’s Dot Scores tab does not try to retrieve data for the UNKNOWN carrier. This change:

    • Improves the speed at which the window opens

    • Reduces the memory used to open the window

Commodty profile

  • NSUITE-210971
    Improved performance speed and memory with changes to the Commodities Link To tab.
    Note: The update may affect any customization you made to the Commodities Link To tab using Quick Designer. If that happens, you must recreate the layout.

Company profile

  • NSUITE-210969
    Improved performance speed and memory with changes to the Pictures tab.

  • NSUITE-210970
    Improved performance speed and memory with changes to the Load Requirements tab.

  • NSUITE-210972
    Improved performance speed and memory with changes to the Operational Hours tab.

  • NSUITE-211179
    Companies are now retrieved more quickly in the Company Profile window.

  • NSUITE-211174
    If you use TMWImaging, performance was improved in the following areas:

    • Carrier Profile

    • Company Profile

    • Driver Profile

    • Trip Folder

Pay To profile

  • NSUITE-211390
    A memory leak was found related to the Vendor Maintenance button in the Pay To Profile window. This caused a delay in opening the profile windows.

Planning Worksheet

  • NSUITE-210511
    The trailer options did not populate as expected in the Inbound, Trailer and All tabs.
    This happened because these INI settings did not work as defined:

    • [Dispatch] TrailerOption

    • [Dispatch] PupTrailerOption

    • [Dispatch] DefaultPupTrailer

  • NSUITE-210770
    Freight Board Interface requires licenses specific to each load board you use. You could post to a load board without its required license. Now, a system load error message appears. It tells you that you are not licensed for a specific load board.

Profit and Loss tab

  • NSUITE-210839
    The total charges shown on the Summary tab were different from the charges shown on the Profit and Loss tab. This happened when you were set up to rate orders on save.

  • NSUITE-211098
    When computing an order’s charges on the Profit and Loss tab, the system was not pulling mileage for certain types of trips. This happened when the stop locations were defined only by city. Mileages pulled correctly when stop locations were defined by company.

  • NSUITE-211185
    The system was not setting the Company ID or Stop Number on invoice details for Rate by Detail Invoices.

  • NSUITE-211197
    Selecting the Fix Rate checkbox caused an error.

Scrolls

  • NSUITE-202278
    In the Order Scroll window, the Shipper City and Consignee City fields were not being cleared. This happened when the fields were populated for a search and then you tried to do a second search.

Route Maintenance

  • NSUITE-210533
    You can unretire a route by changing its expiration date. When you did this, a system message appeared. It stated, "You have entered a route that already exists in the database. Routes must be unique across the branch, bill to, and start/end dates. Please enter a unique route." The only way to change the date was to update it in SQL.

Telemetry

  • NSUITE-211349
    TMW Operations V. 2020.4.157 and later would not open. This happened when you installed over an earlier version. The problem was caused by a change to Telemetry Logging.

Tractor profile

  • NSUITE-210929
    Entries made on the *Distribution Info     tab were not saved.

Trip Folder

  • NSUITE-202372
    You can open the Trip Folder from the Order Scroll window. If you had a custom menu layout in the Trip Folder, it was ignored. This did not happen when you accessed the Trip Folder from the Operations menu.

  • NSUITE-209933
    The system was incorrectly requiring a trailer on split trips. This happened when you:

    • Had [Split]TrailerRequiredToSplit=Y in your TTS50 file.

    • Used the Return Empty option while splitting a trip The system was ignoring the presence of the trailer.

  • NSUITE-210515
    Saving an order that had a NULL value for the event.ord_hdrnumber on a secondary event caused an error. This happened when update_move_processing was called.

  • NSUITE-210989
    The scroll bar on the Documents tab was not available when an order or leg was locked.

  • NSUITE-211110
    When you added a new stop to an order and entered the earliest time, it was reset to the current time. The reset happened when you tabbed out of the field.

  • NSUITE-211064
    A time conflict could occur on a DMT (Drop Empty Trailer) event. This happened when you:

    • Created a second trip segment on an order that has a HPL (Hook Preloaded Trailer) event.

    • Assigned a tractor in the Asset Assignment window.

    You can use the [Asset Assignment] AllowDeadHeadDateRipple=Y setting to resolve this time conflict. This is a new setting that you must add to your TTS50.

  • NSUITE-211065
    You can create a custom grid layout in the Profit and Loss tab and specify it as your default. The system ignored this. Instead, it always loaded the factory default.

  • NSUITE-211117
    The system reset the time you entered in the Earliest field on a new stop.

  • NSUITE-211181
    When you enter an order’s freight, you specify the amount and identify the unit used to quantify that amount. For example, you set the Quantity Unit to Gallons and enter the number of gallons. Your entries should populate the Volume field with the quantity and the Volume Unit field with Gallons. The system did not populate the correct quantity field or show the correct unit type.

Trip Planner

  • NSUITE-210509
    In the Edit Shift Information window, the trailer options did not populate as expected.
    This happened because these INI settings were not working as defined:

    • [Dispatch] TrailerOption

    • [Dispatch] PupTrailerOption

    • [Dispatch] DefaultPupTrailer

  • NSUITE-211241
    When you updated a tractor or trailer on a driver in the Edit Shift Information window and clicked Close, the tractor/trailers did not ripple through the planned legs for the driver. This happened when a driver had multiple trips.

TruETA

  • NSUITE-210145
    The Dispatch Advisor Recommendations grid shows all the recommendations sent through the algorithm. When you select the leg or tractor, it filters the grid to the selection. If you clicked Auto-Assign Selected, the expected tractor/leg assignment was not made.

WorkCycle/TruETA

  • NSUITE-210815
    Applying WorkCycle SQL updates caused multiple SQL errors. This happened if you were not using TruETA or had an older version of TMW Operations.