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 PReS 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 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.
Embed/Extract PReS Workflow Metadata
Embed the current PReS Workflow metadata inside the current data file in a PDF emulation. It
can also extract PReS Workflow metadata from the current data file and make the extracted file
the new current metadata file.
Input
A PDFFile, either with no metadata and along with metadata that presumably corresponds to
the PDF file, or a PDFfile with embedded metadata.
Processing
If the Embed option is used, the metadata information is embedded directly into the PDFFile as
binary data. This does not change the way the PDFis viewed by any PDFviewer.
If the Extract option is used, metadata present inside of the PDFfile is extracted from it. If no
metadata is embedded, the task generates an error W3976.
Page 478