process some jobs, wait for user input to inject the others
Posted: Fri Aug 29, 2014 7:11 pm
Hi,
I'm trying to create a workflow for this scenario:
All jobs are flat single file jobs in one incoming queue. Each job has 3 pdf files:
- order sheet PDF
- box (the packaging) PDF
- content (the product itself) PDF
Naming is strict as follows:
AAA_BBBB_CCC_DDDDDDDDDD_E_F.pdf
AAA: product-type (box, content_a, content_b, order-sheet)
BBBB: product variant (used to determine the printing process)
CCC: ascending number for order
DDDDDDDD: barcode -ordernumber (printed on the box itself)
E: reserved
F: reserved
the products should be routed through different output channels according to their variant-type (BBBB). Therefore I currently use a static pattern based output scheme. A lookup table or simply a script-hint that sets the according output queue for Fiery would be great.
Product types order-sheet and box should be immediately processed, the others should wait for the box.
My idea is to use Switch Client to generate a dummy-job. The operator should scan the barcode (DDDDDDDDDDD, in every filename) and inject the corresponding job for processing. So the content of each box is produced after scanning its box.
Attached the Workflow idea here.
Any help welcome!
regards,
Ralf Gebhard
I'm trying to create a workflow for this scenario:
All jobs are flat single file jobs in one incoming queue. Each job has 3 pdf files:
- order sheet PDF
- box (the packaging) PDF
- content (the product itself) PDF
Naming is strict as follows:
AAA_BBBB_CCC_DDDDDDDDDD_E_F.pdf
AAA: product-type (box, content_a, content_b, order-sheet)
BBBB: product variant (used to determine the printing process)
CCC: ascending number for order
DDDDDDDD: barcode -ordernumber (printed on the box itself)
E: reserved
F: reserved
the products should be routed through different output channels according to their variant-type (BBBB). Therefore I currently use a static pattern based output scheme. A lookup table or simply a script-hint that sets the according output queue for Fiery would be great.
Product types order-sheet and box should be immediately processed, the others should wait for the box.
My idea is to use Switch Client to generate a dummy-job. The operator should scan the barcode (DDDDDDDDDDD, in every filename) and inject the corresponding job for processing. So the content of each box is produced after scanning its box.
Attached the Workflow idea here.
Any help welcome!
regards,
Ralf Gebhard