2020.2

Appian integration modifies the arrival and departure times of a stop that already has a scheduled appointment. Now, it updates the appointment record and collects all historical information as if you manually open the Schedule window for that stop and modify the appointment time.

The AppianRouteResponse required additional fields be added to the Route Response window. You can now add these fields to the Route Response grid.

The Appointment scheduling feature was updated to correct the following issues:

You can now add the Company Alt ID field to various grids in the system. The field is a user-defined code assigned to a company. You select the field from the Field Chooser.

You can add the field to these grids:

In previous versions, when you created a manifest with scheduled drop stops from a schedule/route, the system only pulled stops whose DOW field matched the DOW of the manifest start. Now, the stops created match the DOW of the scheduled delivery dates and times.

Note: The DOW field is found in the company_hours_of_operation_sched table.

Drivers log into their devices to receive their initial dispatch (manifest with a list of stops). If the stops are modified after the initial dispatch, you can view a list of them in FleetConneX.

LTL Operations now supports TMW.Suite’s third-party accounts payable process. It allows Driver1, Driver2, and Helpers on LTL Manifests to be paid through the settlement application.

The customized ETA system can now calculate a driver’s Scheduled Early Arrival and Scheduled Late Arrival dates and times. The calculations are based on your company’s specific requirements. TruETA validates arrival and departure times to determine if a driver is on time for upcoming stops. This feature lets you customize ETA calculations to match real-time arrivals and departures.

Previously, you could use the API to remove a stop with no freight details from a route. Or, you could remove it manually from the Manifest’s Stops grid in the Deliveries window. Now, the LTLDispatchBackgroundService FreightOrder import service can process Freight Orders and updates and changes for other orders as well.

Previously, when you created a freight order and mapping data, the Freight Order Import service used two options to set a route and the stop sequence:

New calculation changes make these settings unnecessary. Now, the system calculates:

Additionally, the Freight Order Import service sets an order’s service level based on ReferenceNumber4 (ORDTYP).

Security concerns existed over having plain text usernames and passwords in .INI files. Now when you enter a username and password in an INI file, the LTL Dispatch Background Service encrypts them automatically upon its first run.

If you need to change a username or password and apply the encryption:

New functionality assigns a scheduled stop to a leg other than the last one. This occurs if the leg’s start (terminal) services the customer (based on zip AND route). Otherwise, scheduled stops (picks and drops) default to the last leg.

The system adds the On Hold message to the manifestheader and includes an Undo (release hold) and a mass (multi-select) change option.

When scheduling an unload stop on a new manifest from the Company Hours of Operation Overrides grid, the route_id now shows in the stopltlinfo table. The grid is located on the Terminal Companies window’s Hours tab. If a Customer CmpRevType3 is set to HOTEL, then stops created for that company will use the DIV (diversion) stop type instead of the Scheduled Unload stop type.

The system provides RestFul Endpoint functionality to allow external systems to update a manifest’s status. The LTLDockService.REST project in LTLMobile Solution was modified to support manifest status updates.

The Manual Slotting Scenarios now include these updates. The LghType 1-4 fields are also available.

The Mass Status Change functionality has been updated to provide additional status commands such as:

The system now shows a history of changes made to routes in the Hours of Operation Overrides – Details grid. The grid is located on the Terminal Companies window’s Hours tab.

With the proper permissions and setup, you can export required data from Import Route Book to create Master Routes in DirectRoute.

With the proper permissions and setup, you can use Import Route Book to import Master Routes from DirectRoute into LTL Operations.

The Company Alt ID field now shows in the upper grid of the Terminal Companies window. You can filter the list of items in the grid based on a company’s alternate ID. To filter the list, click the column heading and then enter the alternate ID in the Filter field.

The LTLAppian Route Response window now applies the setting (BranchOrgType1=Y) in the branch profile to change the UserfieldLabels to Original Arrive, and Original Depart.

New routing fields provide details on scheduled deliveries. Both fields are read only.

You can view the fields in these windows.

The LTLAppian Route Response window now applies the setting, (BranchOrgType1=Y/N) to determine:

The Appian Integration now allows for Re-sequencing and Optimization of stops between multiple existing manifests.

The Appian Integration now allows for Re-sequencing and Optimization of a single manifest. Additional empty manifests can also be added from the results window.

When DirectRoute Export Tool imported the daily route from DirectRoute, it created the initial appointment for each required appointment. It did this by duplicating the appointment time brought over from DirectRoute. This way Schedule / Reschedule was actively monitoring any manual changes to a stop appointment. If the initial appointment was not created automatically, you had to set the initial appointment for each stop. This caused unnecessary work. Now, each new manifest automatically sets the initial appointment for each delivery stop equal to the cloned schedule’s appointment time.

The new LTL Dispatch Background Service supports automatic manifesting of imported Freight Orders.

By design, the system does not automatically manifest imported Freight Orders that:

The Trips tab in the Trip Manifest Control was modified to use a stored procedure rather than inline SQL.

These fields are now available to add to various manifest grids. You select the fields from the Field Chooser.

Previously, you could set a dwell time for a fixed amount of time, for example 1 hour. Now you can set up a dwell calculation to specify a rate-per-hour for a particular unit of measure, for example 64 cases per hour. The units of measure include Count, Volume and, Weight.