Peoplevox

Peoplevox 25.08.01 Release Notes


Descartes® is pleased to announce the latest release of Peoplevox. This update is primarily focused around the new action creation 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

🟨 Improvements to order filters - Preview (1248226, 1248225)

This release includes a preview of upcoming improvements to how order filters will be managed. At the moment, the page just provides a simple search page functionality, without no option to edit filters yet. We will continue to introduce new features for this screen in coming releases.

Rather than relying on the search box within the action creation workflow, the new screen will in the future allow you to manage your order filters from a central location. You'll be able to see where they're used across your various order profiles, and (finally) allow you to share filters with other users. While the upcoming action profile functionality will reduce the need for sharing filters, this screen will support those scenarios where managing and sharing remains useful.


Resolved Issues

🟩 We resolved an issue that could lead to various problems related to action creation, stemming from database deadlock issues. These issues manifested in several ways, from disappearing actions to orders being locked by pending action creation tasks. We are continuing to monitor logs for any related issues and will address any that are found. (1294719, 1294720, 1294054, 1293195)

🟩 We resolved a small inconsistency in column header capitalization around locations and location groups. (1293333)


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.

🟦 Finally, we are extending the mobile workflow for performing the cycle count action. At the moment, operators are limited to a a simple "count items in location/container" prompt. An upcoming update will allow mobile operators to use this workflow to:

  • Count items in locations/containers

  • Count containers in locations

  • Mark the location/container as empty

The single workflow will support all of these actions without the need to exit or switch screens.


Descartes ShipRush

You can also find the latest release notes for ShipRush here:

ShipRush release notes

Back to Top