2019.2

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 accompanied 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: Not used in PReS Workflow version 2019.2 (see "Known Issues" on
page25).
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.
l
Use custom HTTP server response code: When the process ends and a response is
sent to the requesting client, a custom response code can be specified depending on how
the process goes. While in previous versions the "200 OK" code was always used, this
option overrides it to, for example, "404 Not Found" or "401 Unauthorized".
Note
The response code must start with 3 digits, followed by a space and then the error
message. If the first few characters can't be converted to a valid number, the server
automatically returns "500 Internal Server Error", regardless of the actual response
code provided by the process.
l
Variable containing the response code: The contents of the job information or
local variable selected in this drop-down, presumed to be a valid response code,
will be returned in the response header. This is the value that is present at the end
of the process, not the beginning.
Note
In order to make the Capture OnTheGo app delete the submitted form from the
device's library upon successful transmission of the data, the Workflow process
must return status code 291. The standard 200 response leaves this up to the
Page 367