🚀 Releases

5.11.1 - 11/20/24

Core

Enhanced Route ID Visibility for Improved Order Management

We’ve expanded Route ID visibility to now include the Order Details page. With this update, users can easily view the Route ID associated with each delivery or shipment directly from the Order Details, improving clarity and navigation. This enhancement helps users efficiently track and manage deliveries by providing a clear link between orders and their corresponding routes, ensuring better visibility and a smoother workflow.

Alternate Location Functionality on Manual Order Forms

We’ve added a new feature to improve the accuracy of delivery routing when addresses don’t geocode properly or when specific locations like loading/unloading areas need to be designated.

What's New?

Enhanced Order & Delivery Creation

Users with the necessary permissions can now:

• Input alternate location data when creating or editing orders/deliveries.
• Update draft deliveries with new alternate location details.
• Edit alternate locations for specific flows, including returns and consolidations. -

Seamless UI Updates

• Alternate location toggles let users switch between standard and alternate address input.
• Latitude/longitude fields and interactive map pins ensure precision.
• Saved alternate locations automatically populate and are editable in subsequent orders/deliveries.

Key Benefits

• Improved Accuracy: Eliminate routing issues caused by incomplete or non-geocoding addresses.
• Flexibility: Specify exact locations for pickups and drop-offs, even in complex delivery scenarios.
• Historical Data Retention: Completed deliveries retain their original address and location details for audit purposes.

This feature ensures drivers reach the intended destination every time, enhancing operational efficiency and delivery success rates.

Mobile

• Display Scheduled Dates in ORD for Deliveries Created with Service Levels Specifying "Pickup Dates & Times"
• Exclude unnecessary Android permissions

General Fixes and Improvements

• Display Older Deliveries in the LP Control Towers
• Add "Store Number" to "Pickup Info" on Delivery Details
• Update "Order Details" and "Delivery Details" to Display "Pickup Deadline"
• Display error message in form returned when scheduling a delivery
• Geo events alililying to driver canceled route deliveries
• Show What LSP is Set to Disliatch to in "Carrier" Column When a Delivery has a "Scheduled Dispatch"
• "Schedule Dispatch" button on "Order Details" page locks up for a few minutes before allowing input
• Mismatching between the Accessorials on the Add Filter and New Order Pickup/Drop Off accessorials lists
• Ability to name Markets
• View in Control Tower button is available for revoked delivery

Client-Specific Fixes and Improvements

• * Only
  • Leader/Follower OrderID Display (Delivery Details)
• *** Only
  • Client-specific permissions to allow dispatch at location level

5.10.2 - 10/23/24

Mobile

Mobile Fixes and Improvements

• Return Containers and All Nested Children for Deliveries with Containers in ms-mobile
• Visibility Bar Code Scanning "Picked Up" event not sending scan data
• Driver/LP Dispatcher unable to accept or assign delivery. The error message "Delivery is not available anymore" does not disappear from the driver screen and blocks the driver from action. This can be resolved if the driver reopens the app
• Item dimension is displayed as a metric when drivers use the imperial
• Date for delivery window is not displayed on the app
• Display Dates on All Deliveries

Integrations

Routed Events Fix for a Specific Provider

Bug fix to address missing route status events for a specific provider.

Origin Store Number for a Specific Client

Enhancement to add store number of the origin location to the Delivered event for client-specific deliveries to support an issue with event hub reporting for a specific client. Client-specific deliveries to support an issue with event hub reporting for a specific client.

General Fixes and Improvements

• Ability to mark Service Levels as active/inactive
• Active orders with future dispatchAt do not display
• Parent Organization list stops before a user can select all Organizations in Omnipoint

5.10.1 - 10/09/24

Mobile

Mobile Fixes and Improvements

• Driver/LP Dispatcher unable to accept or assign delivery.
• Item dimension is displayed as a metric when drivers use the imperial.

Integrations

Routing Contract Identifier for a Specific Provider

Add the capability to support routing contract pricing for a specific provider. This task also enabled a client-specific functionality for routing pricing.

Visibility Carrier Code Enhancement

Completed backend work to support the ability to add carrier codes to visibility carriers using the UI.

Item Level Attributes for a Specific Provider

Addition of item level attributes have been added to the integration for a specific provider instead of being stored in notes. The enhancement is flagged and will be implemented in coordination with the specific provider.

General Fixes and Improvements

• Fix Vehicle Recommendation for SUV / Mini Van
• Bug: Upload CSV should Create Predefined Container if it does not exist in DB
• Bug: Upload CSV is mixing/missing container items on orders
• Show quantities for Service Accessorial on LP Control Tower
• Updates to Notes on "Route Details" Page
• Keep Filter Selections When Refreshing on Control Tower
• Support additional barcode formats in organization settings
• Location filter duplicate issue when refreshing the page after removing the Location from the filter without "Apply"
• Selecting multiple pickup locations in the filter causes external routes not to load
• Accessorial Displaying in the Incorrect Order
• Add "Incorrect Accessorial" option to the Exceptions list
• Cancelling a scheduled delivery doesn't clear the scheduled information

Client-Specific Fixes and Improvements

• * Only
  • Filtering for client-specific locations displays UUID.

5.9.2 - 09/25/24

Core

Enhanced Route API Endpoint

• Full Route Payload for Updates: Customers will send the complete route payload for each PUT upsert.
• Automatic Route Adjustments: OneRail will detect differences in stop quantity and/or sequence within the payload and update the route accordingly.

Integrations

Barcode Functionality for a Specific Provider

Add the ability for a specific platform to receive barcode information from OneRail that will enable as spto generate barcodes to appear on the drivers mobile application.

