7.5

l Number of iterations: The number of times the loop should be repeated. Every task after the Loop Action Task will
be repeated this number of times. The number may be static, or use a variables (see Variable Properties).
l Store current iteration in Job Info #: The Job Info in which the loop's iteration should be stored. Useful for
sequential filenames or conditions based on the iteration. The value of this Variable Properties box should be a digit
between 1 and 9.
l Use value of Variable/JobInfo # expression:If the contents of the previous option is a variable, it's 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 iter-
ation 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 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
The On Error Tab is common to all tasks. Details can be found on Task Properties Dialog.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process where errors are
being forwarded. In all cases, if your process continues after the error, the contents of the variables selected in this window
will be available for the rest of your process, or whenever they are overwritten.
Common Errors
Though some error messages are specific to a task in particular, others may apply to any and all tasks because they are
related more to the system than to PlanetPress itself. Some examples would be W3813, W3830, W3991, W4005. These cor-
respond to issues such as not having any space to write files, permission errors on folders or files, etc.
Comments Tab
The Comments tab, added in PlanetPress Suite 7.5, is common to all tasks. It contains a single 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.
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). However,
they can be slower to execute.
The Run Script action task can be used either as an action or a condition. When dragging and dropping a Run Script action task
on a given process, you select whether to use this task as an action or a condition from a contextual menu.
For more information on scripts, what languages are supported and how to write scripts and conditions, please see the related
chapter, Using Scripts.
Input
Any data file, in any format.
Processing
The script is executed. The script can modify anything such as the data file, job infos, metadata, or even other files on the oper-
ating system.