2022.2

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 of these release notes is available here.

Warnings

Engage.Bid, Token Vault warning

Engage.Bid is an online subscription product. It lets trucking companies process bids from shippers. The feature uses a Token Vault to store login information securely.

Starting in 2022.2, Engage.Bid began using a new Token Vault in the Trimble Transportation Cloud (TTC). The change made old values invalid. They have been deleted.

If you were using Engage.Bid in versions prior to 2022.2, you must enter new values to continue using it.

Version warning

When you upgrade TMW Back Office, you must also upgrade TMW Operations and TMWSuite to the same version.

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.

Having encrypted Social Security numbers could interfere with third-party applications accessing the data. This happens because the data is encrypted when transferred. The third-party application would not have the ability to decrypt it.

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 allows you to 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.

Invoice output configurations warning

Starting in version 2019.1, there is a new procedure for setting up and assigning invoice output configurations for print and EDI.

In previous versions, you set up output configurations in the EDI 210 field or in the Advanced EDI Output Settings window in the company’s File Maintenance profile.

Starting in V.2019.1, those two locations are no longer available. Now, you set up invoice output configurations in the Billing Output Configuration Folder. To access this window, go to Tools > Setup > Billing Output Configuration.

Now, you can assign companies to invoice output configurations from either of these locations:

  • The Billing Output Configuration Folder

  • The Distribution Method section on the Distribution Info tab in the company profile

The upgrade script is designed to automatically import all the invoice output configurations you previously set up. You should not need to do any additional setup for your existing configurations. However, as with any major upgrade, we recommend that you verify the results after running the upgrade script.

For information about setting up and using invoice output configurations, see the Configuring your invoice output topic.

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 Back Office version 2022.2, check that you meet these requirements:

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

  • TMW Operations
    If you are using TMW Operations, your version of TMW Back Office must be the same as your version of TMW Operations.

  • Microsoft® .NET Framework
    .NET Framework 4.6.2 or later (full package not client)

    The framework must be installed on the TMW Back Office server, client, and administrator systems before you install TMW Back Office. 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 2012, 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 Back Office, and have administrator rights for that system.
    Like most applications, TMW Back Office can be installed locally on a user’s system. It is also possible to install TMW Back Office 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 Back Office 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.

Enhancements

Settlements

Re-Open Transferred Pay (TTESUITE-202636)

When you transfer a pay header to your accounting system, the system assigns a status of Transferred to it.
Before, you could not reset the status of a pay header from Transferred back to Closed in Final Settlements.
The new Re-Open Transferred Pay command lets you change a pay header’s status from Transferred to Closed.
Then you can use the existing Re-Open command to open and edit the pay details.
After editing the pay data as needed, you must manually delete the original transferred pay in your accounting system. Then you can retransfer the edited pay.

Resolved issues

Board view setup

  • TTESUITE-155050
    Several fixes were made to the Board Setup feature:

    • Non-functional buttons were removed from the Board Definitions window.

    • In the Board Setup window, the Save and Open buttons were not working. Now they are functional.

  • TTESUITE-203157
    You could not copy or edit these types of views:

    • Trips Ready To Settle

    • Trips Settlement On Hold

    • Trips On Hold for Audit Queue

    The view options were missing in the View Name drop-down field located in the Create/Edit Board Definitions window.

Company order requirements

  • TTESUITE-160482
    You can specify that an appropriate reference number must be recorded on an order before saving. You set up this requirement in the Company Order Requirements window.

    As part of the requirement, you can add one or more validation masks. The mask specifies a required format for the reference number.

    The system was not comparing the order reference numbers to all the recorded validation masks.

Dedicated Billing Folder

  • TTESUITE-156811
    When you used the revenue allocation feature, the system incorrectly showed an Out of Balance error. When this happened, you could not save the record.

