Is it possible when making an output preset in designer to use a field from the XML and create a job name using that field. Currently when I print jobs through the workflow they come out with static names and would like some way to identify them. I am new to Planetpress and am still learning. Thanks!
Yep!
However, the fields from your data mapping are not immediately available to the output preset. You’ll have to do a bit of setup to pass them through.
First, you’ll need to create a Job Preset that creates metadata. Specificaly, you’ll be looking to add ‘Field Metadata’ which will let you pick from the various first level fields of your datamapper for inclusion.
For a bit more depth on that, see the help guide on Job Creation Presets: PReS Connect 2018.2 User Guide
One last note on the Job Preset: It matters where you place your metadata. Note that there are various levels of metadata (Job Tags, Job Segment Tags, Document Set Tags, etc). If you set something in the Job Tags section of metadata, the same value will be used for the entire job set. So if you want a different value for each document, you’ll need to set the tag in the Documents tags.
Now, on to your Output Preset where you’ll actually make use of that metadata. First, the variable reference: PReS Connect 2018.2 User Guide
The link above contains a list of variables available to you for output. For example, if you set a Field Metadata in your Document Tags, you’re going to call it like this:
${document.metadata.propertyname}
Note (and the documentation stresses this too) a document level metadata tag is only available to you if you are also separating by document.
Is there a way of calling back to this data without using the “Print to Directory” option in the output presets? This is the only place that I see an option to make a Job Output Mask. I am however trying to do the LPR Queue option which only allows me to put a Job Name and doesn’t seem to accept the callbacks.
Sure, the Job Name field in LPR output accepts these values too. You just don’t have the fancy editor like you see in the Job Output Mask for Folder Output.
In fact, you’ll note that in a default output preset, the Job Name field is already populated with one such variable: ${template}
So for example, this preset:
With this data:
Gets me this on my printer:
Note that I’m using a document level metadata tag. This only works because I’ve also set Document Level Separation as well. Without that separation level, the job fails with an error. I only have the one record in my data, so I only end up with a single print job at the printer. But if I had had multiple records, I would have had one print job for each and the numbers would have incremented for each because of the ${file.nr} in my Job Name.
The problem I am having is that I am only sending one document with multiple records. Which causes this naming convention to not work, it errors out every time. Is there any workaround for this?