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

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

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

Resolved Issues

Final Settlements

  • NSUITE-210769
    In certain circumstances, Final Settlements was creating pay headers incorrectly. This happened only when you added a pay detail and navigated away from the record before saving.

Invoicing

  • NSUITE-210504
    Saving a miscellaneous invoice with a reference number created two reference number records. The records were created in the referencenumber table with the same invoiceheader key.

  • NSUITE-210482
    The Print Preview function was marking an invoice as Printed even when an error prevented the print process.

Microsoft Dynamics GP

  • NSUITE-211344
    Deleting an EFT (Electronic Funds Transfer) entry was affecting multiple vendors. It should have affected only the vendor being edited. You edit EFT data on the Banking tab in the Vendor Maintenance window.

Paperwork Requirements

  • NSUITE-210963
    The system was not checking in Resource Requirements submitted by the Synergize Imaging interface. The Resource Requirement check box is located on the Paperwork tab.

Profiles

  • NSUITE-211200
    The Add and Remove buttons were missing from Operational Hours tab in the Company Profile.

Rating

  • NSUITE-210932
    Two issues were causing the system to calculate minimums incorrectly for roll into line haul rates.

    • The Custom Invoice flag was triggering the roll into line haul feature in the Invoice Folder. The Custom Invoice flag should affect only the printing of certain custom invoices. It should not affect the invoice record itself.

    • The feature was using the value in the Min quantity field to calculate total minimum charges. It should have been using the value in the Total LH min charge field.

  • NSUITE-210909
    The system was recording mileage on all commodity details on the stop. Mileage should be recorded only on the first commodity on a stop. This was causing inaccurate charges for mileage-based invoice details.

  • NSUITE-211106
    Continuous errors were occurring when you closed the Tariff Maintenance window.

Recurring Adjustments

  • NSUITE-211215, TTESUITE-160615
    The system was not calculating simple interest for escrow correctly. It was not including the initial account balance in the computation.

Scrolls

  • NSUITE-202278
    In the Order Scroll window, the Shipper City and Consignee City fields were not being cleared. This occurred when the fields were populated for a search and then you attempted a second search.

Trimble Places

  • NSUITE-211227
    The API Key check function in the Trimble Places Configuration window gave inconsistent results.
    When the API Key check function runs, it should indicate whether the API key is valid.

  • NSUITE-211229
    The Company Not Linked Scroll was not correctly anchored to the window.

Trip Settlements

  • NSUITE-210793
    The Period Cut Off date used for a pay period was different from the date used in the Trips Queue. Now, when the pay period is defined by Start Date, the system uses the Arrival date at the first stop. When the pay period is defined by End Date, the system uses the Departure date from the last stop.