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 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 2022.3, 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, and SQL Server 2019 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

General

Update multiple appointments quickly (TTESUITE-204035)

Previously, if you needed to make changes to multiple appointments, you had to handle each appointment individually in the Appointment window.

Now, you can:

  • Select multiple records in the Deliveries windows, the Appointment queue, or a Stops tab

  • Click Appointment (or Make Appointment in the Appointment queue)

  • Make these changes:

    • Move schedule appointments for selected stops forward by a number of minutes that you specify

    • Adopt current projected times as determined by TruETA

For each change, you must provide a reason code or other data needed to update the appointments for the selected stops.

Group a domicile route’s legs/manifests (TTESUITE-204118)

A new Trip Manifest column has been added to the grids on the Pickups and Deliveries windows. It lets you locate all the manifests and/or legs that belong on the same domicile route.

Appian

New WindowUsed column (TTESUITE-200706)

In the Stops section of the Appian grid, the read-only WindowUsed column contains a number representing the pattern window in use.

Enter trailer capacities on Schedules window (TTESUITE-203680)

You can now enter trailer capacity values (such as gross weight, height, length, width, and pallets) required for Appian/DirectRoute on the Schedules window in the Manifest grid.

Previously, you would need to create a "dummy" trailer profile with the capacities and then enter that trailer in the grid. These profiles were confused with actual profiles when assigning trailers on trips.

EDI

New fields available for EDI 404 transaction documents (TTESUITE-203266)

The following fields are now available for inclusion in EDI 404 (Rail Tender) transaction documents:

  • Trailer owner (defined in the trailer profile)

  • Manifest seal number

  • STCC number (per order)

  • Border broker address fields

  • Declared value (per order)

All new fields are in the staging table EDI_OUTBOUND204_REFS. You must modify the process that generates the EDI text file from data in the staging tables.

Generic Windows Communication Foundation (WCF) service

Rail reservation information available (TTESUITE-203008)

Previously, rail reservation information (T23) was only available in EnRoute comments. Now, it is available within the WCF service as properties in its own object.

Stop reason code descriptions available (TTESUITE-203010)

In addition to the stop reason code, the WCF service now provides the corresponding stop reason code description.

Trailer information available (TTESUITE-203012)

A new Trailer Profile API was added to the WCF service.

Resolved issues

General

  • TTESUITE-204218
    For grid columns that displayed integers as hypertext links, the filter drop-down sorted them as if they were strings.

  • TTESUITE-204497
    A dependency injection issue prevented the Invoice Queue from opening. This issue is now resolved.

  • TTESUITE-204535
    In the Stops tab of various windows, data masks added to the Actual Arrival and Actual Departure date-time fields prevented edits to the month. This issue is now resolved.

Appian

  • TTESUITE-203354
    In the Stops section of the Send To Appian window, you can indicate how long it takes to unload the freight at each stop by setting either of two numeric columns:

  • UnoadTime (flat time in minutes)

  • VolumeRate (rate in minutes per CUB volume)

    Normally, you set the value for each stop on the master schedule. The value is copied to the stops on the manifests created from the schedules. However, you may want to override the value for one or more stops on a manifest.

    In the Send To Appian window, it appeared that the override value was saved, but the manifest still had the value applied to the stop(s) in the master order. This issue is now resolved.

    • TTESUITE-203679
      When unsplitting a leg (by reverting a domicile route to a simple delivery route), the leg user field values on the remaining leg are from the delivery leg. Previously, the values were from the non-delivery leg.

    • TTESUITE-204395
      In the Appian Route Response screen, a ltl_dwell_header record is used to hold some of the Direct Route stop fields that are related to unloading time.

      Previously, if the dwell records did not already exist when a customer was added to a route, then these fields were not saved to the database.

      Now, if the dwell records are missing, a ltl_dwell_header record is automatically created and these fields are saved.

    • TTESUITE-204425
      Previously, when a master schedule with Use Absolute Start Time selected in the Terminal Schedules Leg grid was sent to Appian, the following problems occurred:

  • The pre-trip time was applied incorrectly.

  • The scheduled departure time was later than intended because the pre-trip time was applied to it.

    This issue is now resolved.

Database

  • TTESUITE-204120
    Database enhancements have improved performance for the SystemsLink LTL API.

  • TTESUITE-204457
    Occasionally, when an LTL order was created from a freight order, some of the details (such as pieces, weight, or volume) would be missing from the LTL order.

    Now, freight orders are no longer flagged by default as available for import into LTL Operations. The orders are available for import only after all of their information is saved to the database.

