Version 21.0

We think you’re going to love what we’ve been up to.

Visual Dispatch

Transform how you dispatch.


Our new Visual Dispatch Board is a modern and inclusive design that combines the familiar dispatch board grid with an interactive map – so you can visualize your drivers and orders in one place at the same time. Read more on Visual Dispatch here.

SMS Messaging

In the know, on the go!  Alert your customers where they’re already looking.


Send SMS messages to your clients to notify them of shipment status updates such as confirmed, picked up, and delivered. Continue to send email notifications, change to text notifications, or send both! Read more about setup and usage here.

Reports & Dashboards

Discover opportunities to elevate your service offering.

Expanded search capabilities and dashboard enhancements make analytics available and accessible to everyone. Copy and share dashboards, create multiple dashboards for various purposes, and use advanced finds to see the data you need to make critical decisions. Read more about Dashboards here.

Client Portal

Great things are happening in the Client Portal!

  • Guest User: You can now set up a guest internet user for one-time order placement (accepting credit card payment). Read more about Rapidship guest users here.
  • Location and Lookup Barcodes: Create orders faster than ever – automatically populate an address by scanning (or typing) an address or location barcode into the order form. Read more on entering an address using location and lookup barcodes here.
  • Live Driver Tracking: Implement Uber-like tracking for clients, enabling visibility of driver locations during delivery. Read more about driver location in Rapidship here.
  • Client Portal Customization: Create custom styles, adjust your logo, and theme your client portal with your company’s brand – from within X Dispatch. Read more on how to customize Rapidship in X Dispatch here.

Accounting Exports

Making it easy to integrate with Quickbooks.


In addition to available invoice exports, getting invoice information out of X Dispatch and into Quickbooks 2019+ and Quickbooks Online, you can now export settlement data into QuickBooks Desktop 2019+ also. Read more about the new export format here.

Assisted Dispatch (Beta)

The next generation of dispatching is here.


CXT Software has partnered with Wise Systems to bring you a powerful ai-driven dispatch and route optimization solution. Enable the tried-and-true Wise algorithms process your data to suggest the best driver for a job, provide ETA’s, and optimize shipments. Read more on assisted dispatch here.

X Dispatch 21.0.3 (April 2021)

  • Permission-based SMS Text Messaging configurable in Global Options’ Misc tab that will allow SMS messages to be sent out for various status events. ADDITIONAL RATES APPLY. Read more…
  • New fields added to the vehicle record and dispatch board driver pane, so dispatchers can view current “Dimensional Weight Totals” on their drivers and the “Maximum Dimensional Weight” allowed for their vehicle type. Read more…
  • Recurring order functionality that allows users to set up automatic order and/or driver pay re-rates upon posting, so users do not have to manually run a bulk order update every day and can have more of a granular control over which posted orders are auto-updated with current rates and surcharges. Read more…
  • Route optimization services for the new Assisted Dispatch functionality allow optimal drivers to be suggested to dispatchers for on demand orders based on a custom route optimization service configuration. Additional account set up is required for this service. Read more…
  • New permission-based order verification functionality created on the Order Type and Customer record forms that allow users to require verification before jobs are included in driver settlements.
  • Global Option in the X Route tab’s Misc container called “Display POD Name on Route Manifest” will display a new column with the proof of delivery text on route manifests. Read more…
  • New menu option called “Use print and custom invoice formats” was created within the customer record’s Accounting tab under the “Email Invoice Detail Format” field that allows users to be able to send out an invoice in two different formats at the same time. Read more…
  • New option within the Deductions tab of the human resource record called “Schedule” that allows users to dictate how often deductions are applied to their workers. Read more…
  • New field within the customer record Parcels tab called “Enforce parcel type list in X Dispatch” that when enabled will only display customer-allowed parcel types when placing orders in X Dispatch. Read more…
  • Ability to email shipping labels to 3rd party users directly from the order form. Read more…
  • Added a new tab on the route stop form called “Notes”  to create feature parity with on demand orders and renamed the original “Notes” field on the route and contract stop forms to “Driver Notes” to better represent the functionality of the field.. Read more…
  • Added ability to set the Route Load Stop, Customer Load Stop, or Return Stop option from the contract stop form, so users no longer have to navigate to the route planning page to control that setting. Read more…
  • Added the ability for users to select Reference 1 and Reference 2 options for Stamp Route Stops, Contract Stops, and Contracts within the Invoice Formats, so that data is available for display on customer invoices.
  • New functionality within the On-Demand and Route Dispatch board’s driver pane to display both on demand and routed work assigned to each driver. Read more…
  • Created a new Settlement Export option called “CXT – Quickbooks 2019+ Settlement Export (As Bill)” that allows settlement file exports for Quickbooks 2019+ Advanced programs.
  • Automatic email subscriptions for saved basic and advanced finds will now adhere to the “Show/Hide Columns” settings.
Next Dispatch
  • Visual Dispatch (BETA) is the first phase of our new dispatch board offering that allows users to view drivers and assign on demand orders from a map. Future phases will include more on demand functionality, routed work, and a grid view option. Read more…
  • Added a driver specific audit trail to Visual Dispatch (BETA).
  • Visual Dispatch (BETA) allows users to dispatch by dragging orders to a driver icon on the map, dragging a driver to an order on the map, and dragging orders to a driver within the driver pane.
  • Quick Filter functionality created for the new Visual Dispatch Board that allows users to have access to their most frequently used search displays.
  • New functionality that allows users to create multiple dashboards, share them with other users, and decide whether those users have the ability to make edits to the shared data. Read more…
  • The Dashboard’s pie chart, column chart, filter results, and filter count KPI widgets now allow Advanced Finds to be applied to the interactive charts.
  • New “On Time Status” and “Parcel Scan Status” columns will now be visible within the Find’s result sets, so users can display the information within their dashboard widgets and have a better way to visually display job status by exception.
  • Created a new version of the X Dispatch Monitor within the Dashboard that now gives users the option to monitor the current day’s on time performance for routed work along with the original on demand functionality.
  • Created the ability within the Find (BETA)’s Basic Find tab to add and save more than 4 rows of criteria. Users can now also exclude already invoiced records from their result set by unchecking the “Include Invoiced Records” checkbox.
  • Adds new logic to allow the “Show/ Hide Columns” settings on Basic and Advanced
  • Finds in Next Dispatch to be applied to the associated automatic email subscriptions.
  • Upgraded the Maintenance – Permissions section to the new web-based Next Dispatch functionality with a new help text display, permission-associated documentation links, and a search feature that easily filters permissions for a more efficient navigation of the page. Read more…
  • Upgraded the Maintenance – Images section to the new web version of X Dispatch. The original page is still currently available within the new “Legacy” section located in the left navigation menu. Read more…
  • Upgraded the Maintenance – Drivers section to the new web version of X Dispatch. The original page is still currently available within the new “Legacy” section located in the left navigation menu. Read more…
  • Upgraded the Maintenance – Message Formats section to the new version of X Dispatch with functionality to preview HTML on demand and routed email updates and new available fields Driver Name and Driver Photo. The original page is still currently available within the new “Legacy” section located in the left navigation menu. Read more…
  • The application will adhere to a user’s browser zoom settings and has new right-click menu zoom options within the Next Dispatch embedded browser. Read more…
Rapidship
  • New guest user link on the Rapidship login page and the ability for anonymous users to place orders online by credit card without having an account. Read more…
  • Users can enter in origin and destination location addresses by scanning a Lookup or Location Barcode on the Place Order page. Read more…
  • New permission-based option “Rapidship Customization” under Tools allows XD users to easily change and customize the logo, font, label names, and color themes for their Rapidship site(s). Read more…
  • Global, customer, and internet user option called “Display Driver Location” that, when enabled, will allow Rapidship users to see their assigned driver’s location on a map and follow their progress until arrival. Read more…
  • Created a new “Email” field within the internet user profile’s Options tab that allows carriers to add additional email addresses to default onto all internet orders. Read more…
  • New field within the internet users Rapidship container called “Default Order Type” allows carriers to set a default selection for their end users. Read more…
  • New setting within the internet users Options tab called “View Inet User Orders Only” that, when enabled, will only display orders in Rapidship that were placed by the logged in user. Read more…
  • New internet users tab, “Contract Stop Alerts”, for alerts to Rapidship users attempting to place an order that can be accomplished on their already scheduled route stops. Read more…
Nextstop
  • Added the Global Options Dispatch tab’s Received at Dock functionality into Nextstop 3, so it has feature parity with Nextstop 2.
  • Added permission-based “Forgot Password” link to Nextstop 3 login, so mobile users can initiate password recovery without contacting the carrier.
  • Added a new “Email Password Reset” link option on the driver record that will allow XD users to initiate a password rest for the associated Nextstop 3 user.
  • Added flight information related to dispatched orders in Nextstop 3.
X Stream
  • Upgraded the X Stream – Import Audit Log section to the new web version of X Dispatch. The original page is still currently available within the new Legacy section located in the left navigation menu. Read more…
  • Allows users to now select whether their Return stops are classified as a “Customer” or “Global” Return stop, so customers can now have more than one customer-specific Return stops on a route.
  • Created the ability to deactivate rate charts from the right-click menu, so users now have the option to deactivate an entire rate chart all at once or on an individual basis. Read more…
  • Improved functionality for unauthenticated track order data.
  • Improvement made to prevent invalid message formats from being created and incorrect message types from being assigned to a status event.
  • Updated the CXT Parcel Item Over/Short Counts default reports available through the Advanced Find Service.
  • Added ability for users to deactivate advanced finds, so they can be removed from the filter display, but be kept in the system for possible later use.
  • Sped up performance with loading and refreshing the posted route stop form.
  • Added functionality to display a pop up alert with driver data when attempting to link a driver to a human resource record that is already associated with 1 or more drivers.
  • Updated help text within the internet user profile to better explain functionality.
  • Increased CPU performance to better handle caching of large objects being de/serialized to improve user experience.
  • Added the ability to set up advanced zone to zone surcharges based on percent in addition to the existing dollar amount.
  • Added the ability to throttle API calls at periodic intervals at both the user and global level, so carriers can better manage their API charges.
  • Improvement made to sort invoices on the customer record form and within X Internet by invoice date to match the Invoice Center and Rapidship displays.
  • Renamed the “AllowDriverTracking” column label within the customer record Internet Users tab to “AllowDriverTracking(XI)” since it will now only display settings for X Internet’s driver tracking.
  • Improved “Today with Rollover” order type logic, so continuation order’s ReadyTimeTo and DueTimeTo values are calculated based on the order type time window setting.
  • Adjusted logic to restrict users from adding in duplicate parcel types within the customer record’s Required Mobile Route Parcel Types section.
  • Moved the “Display Duplicate Status Codes” mobile option set permission to be under the “Allow Stop Level Status Codes” permission to better display its dependency on the associated permission.
  • Created new logic to automatically reset web passwords in Permissions when new X Dispatch users are created through the Cloud Client, so they no longer have to be manually updated.
  • Improved the permissions audit trail to include data on users that delete permission entries.
  • Popup warning added to alert users if they attempt to add an item that is already in use as a sales tax item when creating new or editing existing accessorial or surcharge rate charts.
  • Updated the help-text on the order type’s “Use deadline for return/continuation order ready time” field and the internet user profile’s “Show Deliver By Time” field to indicate that the “Use deadline” functionality only works if the internet user can see delivery times.
  • Added additional information to the on demand order’s route button hover text and within the audit trail for route sort rules and route stops to more easily display what sort rule was applied.
  • Added *DEFAULT* wildcard rating functionality within the stamp weight rate charts to allow for default zone rating.
  • Updated the Sales by Date (On Demand) report by sorting the date column in the proper order.
  • Added “LastResult” fields for tracking credit card processing attempt responses, so users can see this information when running the following advanced finds: “CXT – Credit Card Invoice Processing Activity For Date Range” and “CXT – Credit Card Order Processing Activity For Date Range”.
  • Added new settings Active Orders, Attachments, Required Driver Input, and Signatures, to the Audit Options in Tools.
  • Updated the Audit Options window to display the checkbox options in alphabetical orders.
  • Improvement made to auto-hide the left navigation bar within X Dispatch to allow for smoother navigation and viewing of the Next Dispatch web pages.
  • Added hyperlink to all copyright displays within Rapidship and Next Dispatch, so users can be directed to the CXT Software website if needed.
Next Dispatch
  • Dashboard widgets can now display all Find types instead of being limited to only Order, Route Stop, and Driver.
  • Reduces the number of database calls made when accessing Next Dispatch’s internet user record to increase performance and usability.
  • Functionality added to minimize the performance impact of the dashboard widgets to improve user experience.
  • Added a new field within the dashboard’s widget drawer called “Widget Type”, so users can easily switch the widget type selection on existing displays without having to delete and re-create the widget.
  • Display an error message when there are negative values within the pie chart widget’s find filter results.
  • Added a confirmation prompt on the dashboard when a user attempts to delete a widget, so they can cancel the action if they initiated the delete by mistake.
  • Implemented a new 10 widget maximum on the dashboard to ensure proper performance speeds.
  • Added new functionality within the Advanced Find (BETA), so users will now see input entry fields within a single form that lists all required information instead of receiving a pop up for each individual input.
  • New drop down menu option added to the “Value” column within the Next Dispatch Basic Find that allows users to search by “NULL”, so users can have a better way to manage by exception.
  • Added red “X” icon on the Find (BETA)’s basic view to allow users to quickly remove unneeded rows of criteria.
  • Added in the ability to save specific “Show/Hide Field” settings for each individual saved find.
  • Allow internet address comments to be updated from within Next Dispatch and Rapidship.
  • Updated mobile option set permissions for easier navigation of permissions.
  • Added spinner display on all Next Dispatch records whenever they take more than two seconds to load.
  • Improved required field alerts when users do not enter required information on forms.
  • Updated all of the Next Dispatch pages to now default sort upon the name or description of the records instead of the ID value to allow for a better user experience.
  • Updated the Next Dispatch drawer and window displays to show the name or description of the records instead of the ID value to allow for a better user experience.
  • Updates logic within the Next Dispatch internet users form’s Customers tab so that it no longer displays customers that have been marked as inactive or blacklisted.
  • Maintenance – Sales Tax will now display “FromProvince” and “ToProvince” column options when customers have their global option set to default Canadian addresses.
  • New notifications for users setting up or adjusting sales tax entries if the item they selected is already in use by an accessorial or surcharge rate chart.
Rapidship
  • Adjusts the search parameters on Rapidship’s Place Order address book search, to only include name, address, city, state, and zip/postal to ensure users receive a more intended result set.
  • Improved error messages for Rapidship login issues to minimize information provided to potential hackers and increase security.
  • Improvement made to only display the Email Notification checkbox options that are set up on the Contacts tab of the customer record, so Rapidship users are not given notification options that are not available for the customer.
  • Improvement made to the internet user profile’s Custom Procedures tab in Next Dispatch, so users now have the ability to disable and hide default shipping label options for Rapidship end-users.
  • Displays master barcode data in Rapidship, if applicable, when tracking orders and route stops.
  • Added the “POD Comments” field to the Route Tracking page.
  • Take Rapidship users to the “Detailed” view instead of the “Basic” view when editing an order.
  • “Email” field is now required on the Rapidship User Profile, so end users cannot completely remove the value.
  • Removed all “CXT” text from default shipping label names.
