Fiery JobFlow Ticket is a feature in Fiery JobFlow Base that allows users to submit jobs via a simple, text based ticket with which they can define order of jobs, number of copies per jobs, and if jobs should be merged or not.

A Fiery JobFlow Ticket is a text file with comma separated values. Currently Fiery JobFlow supports two columns: job location and number of copies. You do not need to add a header or name the columns. Fiery JobFlow always assumes job location is in column one and number of copies is in column two. You can add comments in the ticket by beginning a line with //. Anything in a comment line will be ignored by Fiery JobFlow. You can tell Fiery JobFlow to merge jobs in a ticket by adding an action. An action is prepended by the # character. Currently Fiery JobFlow only supports the #merge command.

The resources used below can be found at: http://resources.efi.com/jobflow/library.

Example of a ticket to retrieve jobs from a local folder or network location and sets copies per job:

// Filename, NumCopies

c:\folder\Bedding Flowers.pdf,10

c:\folder\Direct Sow Flowers.pdf,10

c:\folder\Flowering Bulbs.pdf,5

\\networkdrive\Roses.pdf,20

Example of a ticket which merges jobs in ticket and sets copies for merged job:

// Filename, NumCopies

#merge,10

c:\folder\Bedding Flowers.pdf

c:\folder\Direct Sow Flowers.pdf

c:\folder\Flowering Bulbs.pdf

\\networkdrive\Roses.pdf

If jobs are merged, Fiery JobFlow automatically adds bookmarks for the first page of every job that is merged . The bookmark title is taken from the job name minus the file extension. These bookmarks can be used in Fiery JobMaster to automatically add tabs.

Example of a ticket which merges jobs in the ticket and sets copies for merged job. Jobs and ticket are submitted as a folder or archive:

// Filename, NumCopies

#merge,10

Bedding Flowers.pdf

Bedding Flowers.pdf

Flowering Bulbs.pdf

Roses.pdf