Descartes Peoplevox 24.09-02 includes the New Features, Enhancements and Resolved Issues (bug fixes) described below. If you have questions about an item, please reference the number in parentheses, if available, when contacting Descartes Customer Support.
This release includes several enhancements to recent features, a range of bug fixes across the application, and some general performance improvements in preparation for peak.
Tip: User our Ideas Portal to submit your Enhancement ideas for Descartes Peoplevox. Click here for additional information and instructions for requesting access to the Ideas Portal.
Note: As we continue the migration of screens to the new web app styling, we will move the older version of each screen to legacy mode. The older versions will remain available for the immediate future, but you are encouraged to use the new screens wherever possible. Also, we welcome your feedback on the new screens. Your input helps us to ensure that the new screens meet your needs before the legacy screens are switched-off at a later date. The new versions of those screens include:
- Locations
- Location groups
- Removals
- Sites
- Returns
Thank you to everyone that has provided feedback on these screens so far. Please rest assured that we are reviewing all feedback, and have several enhancements planned to implement many of those changes that you have proposed.
Note: The legacy web app returns workflow will be moving to end of life in the near future. Please use the new returns workflow to process your returns. If you currently use the legacy workflow, you will see an in-app announcement in the coming days. For guidance on the new workflow, please check our help documentation here. If you have any concerns that the new workflow is missing any key functionality that your business needs, please reach out via the support desk so that we can work with you to identify and resolve those gaps.
New Features and Enhancements
🟨 A new "Returns states" integration template is now available. This template will allow integrations to create and update returns states in the same manner as returns reasons and RMAs. (1039601)
🟨 The carrier integration framework's response schema was updated to support carrier integrations that need to provide tracking data for multiple packages in a single response. This is supported via the addition of the optional new parameter "despatchPackageId" for each tracking segment (alongside the trackingType and trackingNumber elements). The new parameter "despatchPackageId" ensures that the specified tracking number is applied to the designated package, even if it differs from the package for which the label request was originally generated. The new parameter is intended to provide support for partners that wish to implement a form of consignment shipping. However, its use is entirely optional. All existing carrier integrations will remain fully compatible with the current responses. (1081093)
🟪 The security of the event subscription mechanism is now improved. Although all outbound subscription connections were established using TLS 1.2 or greater, there were some rare edge-cases in which the subscriber was able to downgrade the security of that connection. All subscriptions will now enforce the higher security standard. Protocol downgrades are no longer allowed. (1040316)
🟪 The performance of the sales order summary report was improved by separating it into a live version for current data and an archive report for historical data. With this update, the live sales order summary report will be restricted to displaying data from only the most recent two months. (1040281)
🟪 The legacy "Despatched items by package" reports (simple, v3, and v4) have been deprecated and removed. They are replaced by the higher performance v5 reports. (1039448)
🟪 The new advanced put away rules configuration is now extended with the ability to define rule-specific sorting conditions. This will allow you to set up rules that prioritize putting away items based on conditions other than the IP sequence, for the zone name, to align with the allocation sequence used during advanced action creation. (1084931).
Resolved Issues
🟩 A recent change to action creation introduced in the previous release was reverted. The goal of the change was to improve the performance of the action creation process by deferring a calculation on the total number of orders to be batched. Based on feedback from several users, that calculation has been reinstated and users will continue to be able to see the total number of orders returned by action creation filters before they create the action. (1091988)
🟩 An issue that prevented print template rules from working correctly during mobile despatch was resolved. Mobile operators can now select "[Use rules]" during a mobile despatch and these rules will correctly select the appropriate template for printing. (1037636)
🟩 A problem with ambiguous barcodes and SKUs on the mobile application was resolved. The issue could cause some picked items to be unscannable during the despatch workflow if those items shared either a barcode or an item code with another product. For example, while barcodes and item codes are unique, the situation manifested when the item code for one product matched the barcode of another. The application will now correctly identify the products. The products are now scannable throughout the picking and despatch workflow without interference. (367693)
🟩 An issue related to date time formats with the ChannelAdvisor integration was resolved. This issue specifically caused some problems with requested delivery dates for Peoplevox environments configured to use a non-UK date time format. (1037582)
🟩 A data issue with the MetaPack integration was resolved. The issue manifested in situations where the shipping information being transferred to Peoplevox was incomplete. In these situations, the integration applied a value of "." to some of the missing fields. This passed initial validation checks within the MetaPack API, but led to subsequent failures when transmitting the shipping information to carriers. Now, the integration will no longer try to fill blank shipping data and will instead transmit the information exactly as it was provided on the original sales order. (1024201)
Descartes Zangerine and Descartes ShipRush
You can also find the latest release notes for Zangerine and ShipRush here: