Descartes® is pleased to announce the latest release of Peoplevox. This update includes various improvements designed to enhance system performance and user experience. Below, you'll find a summary of the changes implemented in this version. For any questions about specific items, please reference the associated number (if provided) when contacting Descartes Customer Support.
In this release, we are continuing work on the final back-end components to support the new print client, automatic cycle count creation, and the new action creation mechanism. We expect to start rolling out those features in the very near future. This release also includes the new PVX+ navigation menu, introduces a new sales order field to help with linking orders to RMAs, and fixes several bugs.
Tip: Use our Ideas Portal to 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.
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
Reports
Dashboards
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.
Highlights
New sales order field for joining to RMAs: MarketplaceOrderIdentifier
RMAs can already be linked to sales orders via the SalesOrderNumber or the CustomerPurchaseOrderReferenceNumber field, but we have seen several instances where the returns portal raising the RMA does not have the order values that's provided in those fields. This new field provides a dedicated place to hold the order number from the original marketplace, even if the order number used to identify the order in Peoplevox is different (for example if it includes additional prefixes / suffixes, or if it is the identifier for the order in a marketplace aggregator). This new field will ensure that regardless of the format of the order number used to identify the order, returns portals will always be able to link RMAs to the correct order in Peoplevox. (1235121)
New PVX+ navigation menu
This release includes an updated navigation menu for PVX+. This new navigation will feel familiar to current PVX+ users, while offering a more approachable experience for new users as well. Although it is mostly a visual update, this new navigation will feature its own page on mobile: It will offer a standalone page rather than an overlay of other screens. You can still switch back and forth between the navigation and other activities and the navigation for the standard PVX app will not change. (1152858)
New Features and Enhancements
🟪 The workflow for skipping items during a pick is now simplified. When skipping, rather than prompting the user to ask whether they want to find another location, the app will now automatically find another location for the item. (1221349)
🟪 We have adjusted some of the configuration related to the replenishment workflow. Currently, there are two versions of the replenishment workflow. There are two primary differences between v1.0 and v2.0, related to the trigger condition and the destination suggestion. With regards to the trigger condition, v1.0 will only trigger the creation of a replenishment when the physical stock quantity drops below the threshold, whereas v2.0 will also consider orders that have been allocated and are therefore likely to drop the pick face quantity below the threshold when picked. With regards to the destination suggestion, the v1.0 will suggest mixed locations (i.e. it supports locations that hold more than one SKU), whereas v2.0 will only suggest empty locations or locations that contain only the SKU to be replenished. Up until now, the only option has been to switch between v1.0 and v2.0. We are expanding that configuration to allow operators to benefit from the improved trigger condition in v2.0, while maintaining mixed-SKU recommendations. (1221122)
Resolved Issues
🟩 We resolved an issue in one of our import optimization processes related to the Rithum™ (formerly ChannelAdvisor™) connector. When importing very large datasets, the import process can compare the imported data to the values already held by Peoplevox, and skip the import if there is no impactful change. This is an intentional process to avoid unnecessary updates within the system that may then trigger subsequent updates to the mobile devices. This process was previously not as effective, which caused some large data imports to trigger extremely large snapshots for the mobile devices. The process has now been fixed and as a result those large product imports should be significantly less impactful to mobile performance. (1247616)
🟩 We have resolved an issue with the volumetric calculations introduced in the new advanced put away feature. The volumetric calculations were only evaluating the cubic volume of a single product, even if multiple units were being moved. The calculation will now consider the total number of a product being moved, and evaluate the combined cubic volume of those products. (1235225)
🟩 We have resolved an issue with the stock valuation report that could occasionally cause some products to be ommitted in multi-warehouse environments that involve the transfer of those items between warehouses. The report should now correctly include each product in each site, regardless of any transfers between sites. (1224193)
Preview of Changes Coming Soon
New simplified action names
🟦 As part of our ongoing work to improve the action creation workflow, we are simplifying some of the terminology around action creation. The functionality of these actions is not changing, only the descriptions. The following actions are being renamed:
PICK: 1 person picks 1 sales order at a time -> 1 person picks 1 order
PICK: 1 person picks multiple sales orders in a batch - orders -> Multi-order batch pick - orders
PICK: Single item batch picking, with scan, assign & print invoice at pack bench -> Single item batch picking
PICK: 1 person picks multiple sales orders in a batch - items -> Multi-order batch pick - items
We expect to start rolling out the new names in the next release (25.06-02).
Descartes ShipRush
You can also find the latest release notes for ShipRush here: