2023.5

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

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

  • 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

Asset Assignment window

ReturnLegEvent not coded in .net operations (TTESUITE-207266)

The [Asset Assignment]ReturnLegEvent TTS50 setting is now supported in .Net Operations as in TMWSuite.

Carrier Profile

Increase child Carrier ID field character length to 10 digits (TTESUITE-205907)

Increased the child Carrier ID field length to allow for up to 10 characters for the Fuel Card Information in the Additional Info tab.

Planning Worksheet

Dispatch Multiple Trips at One Time (TTESUITE-202460)

Previously, you were only able to dispatch one trip at a time in the Planning Worksheet for TotalMail. Now, a String3 option has been added to the TMLoadAssignFormId General Info Table setting. When set to Y, it will allow processing for multiple selected rows in the Planning Worksheet, when selecting the menu option Mobile Comm > Load Assignment.

TruETA

Change the process in SystemsLink that calls the TruEta Modify API to "match" previously sent trips (TTESUITE-206654, TTESUITE-207504)

Modified the SystemsLink TruETA interface logic. When a trip has already been sent to TruETA, the logic now checks to see if the stop has been sent to TruETA before (using the stp_number). If it has, AND the location of the stop is the same (i.e. the lat/long match or the State and City or Zip match) then the logic uses the UTC value assigned by TruETA to adjust the date/time for the location. Prior to the change, the TruETA interface did NOT adjust the timezone and simply sent the value stored in TMW - which required TruETA to geocode the stop every time it was re-sent.
Note: NEW stops added since the last TruETA update or existing stops that have had the location changed will NOT have the date/time geocoded so TruETA will have to run the geocode again based on the new location.
Changes made in TTESUITE-207504 simply updated the API contracts in TMW Operations to match the changes in SystemsLink.

Resolved issues

Company Profile

  • TTESUITE-206408
    Ops validation of Operational Hours for delivery stops will now display a warning when the arrival or departure is outside the Operational Hours set for the delivery company. Previously, TMW Operations would display a warning message about "restricted hours" when the arrival or departure time was within the company’s Operational Hours.

  • TTESUITE-207860
    The application will properly convert company latitude/longitude coordinates if necessary based on the [Internationalize]DefaultLatitude and [Internationalize]DefaultLongitude TTS50 settings.

Order Scroll

  • TTESUITE-205211
    Export To Excel fails intermittently when using Citrix Workspace. Retry logic added around the excel export. Exception will be caught with a message asking to retry (Y/N). Exception will be logged to telemetry as well.

Profit and Loss tab

  • TTESUITE-206944
    This fixes an error when a trip is saved in TMW Operations that is a Rate By Detail billto and the INI setting RateOrderOnSave is turned on. The next update to the trip was duplicating the primary drop charges for each commodity.

Trip Folder

  • TTESUITE-151590
    Fixed a bug that could result in stops being out of sequence on an Order when a stop’s Event Code is switched to a non-billable event and then back to a billable event.

  • TTESUITE-204456
    Fixed an issue where the Driver Note Type could be missing from the Note Types drop down list when a trip is split into multiple segments.

  • TTESUITE-207488
    Given scenario provided with TTS50, [Asset Assignment] IgnoreTrlStart is set to Y. This ignores the existence of a trailer to start trip and effectively ignores trailer validations while the trip is in started status. Setting to N would result in some validations failing given sample trip provided. The suggestion is to consider changing this setting.
    Even with setting IgnoreTrlStart=N though, there is a problem with HPL with UNKNOWN trailer once the trip is started. This is not raised as a validation issue and will be addressed with code change.
    Note that these sets of trailer validations occur upon save, not during editing. Also, note that trailer validations quit if there are already detected validation errors. So, multiple trailer validation issues will not be displayed. As each are corrected, any remaining validation issues will be raised on next save attempt.

  • TTESUITE-207521
    In previous versions of TMW Operations, changing a trailer on any stop of an empty trip containing a split would automatically change the trailer on all stops. Changes merged for this Jira prevent trailer changes on empty splits from rippling across splits.