Nextstop
  • Added a Batch Scan option within the options menu to give users the ability to mark all parcels on a receive stop as scanned after the first initial scan.
  • Push notification logic was improved so it will now send a message to the Nextstop 3 user if they have been logged out due to another user logging in with the same credentials.
  • Made improvements to properly display parcel item descriptions added from Nextstop on the associated order in X Dispatch.
  • Fixed an issue with routed parcel sync performance.
X Stream
  • Developed the ability to add and edit attachments from the XStream definition form, so customers are able to make changes to integrations without needing access to the local file system.
  • Made an improvement when importing stops and orders using consolidation to trigger the “create stop” or “order placed” status event message formats.
  • Added the ability to un-post imported route stops even when scan data is present. Read more…
  • New setting to XmlListener that allows users to indicate whether they want the pieces and weight values to be generated from the stop level or parcel level.
  • Fixed an issue where driver pay was failing to calculate on orders if a user manually typed in the driver assignment data and immediately saved the record without tabbing out of the field.
  • Fixed an issue where item and surcharge rate charts were displaying an option to activate/deactivate within the right-click menu before the full functionality was in place. Full functionality coming in XD 21.1.
  • Fixed an issue where the Weight Scan feature was running slow and in some cases stopped responding when using an RDP session.
  • Fixed an issue where invalid non-empty ZIP codes were causing incorrect time zone labels to be displayed.
  • Fixed an issue where Active Report WCF Service was rejecting reports over 30MB and canceling requests taking longer than 100 seconds.
  • Fixed an issue where a Foreign Key Error was being thrown when entering route stops on the fly.
  • Fixed an issue where the auto sequence functionality would allow a delivery stop to be sequenced before its associated pickup stop when the “Deliver To” time frame was mistakenly marked as earlier than the pickup by a user.
  • Updated the warning message that appears when users change the order type on a saved order which causes an automatic rerate.
  • Fixed an issue where “No Rollover” order types could roll over to the next day under some conditions where the “Due Time To” was outside of the hours of operation.
  • Fixed an issue where “Look For”/”Search Under” filters were not retaining their selections properly after opening a record.
  • Fixed an issue where some of the “Look For”/”Search Under” filter options on the X Route Planning page were not returning the correct results.
  • Fixed an issue where the email status updates were being sent out even when the email request was canceled.
  • Fixed issues that caused exceptions to be logged numerous times and changed driver GPS location history to allow unknown GPS location error values to be saved to ensure entries are not lost.
  • Fixed an issue where a route stop’s audit trail was showing the User ID as “Unknown” when a change was made through the Bulk Rate Update tool instead of logging the User ID that initiated the bulk action.
  • Fixed an issue where parcels were allowed to be added to a cloned route stop before saving the record.
  • Fixed an issue where a missing Sales Tax Item selection on the Sales Tax page was causing an error when trying to place orders.
  • Fixed an issue where the time window’s calendar on the order form could start populating the next day’s date in the late afternoon hours depending on what time zone the customer is in since it was based on GMT time.
  • Fixed an issue where consolidation was not updating parcel count and weight on orders properly.
  • Fixed an issue where a non-specific error was received if an order type was created without any hours or operation being selected.
  • Fixed an issue in the Basic Find where “Alternate Lookup” was incorrectly showing up as an available option in the “Where” column when searching for orders.
  • Fixed an issue where X Dispatch was not setting the created by value when posting routes or using route sort rules.
  • Fixed an issue where the “Adjust Stop Times Wizard” was allowing updates to stops that were created from on demand orders via route sort rules.
  • Fixed an issue where time zones were not displaying properly for some postal codes in British Columbia.
  • Fixed an issue where “[InsertedStatusCode]” was no longer allowed to be used within the message format’s Advanced tab.
  • Fixed an issue where CXTUtilities was logging an error when message formats contained more than one “[Attachments]” or “[VPOD]” field.
  • Fixed an issue where an error was being thrown if you attempted to set scan details on an imported on demand order without a set parcel type.
  • Fixed an issue where an error was being thrown if the “Calculate Sales Tax” setting was enabled, but a state-to-state pair was not found.
  • Fixed an issue where an error was being thrown when attempting to use the Bulk Order Update tool and no records were returned in Find’s result set.
  • Fixed an issue where duplicate route stops could appear on the route dispatch board if a route was dispatched to a driver at the same time that another user had one of the route stop records open and manually changed its route assignment.
  • Fixed an issue where right-clicking on the Routed Dispatch Board can cause some hidden fields to show with a very small width.
  • Fixed an issue where the dispatch boards were not saving the split pane heights properly.
  • New pop up alerts are displayed to users that are attempting to dispatch orders with locked driver pay to new drivers, so they can decide whether they want to maintain the driver lock or rerate accordingly.
  • Fixed an issue where some dedicated customers in the Cloud environment were able to create tables in the cusdbo schema, but were unable to modify the table contents from CustomTables.
  • Fixed an issue on the pieces and weight rate chart tables where the form was closing after receiving a warning message for a missing or incorrect value in the “Per” column.
  • Fixed an issue where an error was being received when running basic finds using a text column with empty value.
  • Fixed an issue where set route stop weight values were being overridden by a zero parcel weight upon import into the system.
  • Fixed an issue where some users were receiving a “This record has been modified by another user. Your changes cannot be saved” error when trying to save a route stop record.
  • Fixed an issue where exports into QuickBooks versions 2019+ were failing if there was a semicolon present within one of the fields.
  • Added a new warning to users attempting to add a route ID of “Unassigned”, to let them know that it is already a reserved route ID.
  • Fixed an issue where an audit trail entry could fail to be added when the UpdatedBy and/or UpdatedWhen value was NULL.
  • Fixed an issue where stopping the Mail Manager from its form was not logging the Updated By and Updated When fields of the audit log.
  • Fixed an issue where “LastLogin” times were not being recorded for internet user logins via web services.
  • Fixed an issue where the internet user template drop-down selection could not be removed from the Global Options Internet Options tab.
  • Fixed an issue where an “Invalid property array index” error was being displayed when attempting to completely remove a selection from the left and right click mapping fields in Global Options.
  • Fixed an issue where the column sum display on a Find’s result set was being saved as part of the column layout.
  • Fixed an issue where some users were receiving an “invalid use of null” error when opening address records in Legacy.
  • Fixed an issue where the application would close when attempting to delete an internet address that was set as the user’s default origin or destination.
  • Fixed an issue where order/stop audit trails could occasionally show information (e.g. status codes) for a non-associated order/stop with the same ID.
  • Fixed an issue where some fields from tblOrderRouteStops were not being audited.
  • Fixed an issue where Required Driver Input from the customer record was incorrectly being added to posted recurring orders.
  • Fixed an issue where the customer invoice SP was using slightly different parameters for pulling item and order type GL Codes.
  • Fixed an issue where users were receiving an error while trying to update a recurring order if the order was previously added or updated directly in the database.
  • Fixed an issue with slow performance using Classic ASP API for order status updates.
  • Fixed a performance issue by increasing credit card processing performance.
  • Fixed an issue where an inactive human resources record’s “View Orders” link was taking the user to the Inet Account tab instead of the Recurring tab.
  • Fixed an issue with the tab order on the Contracts and Contract Stops pages.
  • Fixed an issue where an unexpected error was being displayed when trying to add a label to a new contract stop.
  • Fixed an issue where a SQL Error was being thrown when trying to view Order Time History on an on demand order.
  • Fixed an issue with zone rating by improving the rate zone data display when orders are set up to use the advanced zone to zone surcharge rates.
  • Fixed an issue where users were unable to print dispatch tickets when a database field was specified followed by a space for the “PrintElement” field.
  • Fixed an issue where an error was being thrown when Cloud Client users selected the “Save As” option on the on demand order’s Attachments tab.
  • Fixed an issue where an error was being thrown when users tried to create a new custom report format with an ID of 0.
  • Fixed an issue where users were able to modify some of the standard report formats that are restricted.
  • Fixed an intermittent issue where some Rapidship and Nextstop users were receiving an authentication error on some of their log in attempts.
