2023.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 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 2023.4, 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 2012 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-206179 |
Manifest Editor |
Add ability to place security restrictions on Arrive and Depart datetime fields in the manifest editor stops tab based on the users Terminal permissions. |
TTESUITE-206180 |
LTL Dock Service |
The LTL Dock Rest Service has been enhanced with several new API methods that provide the following features.
The trailer temperature information collected is now visible in the Terminal Equipment Screen. |
TTESUITE-207210 |
LTL Background Service |
Added a new button to the LTL Setup - Background service screen that allows users to perform a test run of the LTL Background services manifest creation methods. This allows users to validate that a terminal’s routes have been setup correctly. |
Resolved issues
Case number | Feature affected | Release note |
---|---|---|
TTESUITE-206254 |
Invoicing |
To allow for more customizability, the DocumentNumber used in the export to Microsoft Dynamics GP is now controlled by a SQL stored procedure ltl_greatplains_ap_docno. |
TTESUITE-207019 |
LTL WCF |
Resolved an issue where Recall Manifest was not work during Driver swap on a multi leg manifest. |
TTESUITE-207020 |
LTL WCF |
The LTL WCF GenericGetEquipment method can now search for equipment based on the Misc1 value. |
TTESUITE-207190 |
Deliveries/Pickups/ |
The various asset columns in the Trip and Stops tabs in the Trip Manifest Control now use a Dropdown rather than manual text entry. |
TTESUITE-207359 |
LTL Background Service |
The LTL Background Service config screen, now allows the inclusion of child/rail terminals for a couple of the modules, includes an app.config file setting missed in the original design, and clarifies some confusion between a couple of the EDI modules. |
TTESUITE-207361 |
Crossdock Screen |
Fixed an issue were attempting to load a Linehaul manifest before all the manifest’s order were available, would correctly throw an error that prior events were still in progress, but could inadvertently complete those events. |
TTESUITE-207387 |
Manifest Editor |
A trailer/container seal number is now always required when tendering a reservation to a rail company (it was previously required on loaded containers, but not on empties). Background: This is a change in policy dictated by the (only) rail company used by the (only) LTL trucking company using the LTL intermodal functionality. In the future, should an LTL customer want the seal number to be optional on tendering empties, a GI setting would need to be added. |
TTESUITE-207428 |
LTL Background Service |
Resolved a very intermittent issue were manifesting an order would throw a primary key violation error. |