2021.4

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

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

Activity Audit

Activity Audit missing Tractor changes (TTESUITE-60041)

The Activity Audit feature tracks changes to orders or trips. Before, if you changed a tractor on an order that was part of a split trip, only changes to the first trip segment were tracked. This happened because the system tracked changes at the order header level. It did not track changes made to other trip segments. Now, the Activity Audit tracks changes to all trip segments on orders that are part of split trips. It creates records for changes to:

  • Tractor

  • Primary Trailer

  • Carrier

  • Start Date

  • End Date

  • Status

Company Planner

Retrieve button added (TTESUITE-200875)

Before, when you opened a Company Planner board that contained a BranchTree cell, the system would start retrieving data as you entered dates or selected branches. This meant that you had to wait additional time after making your entries and/or selections to see the data you wanted. Now, the Retrieve button has been added. The system no longer tries to retrieve data right away. You can make your selections to filter data, and then click Retrieve. Only data that matches your selections is shown.

Reference Number Requirements

Adding Reference number requirements for Shipper and Consignee (TTESUITE-201082)

The Company Order Requirements feature lets you specify criteria that must be met when a company is used on an order. When you save an order, the system checks to make sure it meets all requirements. If it doesn’t, a warning appears. One type of requirement you can set is reference numbers. In TMWSuite’s File Maintenance application, you can set up reference number requirements for Bill To, Shipper, and Consignee companies. TMW Operations was not recognizing these requirements for Shippers and Consignees. It only applied them for Bill To companies. Now, TMW Operations applies reference number requirements for all three company types.

Trimble Dispatch Advisor

Add ability to view URL link returned from TDA service (TTESUITE-200877)

A link to the results returned from the TDA service is now available. You can add a hyperlink to the Dispatch Advisor window header using QuickDesigner. When you click on the link it shows the TDA service results.
Note: The link to the solution exists only in memory. When you close the window or a new solution is generated, the link is updated. The URL to an earlier solution is not available.

TruETA

Keep Earliest/Latest values prior to completion on the stop (TTESUITE-160686)

When you have [MobileComm]ETAArrDepDeterminesLate=D in your TTS50, the system sends TruETA the stop’s Arrival/Departure dates and times as the Earliest/Latest values. When the stop was completed, the Earliest/Latest values would change. They no longer showed the estimated date and time from before the stop was completed. This meant you could not compare the actual stop time with the earliest and latest times. Now, once the stop is completed, the Arrival/Departure values are the values last sent to TruETA before the stop’s arrival and/or completion.

Resolved issues

3PL orders

  • TTESUITE-156833
    The system let you consolidate 3PL orders that had different Bill To companies. It should not allow this.

Application upgrade SQL

  • TTESUITE-201244
    When you upgraded to the latest version of TMW Operations and ran the upgrade scripts, errors displayed in the SQL display. This happened when running the TMWOperationsDBMods.sql and TMWCRMRightDBMods.sql scripts.

Asset Assignment

  • TTESUITE-201389
    The Asset Assignment window was not setting the correct deadhead trailer for a tractor. This happened when you had these INI settings in place:

    • [Dispatch]TrailerOptions=Yes

    • [DateTimeChecks]IgnorePlanned=No

Bill To Relations

  • TTESUITE-201428
    Stop Type Priority records effect how the rating engine counts the number of stops on a trip. Unknown to the user, the system was creating new Stop Type Priority records.

    This happened simply by opening a Bill To record in the Bill To Relations window. There was no indication in the user interface that this was happening.

Brokerage

  • TTESUITE-200376
    This fix addressed two Brokerage problems related to the Bid Award component of the Carrier Auction feature.

    1. When you entered a counter offer in the Add/Edit Offer window, it was not saved. Now, entries in the Counter Amount and Counter Date fields are saved correctly when the offer is saved. When you open an existing offer, you will see any changes that were made to these fields.

    2. The Carrier Load Information window’s Offers Data grid shows values in these fields as currency:

      • cb_reply_amount

      • cb_reply_counter_amount

      • Margin
        If you are using a custom grid layout for this window, you must reset it to have this take effect.

    Note: To use this functionality with TMW Operations, you must have these licenses applied:

    • Advanced Carrier Selection

    • BidAward (the Carrier Auction license)

    • Carrier Lane Maintenance

    • CarrierHub

Company Planner

  • TTESUITE-200657
    Recording reference numbers for a stop on the Brokerage board caused a GEH error. If you closed the message window and opened another order on the Brokerage board, you got another error message. It stated "Error in Company Planner setup." You had to close the application and re-open it.

Dedicated Ops

  • TTESUITE-200841
    Improved performance related to:

    • Billing Adjustments

    • Payroll generations

    • Billing generation

