Thank you Javier. I tried adding zero's to 1 - 9 and that also works.
Thank you very much,
When I set the routing to job name ends with 19, it imposes it 9up. Even though I put 19, not 9. BUT, when I write in, job name ends with nineteen, it imposes it 19 up. Whats up with that???
Everything is set perfectly, just like 1-10. Then why doesn't 11-19 work? 20 works fine. 20 is 20 up. This is unbelievable,
Very Very frustrating. I am working this method, and it works great until I get to number 11. Numbers 1-10 are 1up, 2up, 3up etc, according to the number that I place at the end of the file name. When it gets to the file with the filename 11 at the end, the business card is only 2up. 14 is 4up, 15 is 5up etc. Under routing rules I put, 15, but it's only using the 5?
Here's a simplified version of this workflow
The route component will evaluate the job name (which is based on the filename) to send the job to one of 1 Insert pages components
Each of the rows in this layout maps to a branch in the workflow.
The job characteristics for the route component evaluate the job name (in this case the number of repetitions in the layout is at the end of the filename / job name)
The insert pages components duplicates all job pages and adds them to the document after each set of contiguous pages
Each insert pages components duplicates a different set of pagfes (in the above case 2 sets of pages are inserted so the document is put 3x in the layout).
After each document is duplicated, the files in the job group are joined into a single file which is then imposed.
The Page Order should be set to Cut & Stack with the number of sheets set to 1.
Once that's configured, the only other requirement is to submit the jobs you want to impose together as a job group.
Thank you very much Javier.
Is it possible for you to give me a more detailed scenerio of the first example that you showed me.
There are multiple ways in which this could be done.
the above will require that the workflow contain routingnbranches for every possible quantity which should be workable since the most you would duplicate is the max number of pages in the layout.
as with the above this will require submission of a group of jobs that will fill a layout
optionally, after duplicating pages you can split jobs into single page jobs and collect jobs until you have a specific number of pages. This will
the downside of the last item is that you will have to ensure the queue has the required print quantity set as a hard coded value since the duplication will adjust the quantity to 1.
Alternatively, you could use a script to restore the quantity to the print ticket (this should be fairly simple to implement in the external component)
there re are other ways to do thesis as well but the above should be workable.
Example: I have 2 business cards that I want to impose on the same sheet. Because of the differences in quantity for each card, I need to impose business card 1, 5up on a 18x12 sheet, and card 2, 15up on the same sheet. What I would like to do is use the Routing Component to set up a 1up - 18 up set of Branches, so then as business cards come in, all I have to do is type in how many up on the file name, and they will impose the correct number up on a sheet.
Example: I receive a job with 4 business cards.
Business card 1, I want 4up.
Business card 2, I want 3up.
Business card 3, I want 6up.
Business card 4, I want 7up.
These need to be all on the same sheet.