11-29-2016 11:24 AM
I have a related question. I would like to separate covers and text, adding a split node to separate each. Covers, I would like to split at every 250 "sheets", not pages, imposing them cut & stack on a 17x11 sheet size. "Page size" is 8.5x11. The text of the book, I would like to split at every 500 sheets. This helps bindery when cutting lifts.
I thought that I could set up the imposition node before the split node, that way, the split would be at every 250 sheets, but doesn't seem to work? I can get the split to work nice "before" the imposition node, but then it splits at pages, not sheets. Is there a way I can split at sheets instead of pages?
I would also like to have the option to drop in different page quantities and have Core split correctly. Right now I have branches set up as, 1-250, another branch at 251-500 etc. Javier, In another email related to this subject, you said to set up the first branch of the split node at 1-2000 and the 2nd branch at 2001--1, thus pulling in all pages. You said to connect the 2nd branch back to the split node so as to take jobs at any length. My question is; how do you connect a branch back to it's own split node? I'm confused about this.
Solved! Go to Solution.
11-29-2016 02:29 PM
Note - Assuming that this question http://forum.support.xerox.com/t5/FreeFlow-Core/Ou
is the same as the one in this thread.
Not totally sure that I understand the workflow you are trying to enable.
The previous post you referenced talked about large files with tens or hundreds of thousands of pages.
In that case, you can setup Split (in FFC v5) to divide the file into segments that have a fixed number of pages. You can use the following option to split files into segments with a specific number of sheets
One thing to note - this is based on the number of pages in the PDF.
If the job has 600 pages then the above will split that PDF into 3 files (250, 250 and 100 pages).
The above should function whether you are splitting before of after imposition.
Based on your description, however, it seems that you may be thinking about offseting output stacks at the DFE.
Offsetting every N pages is ususally something that's defined in a DFE queue.
As such, you could setup a DFE queue to offset every 250 pages and another one to offset every 500 pages.
FFCore would then split covers and blocks off from each other, perform whatever imposition was needed and then use the routing in the print component to send jobs to the queue with the required offset.
11-29-2016 03:29 PM
I don't have the option of Split by Segments. The workflow we want to create is to split pages in quantities of 250, or 500 etc. How do I do that if I can't use split by segments. Currently, if I set up branches on a split node at, 1-250, 251-500, 501-750 etc, it will stop after 750 pages. But what if I drop in 2000 pages. I tried 251--1 as the second branch but it did not divide out the final 250 page pdf's.
11-29-2016 03:44 PM
That option was introduced in v220.127.116.11.
I would guess that you are using an earlier version. You should be able to upgrade at no cost as all updates are covered by maintenance.
You should be able to do the same thing in earlier versions using the following settings
You would then connect the second branch back to the split node
11-29-2016 04:08 PM
Is there a variable that I could insert into the Rule Name box on the 2nd branch so that it doesn't put next, nextnext, nextnextnext etc, in the file name. Is there a variable so that it will state in the filename, 1-250, 251-500, 501-750 etc?
11-29-2016 04:31 PM
I would disable job renaming when using loops. It's problematic in that case.
There's no way to dynamically rename the jobs created by split.
However, you can use FFCore variables when saving files to a hot folder (the list of variables are in the Appendix in the Help).
There's a variable for the sequence number in the job group. You should be able to add this to the name to ensure that the documents are printed in the expected sequence.
11-29-2016 04:32 PM
I would also node, the output management license in FFCore enabled FIFO printing which will submit the jobs to the DFE in the job group sequence. If the DFE is configured for FIFO printing (a global setting for FFPS and a queue setting for the Fiery) then the files should print in the required sequence.
11-30-2016 01:43 PM
I cannot find a sequence variable for this.
Could you give me the variable, and where to put it?
Do you put the variable under File Name in the save node? Right now I have $FFwfJob.jobName$ under File Name in the Save node.