Descartes® is pleased to announce the latest release of Peoplevox. This update is primarily focused around the new stock take and cycle count process. 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.
Tip: Use our Ideas Portal to submit your enhancement ideas for Descartes Peoplevox. Click here for additional information and instructions on how to request access.
Highlights
🟨 New and improved stock take workflow for cycle counting (1268137)
This release includes an update to the cycle count mobile workflow. Up until now, if a cycle count action was created for a location, the mobile operator was only prompted to scan items in that location, and they had no option to mark it as empty. With this release, mobile operators will have a unified workflow that allows them to:
Scan items in the location
Scan containers in the location
Mark the location as empty
The new Contents field can be used for either items or containers (or both), and scanning anything into the contents removes the option to mark it as empty:
If the operator needs to clear the location, they can simply tap the toggle at the bottom of the page and then complete the stock take:
Resolved Issues
🟩 We resolved an issue that was preventing the creation of actions under rare circumstances. (1302168, 1300255)
🟩 We resolved an issue that prevented the recently added "Hide quantity input" permission from being visible during the new stock take workflow. This permission should now be visible, and allows administrators to control which roles have access to the quantity input control during stock take. (1270507)
🟩 We resolved an issue that caused the system to incorrectly change actions to "one person picks one order" type actions for single-order batches. This functionality had already existed for some time, but would only convert actions if the user creating the action specifically selected a single order to batch. The issue here manifested as a result of changing any single-order batches, even those that were created as a part of batching several orders together (for example batching 11 orders with a batch size of 10 orders, the remaining 11th order would be put into its own batch). We have temporarily disabled the auto-conversion functionality, and we plan to make it a configurable parameter against the profile that you will be able to define during action creation. (1301855)
🟩 We resolved an issue with the replenishment by sales order report that could result in some items not being present on the report. (1268302)
Preview of Changes Coming Soon
Decommissioning old screens
We plan to decommission some old UI screens over the coming months. Users in the app will see a warning message when they open these older screens. Please make use of the new UI replacements sooner rather than later so that you are familiar with those screens when the old ones are decommissioned.
September
The following legacy screens are scheduled to be decommissioned on September 1st:
Removals
Sites
Returns
October
The following legacy screens are scheduled to be decommissioned on October 1st:
Reports
Dashboards
Mobile Register update
The Register function on mobile will soon be updated to use the new PVX+ app. The functionality of this workflow is not changing, but you will be prompted to download and install the PVX+ app if it is not already installed.
Cycle Count improvements
We’re working on several improvements to the cycle count process. We would love to hear your feedback on these topics.
🟦 We're working on a new variance approval workflow for the web application. This will allow you to easily search for variances using a new unique reference applied to each one, and to approve or reject those variances on a line-by-line basis. This new workflow will allow you to approve or reject individual item lines while leaving others undecided. It also simplifies the presentation of each variance and clearly distinguishes between item and container variances in a location, so that users can easily see what the impact of approving the variance will be.
🟦 In addition, we already work on an auto-approval mechanism that will allow you to define thresholds for auto-approval based on the total item variance, or a percentage variance, or a total value variance (or any combination of the above). These thresholds will be set at the Site level and are entirely optional. You will be able to enable auto-approval with a variance threshold of zero if you only want to auto-approve variances with no discrepancies.
🟦 We plan to improve the way cycle count actions are displayed on the web application. The current actions pages are geared around pick actions, making many of the fields and columns not applicable to cycle counting. The goal is to introduce screens that are relevant to the specific action type.
Descartes ShipRush
You can also find the latest release notes for ShipRush here: