7.4

l Loop each attachment as a data file: When receiving attachments through a POSTrequest (HTMLForm), this
option will make the HTTPServer Input task loop through each attachment. Each data file is an XMLwith the accom-
panied file.
l Do not include XMLenvelope:Only active when the previous Loop option is checked. When checked, the
XMLfile containing the request data will not be available. Only the attachment itself is sent as a data file.
l Respond on error: Enter a message to be sent to the client as the output file if the process encounters an error and is
unable to send a reply that includes the actual output file. The information can be in any desired format such as
HTMLor plain text, but most browsers will interpret it as plain text.
l Send immediate response to client:Do not wait for the process to finish and send a static HTMLor Text file back
to the client instead. This prevents any timeout from occurring. When checking this option, the field under the option is
used to select which file to return.
"Other" Tab
l Job Information group
l Information elements:indicates what job infos are automatically created by the input task.
l Add lines before first data page:Using the arrows keys you can add any job information directly at the
beginning of your data file.
l Backup input files:Check this to save a copy of each data file that is captured by your input. These files are saved in
the PlanetPress Suite Workflow Tools working folders under the "Backup"folder.
l Backup filename:Enter the filename that you wish the input data file backup to be saved under.
l Delete Existing Metadata:Check to remove any metadata from memory. This option is disabled on initial input
tasks, and is checked by default on secondary input tasks.
Examples &Use Cases
This task is put into effect in the following use cases and example processes:
l HTTP PDF Invoice Request
l HTTP Brochure Request
l Capture Web Manager Workflow
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.
Input Error Bin
The Input Error Bin Task is used specifically and only to create error management processes. These processes do not run
on their own but are rather triggered by the "On Error"tab of tasks in other processes, when that task fails.