2021.2

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
COTG user or the expiry date of the form.
"Other" Tab
l
Job Information group
l
Information elements: Indicates what Job Info variables 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 Workflow Tools working folders under
the "Backup" folder.
To navigate quickly to the Workflow working folders, press the keyboard shortcut
Page 334