Same Label, Different Destination Printers Follow

0
Avatar
Legacy Poster

Hello.

We are using Bartender 9.1.
I have a problem, which a cannot solve at the present time, and i really hope, that someone here could give me a hand.

I get different files (Trigger Files) on different shares. Can i choose a printer based on where the trigger file appears, but using the same label?

example: I have a folder "AUDI", and if the trigger file appears here, i want to print the "VDA.btw" label on printer "15"
I also have a folder "BMW", and if the trigger file appears here, i want to print the "VDA.btw" label on printer "25".

Is this possible?


Thanks for your help

5 comments

0
Avatar
Ian Cummings
Moderator
Comment actions Permalink

I assume you are using pre-defined BarTender commands in the task properties?

Have you not created individual tasks to monitor different files/folders and therefore then call off a BarTender command that specifies the particular printer to use for the print job?

A better way is to use Commander Script or BarTender XML Script in the trigger contents as this allows you to specify such variables as label format and printer to use in the trigger itself rather than be predefined in the task.

Take a look at the Commander white papers for more guidance.

Commander Overview:
http://s3.amazonaws.com/SeagullBarTender/ftp/WhitePapers/WhitePaper_Commander_English.pdf

Commander Examples:
http://s3.amazonaws.com/SeagullBarTender/ftp/WhitePapers/WhitePaper_CommanderExamples_English.pdf
0
Avatar
Legacy Poster
Comment actions Permalink

Thank you for the answer.
I'M using trigger file already:

%BTW% /AF=C:\LABELS\ZF_DE.btw /D= /PRN="PRTDH40" /R=3 /P /DD
%END%

The Problem is, that I'm not able to defind the "/PRN=" in the label definition. I have one label definiton on a mainframe and just hand date over to Bartender.

What i want to have is a trigger like:

%BTW% /AF=C:\LABELS\WA01.btw /D=<Trigger File Name> /R=3 /P /DD

but add the /PRN=PRINTERNAME based on where the triggerfile was created/found.
Of course i'll have different jobs for monitoring different locations of the trigger files.
0
Avatar
Ian Cummings
Moderator
Comment actions Permalink

So are you using a BarTender command or Commander script? Your last post makes this unclear.

If a BarTender command then simply create a new task for each printer variation looking for the file/folder in the unique way. Then in the BarTender command, specify to which printer triggers that this task picks up should print to.

If using Commander Script then the "system" can write in the name of the printer to use at the time that the trigger is generated.

%BTW% /AF="C:\LABELS\ZF_DE.btw" /D="<Trigger File Name>" /PRN="PRTDH40" /R=3 /P /DD
%END%

*Note that "<Trigger File Name>" is a Commander variable which get replaced with the actual path and filename of the trigger that just got detected and renamed.
0
Avatar
Thilo Schwender
Comment actions Permalink

Is this procedure still working in the 2019R4 version for the Integration Builder or is there a different way to print to different printers, depending on the contents of a text trigger file?

 

Thanks for your help,

Thilo 

0
Avatar
Ian Cummings
Moderator
Comment actions Permalink

Thilo: The use of Commander Script is still supported for legacy purposes.  Instead you should make use of integration variables to assign the printer to use in a dynamic fashion.  It should be noted too that a BarTender document can also data source the printer to use itself, so you could take that approach instead.

I suggest you take a look at the articles and tutorials at our Support Center website: https://support.seagullscientific.com/hc/en-us/categories/204151647-Integration

Please sign in to leave a comment.