2019.2

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.
Note
While you can insert the NodeJS Server Input task anywhere in your process as a
secondary input task, in reality the NodeJS Server Input task will only function when
used as the initial input, as it is triggered when Workflow's NodeJS Server receives a
request and passes it on to the correct task.
Warning
It is highly recommended to make all processes using the NodeJS Server Input task
self-replicating and to reduce their polling interval in the "Process properties" on
page890.
Note
The NodeJS Server Input plugin is not compatible with PlanetPress Capture.
Input
The NodeJS Server Input task does not, by itself, capture any files. Neither does it directly
wait for requests to be received. Actually, it is the NodeJS service that receives the requests
and places them in a specific location on the drive. When a request is received, the NodeJS
Server Input polls that location and finds the requests and all attachments. It will always pick up
the "oldest" request received first.
The request can contain one or more files, one being an XML file containing the request
information as well as any GET, POST, PUT or DELETE variables that were received within
this request. Other files are POST or PUT attachments.
Page 376