Next Dispatch
  • Added spinner displays to all save button functionality in Next Dispatch.
    Fixed an issue where “Alternate Lookup” was not working properly within the basic find.
  • Fixed an issue where the Find (BETA) was displaying an error when users emailed a find result with no default dispatch email address set in the global options.
  • Fixed an issue where a data type mismatch error was being thrown when users cleared out the “Max Records” value within the Find (Beta) modal.
  • Fixed an issue where advanced finds that returned RowVersion data (e.g. SELECT * FROM tblLabels) was failing to generate the CSV file.
  • Fixed an issue where the Next Dispatch internet user form options were not saving properly when loaded from templates.
  • Fixed an issue within the internet users section where users were allowed to remove all columns from the “Visible Columns” container leaving the main page display empty.
  • Fixed an issue where changes to the Next Dispatch internet user address book’s “Group” field was not updating properly on each associated address.
Rapidship
  • Fixed an issue where new internet users created from Next Dispatch were not being defaulted to the Address Book tab within Rapidship as intended.
  • Fixed an issue where some Rapidship shipping labels were not printing as expected.
  • Fixed an issue where an error was being thrown in the Rapidship driver portal when the “Show Totals Only” option was enabled on the associated human resource record.
  • Fixed an issue where an error was being thrown in Rapidship when trying to use recently placed orders and templates with addresses that had since been deleted from the internet address book.
  • Fixed an issue where Rapidship was not allowing users to edit orders if one or both addresses on the order were not validated.
  • Fixed an issue where the original “Schedule Later” time on Rapidship orders were not prepopulating correctly when in “Edit Order” mode.
  • Fixed an issue where internet users were not able to cancel orders in Rapidship if they did not have the “Show Delivery By Time” permission enabled.
  • Fixed an issue where Rapidship’s “Schedule Later” time picker was not always adding the selected time on the clock into the time field.
  • Fixed an issue where canceled orders being displayed on the Track Order page were not showing the user that canceled the order.
  • Fixed an issue where surcharge items that were based on other surcharge items needed adjustment.
  • Fixed an issue where an error is being thrown when exporting a report in Rapidship if the associated user’s customer record Reference tab’s Display Caption 1 and 2 have identical values.
  • Fixed an issue where Rapidship’s General Order Report could be cut off when being printed.
  • Fixed an issue where some logos were being stretched too wide on the mobile Rapidship registration page.
  • Fixed an issue where Rapidship’s “Save Login Shortcut” was incorrectly saving on the desktop as a text file when using Firefox on Windows.
Nextstop
  • Fixed an issue where the driver order sequence set through the driver grid on the dispatch board was not updating the “Sort by Itinerary” view in Nextstop 3.
  • Fixed an issue where parcel description information wasn’t displaying in Nextstop 3 on all of the intended fields.
  • Fixed an issue where Nextstop 3 was not triggering the next pickup/next delivery status events configured on the customer record.
  • Fixed an issue where an error was being thrown when opening a route stop if the required driver input text had a quote in it.
  • Fixed an issue in Nextstop 2 where some automatically chained parcels could be removed from the mobile device after a sync.
  • Fixed an issue in Nextstop 2 where flagging an order as “Next Stop” wasn’t working properly.
X Stream
  • Fixed an issue when an import has failures, so now the system will create a new file with all of the successful imports and then a separate file with any failures which will stop duplicate route stops from being created.
  • Upgraded the X Stream PostingTool functionality, so it will retry any failed automatic postings until it reaches the maximum number of attempts limit.
  • Fixed an issue where errors were being thrown when creating new X Stream definitions where the Key drop-downs had values in them.
  • Fixed an issue where Master Barcode data on parcels that were being receive scanned prior to an ASN file being imported, were being cleared out incorrectly upon the import action.
  • Fixed an issue where an error was being thrown if an apostrophe was being used within XINI ConsolidationText.
X Tracking
  • Fixed an issue where the logout button was not working as expected.
    Fixed an issue where an error was being thrown when plotting drivers in X Tracking Map Point if the driver(s) had a bearing value of NULL.
  • Using Hotkey / keyboard on the Dispatch board to confirm the deactivation of a driver causes the driver active work screen to open instead of confirming the previous action.
    Workaround: Use the mouse to click the confirm button to deactivate the driver instead of the keyboard.
  • An unexpected error is displayed when setting a message format on the customer record when the Message Format ID is greater than 32,767.
    Workaround: Keep Message Format ID values under 32,767.
  • Audit trails may not be viewable if the enclosing document has special characters in the id, which can occur with X Dispatch Users (Permissions section) and Inet Users.
    Workaround: Use the Legacy view in X Dispatch to view audit trails for X Dispatch users that have special characters in their User ID.
  • Changes made in Next Dispatch’s Permissions section are not being captured in the Audit Trail.
    Workaround: Use the Legacy view of Permissions to make changes.
  • Adding multiple parcels from the Parcels tab of posted route stop that does not have any parcels will cause X Dispatch to crash.
    Workaround: Add the first parcel then save the stop or add parcels from the parcel manifest.
  • For Canadian customers, the date picker on the order form in X Dispatch returns the incorrect date.
    Workaround: Enter the date manually.
  • After deleting a saved attachment on an order, attempting to save any other changes to the order will throw a warning that the record has already been updated.
    Workaround: Immediately save the record right after deleting the attachment. After the record has been saved, all other changes can be made.
  • When editing a required driver input in X Dispatch, the value will change from NULL to 0, appearing as though the field already has an entry and will not display to the driver.
    Workaround: Delete the required driver input and create a new one.
  • An error occurs whenever an X Dispatch user tries to email settlements to drivers that do not have an associated email address and/or settlement message format within their human resources record.
    Workaround: Update the driver’s human resource record with an email address and/or settlement message format.
  • Rapidship throws an error when loading.
    Workaround: The browser’s “service workers” need to be unregistered.  Read more…
  • Error “Either BOF or EOF is True…” received when going to Order page on X Internet if there is a default address indicated for the inet user, but no addresses present in the inet address book.
    Workaround: Add an address to the internet user’s address book. The issue only occurs in X Internet when there is a default, but no address book entries.
  • Lat/Lon values are not being copied over for cloning of Inet User Address books.
    Workaround: Run an Internet User Address Points bulk address update. This will run all the internet addresses through the validation process and assign Lat/Lon values.
  • An error is thrown when trying to update passwords through Tools when the required password field is empty on the Internet User Profile
    Workaround: Save passwords into the Internet User Profile.
  • Subscription based reports fail to export and generate an email when certain field types like TimeStamp are included.
    Workaround: Do not include the TimeStamp field; as it is not supported.
  • X Dispatch Monitor – Help – View Manual results in a Run-Time error ’13’ Type mismatch.

X Dispatch 21.0.3.2 Cloud Patch (April 2021)

  • Added in the ability to parse out data values by commas in addition to semicolons for online ordering.
X Stream
  • Improved logic for X Stream audit trail processing, so it will continue to process even if there is bad data within the queue.
  • Fixed an issue where route stop POD enforcement was preventing arrival scans from processing correctly.
  • Fixed an issue where the posted route stop form was not properly allowing users to add multiple parcels on the Parcels tab if the first parcel wasn’t first saved on the record.
  • Fixed an issue where some Basic Find subscriptions were failing to be emailed out if the Find had selected columns to be hidden.
  • Fixed an issue where errors were being thrown when using the conversion wizard to import internet address points that included the barcode column.
  • Fixed an issue with dates were not appearing in the correct date format for Canadian customers.
  • Fixed an issue where the Sales by Day report was sorting the days alphabetically instead of chronologically.
  • Fixed an issue where an error was being thrown when using the Save, Clone, Continuation options.
Rapidship
  • Fixed an issue where an error was being thrown when trying to edit Rapidship orders that get sent through route sort rules and have an associated route stop.
  • Fixed an issue where internet users were temporarily allowed to place orders online after the intended cut off.
  • Fixed an issue where the ‘Hide Item Amounts’ setting in the Human Resource Inet Account tab was temporarily not being respected when viewing settlements in Rapidship’s driver portal.
  • Fixed an issue that prevented the Estimated Settlements report within Rapidship’s Driver Portal from displaying all the columns correctly.
Nextstop
  • Fixed an issue where Nextstop users were temporarily receiving an error when trying to log in if they didn’t have Accessorial permissions enabled.
  • Fixed a temporary issue where driver capabilities were being removed when recording a driver’s latest connectivity time.
  • Using Hotkey / keyboard on the Dispatch board to confirm the deactivation of a driver causes the driver active work screen to open instead of confirming the previous action.
    Workaround: Use the mouse to click the confirm button to deactivate the driver instead of the keyboard.
  • An unexpected error is displayed when setting a message format on the customer record when the Message Format ID is greater than 32,767.
    Workaround: Keep Message Format ID values under 32,767.
  • Audit trails may not be viewable if the enclosing document has special characters in the id, which can occur with X Dispatch Users (Permissions section) and Inet Users.
    Workaround: Use the Legacy view in X Dispatch to view audit trails for X Dispatch users that have special characters in their User ID.
  • Changes made in Next Dispatch’s Permissions section are not being captured in the Audit Trail.
    Workaround: Use the Legacy view of Permissions to make changes.
  • After deleting a saved attachment on an order, attempting to save any other changes to the order will throw a warning that the record has already been updated.
    Workaround: Immediately save the record right after deleting the attachment. After the record has been saved, all other changes can be made.
  • When editing a required driver input in X Dispatch, the value will change from NULL to 0, appearing as though the field already has an entry and will not display to the driver.
    Workaround: Delete the required driver input and create a new one.
  • An error occurs whenever an X Dispatch user tries to email settlements to drivers that do not have an associated email address and/or settlement message format within their human resources record.
    Workaround: Update the driver’s human resource record with an email address and/or settlement message format.
  • Rapidship throws an error when loading.
    Workaround: The browser’s “service workers” need to be unregistered.  Read more…
  • Error “Either BOF or EOF is True…” received when going to Order page on X Internet if there is a default address indicated for the inet user, but no addresses present in the inet address book.
    Workaround: Add an address to the internet user’s address book. The issue only occurs in X Internet when there is a default, but no address book entries.
  • Lat/Lon values are not being copied over for cloning of Inet User Address books.
    Workaround: Run an Internet User Address Points bulk address update. This will run all the internet addresses through the validation process and assign Lat/Lon values.
  • An error is thrown when trying to update passwords through Tools when the required password field is empty on the Internet User Profile
    Workaround: Save passwords into the Internet User Profile.
  • Subscription based reports fail to export and generate an email when certain field types like TimeStamp are included.
    Workaround: Do not include the TimeStamp field; as it is not supported.
  • X Dispatch Monitor – Help – View Manual results in a Run-Time error ’13’ Type mismatch.

X Dispatch 21.0.3.3 Cloud Patch (April 2021)

  • Fixed an issue where email addresses that contained a 10 digit mobile [email protected][phone carrier] were being considered a valid phone number and causing SMS text message notifications to fail.
  • Fixed an issue within the Legacy Find where users were receiving an unexpected error when trying to do a bulk update on contract stops through the “Adjust Stop Times” option.
Nextstop
  • Fixed an issue where the “Closest to Me” and “Itinerary” sorts were not working as intended for route stops in Nextstop 3.
  • Using Hotkey / keyboard on the Dispatch board to confirm the deactivation of a driver causes the driver active work screen to open instead of confirming the previous action.
    Workaround: Use the mouse to click the confirm button to deactivate the driver instead of the keyboard.
  • An unexpected error is displayed when setting a message format on the customer record when the Message Format ID is greater than 32,767.
    Workaround: Keep Message Format ID values under 32,767.
  • Audit trails may not be viewable if the enclosing document has special characters in the id, which can occur with X Dispatch Users (Permissions section) and Inet Users.
    Workaround: Use the Legacy view in X Dispatch to view audit trails for X Dispatch users that have special characters in their User ID.
  • Changes made in Next Dispatch’s Permissions section are not being captured in the Audit Trail.
    Workaround: Use the Legacy view of Permissions to make changes.
  • After deleting a saved attachment on an order, attempting to save any other changes to the order will throw a warning that the record has already been updated.
    Workaround: Immediately save the record right after deleting the attachment. After the record has been saved, all other changes can be made.
  • When editing a required driver input in X Dispatch, the value will change from NULL to 0, appearing as though the field already has an entry and will not display to the driver.
    Workaround: Delete the required driver input and create a new one.
  • An error occurs whenever an X Dispatch user tries to email settlements to drivers that do not have an associated email address and/or settlement message format within their human resources record.
    Workaround: Update the driver’s human resource record with an email address and/or settlement message format.
  • Rapidship throws an error when loading.
    Workaround: The browser’s “service workers” need to be unregistered.  Read more…
  • Error “Either BOF or EOF is True…” received when going to Order page on X Internet if there is a default address indicated for the inet user, but no addresses present in the inet address book.
    Workaround: Add an address to the internet user’s address book. The issue only occurs in X Internet when there is a default, but no address book entries.
  • Lat/Lon values are not being copied over for cloning of Inet User Address books.
    Workaround: Run an Internet User Address Points bulk address update. This will run all the internet addresses through the validation process and assign Lat/Lon values.
  • An error is thrown when trying to update passwords through Tools when the required password field is empty on the Internet User Profile
    Workaround: Save passwords into the Internet User Profile.
  • Subscription based reports fail to export and generate an email when certain field types like TimeStamp are included.
    Workaround: Do not include the TimeStamp field; as it is not supported.
  • X Dispatch Monitor – Help – View Manual results in a Run-Time error ’13’ Type mismatch.

X Dispatch 21.0.4 (May 2021)

An asterisk (*) indicates items that are new for Cloud as well as on premise customers. All other items were included in previous Cloud patches.

Next Dispatch
  • Added a download button to Maintenance Images and a delete confirmation window when deleting images.*
  • Improved logic to classify unique lookup barcodes for Inet and X Dispatch Addresses to incorporate the barcode ID and either the inet user ID or customer ID, respectively.*
  • Added a friendly error message if a duplicate Lookup Barcode is used in an address*.
  • Added a new option within the X Dispatch Action menu called “Processed Credit Card Transaction Report” where users will be able to search their previously processed records by date range to view and print the report.*
  • Expanded the Count field column on the Dispatch Board’s driver pane to better display what kind of count totals are being shown: Count (Total), Count (On Demand), and Count (Routed).*
  • Improved the active work screen to remember the pane height per driver, so each driver that is clicked on can have their own display.*
  • Updated unsafe SQL queries to use parameterized queries that are safer and less error-prone.*
Next Dispatch
  • Increased the character limits within the Message Formats body, so users are able to use longer HTML code displays for their end-users status email updates.*
  • Added status filter options to the Drivers page, so users can view by Active, Inactive, or All records.*
  • The Maintenance Images page now allows PNG files to be saved and used throughout the X Dispatch application.*
  • Improved filter logic on drop down menu fields within Internet Users, Drivers, Permissions, and Sales Tax pages to allow for a search that is more user-friendly and displays more accurate results.*
  • Improved column selection in Next Dispatch to have the Hidden Column fields sort alphabetically, so they can be located more easily.*
