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

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 2020.4, check that these requirements are met:

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

  • 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

Privacy Policy Link

The Trimble Privacy Policy Link added to TruETA Agent (NSUITE-210578)

The Trimble Privacy link has been added to the TruETA Agent login window. When you click the link, the Privacy Policy page opens in a web browser.

Brokerage

Carrier Management Equipment fields added as Ad Hoc Carrier filter (NSUITE-209885)

You can access the Company Carrier Restrictions window from the Planning Worksheet or the Company Planner Brokerage Board. The window lets you set ad hoc filters based on a carrier’s profile:

  • Carrier’s Tractor Accessories

  • Carrier’s Trailer Accessories

  • Carrier’s Driver Accessories

  • Carrier’s Qualifications

  • Entries in the CarrierType1-4 fields

  • Carrier’s cargo and liability limits

  • Presence of the Certificate of Insurance, W9, and a contract on file

Now, ad hoc filtering includes information from the Carrier Management Equipment tab in the carrier profile window. The tab is available when you have a String1 value of Y in the CarrierMgmtSystem General Info Table setting.

Company Profile

Allowing ad hoc Contacts information to update Company Profiles (NSUITE-211067)

You record a company’s contacts in its profile. Contacts appear in windows throughout the system.

In Order Maintenance and the Trip Folder, you can edit contact information in the Stops grid. For example, you may need to change a phone number or email address for a specific order. When you did this, the system updated the contacts defined for the company.

Now, you can decide whether your changes recorded in the Stops grid update the contacts for the company. You use the AllowAdHocContactsPhoneEmail General Info Table setting to control this.

  • To prevent ad hoc entries from updating a company’s contacts, set the String1 field to Y. Ad hoc entries will apply only to the stop record.

  • To allow ad hoc entries to update a company’s contacts, set the String1 field to N. This is the default.

Linking Pay Tos in the Company Profile window (NSUITE-210574, NSUITE-210575)

The Company Profile window now includes the Third Party tab. You use the tab to link Third Party profiles to a Bill To company.

To view the tab, you must:

  • Have the ThirdPartyPay license applied to your database

  • Be viewing a Bill To company’s profile

Cross-dock freight transfer

Setting dates/times in the Cross-Dock at Company or City window (NSUITE-210113)

Before, when you cross-docked a trip, you could not set the Scheduled, Earliest, or Latest arrival dates/times for XDU and XDL events. Now, the Cross-Dock at Company or City window includes fields for you to set these times when you create cross-dock events.

Grid filtering

Showing all items when filtering a column (NSUITE-211058)

The grids in the application use a third-party’s controls for filtering. A recent update to those controls changed how enhanced filtering in a grid work.

  • Before, when you set a filter in one column, you could still see all the items in other columns when setting filters for them.

  • After the update, only items related to the filter set in the first column were available to use as filters in other columns.

This change affects:

  • The Planning Worksheet’s Available Trips and Available Resources grids

    Note: The EDI tab is not affected.

  • The Trip Planner’s Trips grid

  • The Appointment Scheduler’s Trips grid

To restore the original functionality, you can use the ShowAllItemsInEnhancedFilter General Info Table setting. Set the String1 value to Y. The default value is N.

HubTran

Specifying default pay detail status (TSI-734)

By default, pay details coming from Hubtran have a status of Pending. This status is not always correct. Some settlement processes require a different status. The HubTranIntegration General Info Table setting has been updated. You can enter a String3 field value to identify the default status assigned to imported pay details.

Shift-based dispatch

Expanded Trip Planner resource find feature (NSUITE-210206, NSUITE-210207, NSUITE-210208, NSUITE-210754)

Before, you could use the Find window to search for a resource in the Assignment Plan pane. Using the window was awkward. There was no direct on-screen access. You had to know where to access it from a shortcut menu. You had to make entries to tell the system how to look for the asset you wanted, not just provide the identifier. Now, you access an expanded Find search window using the Find button in the Trip Planner header. The system automatically applies all the possible search methods. You can search for multiple resources.

Note: The original Find window is still available.

TruETA

Custom Early/Late Time window added (NSUITE-210973)

When you submit a trip to TruETA, it takes an earliest/latest date for each stop to use in determining if the load will arrive on time. Before, the [MobileComm]ETAArrDepDeterminesLate INI setting identified the dates to send to TruETA for the stop window.

If you use a custom stored procedure to determine the expected arrival and departure times, the system ignored that setting.

