2024.7

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.

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.

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

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

  • 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 2014 or later

      Note: SQL Server 2016, SQL Server 2017, SQL Server 2019, and SQL Server 2022 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.

  • PC*Miler®
    Certified with PC*Miler v.38

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

Enhancements

TMW Data Exchange

DX Configuration to authenticate credentials of the From address (TTESUITE-208747)

Port, username, password are now added to email configuration within DX.

TruETA

Update the TruETA interface from TMW to send the remaining time before a reset to TruETA (TTESUITE-211310)

Added logic to pass the remaining Driver Rule time to TruETA. TruETA now can calculate Rule Reset stops. The value in TMW is calculated and updated by MobileComm.

Resolved issues

EDI

  • TTESUITE-210941

Allow the EDI import process to preserve stop events from the Master order when importing Orders are matched to a Master.

Planning Worksheet

  • TTESUITE-210247

Fixed an issue where the default grid layout set for an Inbound Scroll View board in Board Setup wasn’t applying in the Planning Worksheet. If set, the layout is now loaded when you switch the Resources board dropdown at the top of the Planning Worksheet and overrides a locally set default layout for the Inbound grid (if set) in the lower (tabbed) section.

Trip Folder

  • TTESUITE-209859

The ord_maxtemp and ord_mintemp fields are no longer being updated from the ord_hitemp and ord_lowtemp fields when the order is Cross Docked (or Undo Cross Dock) in the Trip Folder.

  • TTESUITE-210313

Fixed a loophole that allowed add/delete in the Trip Folder’s Profit and Loss tab for a locked trip for certain steps.

  • TTESUITE-210379

For consistency, made the NonBoardCarrierWithAssetsWarn TTS50 setting work in TMW Operations as it does in TMWSuite. For a trip with a non-board carrier and a trailer, if the setting = Prevent, it will throw a warning, not an error (i.e. allow save).

  • TTESUITE-210719

To prevent an error when arriving at a stop that requires a trailer (e.g. a HPL) and no trailer is assigned, you may set the INI setting [Asset Assignment] IgnoreTrlStart=ACTARV. The error-check will be delayed until you try to depart/complete the stop.

  • TTESUITE-210890

When copying a trip with a carrier, the invoice number on the copied carrier transaction is now left blank to avoid confusion (as the copied carrier invoice will be a new transaction with a different invoice number).

TruETA

  • TTESUITE-210405

Added SQL to update the links in the TruETA Company Planner board to point to the "new" TruETA map link for Trip ETA solutions. It will require the user to run the TruEtaBoard.sql file.

  • TTESUITE-211356

Modified the logic to send the Alternate HOS rule type from the Manpowerprofile for the driver, if one is defined. This works Only for US and Canada. TruETA does not allow the Primary and Alternate HOS rule to be for the same country. If the Primary HOS rule is for the US and the Alternate is not defined, it will default the Alternate rule to the default Canadian rule. If the Primary HOS rule is Canadian, and the Alternate is not defined, it will default the Alternate HOS rule to the default US rule.