2020.1

Note
Athough Workflow can serve both static and dynamic resources to a web browser, it is
not meant to be used as a fully featured web server as it is not built for responsiveness
nor guaranteed uptime. It is recommended to use a common web server (for example, IIS
or Apache) to serve your contents and to let Workflow process things only it can do.
For more information on how to serve HTML and PDF generated by Connect through IIS,
watch the Connect with Evie - IIS series.
Warning
It is highly recommended to make all processes using the HTTP Server Input task self-
replicating and to reduce their polling interval in the "Process properties" on page853.
Examples
This task is put into effect in the following example processes:
l HTTP PDF Invoice Request
l HTTP Brochure Request
l Capture Web Manager Workflow
Note that Capture can only be used with PlanetPress Suite.
Known issue
In order to wake up a trigger-based process that starts with the HTTP Server Input task the
server issues a signal to all trigger-based processes, not just those that start with an HTTP
Server Input task. This means that some processes may get woken up when they do not need
to. This issue only occurs in version 2020.1 and will be fixed in version 2020.2.
Input
The HTTP Server Input task does not, by itself, capture any files. Neither does it directly wait
for requests to be received. Actually, it is the HTTP service that receives the requests and
places them in a specific location on the drive. When a request is received, the HTTP Server
Input polls that location and finds the requests and all attachments. It will always pick up the
"oldest" request received.
Page 331