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

  • TMWSuite®
    You must be using TMWSuite V. 2022.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 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

Load Requirements and Expirations validation

Add existing setting CheckExpirationsForCompletedTrips to TMW Operations (TTESUITE-201725)

In TMWSuite when you save an order, a system pop-up window may display to inform of priority expirations or load requirements that affect the order. In TMW Operations, a Save Warnings pop-up window displays. These system warnings show expirations and load requirements for all the order’s trip segments, even past completed legs. In TMWSuite if you wish to turn off the system pop-up window for completed trip segments, you use [Dispatch] CheckExpirationsForCompletedTrips=N in your TTS50. Now, the setting also applies to TMW Operations.

Mileage Inquiry window

PC Miler Web better error handling (TTESUITE-159768)

You use the Mileage Inquiry window to look up the mileage between two locations. In some cases when doing a lookup a “no results returned” message appeared. This may have been due to an expired ALKWebAPIKey in the TTS50 or an invalid key. Now, a Test button has been added to the window that does a mileage lookup between known points. This lookup will:

  • Return the values if the lookup works.

  • Display any message returned from PC Miler web during the lookup if it fails.

The window will also display a list of the settings being used for mileage as well as a red error indicator that displays if a message is returned from PC Miler web during the lookup.

Note: This applies only for Web Mileage lookups through ALK.

Trip Folder

Adding Extra Service Exception Additional Fields (TTESUITE-202793)

In the Service Exceptions window, you can report service exception details. The fields can be used to record important information. Four new Misc Field entries are available to use in the Service Exception window. These string fields are:

  • Misc1

  • Misc2

  • Misc3

  • Misc4

The fields are available through QuickDesigner and can be screen designed onto the window.

Resolved issues

ALK Maps

  • TTESUITE-202894
    When viewing a driver’s route on the ALK Map in the Trip Folder Check Calls tab in TMW Operations, the plot line did not display the check calls. This happened when using:

    • ALK Web version.

    • PC Miler version 29 and up.

    • [TmwSuiteAddins] EnableMapping=Y in the TTS50.

EDI

  • TTESUITE-70571
    Location Report 214s generated incorrectly with an order in a started status and no leg associated with it. This happened in some cases and an X6 was still sent out.

  • TTESUITE-201588
    When you used the OrdNotRefNum1 Interface Setting, the SID number was placed in the sequence of 1 instead of the Reference type. This happened when:

    • An order is copied from a Master order during the DX 204 import process.

    • Used the CreateOrderFromMaster Interface setting.

The setting is supposed to replace the SID reference number in the sequence of 1 with the first orderheader reference number passed on the 204.

Load Requirements

  • TTESUITE-203020
    In the Commodity Profile, if you had a Load Requirement set to “not have/not be”, the system instead applied it as “have/be”. This happened when the commodity with the requirement was added after or at the same time the trailer was added and saved. In the Trip Folder this caused:

    • Valid assignments prevented.

    • It allowed loads to be assigned with requirements not met.

Profit and Loss tab

  • TTESUITE-201854
    You were not able to edit a non-invoiced order in the Invoice Charges section. This happened:

    • When a consolidated order contained both an invoiced and non-invoiced order.

    • After you saved the order.

  • TTESUITE-203957
    When calculating Rate by Detail charges for a cross-docked order, the rating engine was not getting freight data from all of the moves. This could cause incorrect charges.

Route Maintenance

  • TTESUITE-204211
    When you searched for a route using the Route Code field, all results did not display in the drop-down list. Only the first 1000 rows showed and would not filter to the specific desired result. The General Info Table setting FixedRouteLookupRows is now available to set the number of rows you want the Route Code field drop-down list to contain.

Trip Folder

  • TTESUITE-203624
    When you tried to cancel an order in the Cancel Trip/Order window, the order remained available.
    This happened when:

    • The order was a split trip with a return empty.

    • You selected the Order Status of Cancelled and Trip Action of Cancel Stops in the Cancel Trip/Order window.

  • TTESUITE-204379
    The Permits option in the Edit menu has been removed. It was also removed from the EditMenu Categories of the Customize > Commands screen. This link was null and never implemented.

  • TTESUITE-202564
    When freight weight for an order came from data input through TotalMail, the total weight was being overwritten to a weight of 0. This happened when edits were made to the order header of the order and saved.

  • TTESUITE-204203
    When you added or edited a reference number for an order, an error occurred when you tried to save. This happened when:

    • The order was not invoiced.

    • The order had a consolidated trip that included an invoiced order.

The invoiced order was incorrectly being marked as modified.