2022.3
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
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 Configuring your invoice output.
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.3, check that you meet these requirements:
-
TMWSuite®
You must be using TMWSuite V. 2022.3. -
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 laterNote: 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
Engage.Bid Import
No Touch Billing
Configuring wait times (TTESUITE-203649)
The No Touch Billing service runs three processes:
-
Orders ready to be invoiced
-
Invoices on hold
-
Invoices ready to print
The No Touch Settlements service runs one process for Trips ready to settle.
Sometimes the system determines a record is not ready to be processed. When that happens, it puts the item on hold for a specific amount of time. When that time passes, the system tries to process the record again.
Before, you set the wait time for each process. The wait time was the same for all items put on hold for that process. The reason an item was put on hold did not affect the wait time. Now, you can set wait times specific to the reason for putting the item on hold.
This enhancement added new settings in the app.config file. These settings replaced existing settings. |
Resolved issues
Board Setup
TTESUITE-202713
The Board Setup window was not saving changes made to Invoices On Hold For Audit boards. It discarded the changes when the Board Definition window was closed. Now, the changes are saved. Also, clicking the Clear button in the Board Definition window did not clear the Rev Type fields. Now, clicking Clear button clears the fields.
Microsoft® Dynamics GP integration
TTESUITE-202888
When transferring a Pay To to Dynamics GP, the Check Name field in Dynamics GP was blank. It did not matter whether the Company Name field in the Pay To profile was populated. This happened when using the Vendor Maintenance or the Vendor Export window to transfer.
Now, the Check Name field is populated correctly.
Invoicing
-
TTESUITE-203121
When creating a Miscellaneous invoice, the ivh_originpoint column was not populated. Now, the column is populated. -
TTESUITE-202957
The Paperwork tab was not showing asset-based paperwork recorded for both legs on a cross-docked order. -
TTESUITE-203945
Tariffs can be restricted by load requirements on the rated order. Previously, only requirements from a single move were considered. Now, all requirements from all moves for the order are considered.
Recurring Adjustments
TTESUITE-157251
Previously, when reopening a recurring adjustment that was on hold, the adjustment status was set to Drawn. This happened even when there was no transaction record present.
Now, when you reopen the adjustment, the status is set to Initial.
Trip Settlement Folder
TTESUITE-202437
-
The system offers the option to re-compute pay for any asset for which a pay detail is deleted. Previously, the message that appeared was unclear. Now, additional text has been added to make the meaning clearer.
-
Previously, if
[Settlement]SuppressMsgRemoveTripFromComputeQueue=ON
in the TTS50, the system always made the asset re-eligible for computing. This caused duplicate pay for the same trip.Now, the asset is no longer re-eligible for computing until all details are deleted from the asset on the trip.