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

A PDF version of these release notes is available.

Requirements

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

LTL background service

Improved metrics logging (TTESUITE-200984)

Freight Order Import performance used to be assessed by querying the freightorder and expedite_audit tables. Freight order data changes if you rerun the query. This makes the assessment inaccurate.

Instead, you can now activate new app.config settings. The settings move metrics data into tables that do not update with a new query. There are app.config settings for each service type:

  • Freight Order Import: logMetricsImport

  • Order Slotting (automatic manifesting of orders): logMetricsSlotting

  • Manifest Creation: logMetricsManifests

  • ETA updates of active manifests: logMetricsETA

If active, they let you log metrics data to dedicated tables for easier and more accurate analysis.

LTL to DirectRoute export includes distance file (TTESUITE-204032)

When a set of routes was prepared to be sent to DirectRoute, only the route, truck, and stops files were created. The distance file was not created. It shows the distance between every pair of stops on the road.

Now, you can choose to send a distance file to DirectRoute.

The new General Info Table setting LTLAppianDRExportDistFileDflt determines the default value in the Include Distance File field on the Export to Direct Route window.

exporttodirectroute

The LTLAppianDRExportExtensions setting now lets you distinguish distance files in the String4 field.

Resolved issues

  • TTESUITE-160421
    The mobile service now handles Driver Unload (DUL) and Driver Load (DLD) event codes the same way it does Live Unload (LUL) and Live Load (LLD) event codes.

  • TTESUITE-202400
    These changes have been made in the Copy Schedules window accessed from the Routes tab in the terminal profile:

    • You can no longer create a master schedule "on the fly."

    • You can no longer duplicate a master schedule.

  • TTESUITE-204317
    Error messages used to be hidden by mass manifest status change buttons. The messages now appear correctly.

  • TTESUITE-204380
    The Send Stop Info button is unavailable when a workload is sent to the unit. This ensures that the same workload is not sent to a unit more than once.

  • TTESUITE-202703
    Legs can be assigned to a carrier or a combined tractor/driver, but not to both. Before, LTL Operations did not let you assign a carrier if a tractor/driver was already assigned. Now, you can remove the assigned carrier or tractor/driver to change the assignment.

  • TTESUITE-204887
    Previously, using Complete Orders changed the order’s invoice status to Available regardless of where the invoice was in the life cycle. This caused double billing in some cases. Now, when using Complete Orders, the invoice status only changes if the original status is Pending.

  • TTESUITE-204946
    DirectRoute lets you set up these properties when mapping stops:

    • Symbol

    • Size

    • Color

    These properties go missing on schedules that were created, imported, or copied, edited, and exported in LTL Operations.

    The new LTLAppianMapStopDefaults General Info Table setting lets you set up these properties on schedule stops. The setting makes sure these properties show up in DirectRoute.

  • TTESUITE-204948
    Adding a new trip in the Deliveries window showed the Outside In domicile route twice. One choice was an incorrect one-leg manifest, while the other was the correct two-leg manifest. The issue has been resolved.

  • TTESUITE-204967
    Before, if there was a non-EDI order on a stop, no message was created for leftover valid EDI 214 orders on that stop. The error was fixed.

  • TTESUITE-204986
    For multi-leg manifests (such as intermodal), you can switch assets on later legs without error.

    When LTLAllowTripForceAssetSwitch=Y in the General Info Table, an error occurred when switching assets on an active multi-leg manifest. The logic of this setting did not apply when removing assets from the manifest. The logic now considers if the current leg is active, not if the current manifest is active.

    A new setting, LTLAllowTripAssetRemoval, considers assets removed from an active manifest. This setting lets you decide if an error shows when assets are removed. This setting is set to N by default. The logic of this setting considers if the current leg is active, not if the current manifest is active.

  • TTESUITE-205022
    The following changes were made:

    • Before, SMC3 and RateWare rating endpoints were hard-coded in the software. This meant that a new build was needed if any SMC3 changes were made.

    • Before, account credentials (user, password, and license key) were saved in a General Info Table setting as plain text.

    Now, SMC3 and account credentials must be set up in the Token Vault under the SMC3 Rating Service key.

  • TTESUITE-205061
    Two errors occurred after adding features to LTL appointments.

    • Non-multi-leg appointments showed a blank appointment time range instead of the default earliest or latest dates and times.

    • When creating new appointments, the new schedule ID was not recorded correctly. This caused reporting issues and errors when trying to set a manifest.

    Both issues have been resolved.

  • TTESUITE-205112
    Occasionally, when a freight order import failed, the expected error message was not saved to the database. The issue has been resolved.

  • TTESUITE-205132
    Your individual Windows registry now remembers if you select the Linked Term checkbox. The checkbox state is stored between windows and sessions.

  • TTESUITE-205180
    Previously, attempts to print certain invoices from the invoice queue failed with no message explaining the problem. This issue has been resolved.

  • TTESUITE-205202
    Previously, you could make a limited number of changes to two or more selected appointments using the Multiple Appointments tab. This tab has now been disabled by default. You can enable it using a new General Info Table setting, LTLShowMultipleApptsTab.

  • TTESUITE-205212
    If you need to correct an LTL invoice that was transferred to accounting, then you must create a credit invoice. The credit invoice is editable, so you can correct the mistakes of the original invoice. You must then rebill using the credit invoice. This process cancels out the original invoice. If you click Credit/Rebill to begin a correction, the fields are disabled until you are ready to rebill.

    Before, if an error occurred during the credit and rebill process, the process would abort. Now errors display.

    Mileage lookup was also changed to ignore overrides that are not found and to use available defaults.

  • TTESUITE-205216
    An error occurred when copying grouped routes or schedules resulted in two routes or schedules with the same route ID and schedule group but different batch numbers. If you deleted the duplicate, the remaining route or schedule had no stops. Now, stops appear as expected.

  • TTESUITE-205255
    Previously, an error occurred when inserting a diversion stop. The error affected multi-leg (for example, intermodal) manifests converted using the Pickup to Linehaul option. If all legs except the last one were completed when you added a stop to the last leg, the stop was inserted on the first leg. The error has been resolved.

  • TTESUITE-205272
    If you choose multiple appointments, you can now apply the same comment to all of the appointments at the same time. A new General Info Table setting, LTLAllowTripAssetRemoval, considers assets removed from an active manifest. This setting lets you decide if an error shows when assets are removed. This setting is set to N by default. The logic of this setting considers if the current leg is active, not if the current manifest is active.

  • TTESUITE-205368
    LTL Dispatch has an optional service that updates ETAs and ETDs on active manifest stops. Previously, if you used both LTL Dispatch and TMW Operations, the service would update stops inappropriately.

    Now, the service only updates stops on legs that are assigned to LTL and require an update due to LTL change.

  • TTESUITE-205390
    LTL Dispatch captures data about rail containers and their contents. The data is then sent to a service that creates a file outlining the EDI transaction type. If any of the data fields are NULL, the file was not created. Now, NULL fields are changed to UNK so the file is created.

  • TTESUITE-205399
    Previously, the Appian Response window map would not display if one or more unassigned stops were in the bottom grid.

    Now, both routes and unassigned stops display correctly. Also, the correct visual options (such as shape, color, label) are correctly applied to the unassigned stops.

  • TTESUITE-205472
    The leg start, dispatch time, and pre-trip time combined cannot fall within one minute of midnight. If you schedule a route during this time, Appian shows a No Travel Time 00:00 Depart error message. Previously, this message appeared only if the departure time was midnight exactly.

  • TTESUITE-205495
    Previously, there was an error when assigning a pickup order with at least one hub in its routing. The error affected multi-leg (for example, intermodal) manifests. If all legs except the last one were completed when you added a pickup to the last leg, you would either get an error or the pickup would be inserted in the wrong hub. The error has been resolved.

  • TTESUITE-205497
    Companies without a CompanyLTLInfo record caused errors in the Route Response window. You could not add those companies to a stop. Now, records are automatically created using existing data.