Capturing print status without "verifying the print job has been printed before continuing" within the Print Documents action
I am attempting to capture the print status of every print job so I can pass that information back to a database to give the user more information if there is an error. However, using the "verify the print job has been printed before continuing" slows down my integration immensely.
My scenario: Users are printing labels four different types of lab specimen containers where each utilizes a different label size, printing from individual printers. Users can print any combination of these labels in a single "request". The integration checks a SQL Server DB for one main "request" record, and that is linked to one or more label data records. So for example if a user wants to print labels for 6 different specimens of the same label type, this will have one Request record and six label data records.
I want to capture the print status of each of the 6 Label Data records, but having them wait for each other to return a print status takes significantly more time to complete the printing than not using the print verification option. It is way too time consuming the more labels the user is printing. I need to keep each label as it's own print job for auditing purposes.
Is there an alternate way to capture print status, so that essentially these print jobs don't have to wait for each other? I am thinking that one option would be to make the trigger for this actually be on the Label Data records, rather than doing a "For each record", and so each integration trigger can run parallel. I have never tried this before though, so any advice would be appreciated.
-
Not sure, but could you use one of the Output options instead after the Print Document Command in the For Each Database Record set?
Dont know if this is workable but could be worth a try.
0 -
pthane thanks for the suggestion. I will see if I can incorporate that. After a lot of trial and error, I think it is going to be too much effort to try and get this to work, so for now I am going to try and just batch print labels instead of each label being its own print job. In the future I may return to this though.
0
Please sign in to leave a comment.
Comments
2 comments