7.4

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.
Digital Action
Digital Action action tasks generates the same types of documents generated by PlanetPress Image output tasks. Since Digital
Action tasks are not output tasks, the documents they create are typically passed on to the following task. The image files they
generate are always saved, along with their index files (if any), to an archive folder.
The Digital Action task requires a PlanetPress Imaging license to be present on the same IPSubnet as PlanetPress
Workflow, either on the same server or a different one with PlanetPress Image installed and activated.
Differences between Digital Action and Image tasks:
l Digital Action is an Action Task and cannot be the last task in a branch or process. Image is an output task, and has to
be placed at the end of a process or branch.
l In PlanetPress Workflow 7.2.4 and older, Digital Action does not update the PlanetPress Search Database, even if a
PDIis generated and even if the option is checked in the preferences. This behavior was changed starting in Plan-
etPress Workflow 7.3.
l Digital Action can accept PostScript (.ps)files as an input, even if they are not generated by any PlanetPress tools.
Task Properties
General tab
l Host: Select the IP address of the PlanetPress Image host to which you want the request to be sent.
l Refresh: Click to update the list of IP addresses displayed in the Host drop-down list box.
l Documents: Select a specific PlanetPress Design document if you want all the jobs to be generated with that doc-
ument. To use a document chosen at runtime for each job, enter a dynamic document name using a combination of
text, variables and data selections. To enable the dynamic document name box, click inside it. To disable it, press
Enter. Note that in the later case, you must be certain that the documents that will be chosen at runtime will in fact be
available locally or at the selected host.
While the Do not use a document (passthrough)is visible in this list, it is not compatible with the PlanetPress
Image output if the PostScript was not generated by merging a design document with data in PlanetPRess
Workflow. In order to generate an image in passthrough mode with external PostScript, please use the Digital
Action task.
l List only documents using VDXcompilation:Check to ensure that only documents that are compatible with the
VDXcompilation method are shown in the list, if producing VDXoutput.
l Run mode group
l Printer centric: Select to send the document along with the trigger and data to PlanetPress Image.
l Optimized PostScript Stream: Select to merge the selected document with the data received by this task
before sending it to PlanetPress Image. Note that some features, such as the Time and Date PlanetPress Talk
functions, require that this option be selected.