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

A PDF version of these release notes is available.

Requirements

Before you begin installing LTL Operations Module version 2023.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 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

Application telemetry (TTESUITE-159824)

You can now track user activity, system performance, and alerts for some LTL Dispatch or LTL Dispatch Background Service events and processes. A user with administration rights can grant telemetry logging permissions by clicking the checkbox to enable telemetry logging in the Application Telemetry window.

It is not possible to monitor only some items or users. Either all items and users are monitored or none are.

That same user can add telemetry to the app.config file in the LTL Dispatch directory by setting its key and value.

Restarting the application saves the changes.

Resolved issues

  • TTESUITE-204672
    LTL Operations currently has 7 service "modules" (or types).

    Service module Description

    Freight Order Import

    A custom service to create docked delivery orders based on various staging tables (with names prefixed with FreightOrder and populated by a systems link service)

    Manifest Creation

    A quasi-custom service to create manifests based on LTL routes/schedules with scheduled stops (picks and/or drops)

    Slotting

    A quasi-custom service to auto-assign orders to manifests based on LTL routes/schedules

    ETA Update

    A standard service to recalculate the ETA and ETD of pending stops on partially completed manifests (based on the actual arrival or departure time of the last arrived stop on the manifest and possibly check call records indicating the truck’s progress to the next non-arrived stop)

    EDI 204 Multi Split

    A standard service to process outbound EDI204 records

    EDI 214 Inbound

    A standard service to process inbound EDI214 records

    EDI DxArchiveImport

    A standard service to archive or unlock pending edi records.

    LTL Operations currently has 2 service "hosts":

    • LTLDispatchBackgroundService

    • LTLEDIService

    Freight Order Import, Manifest Creation, Slotting, and ETA Update currently live in the LTLDispatchBackgroundService host.

    Previously, the three EDI services lived in the LTLEDIService host. They have been moved to the LTLDispatchBackgroundService host. The LTLEDIService host has been retired.

    Unlike in LTLEDIService, the EDI 214 Inbound module can now run multiple threads with a group of terminals for each thread. The terminal matching/filtering for 214s is based on the origin terminal (for an intermodal move/reservation).

    Like in LTLEDIService, the EDI 204 Multi Split and EDI DxArchiveImport modules in LTLDispatchBackgroundService each run in a single thread.

    In addition to sending detailed log data to the event viewer, all LTLDispatchBackgroundService modules provide additional log information as indicated below, assuming the correct app.config value is set:

    • Database updates are logged to the LTLService tables

    • Start service, stop service, and telemetry-targeted LTL methods and exceptions are logged to telemetry

  • TTESUITE-206065
    When the WCF service inserts mobile messages, the FreightLogic service should also receive a list of IDs corresponding to the newly-inserted messages.

  • TTESUITE-206093
    The new General Info Table setting MobComSingleManifestDisplay lets you control how manifests appear on mobile devices. To use this setting, the General Info Table setting LTLCheckSumShiftless must be set to N.

  • TTESUITE-206098
    Previously, the Appian Optimized reason code was available to users. It is a system code and is no longer available.

  • TTESUITE-206119
    A domicile route can have a delivery leg that starts on a different day than the initial relay leg. The pre trip time is calculated differently on domicile and non-domicile routes. This sometimes made the dates on routes sent to Appian incorrect.

    Also, some arrival and departure dates incorrectly showed as 01/01/1950.

    Both errors were fixed.

  • TTESUITE-206200
    Before, if you imported a file using a terminal profile, the symbol and color values would not carry over. This was due to case sensitivity. Now, you can import values with any case.

  • TTESUITE-206232
    Grids in these windows now load and refresh more quickly:

    • Appointment Queue window

    • Billing Queue window

    • Trip Manifest window (available in all Dispatch windows: Crossdock, Pickups, Deliveries, TruckLoad Moves)

  • TTESUITE-206233
    All default SQL server reports included with LTL Operations now have a "read uncommitted" transaction level. This minimizes performance issues.

  • TTESUITE-206245
    Before, advance carriers and beyond carriers were assigned to an order’s probill number instead of each pickup and delivery manifest leg. The probill numbers were then sent to Microsoft Dynamics GP. This meant the integration received the same probill number twice. However, the system did not allow the duplicate probill number to go to Microsoft Dynamics GP.

    Originally, a change was made to assign advance and beyond carriers to the carrier’s probill number to the Microsoft Dynamics GP document number instead of the order. However, this change meant it was not possible to track the carrier’s probill number in Microsoft Dynamics GP.

    Now, the advance and beyond carrier’s probill numbers are assigned to the order with a designation. Advance carrier probills now include the letter A after the probill number. Beyond carrier probills include the letter B.

  • TTESUITE-206253
    A calculation error affected routes with layovers. The drive times would appear as negative values. The error was fixed.

  • TTESUITE-206272
    You can set map properties on the Trimble Maps window. There was an error that kept you from changing the map point base from a shape to an icon. Now, you can switch back and forth between icons and shapes.

  • TTESUITE-206273
    In the past, if you:

    • Had a multi-leg manifest (that is, an intermodal manifest)

    • Had a manifest that had been converted using the Pickup To Linehaul option

    • Had all legs but the last one complete

    • Did a Deliver Enroute (so the manifest’s very last stop is changed from DXT to EMT)

    • Tried to insert a diversion stop on the last leg

    Then the system would also incorrectly change the event of the last completed stop (the last stop of the rail leg) from DLT to EMT.

    Now, the system will never set a completed stop to EMT.

  • TTESUITE-206274
    The last drayage leg of a rail manifest could change when the manifest was pushed to the driver. The Drop Loaded Trailer stop event could change to End Empty. The error was fixed.

  • TTESUITE-206308
    A new General Info Table setting, LTLMultiUserApptsImport, lets you choose whether users can see just the appointments they create or import or if they can see all appointments.

  • TTESUITE-206310
    TruETA estimates if a delivery will arrive before, at, or after the expected time. It then shows the delivery status based on the calculation. For example, a delivery arriving before the expected time has an early status. Once the delivery is complete, TruETA nows show the delivery status based on the actual arrival time.

  • TTESUITE-206338
    A new leg sequence field has been added to the Leg Header table. This field now determines the order of legs on multi-leg manifests. Previously, leg sequence was determined by the start time of the first stop on each leg.

  • TTESUITE-206349
    Previously, splitting a manifest into two legs prevented you from being able to assign a driver and dispatch the second leg. This error has been fixed.

  • TTESUITE-206403
    Previously, if:

    • Two different trailers with different stop events (such as DMT followed by HPL) were in the Stops grid on a manifest window

    • You actualized all the stops in a single session

    then a "Manifest Not Found" error displayed incorrectly when the second trailer departed the first stop. This error has been fixed.

  • TTESUITE-206404
    Previously, in a dispatch window’s Trips tab, if:

    • The grid sorted by leg start date

    • The driver in the Driver1 column was changed on a future dated leg

    • The future date was not kept (you clicked No on the confirmation prompt)

    then the driver could be assigned to the wrong row in the grid. This error has been fixed.

  • TTESUITE-206445
    Previously, you could access the Telemetry Setup window by going to Tools > Tools Maintenance > Telemetry Setup. This menu item has been removed. You can still access this window by going to Help > Application Telemetry.

  • TTESUITE-206495
    While accessing the New Trip window from the Deliveries window, if you manually cloned a domicile route starting at the domicile location, the -D1 suffix did not appear on the relay leg’s route description. This error has been fixed.