If you use WorkCycle to process TruETA data, it always showed those trips as late because the correct dates were not sent.

Now, a new INI setting lets you specify that the system should use the dates determined by your stored procedure. To use this functionality, the TTS50 used by SystemsLink must include the [TruEta]UseCustomEarlyLateTimeWindow=Y setting.

Note: The default value for the setting is N.

Custom duration times for overnight rest stops added (NSUITE-211008)

In previous versions, you could use the StopType3 label to identify rest stops sent to TruETA that were not standard work stops.

Some LTL Operations customers used the label to identify hotel stops where drivers spend the night. The intent was to exclude the time for these stops from TruETA’s Hours of Service calculations for a trip. For these hotel rest stops, the Arrival/Departure dates are set to the same date and time. This means the duration of the Rest stop in TruETA appears to be 0 (zero).

LTL stores the actual duration for these hotel stops in a separate table called stopltlinfo. Now, an LTL-specific stored procedure tells TruETA to get the duration information on non-work stops from that table. This change applies only to non-work stops.

If you use WorkCycle to process TruETA, you can set up the system to use that stored procedure. To use this functionality, the TTS50 used by SystemsLink must include the [TruEta]UseCustomDurationCalculation=Y setting.

Note: The default value for the setting is N.

Resolved issues

Advanced Carrier Selection window

  • NSUITE-210768
    When assigning carriers to a lane, the commitment period should default to a Month.

  • NSUITE-211004
    The ACS window did not save fields you added using Quick Designer. You could add a field and save the layout. When you made an entry in the added field, it was not saved to the database.

Board setup

  • NSUITE-205977
    Clicking the Setup Defaults button caused an out of memory error.

Brokerage

  • NSUITE-97560
    An error could occur when you tried to cover a load on the Brokerage board’s Available pane. A string or binary data was truncated which terminated the stored procedure. This happened when you have the CarrierMgmtSystem General Info Table setting’s String1 field set to Y.

  • NSUITE-210214
    You can set up a carrier to use a specific carrier confirmation report in its profile. This overrides the default confirmation report. When you assign a carrier to a load, the ACS window shows the carrier confirmation. The ACS window was ignoring any carrier’s override and using the default confirmation for all carriers.

  • NSUITE-210274
    You use the Email Confirmation template to set up the emails sent to carriers when you assign them to a load. The template lets you enter parameters to identify information the email gives the carrier. For example, you may set up the template to give the order number in the subject line. The system was not including these parameters when it created the email.

  • NSUITE-210484
    The Pay To was not being set on pay details that were manually added in the ACS window.

Copy Orders

  • NSUITE-207647
    Copied orders retained the order source of the original order. The order source should be the application used to copy the order.

CRMRight

  • NSUITE-207366
    From the Bill To Profile window’s Orders tab you could not view orders that had these statuses:

    • Available

    • Started

    • Dispatched

EDI

  • NSUITE-201087
    The system was not always sending 214s when an IBMT-(BillableBeginEmpty) event was completed. The 214s were not sent when a company was flagged as both a shipper and a BillTo. This would happen if you set up EDI codes for notifications to be company-based instead of BillTo-based.

  • NSUITE-211056
    You could not dispatch orders with pending EDI updates using the Load Assignment command. You access the command from the Mobilecomm menu.

Job Orders

  • NSUITE-210802
    When you cancelled the second or later leg of a split Job order, the system also canceled the prior leg if it was:

    • Planned

    • Started

    • Completed

    Now, the prior leg keeps its status. The canceled leg is set to Available.

Order Maintenance

  • NSUITE-210650
    You can use the [Misc]ForceOrderStatusWhenCreditCheckFails setting to specify the non-dispatch status to apply to orders when the Bill To fails a credit check. The system was ignoring this setting. It let you set an order’s status to Available.

  • NSUITE-210829
    On the All Stops tab, you could not enter multiple reference numbers on a stop. The system displayed an object reference error.

  • NSUITE-210766
    You can set up order requirements that are specific to a Bill To company. If there were orders in the system for the Bill To before you added the requirements, the move manager caused an error when you created a new order. This happened because the load manager tried to apply the requirements to existing orders.

Planning Worksheet

  • PB-200527
    The Planning Worksheet was not showing order header reference numbers correctly. By default, it should show them in sequential order. Instead, it was showing them sorted alphabetically by reference number type.
    Note: You can override this default behavior using the ReferenceTypeRestriction General Info Table setting.

  • NSUITE-207381
    Using the Show Group By Box command from the right-click shortcut menu caused a GEH error.

  • NSUITE-210556
    When you tried to process a solution, Trimble Dispatch Advisor produced an error. The error happened if a tractor’s expiration did not include a city location.

