2023.1

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.1, 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

Progress Bar

Progress bar for creating manifests and copying orders (TTESUITE-160599)

There is now a bar that shows your progress when you create manifests from schedules. The bar also shows when you copy orders. There is also an Abort button on the progress bar. Clicking the button stops the process.

Tablet Display

Display multiple trips on tablet (TTESUITE-203011)

Drivers can now see more than one active manifest in the same shift. Only the current manifest can be manipulated.

Telemetry Data Collection

Telemetry data collection consent form (TTESUITE-205714)

You must explicitly permit telemetry data collection while the LTL Dispatch is running. This is due to a legal requirement. Now, you must either check or uncheck the option to enable Telemetry logging. The box is checked by default.

Resolved issues

  • TTESUITE-203733
    The new General Info Table setting LTLApplyRoutePickupCutoff changes an order’s service plan. The setting selects a different route for pickups that do not fall within the shipper’s time frame. The selected route is either later on the same day or any approved time the following day.

  • TTESUITE-204905
    If the dispatch date of an order is after the dispatch Day of Week, the Delivery Date incorrectly gets pushed back one week. The new General Info setting LTLFreightOrdImportDateOffset fixes this error.

  • TTESUITE-204911
    The Remove Stop button removed the incorrect stop from the Route Response dialog for routes that were split twice. The error was fixed.

  • TTESUITE-204937
    There was an error when importing routebooks that had domicile routes. The wrong RouteID was used on the return portion of the domicile route. Also, the previous and upcoming schedules were set incorrectly. The error was fixed.

  • TTESUITE-205484
    Before, you had to save Bill To code changes and also click ReRate. Now you only have to save the changes.

  • TTESUITE-205538
    The Routing Admin – Delete Event button removes the order entry. Now the button shows you a prompt asking to delete the Manifest Detail records too. Without deleting the records, the Orders tab still shows the removed order as assigned.

  • TTESUITE-205556
    In the LTL Pickups screen, moving out of the Reference Type field would clear the selected value. The error was fixed.

  • TTESUITE-205558
    If you clicked Pickup to Linehaul on a manifest that did not have assigned pickups, the system showed an error message. The message was removed.

  • TTESUITE-205565
    Before, filtering and loading the bill queue orders grid would cause a timeout error. The database schema was updated to correct the error.

  • TTESUITE-205590
    Changes made to the Direct Route Export files made them easier to work with in the Direct Route application.

  • TTESUITE-205629
    There is a feature that lets you change the appointment window for one or more stops (like in the Stops tab of the Deliveries screen). Instead of picking specific start and end times for each stop, you can move the appointment windows. You can move the windows either by a number of minutes or by the ETA and ETD times. But, adding this feature caused an error when trying to set a specific start and end time for stops. Now, you can move appointment windows and pick specific start and end times for each stop without issue.

  • TTESUITE-205638
    There was an error affecting some Hook Preloaded Trl (HPL) orders. Orders that have a manifest (customer) stop with a trailer to be hooked are listed as Begin Bobtail (BBT). If the stop on that order is removed, then the stop is changed to Begin Empty (BMT). This is because the trailer is not being hooked at the customer stop. Sometimes, multiple HPL orders are assigned to a stop. If an order is removed from a stop, then the trailer is incorrectly removed from the first HPL instead of the last HPL. The error was fixed.

  • TTESUITE-205643
    In the Crossdock screen, the Order # filter cell used to open a drop-down list. You could not type an order number directly into the cell. First, you had to click on the drop-down box to close it, then you could type the number into the cell. Now you can type order numbers directly into the cell.

  • TTESUITE-205738
    There was an error that caused some cloned routes to show incorrect dates. This affected routes with a terminal arrival time before midnight and a terminal departure time after midnight. Cloned routes used the arrival date day of week instead of the departure time. The error was fixed.

  • TTESUITE-205838
    Using the New button instead of the Import button to create a terminal sometimes caused an error. The error assigned routes, static load plans, and terminal zip codes in the database to the new terminal. The error was fixed.

  • TTESUITE-205883
    If a manifest’s assets (like a tractor, trailer, or driver) were empty, an error sometimes occurred. The error changed the location of similar assets to display incorrect values. Now you have to add assets before you can actualize stops.

  • TTESUITE-205918
    The default grid layout for tariff profiles and order entry were not appearing correctly. This was because layout values were not calculating properly. The error was fixed.

  • TTESUITE-205958
    Several tabs in the Terminal profiles are used as a drop-down list option for fields in other tabs. For example, the Routes tab is an option in the Route ID column of the Zip Code tab. Before, if you opened the screen, the drop-down lists showed assigned values as integer IDs instead of descriptions. To view descriptions, you had to click Open or close and reopen the profile. Now, the descriptions appear automatically.

  • TTESUITE-205989
    Recently, a change was made to the New Trip dialog for local trips. The value of route_id would be 0 if you created a new trip with the Create From Schedule option without the Add Scheduled Stops option. To work around this, you had to hide the route_id column and instead show the orig_route_id column. Now, the value of route_id will be 0 only if the General Info Table settings LTLAutoCreateRoutePicks and LTLAutoCreateRouteDrops are set to Y.

  • TTESUITE-206058
    Before, there was a change to the copy and edit functionality of the Master Schedules. The change inadvertently caused an error. The problem was fixed.

  • TTESUITE-206064
    The Status sub-grid on the Mobile Messages was reinstated.

  • TTESUITE-206072
    Routes can have delivery legs that start on a different day than the initial relay leg. There was an error that caused all the legs to start on the same day. The problem was fixed.

  • TTESUITE-206092
    Before, you could edit some fields in a canceled order. You had to refresh the order so the fields could not be edited. The error was fixed.

  • TTESUITE-206122
    The tooltip that appears when you hover over a map stop shows details about a stop, including order information. If a stop is unassigned (removed from a route) or does not have an order assigned, the order information is not needed. Before the change, order details would show a value of 0. Now, unassigned stops will not show order details with a 0 value. Stops with no orders assigned will show Schedule Info in place of Orders.