2020.1

This section contains the following for the latest version:

  • System requirements

  • Enhancements (new or updated features)

  • Resolved issues (application improvements)

We have updated our company name and logo to the Trimble brand.

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.

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

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

  • 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 2014, SQL Server 2016, and SQL Server 2017 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

Invoicing

Creating separate tracking records for the master bill and for each invoice (NSUITE-208026)

In previous versions, Trimble imaging was not picking up all master bills. This was occurring because the master bill and all invoices on that master bill were assigned the same tracking record.
Note: The system saves tracking records in the imaging-tracking table (pegasus_invoicelist).

Now for clients that are set up to receive both bills, TMW Back Office creates a separate tracking record for the master bill and for each invoice attached to the master bill.

Logic used to create tracking records:

  • When the Bill To company is set up to print only master bills
    The system creates an imaging tracking record for each invoice on the master bill. It uses the same control number and master bill number for each tracking record.

  • When the Bill To company is set up to print both bills
    The system does two things:

    • It still creates an imaging tracking record for each invoice on the master bill. It uses the same control number and master bill number for each tracking record.

    • It also creates a separate imaging tracking record for each invoice on the master bill. It uses a different control number for each, and it sets the master bill number to zero.
      Note: The control number represents the tracking number for the document printed.

Rating

Linking/unlinking multiple rates at one time (NSUITE-208010)

Often, an accessorial rate may be applicable for multiple primary rates. The Mass Rate Assignment feature allows you to perform a mass assignment of one or more accessorial rates to multiple primary rates in a single step. You can also use the feature to remove the links between multiple rates.

Resolved Issues

Final Settlements

  • NSUITE-207878
    An error was occurring when attempting to release and save an escrow withdrawal pay detail with an On Hold status.

General system setup

  • NSUITE-206906
    Output Maintenance was changed to enable the entry of a session identifier mask. This allows printed output to be used with session printers in hosted environments, such as Citrix.

  • NSUITE-208135
    The system was causing an error and not setting the invoice status to Printed when you printed invoices for a Bill To company that had the Use Email check box selected.

  • NSUITE-208144
    The system was timing out when creating a carrier pay schedule for clients having a large number of carrier records.

  • NSUITE-209512
    When a default printer was not set in Output Maintenance for an output type, the system would not use the computer’s default printer.

Invoicing

  • NSUITE-207950
    When you made changes to an invoice, the system was not updating the existing revenue allocation.

  • NSUITE-208127
    When printing an On Hold invoice that had outstanding paperwork from the Invoice on Hold queue, the system was allowing you to finalize the invoice and make it available for imaging.
    The system now shows a warning message to indicate that an On Hold invoice cannot be finalized to a Printed status.

  • NSUITE-208135
    The system was causing an error and not setting the invoice status to Printed when you printed invoices for a Bill To company that had the Use Email check box selected.

  • NSUITE-208182
    Previously, when computing rates automatically for rate-by-detail invoices, the system was computing taxes with a quantity of 0 (zero). This was not a problem for manual rates.

  • NSUITE-208196
    When you created a credit memo or credit memo and rebill for an invoice that already had one, the system did not warn you it existed. Now, the system prompts for confirmation before you can continue.

  • NSUITE-209532
    The delivery line in the Freight Details section was displaying trip miles in the Distance field instead of the billing miles. This was only a display problem and did not affect the actual rating.

Layouts - Window

  • NSUITE-208114
    Custom window layouts were lost after upgrading to a service pack build.

Microsoft® Dynamics GP integration

  • NSUITE-207825
    When transferring invoices or settlements to Dynamics GP using Windows authentication, the system was still prompting you for a username and password.

  • NSUITE-209636
    The Payroll export window was not retrieving any results.

Mileage

  • NSUITE-209505
    The system stamped the wrong mileage in the stp_ord_mileage_mtid table, which caused reporting errors.

Rating

  • NSUITE-207684
    The system was not computing a secondary rate when it was attached to an hourly-based primary rate.

  • NSUITE-207687
    When you created a new accessorial billing tariff, the system was not copying all the roll-into-line haul flags from the charge type to the new rate.

    Roll-into-line haul flags are copied when you:

    • Create a new tariff

    • Change the item code on an existing tariff

  • NSUITE-207821, NSUITE-209598
    In certain situations, the system was not counting payable stops correctly when set up to ignore duplicate stops for pay purposes.

    For example, this occurred when you rated a trip that had both a loaded stop and an empty stop at the same location.

  • NSUITE-208154
    The TPP Code field was incorrectly limited to a maximum of six characters. Now, the maximum is set to 50 characters.

  • NSUITE-208169
    When calculating pay based on seniority, the system was not applying the correct rate.

  • NSUITE-208241
    Previously in TMW Operations, when rating cross-docked orders based on destination locations, the system was not applying the correct rate.

  • NSUITE-208324
    When applying an Origin to Destination mileage-based rate, the system was using incorrect miles for a manual mileage bucket.