Prior Commodity Cleaning

  • NSUITE-210287
    The Trailer Cleaning Needed window did not open when you used the Assign Driver/Equipment window to plan a trip. This happened only in the Planning Worksheet.

Profit and Loss tab

  • NSUITE-209954
    Primary pay was not including minimum charges in the revenue calculation. This was specific to Primary pay based on the Trip Settlement Revenue pay type.

  • NSUITE-210622
    A minimum charge pulled when it should not apply. This happened in a very specific situation when the system rounded a unit conversion for a revenue-based accessorial.

  • NSUITE-210908
    The Currency field in the Invoice Charges section’s invoice detail grid was not editable. This happened:

    • When you first opened the grid

    • If you reset the grid layout

Reference numbers

  • NSUITE-208214
    If you copied an order that had reference numbers, the system would copy them to the new order. It ignored whether you cleared the Copy Other Ref Numbers checkbox in the Copy Order/Trip window. Only the Ref Number field value was copied.

Trailer Beaming

  • NSUITE-210572
    When you have [Misc]TrlBeamingCheck=6 in your TTS50, the system should check the trailer’s company location when you change a trip’s status from Available to Planned, Dispatched, Started, or Completed. If the new trip doesn’t start at the same location where the last trip ended, you should not be able to save the status change. The system should require that you insert an empty leg at the start of the trip. You should see a message stating that the save was unsuccessful.

    Instead, the system was letting you save the change as long as the cities were the same. It was not checking at a company level.

Trip Folder

  • NSUITE-209726
    Two issues were occurring when you cancelled an order having a Completed BMT event:

    • The new BMT event did not set to Arrived/Completed.
      This affected orders cancelled using the Empty Move or Split Trip options.

    • The new BMT event did not preserve the dates for empty move from the original BMT.
      This affected orders cancelled using the Empty Move option.
      Note: These issues occurred only when you had [.NetOperations]RemoveNonOrderStopsFromCanceledOrder=Y set in your TTS50.

  • NSUITE-210233
    The Currency field appears in many TMW Operations windows. To ensure entries in the field are consistent, the field provides a drop-down list of options. Your company defines these options in the Currencies label. The Profit and Loss tab incorrectly presented the field as a text box. It accepted entries that may not have matched the defined options.

  • NSUITE-210820
    You assign containers to intermodal orders on the Intermodal tab. If you want, you can have the system create expirations for the containers automatically as you make the assignment. To do this, you select the tab’s Create Expiration checkbox. If you made a mistake or changed your mind about which container to assign, you could select a different one. The system created expirations for both containers. This caused the one that was unassigned to have an incorrect location. This happened because the expirations were created as soon as you tabbed out of the field.

TruETA

  • NSUITE-210761
    The TruETA WorkCycle process produced errors on some trips and did not process them through TruETA. This happened to trips with a valid Planned start location. The object holding the Planned start location information in the SystemsLink MiddleTier solution was not created when the code attempted to set the location values.

  • NSUITE-210588
    When building the TruETA request from WorkCycle, the calculation did not include a PlannedDuration value for the stops. The duration is the number of minutes between the arrival and departure times for a stop that is Open or Arrived. A planned duration value should not be sent for Completed stops.

  • NSUITE-210808
    The TruETA WorkCycle process was not processing certain trips. WorkCycle picks up the trips properly, but the TruETA process in SystemsLink received an error. It did not send the trip to TruETA. It did not properly log the error.

  • NSUITE-210844
    The Trip Folder was not retrieving valid orders or moves that had been processed by TruETA. Instead, it tried to open the TruETA tab using the URL of the processed order.
    The Pre-Plan Confirmation window was not opening as expected. To use the window you must have [Dispatch]IgnoreStatusCheckForLoadAssignment=Y in your TTS50.

    You must also have appropriate values for the TMLoadAssign2FormId General Info Table setting:

    • String1 value greater than 0 (zero) to show the menu option

    • String2 value that provides the name of the menu option

      The window should open when you:

      1. Open a planned order that has the leg started.

      2. Go to Mobile Comm > Pre Plan.

      3. Select the Pre Plan option defined by the settings.

    Instead, the EDI Order Status pop-up window would open. It would be blank.