2018.2

Note
Currently the NodeJS Server Input task only supports basic content-types:
l multipart/form-data
l application/x-www-urlencoded
l application/octet-stream
Any raw body content-type (application/json, application/xml, text/html or any other not
mentioned above) might not behave as expected and will be supported in the next
version.
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 POST attachments will be used in the process; the XML file will be
discarded. Attachments are always saved on disk in a specific location, which is accessible
either directly in the XML or directly as a data file through the "Loop each attachment as data
file" option.
How arrays in input data are interpreted
When the names of Form inputs in an incoming POST request contain two pairs of square
brackets: [][], the data are interpreted as an array. The value between the first pair of square
brackets is expected to consist of two parts, separated by an underscore (e.g. row_0). The first
part is considered to be the element's name. All content after the first underscore (preferably an
integer) will be used as index, which is given as an attribute of the element (e.g. <row _idx=0>).
This makes it easy to select all elements on the same level in a data mapping configuration,
and to convert the XML to a JSON object.
For an example see "Incoming HTML" on page706 and "Resulting XML structure with
Enhanced PHP-like arrays" on page707.
Output
First, the output inside the process itself is, depending on the selected options, an XML request
file, POST Attachments files, either one or both.
Page 273