EDI

  • TTESUITE-70636
    When you manually added secondary charges to an order on the Profit and Loss tab, selecting the Fix All checkbox did not retain the charges. This happened when:

    • The order was imported as a 204 record using the Order Import Toolkit/ TMW Data Exchange add-on module.

    • You had the PostProcessMTWRating checkbox selected in the Interface Settings application.
      Note: The setting is found on the Global Setup tab.

    • You had [Order]RateOrderOnSave=E in your TTS50.

    • You processed an update 204 for the order.

    The updated 204 removed the secondary charge from the order.

  • TTESUITE-70745
    Orders imported through the Order Import Toolkit (DX) had the Show Shipper and Show Consignee fields set to UNKNOWN. This caused problems with client reports and scrolls.

  • TTESUITE-70656
    Longitude information from inbound 214s was not recorded correctly. This caused a problem with the check calls created by the inbound X6 (location report) records. We have changed how Longitude data is written to the CheckCall records. Now, it is correct on outbound X6 214 records.

Edit User Definable Fields

  • TTESUITE-200278
    If the ContractMgmt General Info Table setting had String1 set to Y to activate contract management filtering, custom labels did not work in the Edit User Definable Fields grid. You had to select the Global column checkbox in the Edit User Definable Fields grid for it to work properly. You had to add the column using Field Chooser. Now, the Global column is available in the grid by default.

eManifest

  • TTESUITE-70720
    In eManifest ACI freight, the SCN (shipment control number) contained the order number instead of the PAPS number. PAPS numbers are required for pre-arrival clearance by Customs.

Fuel Import

  • TTESUITE-70708
    When you process fuel purchases and advances, the system creates pay details associated with trips. You use the [FuelServ]IgnoreTrips INI setting to specify how the system verifies the validity of a transaction’s trip number. The system was ignoring the setting and not validating the imported data. This could allow bad data to be saved.

  • TTESUITE-70744
    When you processed interactive fuel card purchases from EFS, the system did not update these fields in the cdfuelbill table:

    • cfb_truckstopcode

    • cfb_truckstopname

    • cfb_truckstopcityname

    • cfb_truckstopstate

    • cfb_focusorselect

  • TTESUITE-153695
    When you process fuel purchases, the system checks the Currency field value in the Pay To’s profile. If the value is different from the currency of the purchase, it applies a currency conversion. It was not applying a needed conversion to Rebate amounts. Incorrect rebate amounts were processed.

  • TTESUITE-201362
    When you processed fuel card purchases, the system did not apply currency conversion correctly for all line items.

Label file

  • TTESUITE-156776
    In certain instances, the system let you delete System Code label options in the Edit User Definable Fields window. It should not let you do this.

Mileage lookup

  • TTESUITE-200125
    You can enter manual mileage in TMWSuite’s System Administration application. If you entered manual miles for a Company and tried to look them up in TMW Operations, there was no match. You got a system message. It stated, “The data entered returned no matches”.

  • TTESUITE-201219
    Manual mileage lookups set in TMWSuite were not recognized in TMW Operations. This happened when the origin and destination was set to Company to Company.

Orders scroll

  • TTESUITE-200516
    Terminated assets were not available in the order scroll drop-down menu. This happened even though it was within the timeframe set in the [Misc] GracePeriod setting.
    Note: This was specific to Add in scrolls that are turned on using [TMWSuiteAddins] EnableScrolls=Y.

Profit and Loss tab

  • TTESUITE-201119
    When you re-computed invoice charges, the information in the Remark and ivd_comment fields was overwritten. This should not happen.

Route Generation

  • TTESUITE-200313
    If you used Route Generation to create an order with a route that used a Master Order, the Load Requirements did not display in the tab. The Load Requirements come from the Master Order that was created.

Stops grid

  • TTESUITE-160898
    If you used the ShowAsCompanyID column in the Stops grid, the ShowShipper and ShowConsignee fields did not update when stops were added or deleted. This happened in Order Maintenance and the Trip Folder.

Trip Folder

  • TTESUITE-200214
    If you created and saved a custom Stops grid layout, it would not load when you opened the Trip Folder.

  • TTESUITE-200553
    You could not actualize interim stops on orders. You could actualize the first arrival and the last departure.
    This happened if both these things were true:

    • The TrcRequiresDrvTrl field is set to Driver in the Tractor Profile.

    • You had both the IgnoreTrlStart and IgnoreTrlComplete set to No in the [Asset Assignment] section of your TTS50.

      Trying to actualize other stops caused an error. The message said that a trailer was required.

  • TTESUITE-60137
    If you had the setting [TMWSuiteAddins] EnableInterface=N in your TTS50, a system error occurred when you opened the Trip Folder. This also happened with the Planning Worksheet.

Trip Planner

  • TTESUITE-159622
    When you create multi-order jobs, you can set the earliest/latest date on the trip in the future. When you assigned a trip based on a multi-order job to a driver in the Trip Planner, the system changed the earliest/latest date to today. This did not happen with trips that were not based on a multi-order job.