Terminal Print Job Mappings

[markjw]

This is a long standing bug, I reported it back in April 2019 on v5.2.22…

Problem with terminal mapping on print jobs

I have noticed in v5.2.23 beta, and also in v5.2.22 that the Terminal in Print Job mappings appear to be ignored. I have tested like this: [image] 2 terminals each are sending to a different network printer to open the cash drawer. When I test this scenario, no matter what terminal the print job is executed from, POS1 cash drawer is opening. If I delete the POS1 mapping and only leave POS2 mapping, then as expected POS2 cash drawer will open. So it would seem Terminal is being ignored / n…

The only way to get around it is to create separate Print Jobs for each terminal then trigger then separately in rules. You can simplify the amount of actions you need to create by just passing the terminal name as a parameter, but this is still the only way I could get it to work per terminal in a reliable way.