Peoplevox

Release Notes - Version 7.14.0 (154)

This release contains additional back-end changes related to the ongoing Android sync improvements, as well as some additional groundwork for both Android barcode scanning and an online-focused sortation process. We also made improvements to the advanced action creation functionality mentioned in the past couple of releases, and some general improvements to the action creation experience when inventory can't be allocated (e.g. because it's in bulk).

Enhancement: Continued to roll out improvements to the Android sync process (476352, 476347, 476472, 476195).
Enhancement: Technical design and initial groundwork on some upcoming improvements to a more online sortation process (473288, 477726).
Enhancement: Improvements to internal data obfuscation tasks to help with automating GDPR and similar requests (475576, 477402, 470125).
Enhancement: Updated the "Pick and sort" action type to allow the one-order-per-location validation to be removed (466470, 477348, 477368).
Enhancement: Ongoing groundwork related to the upcoming Android "scan" function (460918, 461197, 478241, 478250).
Enhancement: Extended the action creation workflow to allow users to drill into the details if the action is unable to fully allocate all of the necessary items. Click the Show details button to see information on item quantities, including the quantity available for soft-allocation, the quantity held in bulk  versus in pick, as well as the quantity that is inaccessible due to being held in a pick location for which a failed action exists (366883, 478234).
Enhancement: Extended the MetaPack integration to be able to pass the sender's VAT number on consignment requests (474188).
Resolved Issue: Fixed some UI issues with the new advanced action creation workflow (475108).

These numbers come from our internal work tracking system, and we present them here so that you've got something to reference if you have any questions. If you've raised a specific issue on the support desk, then we'll come back to you on that ticket with any relevant updates.