Rapidship
  • Improved logic for editing orders in Rapidship that allows the original time windows to be maintained unless there is a change to the order type, time windows, or addresses.*
  • Added a friendly error message when an invalid email address format is entered.*
  • Added in the ability to parse out data values by commas in addition to semicolons.
X Internet
  • Added in the ability to parse out data values by commas in addition to semicolons for online ordering.
X Stream
  • Added a check when unposting imported stops to prompt the user if there is scan/POD data on a stop before unposting is completed.*
  • Improved logic for X Stream audit trail processing, so it will continue to process 
  • Fixed an issue where order types using the “Today No Rollover” business line were able to be selected online for days that were not enabled for service.*
  • Fixed an issue where some users were receiving an error when trying to use custom procedure shipping labels.*
  • Fixed an issue where users were receiving an “Invalid use of NULL” error when opening any object tied to a customer where there was a status alert set up, but no message format assigned to it.*
  • Fixed an issue where customer-restricted parcel types were still showing in the Parcel Info field’s drop down menu on orders.*
  • Fixed an issue on the driver record where the Human Resource drop down menu was temporarily displaying all historical records instead of only active and allowed items.*
  • Fixed a temporary issue where email addresses that contained a 10 digit mobile [email protected][phone carrier] was being considered a valid phone number and causing SMS text message notifications to fail.
  • Fixed an issue where orders assigned to multiple drivers would not always follow the proper driver order causing the completed order to show up again on the first driver’s device.
  • Fixed an issue where an error was being thrown when trying to save a Preferred End Time on the driver record.*
  • Fixed an issue where users would receive an error if attempting to dispatch a route to a driver that had a blank email on their driver record.*
  • Fixed an issue where an error could occur when dealing with time window changes that fall during the 2:00am to 3:00am hour during the daylight savings time switchover.*
  • Fixed an issue where some users with “Caller” data that exceeded the 50 character field limit, were not able to successfully place an order.
  • Fixed an issue where an error was being thrown when using the Save, Clone, Continuation options.
  • Fixed an issue where errors were being thrown when using the conversion wizard to import internet address points that included the barcode column.
  • Fixed an issue where importing a single row of data through the conversion wizard was not successfully importing.
  • Fixed an issue where assisted dispatch orders/tasks that are in the future could cause unexpected driver recommendation results.*
  • Fixed an issue with MinIdle not updating on the Dispatch board.*
  • Fixed an issue where parent stops were not updating the “IsActive” field for any linked child stops.*
  • Fixed an issue where a contract would fail to post if a contract stop with the same ID already existed for the same post date.
  • Fixed an issue where the posted route stop form was not properly allowing users to add multiple parcels on the Parcels tab if the first parcel wasn’t first saved on the record.
  • Fixed an issue where the Sales by Day report was sorting the days alphabetically instead of chronologically.
  • Fixed an issue with dates not appearing in the correct date format for Canadian customers.
  • Fixed an issue where some Basic Find subscriptions were failing to be emailed out if the Find had selected columns to be hidden.
  • Fixed an issue with some custom Advanced Finds that prevented opening orders by clicking on a line from within the result set.*
  • Fixed an issue with deleting saved finds in Legacy Finds.*
  • Fixed an issue within the Legacy Find where users were receiving an unexpected error when trying to do a bulk update on contract stops through the “Adjust Stop Times” option.
  • Fixed a performance issue where processing a bulk rate update for the maximum record amount could cause the CPU to spike.
Next Dispatch
  • Fixed an issue where some internet users were getting an error when editing orders online if they did not have the “Edit Accessorials” permission.*
  • Fixed an issue where the Find (BETA)’s “Adjust Stop Times” icon was not becoming enabled when the result set displayed stops.*
  • Fixed an issue exporting find results in XLS format in Next Dispatch.*
  • Fixed an issue where updating an image description within Maintenance Images, could corrupt some file types.
Nextstop
  • Fixed an issue where updates to pieces and/or weight on an order from within Nextstop 2 and 3 were removing status codes.*
  • Fixed an issue where Nextstop users were receiving an error when trying to log in if they didn’t have Accessorial permissions enabled.
  • Fixed an issue where driver capabilities were being removed when recording a driver’s latest connectivity time.
  • Fixed an issue where route stop POD enforcement was preventing arrival scans from processing correctly.
  • Fixed an issue where the “Closest to Me” and “Itinerary” sorts were not working as intended.
  • Fixed an issue where the required driver input updates initiated from Nextstop 2 could display invalid date formats within the audit trail.
Rapidship
  • Fixed an issue where an error was being thrown when trying to edit Rapidship orders that get sent through route sort rules and have an associated route stop.
  • Fixed an issue where internet users were temporarily allowed to place orders online after the intended cut off.
  • Fixed an issue where the Rapidship Track Order page was not always showing all route stops associated with a parcel when performing a search by the Parcel ID.
  • Fixed an issue where Rapidship driver tracking was displaying an error when the associated driver had no GPS location history.
  • Fixed an issue where the Rapidship attachment punch-through links were navigating the user to the attachments page, but not showing the attachment files.
  • Fixed an issue where the ‘Hide Item Amounts’ setting in the Human Resource Inet Account tab was temporarily not being respected when viewing settlements in Rapidship’s driver portal.
  • Fixed an issue where the Human Resource’s “Order Type Desc” checkbox was not displaying on the Estimated Settlements and Settlements pages in Rapidship when the “Show Totals Only” checkbox is disabled.*
  • Fixed an issue where the Rapidship driver portal was intermittently not displaying the worker’s email and phone number on the profile.*
  • Fixed an issue that prevented the Estimated Settlements report within Rapidship’s Driver Portal from displaying all the columns correctly.
X Stream
  • Fixed an issue where there were some unexpected results when sorting the XImport Audit Logs.*
  • Using Hotkey / keyboard on the Dispatch board to confirm the deactivation of a driver causes the driver active work screen to open instead of confirming the previous action.
    Workaround: Use the mouse to click the confirm button to deactivate the driver instead of the keyboard.
  • An unexpected error is displayed when setting a message format on the customer record when the Message Format ID is greater than 32,767.
    Workaround: Keep Message Format ID values under 32,767.
  • Audit trails may not be viewable if the enclosing document has special characters in the id, which can occur with X Dispatch Users (Permissions section) and Inet Users.
    Workaround: Use the Legacy view in X Dispatch to view audit trails for X Dispatch users that have special characters in their User ID.
  • Changes made in Next Dispatch’s Permissions section are not being captured in the Audit Trail.
    Workaround: Use the Legacy view of Permissions to make changes.
  • An error can occur when activating/deactivating a driver when new columns are available on the dispatch board.
    Workaround: Save the layout before activating/deactivating a driver.
  • After deleting a saved attachment on an order, attempting to save any other changes to the order will throw a warning that the record has already been updated.
    Workaround: Immediately save the record right after deleting the attachment. After the record has been saved, all other changes can be made.
  • When editing a required driver input in X Dispatch, the value will change from NULL to 0, appearing as though the field already has an entry and will not display to the driver.
    Workaround: Delete the required driver input and create a new one.
  • An error occurs whenever an X Dispatch user tries to email settlements to drivers that do not have an associated email address and/or settlement message format within their human resources record.
    Workaround: Update the driver’s human resource record with an email address and/or settlement message format.
  • Rapidship throws an error when loading.
    Workaround: The browser’s “service workers” need to be unregistered.  Read more…
  • Error “Either BOF or EOF is True…” received when going to Order page on X Internet if there is a default address indicated for the inet user, but no addresses present in the inet address book.
    Workaround: Add an address to the internet user’s address book. The issue only occurs in X Internet when there is a default, but no address book entries.
  • Lat/Lon values are not being copied over for cloning of Inet User Address books.
    Workaround: Run an Internet User Address Points bulk address update. This will run all the internet addresses through the validation process and assign Lat/Lon values.
  • An error is thrown when trying to update passwords through Tools when the required password field is empty on the Internet User Profile
    Workaround: Save passwords into the Internet User Profile.
  • Subscription based reports fail to export and generate an email when certain field types like TimeStamp are included.
    Workaround: Do not include the TimeStamp field; as it is not supported.
  • X Dispatch Monitor – Help – View Manual results in a Run-Time error ’13’ Type mismatch.

