I have been telling my users that printing from Kinetic is just broken. The only solution they have is to print preview. Then use the file that (hopefully) pops up to email or print.
Some time ago when I was complaining about Edge Agent being a crutch, someone said that we do actually need it to enable printing from Kinetic.
We are cloud, not on prem. Our printers are a mix of local USB dedicated, and networked ethernet/wifi.
What do I have to do to get printing to work from Kinetic? Or can I really give up and make them all do print preview first?
There are so many threads here about printing issues, I can’t tell if it is still a thing or if it has been resolved.
Thank you for your time!
I got to this section in the help file and I have no idea what the.. they are talking about: What’s SignalR?
There can be multiple Edge Agents installed on different machines with access to different network printers. To see a printer you must:
– Be in a Cloud environment
– Verify that within the System Administration Console, the Message hub uses a SignalR account
– Have an edge agent installed in network mode
To be completely honest, we just trained everyone to just live with the Print Preview and resulting downloads, etc. I think Edge Agent has probably come a long way, but it (network printing) was a battle early on. It may have gotten better, but now that everybody is used to print previewing… it hasn’t been much of a problem.
For most of our “printing”, people want to preview it first anyway. And we have APR set up on various documents so they’ll get emailed copies in those cases if they choose. Then it is just standard printing to the device of their choice from the PDF reader.
Obviously one company’s use case is different from another’s. But the Print Preview route has been (a small learning curve/cheese-moving hurdle, but…) more or less widely accepted in my organization.
Yeah, and even if you do setup EA some reports cough jobtrav cough don’t format correctly unless you print preview them anyway. Epicor says there is nothing that can be done when reported to them.
We ended up with both network and local Edge Agents in play.
Network agent had a single failure over the 3-4 months since we went to cloud…and I think there was something squirrely on the cloud side that day. The SignalR thing is Azure-related…might be the base requirement to “enable” the network printing that Epicor had to set up for us. We’ve had local agents since day one with our previously 3rd-party-hosted setup. Not really a fan…more like a necessary evil I guess.
