2025.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 Transportation 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. |
Requirements
Before you begin installing LTL Operations Module version 2025.2, check that these requirements are met:
-
TMWSuite®
You must be using TMWSuite V.2018.18_01.0192 or later.
-
Microsoft® .NET Framework
Version 4.6.2 or later (full package not client)
The framework must be installed on the LTL Operations Module server, client, and administrator systems before you install LTL Operations Module. 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 2014 or later
Note: SQL Server 2014, SQL Server 2016, SQL Server 2017, SQL Server 2019, and SQL Server 2022 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 LTL Operations Module, and have administrator rights for that system.
Like most applications, LTL Operations Module can be installed locally on a user’s system. It is also possible to install LTL Operations Module 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 LTL Operations Module includes the manual application of an SQL script to the TMWSuite database. You must have a SQL Server administrator login and password to apply it.
Enhancements
Case number | Feature affected | Release note |
---|---|---|
TTESUITE-211864 |
LTL Dispatch |
In the Turnpike Doubles dialog, default the Merge and Split points when the manifests have the same start and/or end points. |
Resolved issues
Case number | Feature affected | Release note |
---|---|---|
TTESUITE-211842 |
LTL Dock service |
New GenericGetManifest() method introduced to the LTLDock service that returns order objects by manifest number. |
TTESUITE-211936 |
LTL Background Service |
The LTLDispatchBackgroundService will now flag FreightOrder Import records with setup issues that prevent an import attempt as a warning, not as an error, in the windows event viewer. |
TTESUITE-212029 |
LTL Dispatch |
Fixed a bug that prevented viewing truckload-based appointments in the LTL appointment queue when the existing General Info Table setting |
TTESUITE-212155 |
SQL Database |
Added two new fields, broker address and total pallets for LTL Rail Billing to the edi_outbound204_refs table. |
TTESUITE-212171 |
LTL Dispatch |
Fixed a bug where the custom ruleset was not being applied when changing an order’s appointment status in the Appointment dialog. |
TTESUITE-212204 |
Terminal Profile |
Fixed a bug where the batch frequency column was missing from the multi-row edit dialog in the terminal profile routes tab. |
TTESUITE-212205 |
LTL Dock Service |
Fixed a bug where the GetLegHeaders end point in the LTLDock service would not return equipment when the leg has a container as the primary trailer. |