Fiery Command WorkStation

Fiery JobFlow Help v2.9

Hide or show navigationPrevious topicNext topicSharePrintPDF

Connect Packages settings

Connect Packages are archived zipped folders that have the required components to run a script. Connect Packages simplify the use of third-party application scripts.

You can import a Connect Package as a resource to Fiery JobFlow. Each Connect Package that is imported is displayed as an option in the Connect Packages list.

Note: A Connect Package (.zip) cannot be exported.

Select the Connect Packages radio button and choose a script from the list. All components required to run this script are pre-defined. Click the Change variables link to update additional parameters. Internal parameters such as runtime, relative runtime, option, and so on are not displayed in the Fiery JobFlow interface.

Connect Packages support Master Variables. You can use Master Variables to override and update the module's default settings and rename the jobs in the workflow. For information, see Master Variables.

With Fiery JobFlow 2.8 and later, in the Connect module, you can rename jobs using Master Variables. This helps to easily identify the job on the Fiery server.

Note: The updated job name is displayed only in the Fiery server, but in Fiery JobFlow, the original job name is retained.

Script settings

Select the Script radio button, and enter the location of the script you want to use.

To support user-defined scripts, Fiery JobFlow provides all the necessary information required to process a job using a script. Fiery JobFlow provides the following arguments:

  1. Input Location: A temporary location where Fiery JobFlow will make the file available for processing.
  2. Output Location: A temporary location where Fiery JobFlow waits for the processed file to be copied.
  3. Job Name: The job name as shown in Fiery JobFlow.
  4. Workflow Name: The name of the workflow where the script was initiated.
  5. Preflight Name: Location of the last preflight report generated in that workflow.
  6. Vault: A temporary location that exists while a job is being processed in a workflow.
  7. Next Module ID: The internal ID for the next module in the workflow. The Next Module ID is required for Master Variables.

Arguments do not have names and you must tell the script in what order to interpret the arguments.

If there is an error executing a script on a job, Fiery JobFlow provides a link to an error log in the Error Jobs pane of the Jobs tab. Fiery JobFlow does not provide information on how to correct the script. The skilled user should be able to use the information provided in the log to correct the script.

Hot Folder settings

The first use of the Connect module is through hot folders. Select the Hot Folder radio button, and specify the location of the input hot folder (where to move the job) and the output hot folder (where the result is placed). You can also specify a limit for the processing time, to prevent Fiery JobFlow from waiting endlessly for a job to show up. The input and output locations are relative to the Fiery JobFlow server. Fiery JobFlow copies the job to the specified input folder. After the action is applied, the job is placed in the specified output folder with the same job name.

In the following example, the input and output locations are hot folders on the Fiery JobFlow server:

c:\hotfolders\input

c:\hotfolders\output

Network locations are supported by using the standard Windows notation for network locations:

\\server\hotfolders\input

\\server\hotfolders\output

Note: The Hot Folder in the Connect module is not a Fiery Hot Folder.
Parent topic: Connect