There is too much processing that happens on the client during ticketing. The biggest slow-down I have seen is with Printing and Imaging.
I would like to see all printing and image creation be executed from a service on a server instead of the client. Right now we have to install 100+ printers on each user's computer in order to print correctly.
When printing from the ticketing screen, users often have to wait for the ticketing screen to process all operations (printing, imaging, dispatch order updating, load list creation, sales order qty updates, auditing, and the list goes on) which usually hangs up the screen in a Not Responding state until it finishes. This then requires the client to have more memory and computer power, where we would prefer to beef up a server to do this instead.
The client needs to be just that, an interface into the system, not the actual processor.
Thanks Chris, we have a ticket open for the print service. Ill send you an email.
My recommendation in the short-term would be to use our print service. This will offload ticket printing to a service. Please contact support for additional details. Mention my name so that they know who to ask for background.
This would be good as we have developed our own Crystal Reports for our ticket. As we print multiple pages, the Ticket Screen is basically frozen until the print process is completed. This prevents the batchman/weighmaster from preparing the next load until the printing is complete.
Business Impact: Central Scale Masters often have to wait upwards of a minute for a ticket to clear their ticketing screen. This holds up the scale master from moving on to another process.