2024.3

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

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

  • 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.37

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

Enhancements

Event Code Maintenance window

Able to set specific default times for event types (TTESUITE-205198)

The Event Code Maintenance window allows for specifying a default dwell time at the event code level. The logic which calculates the duration of a stop (dwell time), now takes into consideration the default dwell time specified at the event code. If no default dwell time is populated, the system utilizes its default methods of calculating the time duration at the stop.

Fuel Import

Encrypt Fields within the CDSecuritycard Table for EFS (TTESUITE-209449)

TMW Fuel Import (.Net) and TMW Operations now support encryption of EFS codewords. For classic TMW Suite Products, only those screens made accessible via TMW Suite Addins will support this feature. At this time, EFS is the only vendor for which encryption of codewords is supported. Customers wishing to use this feature should first encrypt their codewords en masse using the Data Conversion Administration Utility.

Resolved issues

Activity Audit

  • TTESUITE-208209
    Prevent duplicate activity audit records from being created for check calls on update.

Company Planner

  • TTESUITE-208933
    Fixed a bug that caused the sub options not to copy in Company Planner Setup.

Driver Schedule

  • TTESUITE-209144
    Fixed an issue with the Max Trips field on the Driver Profile so that the value added is now honored and defaulted in the Edit Schedule By Terminal window, Trip Planner, Edit Shift Information screen, and Edit Driver Schedule window.

EDI

  • TTESUITE-209546
    Previously when the trading partner setting RetainMasterOrderStopType was introduced with TTESUITE-208776, an in memory swap of the stop event was made in order to retain the prior stop type such as from the original master order.
    However, on subsequent 204U(pdates), since the prior stop event is retrieved from the most recent processed dx_Archive_detail which was not swapped when initally logged, the comparison would no longer detect a change from current. This would cause later processing to fail in the event that the stop event is not mapped at all. This change patches the latest dx_archive_detail stop event dx_field003 to match the retained stop event type. Also, modified the log entry to record this activity from '(prior stop type retained)' to eg. STOP #1 PRIOR STOP EVENT RETAINED (KP→PU).
    These changes apply to the TMW Data Exchange module.

  • TTESUITE-208971
    Fixed an issue that prevented the LTSL2 Interface Settings application from opening. Initially, no data will be present unlike before the fix when the data would retrieve upon opening. Additionally, if the user clears the criteria in the grids, they will find that no rows will be present. Criteria must be entered in the fields.

Fuel Import

  • TTESUITE-70736
    Fixed an issue where the Fuel Interactive Import application encountered an error when attempting to download flat files from an sftp site.

Trip Folder

  • TTESUITE-207892
    In the Trip Folder on the Check Calls tab, the Map that is displayed when you click the Map button used to show stop information when the Flags were clicked. Now, clicking on the Map Flag will show Company information.

  • TTESUITE-208373
    This fixes a problem with a trip that has been split and the first leg is completed. If you cross-dock an LUL stop from the second open leg to it’s own cross-docked segment, you should be able to consolidate this new cross-docked segment to other moves.

  • TTESUITE-208734
    The Park and Hook and Earliest/Latest dates were not cascading. Now, when the TTS50 setting [Split]SyncEarliestLatestDatesAfterParkAndHook=Y, after a trip is split with a park and hook, the system will attempt to update the earliest and latest stop dates so that they occur chronologically. Options are Y or N. Default is N.

  • TTESUITE-209254
    An error occurred while navigating to certain movements in Trip Folder for orders with multiple sequential cross-docks. This error has been fixed.

Trip Planner

  • TTESUITE-209081
    When unplanning a billable empty order from a driver using the Trip Planner, the order will no longer be in a cancelled status after changes are saved.

  • TTESUITE-209203
    Fixed an issue where the Shift Pane on the Trip Planner window was not displaying Loaded Mileage correctly.