2022.2

Note: While you can insert the NodeJS Server Input task anywhere in your process as a sec-
ondary input task, in reality the NodeJS Server Input task will only function when used as the ini-
tial input, as it is triggered when Workflow's NodeJS Server receives a request and passes it on
to the correct task.
Caution: 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721.
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 loc-
ation 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.
The NodeJS Server Input task supports basic content-types: multipart/form-data, application/x-www-
urlencoded, and application/octet-stream, as well as raw body content-types:
l
text/plain (.txt)
l
application/xml, text/xml (.xml)
l
text/html (.html)
l
application/xhtml+xml (.xhtml)
l
text/css (.css)
l
text/csv (.csv)
l
application/json (.json)
l
application/javascript (.js)
Note that the maximum number of multipart form data fields is 1000 by default.
Processing
Depending on the options chosen in the NodeJS Server Input task properties, the task may choose to
ignore some of the files. For example, using the "Do not include XML envelope" means that only the
Page 329