I am trying looking for best practices in managing print jobs through devicehub. I’ll give a specific example that hopefully explains why and what I’m looking for.
I ran into a situation where I have several print jobs listed as “Pending”. I expected that list to help me catch print tickets that didn’t print. However, I discovered that those Pending jobs were for Pick Tickets that were indeed printed (manually I assume). If I make that assumption and print the “pending” jobs, I will end up possibly shipping orders twice.
I set up a schedule for Pick Tickets to print every 10 minutes. Some users manually print their pick tickets. I understand that if a user prints a job seconds after the schedule runs, we will end up with 2 printed pick tickets.
If a user prints a ticket before the schedule runs, no print job is created. If a print job fails or is pending, then the user prints it manually, the pending jobs obviously do not changed to “Processed”.
Just FYI -- We also had to limit manually printing pick tickets through the Actions tab (back in 2020 using the Reports tab or through the Process Shipments Screen didn’t check the Pick Ticket Printed box).
This is getting way TLDR, but I’m trying to figure out tools that allow me to find failed jobs and get them printed (NOT MISS A SHIPMENT) and avoid the opposite -- tickets printed, but we think they haven’t and we print them again (DUPLICATE SHIPMENT).
I’m thinking that as I move towards using devicehub more, I’ll find more situations like this. Hence, I am looking for best practices. Business Events to use, GI’s, Screens, business practices, etc
Edit: How should devicehub be setup? Individual computer connected to the printer? Setup a computer to run DH for all users (will that work)? Reboot computer/devicehub every day (see a lot of time out issues)?