2018.2

l
Store current iteration in Job Info #: The Job Info in which the loop's iteration should be
stored. Useful for sequential file names or conditions based on the iteration. The value of
this Variable Properties box should be a digit between 1 and 9 (see "Job Info variables"
on page557).
l
Use value of Variable/Job Info # expression: If the contents of the previous option is a
variable, its content (which is assumed to be a number between 1 and 9) will be used to
determine which Job Info number to use for the iteration number. For example if %
{myvariable} is used and contains the value 9, then Job Info 9 will store the value of the
loop's iteration.
l
Use original Data Stream every time: Select to reuse the original job file received by the
Loop action task at every iteration. If this option is not selected and if the process ends
with a Printer Queue Output task, for example, the second time the Loop action task will
be performed, it will use the PostScript file generated by the output task.
On Error Tab
For a description of the options on the On Error tab see "Using the On Error tab" on page88.
Comments Tab
The Comments tab is common to all tasks. It contains a text area (Task comments) that lets
you write comments about the task. These comments are saved when the dialog is closed with
the OK button, and are displayed in the Task Comments Pane.
Check the option Use as step description to display the text next to the icon of the plugin in
the Process area.
Run Script
Run Script tasks are used to run scripts that typically perform some kind of processing on the
job file received by the task. Scripts are often simpler to write than programs added with the
External Program action (see "External Program" on page332). However, they can be slower
to execute.
The Run Script task can be used either as an Action or a Condition. When dragging and
dropping a Run Script task on a given process, you select whether to use this task as an Action
or a Condition from a contextual menu.
Page 389