- labelHash hotfix:
Fixes an issue for a specific client where deliveries could not be created when locations were only defined by their store number.
- NO_DATA hotfix:
Fixes an issue for a specific client where "NO_DATA" was not being mapped properly to the business name.
- Driver name hotfix:
Fixes issues where the name of the driver assigned by LP would not be updated if it had been modified past the point of the order being assigned.
2.4.2 – 04/25/23
New Table Filter Options
As we continue to enhance the table filters on the various tables, users can now filter by the following columns to further segment the data to their viewing needs:
- Pickup Location Address
- Pickup Location City
- Pickup Location State
Date Filter Enhancements
When the enhancement to the table filtering was done to add the ability to filter by various dates, the first implementation of this requires you to select the date value to filter then click into the date picker and click "Apply" to apply the changes to the table views.
Now when you select a date value from the pick list, the table-filtered results will automatically be applied when you select the date value instead of having to click into the date picker to apply the changes.
Locations and Customer Locations will have an Alt-Location option for use when the address does not geocode. This will allow the user to enter the latitude and longitude of the location so that the driver is directed to the actual drop-off/pick-up location.
Send Shipper costs for 856 EDI
Fix to report shipper cost on deliveries over two weeks old for a specific client.
Configure Accessorials for Bungii
Configure accessorials for Bungii for pick up and drop off locations.
EDI Architecture for Carriers
Complete implementation of staging environment for EDI carriers to begin EDI integrations.
Freight Class & NMFC Codes
Ability to pass freight class and NMFC codes from shipper to freight carriers (UI implementation still pending).
Fixes and Improvements
- Pickup and Dropoff SLAs for LP Markets Seem to be Ignored During LP Matching with Delivery
- File Validation Before Upload Validation Cleanup
2.4.1 – 04/12/23
Enhancements with UI Changes
* Deliveries with "Containers"
When deliveries have "Containers", this information was not displayed on the "Order Details" and the "Delivery Items" sections on the "Delivery Details" page. On the "Order Details" page, the items in an individual shipment/delivery displayed no information. Now when deliveries have a combination of "Containers" and "Items", this information will be displayed on both the "Order Details" and "Delivery Details" pages respectively. If a delivery has only "Containers", only the container level information will be displayed.
* New "Containers" Column
Related to the above enhancements to display "Containers", we've also added a new column to table views for these "Containers". This will display the total number of containers for each delivery in the following table views:
P44 $60 Lift Gate Charge for Client Specific Deliveries
All deliveries for specific client that are performed by Project 44 require a $60 lift gate charge to be added to their shipper cost.
Add Client Specific as a shipper account for Point Pickup
Point PickUp is now configured to support client-specific deliveries.
Configure Accessorials for Bluegrace
Incorporated supported accessorials for BlueGrace deliveries.
Client Specific Deliveries Dispatching over 75 Miles
Resolves the issue of ensuring that if a delivery is over 75 miles assign the delivery to the UPS bucket for the Get Rate decisioning process.
2.3.3 – 03/29/23
Today, when uploading a CSV file of "Products", any preexisting products within an organization will be overwritten when a new CSV file is uploaded. In the event a user is only adding a new product(s), they will quickly realize that all their product information has been deleted and replaced with the newly uploaded product(s).
The CSV uploading process has been updated to support bulk uploading both new products as well as updating existing products. The "Item Identifier" is now used as a unique key for the product and only one product can use that identifier.
As a part of updates made to the "Products" CSV data ingestion logic to support adding new and editing/updating existing products, there are several enhancements to the UI made to help complete the user experience.
Users can now add individual products manually through the UI without having to upload a CSV file using this new method.
Existing products can now be edited to account for pricing changes or dimension changes to keep up with the evolving markets and product changes all industries face. Existing orders and deliveries that have a product that has been modified will retain all their original product information such as the name, pricing, and dimensions.
Old or outdated products can also now be deleted from the UI manually. Existing orders and deliveries that have a product that has been deleted will retain their original product information such as name, pricing, and dimensions.
LP's Own Customers (Shippers)
LP users will now be able to onboard their own customers into the OneRail platform. These customer will be created as shipper-type organizations and will be "children orgs" of the LP organization.
LP's Own Deliveries
LP users with the appropriate permissions, will now be able to create deliveries for their own Shippers. These deliveries are generated through the LP Control Tower and use the same "create order" form that all users utilize today.
Delivery Details Page for LP Users
Users from LP organizations will now be able to see a limited version of the Delivery Details page. Shipper-specific data will be hidden on this page, as well as Timeline attempts to other LPs.
LPs will also be able to see on the timeline when a single delivery has been assigned to their organization multiple times (i.e., multiple attempts).
Add New Product from Order/Delivery Creation Form
When creating an order, customers can now create and define a new product that didn't exist in their products list prior to creation. After defining a new product through creating an order, delivery, editing, or copying workflows, users will now see the product appear in their "Products" list.
Order CSV Upload File Validation
When a user is uploading a CSV file of orders to create and route, the system will check that the file meets field requirements before creating the orders. If there are no errors, the upload will complete and create the orders. When errors are present, the upload will not complete, and a list of errors to correct will display.
Delivery Status Webhook Retry
Retry Logic added to client specific webhook for delivery statuses.
Adjust Client Cancel Code Logic
Adjusted Client Cancel Codes to read CD-012 for Revoked by OneRail.
Make Bungii a Dynamic LP
Update of code to make Bungii a dynamic LP.
Need to add address2 to EasyPost labels
Fix to ensure labels will contain fill address on an EasyPost label when Address 2 is utilized in CORE.
Webhooks for Client
Configured the event hub to meet Client LP status updates and POD.
Support Decimal Weight and Total Weight for Order Items
Update initially targeting a specific client to support decimal weights from the shipper for order items.
GoShare Cancellation Codes
Code to allow GoShare access to our standard cancel reason messaging shown in CORE.
Failed Delivery Create Email for Client
Email notification to be sent to client when an IMS order fails to create due to a bad address.
Fixes and Improvements
- Auto Revoke Failing Because of cancelParcelDelivery Flow
- Update GetRates to Display LP Cost Actual as Shipper Cost
- Update Get Rates to Return Final Mile Rates When Parcel Fails
- Create Deliveries with Scheduled Dispatch Via the API
- Create Scheduled Returns Via the API
- Update LP Cost to Apply to Shipper Cost When a Delivery Is Dispatched
- Ability to Manually Upload Multiple POP/PODs
- Editing a Delivery to Remove an Item Deletes the Wrong Item
When a batched delivery with two or more deliveries is revoked and re-dispatched along with another delivery for the same Customer/Location, only two deliveries are displayed as the "Order ID". Now when a pre-existing batched delivery is re-batched with new deliveries, the existing batched delivery becomes standalone delivery again and is then re-batched with the new deliveries.
New Table Filter Options
As we continue to enhance the table filters on the various tables, users can now filter by the ETA column to further segment the data to their viewing needs.
GeoFencing for Locations
Locations now have a 0.25-mile geofence to better track when a Driver arrives at a location, how long the driver is at the pickup location and the delivery location, and determine if a driver is in a Market. This includes the following "Location" types:
- When a driver's geolocation is within 0.25 miles of the geofence of the pickup location, the order's status will be changed from 'En Route to Pickup' to 'Arrived for Pickup'.
- When a driver is in the 'Arrived for Pickup' status and their geolocation moves outside of 0.25 miles from the pickup location, the order's status is changed to 'En route to delivery'.
- When a driver's geolocation is within 0.25 miles of the geofence of the dropoff location, the order's status will be changed from 'En Route to Delivery' to 'Arrived for Delivery'.
- When a driver is in the 'Arrived for Delivery' status and their geolocation moves outside of 0.25 miles from the dropoff location, the order's status is changed to 'Delivered'.
Tracking Number Hyperlink
Currently, we only display the tracking number itself on the "Order Details" and "Delivery Details" pages. As an enhancement, when a shipper has their own rate card with a courier or carrier, they will now be able to click on the "Tracking Number" to go to that courier or carrier's tracking page.
OmniPoint currently supports containers and items for orders/deliveries. Some customers, however, only have containers and/or containers with sub-containers. To provide better visibility into orders/deliveries that have both containers with sub-containers, there have been several additional enhancements to OmniPoint:
A new column called "Sub-Containers" has been added to the "Dashboard", "Deliveries", and "Orders" pages. The "Sub-Containers" column will display the total number of containers an order/delivery contains.
Display "Sub-Containers" on "Order Details"
When an order is created with containers and a "container type" of "Bundle", if there are sub-containers present, the "Order Details" will display the total number of sub-containers nested under the parent container accordingly with the cumulative amount of containers. The description of a sub-container will simply be just "Sub-Container".
Display "Sub-Containers" on "Delivery Details"
When a delivery is created with containers and a "container type" of "Bundle", if there are sub-containers present, the "Delivery Details" will display the total number of sub-containers nested under the parent container accordingly with the cumulative amount of containers. The description of a sub-container will simply be just "Sub-Container".
Display Count of "Sub-Containers" as "Delivery Items Total" (Client Specific)
For a specific client, we are going to display the "Total Items" under "Delivery Items Total" as the total quantity of the "Sub-Containers". The "Total Weight" and "Total Volume" will still be based upon the dimensions at the "Container" level. Since this request was directly from a specific client, all other customers that use containers will be based upon the total "Container" count.
Logistics Service Providers will now be able to create their own account and set-up their own Organization, Users, Customers, Markets and Fleet Assets. This workflow will be accessed via the soon-to-be-launched OneRail Driver website.
HD Supply's Transportation custom report:
AAP's Upgraded Dashboard with New Metrics:
- All SLA calculations are based on TTS (Time To Serve)
- TTS Breakdown
- TTF (Time to Fulfill)
- Driver Acceptance
- Drive Time PU/DO
- Abandon Rate
Trimble Maps Integration
Currently, the geocoders we use are limited to just Here and Google. With the addition of Trimble, we are starting to implement their services into this functionality. On both the Front and Back End, Trimble is being implemented as the first option, then going to Here, then going to Google if it fails to find the correct option.
Fixes and Improvements
- Drivers that Use SSO are Experiencing an "unauthorized" Screen When Losing Connectivity
- All Editing and Saving Deliveries with 0 Items
- Column Sorting Not Working Accurately
- Default Custom View Dates Are Note Updating Automatically
- Pickup and Dropoff SLAs for LP Markets Ignored During LP Matching Deliveries
- Exact Match On Item Search Criteria Not Listed First
- Blue Driver Dot Not Tracking
- * Message displayed when an already dispatched Transaction is submitted for dispatch by another CPP is not appropriate
- * Orders Dispatched to 3rd Party are not Getting "Delivery Completed" and Remain in "OneRail Processing"