The Split component should have an option to disabling job renaming. I would suggest disabling that option in this case and whenever you use Split with a loop.
If you do not see that option download the latest version from http://xerox.com/automate
I have run into a challenge here, as you know i can not route by number of pages in a job group, therefor i must split the incoming pdf into 2pp documents which does work however after the document has split 11 times the job fails becouse the job name becoms to long see attached.
What do you think?
The only way this can work is if simplex files have an identifying prefix, which we will have to insist on or else this workflow will not work.
Testing here now i have a workflow which will take and given number of cards any orientation, simplex or duplex and imposes as best as will fit on an SRA3 sheet.
Route by number of pages in a job group, Maybe leave that for future R&D.
Thank you for your imput.
Yes - I see that.
Are the files submitted with a print ticket that indicates simplex vs duplex (or with any other data that may indicate that)?
If so, then you should be able to build a workflow to route the jobs to simplex or duplex splitting. After splitting you can merge all the branches in the workflow and route based on the number of jobs in the job group.
I understand why that would be problematic.
Are all the business cards simplex or duplex? If so, you can use the split component to split up pages into single business card PDFs (send page 1 or 1-2 to one branch and pages 2--1 or -3--1 to the other branch. Take the second branch and loop it back into the split component.
Once you do that you can use the variable for the number of documents in the job group to route the job.
I know that's a bit of a workaround but it will work in a fully automated manner today.
I would like to create a hotfoler that will impose business cards regardless if there is 1 card of 50 cards. I really need the route node to be able to route by number of pages in the job group then i can route to correct imposition.
That's not possible at this point in time.
You would have to either use a series of Collect nodes to release jobs when you have a certain number of pages and then route on the release reason or you would need to join the jobs in the job group into a single PDF and then route based on the number of pages.
Can provide additional details about this scenario?