8.6

Table Of Contents
l
Store the IDin variable:Select in which jobinfo, local or global variable you want to
store the error ID.
l Reset to defaults:Resets all options in this tab to their default values.
When storing the message or ID, if they are stored in a jobinfo they will be available in any
error handling process where errors are being forwarded. If your process continues after the
error, the contents of the variables selected in this window will be available to the rest of your
process, or as long as they are not 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 PReS itself. Some examples
would be W3813, W3830, W3991, W4005. These correspond to issues such as not having any
space to write files, permission errors on folders or files, etc.
Comments Tab
The Comments tab 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.
Notes
l Microsoft Word must be installed on PReS Workflow system.
l Microsoft Word must not be currently opened when the automation task runs.
l Microsoft Word 2003 and up are supported.
l The task uses a printer queue set with the “PReS Word to PDF Printer driver, which is
created and set by default on-the-fly the first time a Microsoft® Word® Document to
PDFaction task is run. This printer cannot be shared on the network in order to avoid
confusion from network users, however it is shared between all Microsoft® Word®
Document to PDFaction tasks on the same system.
l While debugging this task, the printer shows the message that the document can not be
printed. This message is normal and will not appear when running a live configuration.
l If using a Microsoft® database such as Access® or Excel®, each software must be
installed in the same version. For example, using Microsoft® Wor 2007 with a
Microsof Access® 2003 database will cause the task to fail.
Page 423