Split File into Separate Files by Trim Size

[RRD_Jeff]

That did it Thank you.

[StefanT-Xerox · Accepted solution]

As you pointed out it seems that the Trim Size value in the Job Properties window after Split is the same for all pages, and is taken from the first page of the incoming pdf. I noticed that placing an Imposition after Split will update the Trim Size. Try placing an imposition between Split and Route to see if that gives you what you want. Something like Repeated 1x1 on Automatic Sheet Size.

[RRD_Jeff]

OK so I guess I do it manualy.

[DavidU54339-XRX]

Using MAX submission on can designated a job group using the parameters $FFOrder ID$ and $FFGroup key$.

Unfortunately, my proposed solution is a Hotfolder job submission -- not a MAX submission. Each Hotfolder submission is a separate job.

You could keep the job submissions in order using the Collect node. The Collect node has the ability to delay release of a job via the Release Condition of "Time since last job was Collected". One could set the delay(s) differently after the Route node for the different branches.

[RRD_Jeff]

That may work is there a way to have a hot folder do the same thing as "Submit All Documents as a Job Group".

Because I want the files that are split in the first process put together in 1 file for each size and kept in order.

[DavidU54339-XRX]

If I understand what you are trying to accomplish, one solution would be to have save nodes after splitting and routing by split job name. The save node locations would be hotfolder locations. These hotfolders would have different workflows associated with them for the desired operations.

[RRD_Jeff]

So in my case I am splitting the document into individual pages but it looks like the route is looking at the original Document not the split document being passed to it. I that Case the Split is usless.

I have split this Workflow into 2 seperate workflows
1) I split pages.
2) I take the output from split Pages and pass the PDFs to the Route and combine using "Submit All Documents as a Job Group".

That woks perfectly but doubles the work and that is not why we purchased an Automation Product.

[StefanT-Xerox]

From the Help Guide:

Impose Relative to
This option defines the PDF box used for imposition, using the PDF Box Selection Behavior.

Note: Size is defined based on the size of the selected box in the first page of the document.

[RRD_Jeff]

FF Core V5.4.3

I am reciving a single file with 3 diferent Trim Sizes. 

In my Workflow I have a split (Segments, Divide into FixedPage Segments), Number of Pages 1.
it then Goes into a Route Buy Trim Size (With setting for the 3 Trim Sizes). Then each Route gets merged and saved to a file with the size appended to the name. The file I get is 1 with all the pages in 1 file. So not splitting or not reading the trim for each individual page. Does FF Core read only 1 trim size for the file or does it read it for the page?

I tested the split as a seperate Workflow, and it worked, I then sent the individual files and that also worked.