X Dispatch 21.0.4.1 Cloud Patch (May 2021)

Rapidship
  • Fixed an issue where having multiple email addresses in Rapidship templates was causing an issue when trying to add new orders to cart.
  • Fixed an issue where the “Create from Templates” option on Rapidship’s Place Order form was not properly adding new orders to the cart.
  • Using Hotkey / keyboard on the Dispatch board to confirm the deactivation of a driver causes the driver active work screen to open instead of confirming the previous action.
    Workaround: Use the mouse to click the confirm button to deactivate the driver instead of the keyboard.
  • An unexpected error is displayed when setting a message format on the customer record when the Message Format ID is greater than 32,767.
    Workaround: Keep Message Format ID values under 32,767.
  • Audit trails may not be viewable if the enclosing document has special characters in the id, which can occur with X Dispatch Users (Permissions section) and Inet Users.
    Workaround: Use the Legacy view in X Dispatch to view audit trails for X Dispatch users that have special characters in their User ID.
  • Changes made in Next Dispatch’s Permissions section are not being captured in the Audit Trail.
    Workaround: Use the Legacy view of Permissions to make changes.
  • An error can occur when activating/deactivating a driver when new columns are available on the dispatch board.
    Workaround: Save the layout before activating/deactivating a driver.
  • After deleting a saved attachment on an order, attempting to save any other changes to the order will throw a warning that the record has already been updated.
    Workaround: Immediately save the record right after deleting the attachment. After the record has been saved, all other changes can be made.
  • When editing a required driver input in X Dispatch, the value will change from NULL to 0, appearing as though the field already has an entry and will not display to the driver.
    Workaround: Delete the required driver input and create a new one.
  • An error occurs whenever an X Dispatch user tries to email settlements to drivers that do not have an associated email address and/or settlement message format within their human resources record.
    Workaround: Update the driver’s human resource record with an email address and/or settlement message format.
  • Rapidship throws an error when loading.
    Workaround: The browser’s “service workers” need to be unregistered.  Read more…
  • Error “Either BOF or EOF is True…” received when going to Order page on X Internet if there is a default address indicated for the inet user, but no addresses present in the inet address book.
    Workaround: Add an address to the internet user’s address book. The issue only occurs in X Internet when there is a default, but no address book entries.
  • Lat/Lon values are not being copied over for cloning of Inet User Address books.
    Workaround: Run an Internet User Address Points bulk address update. This will run all the internet addresses through the validation process and assign Lat/Lon values.
  • An error is thrown when trying to update passwords through Tools when the required password field is empty on the Internet User Profile
    Workaround: Save passwords into the Internet User Profile.
  • Subscription based reports fail to export and generate an email when certain field types like TimeStamp are included.
    Workaround: Do not include the TimeStamp field; as it is not supported.
  • X Dispatch Monitor – Help – View Manual results in a Run-Time error ’13’ Type mismatch.

X Dispatch 21.0.4.2 Cloud Patch (May 2021)

  • Fixed a temporary issue where an error was being thrown when users were trying to deactivate drivers from the dispatch board without first resaving their layouts due to newly added columns.
Nextstop
  • Fixed a temporary issue where some Nextstop updates on route sort rule route stops were causing their associated orders to not rate properly.
Rapidship
  • Fixed a temporary issue where Rapidship would not load properly in Safari browsers.
 
  • Using Hotkey / keyboard on the Dispatch board to confirm the deactivation of a driver causes the driver active work screen to open instead of confirming the previous action.
    Workaround: Use the mouse to click the confirm button to deactivate the driver instead of the keyboard.
  • An unexpected error is displayed when setting a message format on the customer record when the Message Format ID is greater than 32,767.
    Workaround: Keep Message Format ID values under 32,767.
  • Audit trails may not be viewable if the enclosing document has special characters in the id, which can occur with X Dispatch Users (Permissions section) and Inet Users.
    Workaround: Use the Legacy view in X Dispatch to view audit trails for X Dispatch users that have special characters in their User ID.
  • Changes made in Next Dispatch’s Permissions section are not being captured in the Audit Trail.
    Workaround: Use the Legacy view of Permissions to make changes.
  • After deleting a saved attachment on an order, attempting to save any other changes to the order will throw a warning that the record has already been updated.
    Workaround: Immediately save the record right after deleting the attachment. After the record has been saved, all other changes can be made.
  • When editing a required driver input in X Dispatch, the value will change from NULL to 0, appearing as though the field already has an entry and will not display to the driver.
    Workaround: Delete the required driver input and create a new one.
  • An error occurs whenever an X Dispatch user tries to email settlements to drivers that do not have an associated email address and/or settlement message format within their human resources record.
    Workaround: Update the driver’s human resource record with an email address and/or settlement message format.
  • Rapidship throws an error when loading.
    Workaround: The browser’s “service workers” need to be unregistered.  Read more…
  • Error “Either BOF or EOF is True…” received when going to Order page on X Internet if there is a default address indicated for the inet user, but no addresses present in the inet address book.
    Workaround: Add an address to the internet user’s address book. The issue only occurs in X Internet when there is a default, but no address book entries.
  • Lat/Lon values are not being copied over for cloning of Inet User Address books.
    Workaround: Run an Internet User Address Points bulk address update. This will run all the internet addresses through the validation process and assign Lat/Lon values.
  • An error is thrown when trying to update passwords through Tools when the required password field is empty on the Internet User Profile
    Workaround: Save passwords into the Internet User Profile.
  • Subscription based reports fail to export and generate an email when certain field types like TimeStamp are included.
    Workaround: Do not include the TimeStamp field; as it is not supported.
  • X Dispatch Monitor – Help – View Manual results in a Run-Time error ’13’ Type mismatch.