DX Configuration - Rating

  • TTESUITE-202100
    The linehaul charge was not added to an order when you:

    • Used the Rate by Detail billing method

    • Selected the FreightAsAccessorial checkbox when you set up the trading partner’s 204 requirements

    It is expected that the linehaul and accessorial charges be added to orders that use Rate by Detail.

Engage.Bid

  • TTESUITE-202510
    Engage.Bid is an online subscription product. It lets trucking companies process bids from shippers. The feature uses a Token Vault to store login information securely.
    The existing Token Vault was no longer operational. A new Token Vault was created in the Trimble Transportation Cloud (TTC).

    Warning: If you were already using Engage.Bid, you must enter new value values to keep using it. The change made old values invalid. They have been deleted.

Invoicing

  • TTESUITE-203064
    The system did not let you open a Cancelled Billable order in the Edit Invoice Folder.

  • TTESUITE-203344
    GL Reset rules provide you with more flexibility for tracking revenue and pay. You can set up a GL Reset rule based on the trc_type value recorded on the trip.
    The GL Reset rule pulled the trc_type value from the tractor profile. It should pull the trc_type value from the legheader record.

Microsoft® Dynamics GP integration

  • TTESUITE-156452
    The customer data you export to Dynamics GP must be correct. If there is a mismatch in what you send, you should see an error message. When you exported a company that contained a Salesperson ID or a Territory ID that did not exist in Dynamics GP, you did not see the error message.

Profiles

  • TTESUITE-154498
    If you tried to create a new profile using an existing ID, you saw a confusing message. This happened when you created new driver or trailer profiles. Now, the message identifies the problem.

Rating

  • TTESUITE-160623
    When saving a secondary rate in Tariff Maintenance, the system was attaching the secondary rate to itself. This did not cause any rating errors. However, it could cause confusion. Secondary rates should be attached only to primary rates.

  • TTESUITE-201079
    When the rating engine finds more than one rate that matches the trip, it opens the Duplicate Tariff Index Found window. From there, you can choose the rate you want to use.
    When you selected a CSC rate in that window, the system did not apply it.

  • TTESUITE-202998, TTESUITE-156790
    The rating engine ignored hazmat commodities on trips. It did not use hazmat miles to calculate the invoice or pay details.

  • TTEUITE-203318
    We integrated the CSC External Mapper and Rating API in the Rating Engine and NSuite to use TTC (Trimble Transportation Cloud) instead of Azure. The integration still calls the existing CSC rating feature.

Recurring adjustments

  • TTESUITE-160857
    The system was not always applying per diem pay details to the correct pay period.
    This happened only when a trip spanned two pay periods.
    Per diem pay should be calculated in the pay period in which the trip is released.

Settlements

  • TTESUITE-202869
    Sometimes, the rating engine was not pulling the correct rate for co-drivers. This happened only with table rates based on seniority. This did not affect the primary driver’s pay.

Token Vault

  • TTESUITE-203687
    The system was not syncing claims correctly. This could cause incorrect values in the Token Vault.

Tracking Paperwork

  • TTESUITE-156056
    Two issues were fixed in the Paperwork Asset Setup window:

    • When adding a new paperwork requirement to an asset, the system assigned a random ID number. Now, it increments the ID number it assigns.

    • The Save button was not being enabled. So you could not save changes you made to a paperwork requirement.

Trip Settlements

  • TTESUITE-202381
    Two General Info Table settings control whether orders must be invoiced before the trip can be opened in Settlements.

    • STLMUSTINV
      Determines whether an order must be invoiced before you can retrieve the trip in Settlements.

    • SPLITMUSTINV
      Lets you specify how the system should handle the settle-must-invoice requirement for split trips.

    In previous versions, the system was not respecting two options for the SPLITMUSTINV General Info Table setting:

    • N
      An invoice must exist before any trip segment having a billable drop stop can be retrieved in the Trip Settlements Folder.

    • L
      An invoice must exist before the last trip segment associated with the order can be retrieved in the Trip Settlements Folder.