-
Push messages in Warehouse Mobile App
Send a push message to the worker or a group of workers, all or active only workers in the (new WMSv4) app
This would allow the warehouse manager to request a few workers to finish the current pick work in Pickzone 1 and move over to Pickzone 2, or to announce that there is a celebration in the cantine.
The message should be signaled by a sign (red circle with number of messages) in the top right, like in many apps incl. the yammer viva engage app)
It should be displayed in each screen (not only the start screen or menu), also when the user is executing a work.
The worker can press on the symbol to view the message(s).
https://www.yammer.com/dynamicsaxfeedbackprograms/threads/3217059061481472
-
Create cluster manually by scanning target LPs
Scanning target LP should be accepted just like work ID when creating a cluster manually.
A cluster is created per trolley (e.g. TR01) by the system at the beginning of the first zone.
Work IDs are auto-assigned and are not printed, the worker does not see the work IDs.
The worker scans a target LP (fixed barcode on a plastic bin, e.g. BIN1001, BIN1002 etc.) for each cluster position.
After all the lines in the first zone are picked, the worker passes the cluster, and the bins are put on the conveyor belt.
The conveyor belt will break the cluster through a customization.
Now the plastic bins are pushed out by the conveyor belt to different zones.
At the second, third etc. zone the next worker moves the half filled plastic bins that are pushed out for that zone to a new trolley (e.g. TR02).
This should be possible by scanning the target LPs BIN1001 etc. (= fixed bar codes on the plastic bins).
Unfortunately this is not possible. Only work IDs are accepted by the system at this spot.
At all other mobile processes, the worker can scan work ID or target LP as desired, but here it seems forgotten.
The code change in WHSRFControlData processLegacyControl() is simple i.m.o., but cannot be done by the partner.
https://www.yammer.com/dynamicsaxfeedbackprograms/threads/3234601276899328
https://fix.lcs.dynamics.com/Issue/Details?bugId=1004227&dbType=3