2020.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.

Warnings

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 2020.4, check that you meet these requirements:

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

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

General

The Trimble Privacy Policy link added (NSUITE-210391)

The Trimble Privacy link has been added to the TMW Back Office login window. When you click the link, the Privacy Policy page opens in a web browser.

Invoicing

Option added for the [Invoice]When INI setting (NSUITE-205988)

The [Invoice]When INI setting specifies the dispatch status at which an order becomes available for invoicing.

In 2020.4, a new option, MOVECMP (Movement completed) was added.
The MOVECMP option allows you to invoice an order after actualizing the last stop on the last trip segment of the movement associated with the order.

Changes made to this setting do not affect existing orders. The system looks at the option that was recorded when the order was created.

Resolved Issues

Database

  • NSUITE-209986
    Running the TMWSuite MasterUpgrade SQL script caused an error.

Invoicing

  • NSUITE-209723
    When using the Rate by Shipper functionality, the system was causing an error when you set an invoice to Ready to Print status.

  • NSUITE-210053
    An error was occurring when printing an invoice and marking it as Printed in the Edit Invoice Folder. This was happening when the Bill To company was set up with only an EDI Output Configuration.

Microsoft® Dynamics GP integration

  • NSUITE-207784
    Sometimes an error message stating that Debits and Credits do not match was shown during the AP Export process.

  • NSUITE-210181
    The AP Export window was erroneously applying payment terms (discounts) when transferring pay data to Dynamics GP. This was causing the terms to be applied twice.

No Touch Billing

  • NSUITE-209817
    The join condition on the order destination city was causing the view to return multiple rows for each order. This caused them to be processed multiple times by the service.

Rating

  • NSUITE-210063
    The system was incorrectly updating rate tables. This happened when you changed a value in an existing rate table.

  • NSUITE-210077
    When you used the Transform command to change rows to columns or columns to rows, the system did not correctly change the value in the Option Applies field. This happened when you used an incremental table rate.

Scroll records

  • NSUITE-206824
    When using the reference number restriction to retrieve records in the Invoice scroll, the system was not the records on the first retrieve. You had to click Retrieve twice.

  • NSUITE-209711
    The Scroll Invoices window was not allowing you to search by any reference number recorded on the order. It only searched for the first reference number.

Settlements

  • NSUITE-209657
    The system could not compute line haul and accessorial pay when a Closed trip had an existing pay detail.

  • NSUITE-210293
    When billing trailer storage for trips using a Return Empty split (DRL to HMT), an application error appeared.

Trip Folder

  • NSUITE-210410
    The system was not saving a custom tab added to a layout with QuickDesigner.