The quantity from the printer destination is only used of you do not supply a quantity via MAX. If you are seeing different behavior then please escalate.
So my idea is valid... I do have a quantity in the MAX file setup, however it keeps setting a default of 1 via the job ticket - It reverts my selection to 'printer default' to '1'. When I select the 'user printer default' it reverts it and I get the notification that I posted earlier.
So in summary, I have a quantity set on the MAX, but the job ticket is overriding and setting the quantity to one. I'm thinking this may need to be elevated...
Here's job ticket handling in a nushell (and glossing over a lot of tail cases):
When jobs are submitted to FFCore they may or may not have any ticketing associated with them.
If they have ticketing associated with them those values, including quantity, those values will override the defaults defined in the printer destination.
So, if the quantity is in a manifest column and the field is mapped then that quantity will be used for printing.
The printer destination value will only be used if the job is submitted to FFCore without a quantity.
To make your scenario work all you really need to do is submit the job with the expected print quantity.
The option you see there is a setting that some DFEs support which tells FFCore to ignore the quantity that was submitted so that a default value from the DFE can be used. That does not seem to be relevant to the scenario you described so I would not bother using it.
As for a third solution, would you see this as viable:
I've setup a simple routing conditional that routes as following:
This works, get the information over to the machine; but...
I'm losing all quantities at the machine even though the quantities are showing up in the job summary pane. I get the following message when going back in to edit the output device (It unchecks use printer default for quantity):
When doing a simple workflow that just utilizes the MAX list, I have a success that includes quantities; it does not however include duplexing or collation. Any advice? I'm so close at this point that I'd hate to have to bugger-off to a new route when the simplicity of this one is actually really nice and straight forward. If I can keep quantities, we'd be right where we want to be.
Ticketing beyond quantity and media would require use of the XPIF File Name to submit a job ticket. You would XPIF need the files somewhere (I would also try exporting them from FFC - put a save node after print). Since you only have 4 variations I would put them on the FFC server and then put the path to the proper file in each manifest row. The quantity and media are merged with the submitted XPIF and that's merged with the defaults at the printer during submission.
Thanks for the reply, Troy. While that is a solution - we are looking for the MAX list to take care of this and avoid using the Job Ticket. There is a variable call of $FFwfDoc.collation$ and $FFwfDoc.sidesImaged$ - I'm wondering how we can incorporate these into usage with the MAX list?
There is a "Build Job Names using Data Fields" that ties the field "$FFJobName$" "Job Name" field. Is there something similar we can do to tie in the collation and sides imaged to be driven from the MAX list?
We do this by creating a 2nd printer destination:
Within your printer node you can use Routing Rules.
Routing Rule 1 looks for a Job Characteristic of Collated, Duplex
Routing Rule 2 looks for a job characteristic of collated, Simplex
Routing Rule 3 is Uncollated Duplex
Routing Rule 4 is Uncollated Simplex
Routing Rule 5 is all other jobs, or you could put this in Routing Rule 4.
Then you have 4 different printer Destinations, and you can set the Collate and Sides imaged in the "Apply Job Ticket Settings" function within the "Edit a Printer destination" screen
Maybe Javier has an easier way?! I look forward to his reply.
Once again - a minor roadblock. Right now, we have a MAX list working in basic format. We are picking up the file, applying paper-type and quantity and it is getting to the iGen through CORE well as can be. However, in an effort to make it even 'better-than-before' I'm trying to incorporate collation and sides imaged.
I've exported some xpf from FFPM and used the xml tags as column headers and used the appropriate call in the xml as the column data to no avail. Is there a certain header in the MAX list that should be used, and a certain response in the data that should be used to denotate collated/non-collated and 1-sided/2-sided?