8.6

Table Of Contents
l
Store the message in variable:Select in which jobinfo, local or global variable you
want to store the message content.
l
ID:Enter an error ID. This IDwill be visible in the Windows Event Viewer. However, the
IDis not visible in the PlanetPress Workflow log file.
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 PlanetPress 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.
Metadata to PDI
The Metadata to PDItask takes the active metadata and generates a PDI using the information
in that metadata. It is generally used in conjunction with a PDFdata file and is used to generate
the PDIfile which is used by PlanetPress Search when building, refreshing or rebuilding its
database.
Input
This task can use any data file, as long as it is accompanied by metadata. This metadata may
have been directly generated or could be extracted from a PDFusing the Embed and Extract
PlanetPress Workflow Metadata task.
Page 497