Maintain of the print queue

[JavierM-Xerox]

Ask - replied a little too fast - thought it was still the customer. The hotline will have details. Ken should be able to dig them up as well.

[JavierM-Xerox]

I am not sure about details. I asked your account team to call the hotline and get the detailed info.

[Piotr Miller]

---

That should do the trick in terms of having FFCore submit in the sequence in which jobs are received. This will impact performance but it is done via a change config file so it can be done / undone in a few minutes and should be acceptable for the short term.

Which config file I should edi t to change it? 

[JavierM-Xerox]

There's another option which may be acceptable as a short term workaround:

Change the number of concurrent jobs FFCore processes to 1 at a time. This will serialize execution and should result in FFCore submitting jobs in the order in which they are defined during submission (Manifest sequence, alphabetic order for zip files, or order in submit job UI).

That should do the trick in terms of having FFCore submit in the sequence in which jobs are received. This will impact performance but it is done via a change config file so it can be done / undone in a few minutes and should be acceptable for the short term.

[JavierM-Xerox]

That was a typo - SET is the solutions engagement team:

usa-setops@xerox.com
888.878.9622

They can help with customizations to extend the functionality in our products - including FFCore.

[qbema]

Is SET part of FFCore ?

[JavierM-Xerox]

Typically FFC would save the files locally and once everything was saved the external component in the workflow would submit the files to a FIFO queue one at a time with a script. That will retain the sequence defined in the manifest.

[qbema]

I'm affraid I do not understand what you mean... Can you be mor precise ?

From my perspective document should be send to the printer in the sequence specified in MAX (csv) file. 

It looks like the FFCore process all documents parallel, and send to the printer ASAP it finish processing. So the less complex documents goes before the more complex... I do not believe that SAVE option and External component will give a proper solution when we use different workflows for one hotfolder...

Regarding the idea of MAX (csv) files, mixing the document orders DESTROYS (!!!) hole idea of it... 

Please get into my shoes:

We print a variety of photo product (a lot of them), we group them by size and types to get it easier with finishing. We also add some raports on top of group of prints to be aware what prints starts and end where (in the stock). If the raports gets out before all other documents, and the types of document come out mixed, so please be so kind to come here and sort it out by hands...

[JavierM-Xerox]

SET would not replace FFCore. Instead they would build something atop of FFCore so the workflow ends with Save, Join and External components vs a Print component.

[qbema]

Option 'ONE' is not a solution. We do print with different types of papers on the first two pages, and the document has different quantity of pages, so it we would join all documents it would be hardly possible to set which page should be printed on which type of paper.

I will try to get in touch with our accoount team and get in touch with SET...

Mixing the CSV print order makes FF Core worthless for us :((