Descartes® is pleased to announce the Pacejet 26.6 release. This update introduces Descartes Address Validation as a single, carrier-independent way to verify addresses, along with performance optimizations and a number of bug fixes. For questions about specific changes, please contact Descartes Customer Support.
Enhancements
Address Validation
🟪 Enhancement: Address validation now offers a new Descartes Address Validation service that can be used with any carrier, instead of separate carrier-specific implementations. Customers get consistent results and clearer messages no matter which carrier is used, with broader international coverage than the previous carrier options provided. Administrators can select Descartes Address Validation as the default validation method, and the service is registered automatically on upgrade, so no manual configuration is required to begin using it. Existing FedEx® and UPS® validation remains available for customers who prefer to continue using it. As part of this change support for direct USPS validation as a method is being removed and existing users are being migrated automatically to the Descartes method. (1557891)
🟪 Enhancement: Address validation settings have been consolidated. A single logging option replaces the four separate carrier logging options, and license key and service endpoint settings are now managed in one place rather than per carrier. (1557890)
Performance
🟪 Enhancement: The Pacejet pre-processing web service no longer rebuilds its plugin environment on every request. Customers running pre-processors should see faster and more consistent response times, with no change to how pre-processors are written, deployed, or logged. (1549320)
Resolved Issues
Shipping and Automation
🟩 Resolved Issue: Previously, when the same delivery order was picked up by two processes at the same time in the UI, the order could ship twice and produce duplicate labels and tracking numbers. Pacejet now claims an order in a single step before any rating or label generation occurs, so a second request is rejected and the order ships only once. (1546414)
Carriers and Administration
🟩 Resolved Issue: Previously, no facilities appeared in UPS Connection Management when a site's code and name did not match, which prevented a UPS account from being assigned without renaming the site. Facility lookup now uses the site code, so facilities appear correctly for every site. The site name continues to display in the list, and existing UPS site and facility assignments are unchanged. (1546415)
Administration
🟩 Resolved Issue: Previously, an automation rule using a checkbox Custom Data field could silently fail to run, most often on import, because the stored value was not evaluated correctly in the condition. Checkbox custom data fields are now evaluated correctly, so automation conditions match as expected and the associated action runs on save and on import. (1553903)
🟩 Resolved Issue: Previously, the Site field could be changed while editing an existing warehouse facility, and a success message returned, even though the change was never saved. The Site field is now locked when editing a facility, matching the existing behavior of the Facility field. (1590948)