X Dispatch 21.0.4.3 Cloud Patch (May 2021)

  • New global option child permission called “Orders w/RSRs” (Orders with Route Sort Rules) under the “Edit Orders” parent permission that allows users to select whether the associated route stop should be automatically deactivated or left active when a Rapidship user makes edits to the order type on orders that have been run through route sort rules.
  • Fixed an issue where not all available order types were being shown to Rapidship users if the ‘Edit Delivery Ready Time’ on the inet user’s profile was not enabled.
  • Using Hotkey / keyboard on the Dispatch board to confirm the deactivation of a driver causes the driver active work screen to open instead of confirming the previous action.
    Workaround: Use the mouse to click the confirm button to deactivate the driver instead of the keyboard.
  • An unexpected error is displayed when setting a message format on the customer record when the Message Format ID is greater than 32,767.
    Workaround: Keep Message Format ID values under 32,767.
  • Audit trails may not be viewable if the enclosing document has special characters in the id, which can occur with X Dispatch Users (Permissions section) and Inet Users.
    Workaround: Use the Legacy view in X Dispatch to view audit trails for X Dispatch users that have special characters in their User ID.
  • Changes made in Next Dispatch’s Permissions section are not being captured in the Audit Trail.
    Workaround: Use the Legacy view of Permissions to make changes.
  • After deleting a saved attachment on an order, attempting to save any other changes to the order will throw a warning that the record has already been updated.
    Workaround: Immediately save the record right after deleting the attachment. After the record has been saved, all other changes can be made.
  • When editing a required driver input in X Dispatch, the value will change from NULL to 0, appearing as though the field already has an entry and will not display to the driver.
    Workaround: Delete the required driver input and create a new one.
  • An error occurs whenever an X Dispatch user tries to email settlements to drivers that do not have an associated email address and/or settlement message format within their human resources record.
    Workaround: Update the driver’s human resource record with an email address and/or settlement message format.
  • Rapidship throws an error when loading.
    Workaround: The browser’s “service workers” need to be unregistered.  Read more…
  • Error “Either BOF or EOF is True…” received when going to Order page on X Internet if there is a default address indicated for the inet user, but no addresses present in the inet address book.
    Workaround: Add an address to the internet user’s address book. The issue only occurs in X Internet when there is a default, but no address book entries.
  • Lat/Lon values are not being copied over for cloning of Inet User Address books.
    Workaround: Run an Internet User Address Points bulk address update. This will run all the internet addresses through the validation process and assign Lat/Lon values.
  • An error is thrown when trying to update passwords through Tools when the required password field is empty on the Internet User Profile
    Workaround: Save passwords into the Internet User Profile.
  • Subscription based reports fail to export and generate an email when certain field types like TimeStamp are included.
    Workaround: Do not include the TimeStamp field; as it is not supported.
  • X Dispatch Monitor – Help – View Manual results in a Run-Time error ’13’ Type mismatch.

X Dispatch 21.0.7 (July 2021)

An asterisk (*) indicates items that are new for Cloud as well as on premise customers. All other items were included in previous Cloud patches.

  • Increased the speed for posting and retrieving route stops on the route dispatch board.*
  • Improvement made to Assisted Dispatch results, so they are now automatically displayed when the recommendation dataset is returned.*
  • New global option child permission called “Orders w/RSRs” (Orders with Route Sort Rules) under the “Edit Orders” parent permission that allows users to select whether the associated route stop should be automatically deactivated or left active when a Rapidship user makes edits to the order type on orders that have been run through route sort rules.
Next Dispatch
  • Fixed an issue where users were receiving permission validation errors when trying to edit older X Dispatch permission records.*
Rapidship
  • Removed the service type field from the requirement criteria for what constitutes a valid order on the “Place from Recent Order” tab.*
  • Added functionality to Rapidship’s Add Parcel modal to include a “Create Multiple Parcels” option that allows users to do continuous scanning on parcels without the modal closing.*
  • Fixed an issue in Rapidship where default email addresses were being added onto the order when making an edit.*
  • Fixed an issue with emailing shipping labels from the X Dispatch order form.*
  • Fixed an issue where right-clicking and saving the dispatch board layout for orders/routes on the driver grid was causing users to have to reselect fleets upon navigation back to the page.*
  • Fixed an issue where the date picker for the recurrence schedule was setting the incorrect date whenever the date format was something other than MM/DD/YYYY.*
  • Fixed an issue where the email subject of a shipping label contained the incorrect order number.*
  • Fixed an issue where when a parcel type was manually typed into the field wasn’t always saving to the order properly.*
  • Fixed a temporary issue where an error was being thrown when users were trying to deactivate drivers from the dispatch board without first resaving their layouts due to newly added columns.
Next Dispatch
  • Fixed an issue where users were experiencing performance issues with the import audit log search feature when large record sets were present.*
  • Fixed an issue on the new web-based internet user profile when supporting settings (e.g. custom procedures, drivers, customers, etc) did not exactly match the User ID.*
  • Fixed an issue with X Dispatch permissions where users were receiving an error if they added an “Inherited Permissions From” value to the record and then removed it.*
  • Fixed an issue where some users would receive an error when opening up Maintenance>Permissions.*
  • Fixed an issue where saving column layouts for Find results could replace some prompts with the last entered data.*
Nextstop
  • Fixed a temporary issue where some Nextstop updates on route sort rule route stops were causing their associated orders to not rate properly.
Rapidship
  • Fixed an issue where the track order URL links were not loading properly under certain conditions.*
  • Fixed an issue when creating an order from a recent order if the user did not have permission to edit orders.*
  • Fixed an issue where users were receiving errors when editing orders if the email address field was previously empty.*
  • Fixed an issue where the route tracking maps would not display as intended if there were missing Lat/Lon values on stops.*
  • Fixed an issue where the Rapidship browser time-out countdown was slightly off.*
  • Fixed an issue where default email addresses were overwriting existing data when editing a template.*
  • Fixed an issue where an error was being thrown when creating a continuation order if the internet user record did not have a default address set.*
  • Fixed an issue where not all available order types were being shown to users if the ‘Edit Delivery Ready Time’ on the internet user’s profile was not enabled.
  • Fixed a temporary issue where Rapidship would not load properly in Safari browsers.
  • Fixed an issue where having multiple email addresses in templates was causing an issue when trying to add new orders to the cart.
  • Fixed an issue where the “Create from Templates” option on the Place Order form was not properly adding new orders to the cart.
X Internet
  • Fixed a temporary issue that was preventing users from creating new customers.*
  • Overtime calculations may not apply properly for imported orders when PickupDate and DeliverDate values are not set and Time Window overrides are used.
    Workaround: Populate the PickupDate and DeliverDate values on the XINI.
  • Using Hotkey / keyboard on the Dispatch board to confirm the deactivation of a driver causes the driver active work screen to open instead of confirming the previous action.
    Workaround: Use the mouse to click the confirm button to deactivate the driver instead of the keyboard.
  • An unexpected error is displayed when setting a message format on the customer record when the Message Format ID is greater than 32,767.
    Workaround: Keep Message Format ID values under 32,767.
  • Audit trails may not be viewable if the enclosing document has special characters in the id, which can occur with X Dispatch Users (Permissions section) and Inet Users.
    Workaround: Use the Legacy view in X Dispatch to view audit trails for X Dispatch users that have special characters in their User ID.
  • Changes made in Next Dispatch’s Permissions section are not being captured in the Audit Trail.
    Workaround: Use the Legacy view of Permissions to make changes.
  • After deleting a saved attachment on an order, attempting to save any other changes to the order will throw a warning that the record has already been updated.
    Workaround: Immediately save the record right after deleting the attachment. After the record has been saved, all other changes can be made.
  • When editing a required driver input in X Dispatch, the value will change from NULL to 0, appearing as though the field already has an entry and will not display to the driver.
    Workaround: Delete the required driver input and create a new one.
  • An error occurs whenever an X Dispatch user tries to email settlements to drivers that do not have an associated email address and/or settlement message format within their human resources record.
    Workaround: Update the driver’s human resource record with an email address and/or settlement message format.
  • Rapidship throws an error when loading.
    Workaround: The browser’s “service workers” need to be unregistered.  Read more…
  • Error “Either BOF or EOF is True…” received when going to Order page on X Internet if there is a default address indicated for the inet user, but no addresses present in the inet address book.
    Workaround: Add an address to the internet user’s address book. The issue only occurs in X Internet when there is a default, but no address book entries.
  • Lat/Lon values are not being copied over for cloning of Inet User Address books.
    Workaround: Run an Internet User Address Points bulk address update. This will run all the internet addresses through the validation process and assign Lat/Lon values.
  • An error is thrown when trying to update passwords through Tools when the required password field is empty on the Internet User Profile
    Workaround: Save passwords into the Internet User Profile.
  • Subscription based reports fail to export and generate an email when certain field types like TimeStamp are included.
    Workaround: Do not include the TimeStamp field; as it is not supported.
  • X Dispatch Monitor – Help – View Manual results in a Run-Time error ’13’ Type mismatch.

Let's meet! Request a
guided demo.

Let's meet! Request a
guided demo.

Whatcha looking for?