🚀 Releases

6.1.1 - 01/15/25

Mobile

• Client-specific visibility deliveries not displayed on the driver screen after driver claims a delivery

General Fixes and Improvements

• Resolve dispatch errors by ensuring accurate line item weight for deliveries
• Enhance fleet flexibility for multi-location market coverage
• Geo events applying to re-routed deliveries
• Multi-Pickup routing utilizing multiple vehicles

Client-Specific Fixes and Improvements

• *** Only
  • Add Liftgate Accessorials for a client-specific brand's ordersss
• ******* Only
  • Delivery Details enhancement
  • Ops API Location Endpoints
• ******** Only
  • Modify CREATE_DELIVERY Payload to Include Additional Fields

⏱️Coming Soon

Core

Foreign Currency

As part of Internationalization, we must implement Foreign Currency support to cater to new markets. It is essential that our platform is capable of handling multiple types of currency as per the region that it caters to. We are adding a configuration option for currency at both the organization and location levels so that the setting can be inherited by the associated locations and users, respectively.

New "Route Details" Page

We are enhancing our table views to include a "Route ID" column, which will now link to a newly created "Route Details" page. This page provides comprehensive insights similar to the "Order Details" and "Delivery Details" pages.

Key Features:

• Hyperlinked Route ID: Click on the Route ID in table views to navigate to the "Route Details" page.
• Enhanced Route Visibility: The "Route Details" page includes a granular break down of all route stops, mileage, ETA, etc.

This update offers increased visibility and control over route management, streamlining operations and improving user experience.

Update Manual Order Forms to Allow Any Service-Level to use Delivery Windows

We are introducing a new enhancement to both the manual order forms and our APIs to address a key issue related to delivery window accuracy. Currently, some logistics service providers (LSPs) would prefer to have deliveries dispatched to them a day in advance. While our system supports Delivery Windows, allowing users to schedule future pickups, we’ve found that the defined windows don't always align with the desired service level—such as meeting a 90-minute window for delivery.

To resolve this, we are implementing a "Pickup Window" feature that will automatically calculate the corresponding "Delivery Window" based on the selected service level.

Key Improvements:

• Pickup Window Definition: Users can now define a specific Pickup Window, and the system will automatically calculate the appropriate Dropoff Window.
• Service Level Alignment: This ensures that the dispatch windows meet the required service levels, such as a 90-minute window or any other defined timeframe.
• Operational Efficiency: By streamlining this process, OneRail can dispatch orders more efficiently to LSPs, improving overall operational effectiveness.

This enhancement helps ensure that service-level agreements are met consistently, providing more accurate scheduling and reducing the risk of misaligned delivery times.

Mobile

Mobile Fixes and Enhancements

• Not valid role error during login for client-specific builds
• Unable to cancel deliveries in a route
• Newly assigned delivery on the top left corner menu list button not displaying
• Changes in ORD Edit profile screen to include new service end point
• New backend service that allows a driver user to edit their own profile data
• Newly assigned delivery on the top left corner menu list button not displaying
• Client-specific ability to see the newly scanned delivery from the Control Tower on the Driver dashboard
• Duplicate scans bug
• Show Quantities for Service Accessorials

General Fixes and Improvements

• Enhancements to "Delivery Cost Info" Section
• Ensure Delivery Costs Appear Correctly on CX Notifications
• Update LP Transform to Get Currency Data from Currency API
• Update Brod CSV upload endpoints to Support Currency Type
• Leader/Follower OrderID and Record Display (list page)
• METRICS_DELIVERY_API converting imperial values to incorrect values when not requested.
• CX preview does not show POD image on delivered page
• Updates to Delivery Details Page
• Geo-Ping Not Updating PickupETA on Subsequent Triggers
• When I refresh the page, I can not see the green checkmark sign in front of the view
• Search on LP Control Tower does not load data as if empty when reset to empty text
• Generate URL for Delivery Details Lite webpage containing Barcodes
• Creating a simplified delivery details webpage for Non-ORD LSPs
• Upgrade to NodeJS 20 or newer
• Save RouteCost data to new data points
• New data column for Routes and the Geopath json
• Update Error Handling Message When User Already Exists
• New data column for Routes and the Geopath json
• Bug - Saved View does not retain selected pickup location
• Orders assigned to a specific LP using ‘Dispatch Immediately’ after location is closed ignores user selection
• Display Drivers current location on the Route Details Map
• Route CSV Pre-Check Validation
• Display LSP Assigned to a "Scheduled Dispatch" Delivery
• Show What LSP is Set to Dispatch to When Editing a "Scheduled Dispatch"
• Add "Container ID" Column to Table Views
• Scheduled Dispatch Enhancement to Account for Timezone
• Update Logic to Group Deliveries by Date Based on When the Delivery Needs to be Delivered
• Required front end fields should be required API fields
• Editing a delivery
• Fix windows payload for "Pickup window" feature
• Merge Carrier DeliveryDetail Component[s]
• Incomplete not considered a Final Status
• Multi-pickup routes are front-loaded
• Multi-Pickup Routing Utilizing Multiple Vehicles
• Enhance Fleet Flexibility for Multi-Location Market Coverage
• Shipper and LP cannot access external route details
• Update Cargo/Sprinter Van Dimensions
• Unify Route Paths & Icons Across Route Maps
• Route Details - Estimated Time Completed
• Ability to search on the "Organizations" page
• Do Not Combine Non-Consecutive Pickup Stops
• PUT request to routes endpoint are failing for new route with existing orders
• Notes field character limit causes rejection without reason
• durationMin calculating on Delivered event received time
• Client-specific item parameters being under 1lb fails to edit delivery

Client-Specific Fixes and Improvements

• * Only
  • Ability to configure CX by Service Level
  • Clubbing DOBO and non-DOBO deliveries
  • Visibility deliveries do not display on LP Control Tower
• ** Only
  • Add "Driver Name" Column to Table Views
  • Add "Distance" Column to Table Views
• *** Only
  
  • Client-Specific Provider Fix - Street Lines Too Long
• ***** Only
  • Delivery Details Enhancement