Specific Provider's Vehicle Integration for a Specific Client's Deliveries

Enhancement to a specific provider to cleanly pass requested vehicle for a specific client's deliveries from Shipper Extra Data.

Intra-Day Windows for a Specific Client

OneRail has completed development of the intra-day functionality for a specific client which allows them to send OneRail customer appointment windows. This functionality is behind a flag until this client is ready to test this functionality in their environment.

Suggested Vehicle for a Specific Provider

Enhancement to pass OneRail suggested vehicle to a specific provider.

Driver on the Way Event for a Specific Client

Enhancement to the integration for a specific client to pass them a Pick Up ETA for deliveries. This will require testing with this client as there are updates required on their side before this can be operationalized. Flag will remain off until that is complete.

OrderId Remapping for a Specific Provider

Enhancement made to the integration for a specific provider to enhance their reporting capabilities. This enhancement updates the message sent to this provider and outgoing carrier events back to OneRail.

Specific Provider Creds for a Specific Client

Enable deliveries for a specific provider at a location for a client-specific account

OR Assist

Published OR Assist 2.0 (for OR Assist enabled accounts only)

OR Assist 2.0 has been published to all OneRail environments. This enhancement brings a new look and feel to OR Assist, streamlined functionality, and more usable walkthroughs that can be used in any scenario.

To access OR Assist, select Help in the top-right corner.

General Fixes and Enhancements

• Carrier search
• Current location lookup method prevents customer address update
• Saved locations are overwriting delivery data
• Change how visible vs hidden columns are saved
• Edit Service Levels for orders in "Draft" Status
• POD/Signature image download button does nothing
• Saved Views List not sorted
• Saved Views allow duplicate values
• SLA EP loads too much data for what FE needs to display
• Add New "Documents" Column to Table Views

Client-Specific Fixes and Enhancements

• **** Only
  • Update Manual Creation to Use client-specific SL's
• ****** Only
  • Update Manual Order Forms to Display Select Accessorial for a specific client.

5.8.2 - 09/11/24

Core

In-Store Barcode Scanning (Future Scope)

Introducing a new feature to enhance the driver pickup at store experience with support for barcodes. This feature addresses the scenario where driver can show the barcode to the store associate which helps the associate find the order on their systems to hand it over to the driver. This helps us save additional time and effort required at the store front to pull up orders and reduce overall time required for driver pickup.

Key Features:

1. Ability to generate different types of barcode and QR codes.
2. Ability to generate barcode using different parameters.
3. Displaying Barcodes and QR codes in ORD.
4. Delivery Details Lite webpage URL for Non-ORD LSPs.

Mobile

Migrating Create Account Form

The form that allows LSPs to self-onboard will now be part of the OneRail Driver website. This will allow for a better experience when signing up for ORD.

Grouping Users into Teams (MVP)

We are excited to introduce the ability for ORD LSP users to group individuals into Teams. This feature allows for better organization and management of personnel.

Key Features:

• Users can now create Teams consisting of multiple drivers and a dispatcher.
• The dispatcher will have the responsibility of managing all drivers within the Team.

This update enhances coordination and oversight, ensuring more efficient operations and improved workflow management for ORD LSP users.

Integrations

Barcode Functionality for Specific Providers

Add the ability for specific providers to receive a URL for deliveries requiring a barcode in notes.

Barcode Functionality for a Specific Provider

Add the ability for a specific provider to receive a string value for barcodes and allow a specific provider to generate a barcode. This functionality will not be available in Production on the provider side until late September due to the provider's code deployment schedule.

7 day Schedule Deliveries for a Specific Client

Provide the ability to schedule a delivery up to 7 days in advance and reschedule a delivery up to 8:00 PM local time the day before a delivery. The client is to provide functionality for the cutoff time for rescheduling.

Proof of PickUp Functionality for a Specific Provider

Added the ability to receive Proof of Pickup from a specific provider for deliveries. This is configurable by shipper.

Client-Specific Invoice Service Migration

OneRail has successfully tested with a specific client to ensure they can migrate from Mulesoft to Azure. OneRail will migrate our code and then coordinate the changeover with the client.

Routing for a Specific Provider

Integration with a specific provider has been upgraded to be able to send routes and receive events with the provider for Single Pick Up and mulitple Drop Off routes.

Specific Client Service Duplicate Events in Event Hub

Fix implemented to ensure only one instance of events are received by a client in their specific service's event hub.

Finished Event Enhancements for a Specific Client

Enhancement to add order item payload to the Finished event for a specific client.

POD Required Flag for a Specific Provider

A specific provider requested OneRail to pass a flag to them that formally requests POD for each delivery to increase the reliability of POD images that OneRail receives.

Accessorial for a Specific Provider

Provide the ability to send accessorial and quantities to a specific provider using notes. Share using notes.

Barcodes for a Specific Provider

Enhancement to the integration for a specific provider to be able to pass them a barcode value and barcode type which they will use to generate a barcode to be displayed on the drivers mobile application.

Accessorial for a Specific Provider

Provide the ability to send accessorials and quantities to a specific provider using notes.

⏱️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 AAP 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
• Ability to see the newly scanned delivery from the Control Tower on the Driver dashboard
• Duplicate scans bug
• Show Quantities for Service Accessorials
• Coc Visibility deliveries doe not display on LP Control Tower and driver screen after delivery is claimed.

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

Client-Specific Fixes and Improvements

• *** Only
  
  • Client-Specific Provider Fix - Street Lines Too Long
  • Dispatch and Revoke Logic when "Preferred LSPs" are configured
• **** Only
  • Christmas Tree SKU Update