Domicile routes

  • TTESUITE-203507
    On the Route Response window, a new Swap button lets you swap the start and end locations of Domicile Routes that do not have a meet in the middle stop. You can use this feature for master schedules and manifests.

  • TTESUITE-203678
    The Terminal Profile > Routes > Copy Routes window now works correctly for domicile routes.

    • All schedules on the route are copied, even if they are not all selected.

    • Previous and Next links go to new schedules instead of to the original schedules.

  • TTESUITE-203955
    You can delete a schedule that is part of a domicile route using these methods:

    • Clicking Remove for a selected schedule in the Schedules tab

    • Selecting Delete on one or more rows in the Edit Route Schedule Dialog window

      Each time, a warning message appears indicating that the entire domicile route will be deleted.

      Now, a message appears describing how you can convert the domicile route(s) to simple (non-domicile) delivery route(s).

      Also, when using Edit Schedules, you can now review individual schedule rows and decide which to delete.

  • TTESUITE-204511
    Previously if you selected a Mass Status Change option for multiple rows comprising a domicile route, the feature would execute once per row.

Now, the feature executes once per unique manifest number.

Generic WCF service

TTESUITE-203155

Previously, an error occurred occasionally when check calls were processed for a driver whose profile had not been configured in LTL Dispatch. Changes to the WCF check calls functions resolved this issue.

LTL background service

  • TTESUITE-204300
    To improve performance, the LTL background service no longer writes log messages for orders that could not be manifested.

  • TTESUITE-204321
    If the import service processes a FreightOrder update for an LTL order that is either canceled or completed, then the service correctly stamps the FreightOrder record with:

    • ImportStatus = ERR and

    • ImportError = "Cannot Update order …​ because it is …​"

    Since ImportStatus = ERR, the record is eligible for retry. However, the system retried repeatedly, wasting time and resources.

    Now, when the import service processes a FreightOrder update for an LTL order that is either canceled or completed, the service stamps the FreightOrder record with ImportStatus = NA (Not Applicable). The system no longer attempts to retry importing.

  • TTESUITE-204330
    When processing a freight order update record, a "Delivery date is less than the Pickup date" error occurred.

  • TTESUITE-204242
    Several performance optimizations have been made to the LTL background service and the Deliveries window.

  • TTESUITE-204366
    For companies using the LTL Dispatch background service to import orders and auto-slot them to delivery manifests, the delivery route is a key order field. It is calculated in FreightOrder Import based on the load series and used to automatically slot orders into the correct manifest. It may change after the order has been imported/created.

    The current delivery route now displays in the delivery row of Order Entry’s routing grid. Also, when the route changes, the original FreightOrder Import "calculated" route displays in the FreightOrder Import success line in Order Entry’s Audit tab.

  • TTESUITE-204394
    Previously, if an order was manually assigned to a manifest, the LTL Background service automatically slotted it to a different or incorrect manifest.

    Now, you can turn off automatic slotting of these orders by setting String3 of the LTLSlottingSpecialHandling General Info Table setting to Y.

  • TTESUITE-203706
    Previously, the LTLTripMnfstInclLegsGrpID General Info Table setting determined whether to perform these tasks:

  • Domicile route linkage calculations on the fly when the Trips grid on the Deliveries window is refreshed

  • Apply a unique color (per setup) to all rows that belong to the same domicile route

This setting is now obsolete. These changes have been made:

  • A Trip Manifest column has been added. It is populated only once when the manifest is created from a schedule.

  • A new General Info Table setting, LTLTripMnfstColorDomLegs, lets you configure how to identify rows that belong to the same domicile route.

Master schedules

TTESUITE-204396

When a manifest was created for a master schedule trip, the pre-trip time was added to the departure time incorrectly. In some cases, this caused the first delivery stop to display as arriving one week later than intended.

Mobile communication

  • TTESUITE-203946
    Now, messages are delivered to mobile units even if the driver has not logged in to the unit.

  • TTESUITE-204185
    Previously, if a manifest had more than one leg and an incorrect leg was golden-stated, a database error occurred when the driver logged into the unit. This issue is now resolved.

  • TTESUITE-204186
    For environments that did not use driver shifts, requests to the LTL Mobile API for active trips caused an error. This issue is now resolved.

  • TTESUITE-204201
    In a shiftless environment, drivers assigned two consecutive manifests were unable to load the second manifest into their unit without logging off and logging back in. This issue is now resolved.

Mobile Messages

TTESUITE-203834

The Mobile Messages window now displays messages sent in both shift-full and shiftless modes.