2021.2

Action names are not case sensitive.
l
MIME Type: Select the MIME type of the file that will be returned by the plugin.
l
Form Data Encoding: Specifies how this endpoint will interpret any form data received
by the web server.
Even though it is strongly recommended to use the <meta charset="utf-8"/> element in
web pages, some might use another encoding or not have the element at all, affecting the
character set used by the browser to send the parameters and file names.
l
System language: Sets the encoding attribute in the request XML file to the system
codepage (e.g. Windows-1252).
l
UTF-8: Causes all parameters as well as file names from the request to be
interpreted as a UTF-8 text stream.
With this option enabled, POST attachment file names will be randomized on disk to
avoid misinterpretation. If the original file name is needed, it can be found in the
original attribute of the file tag in the request XML.
Note
If form data are submitted from HTML files that are made with the OLConnect
software, you can expect them to be UTF-8 encoded.
Warning
Don't use any non-ASCII characters in Workflow's working directories path (in
the V8WorkingDirectory registry key). Combined with the UTF-8 Form
Data Encoding setting, this might make it impossible for Workflow to retrieve
files from that path, depending on the actual path name and the system locale.
l
Loop each attachment as a data file: When receiving attachments through a POST
request (HTML Form), this option will make the NodeJS Server Input task loop through
each attachment. Each data file is an XML with the accompanied file.
Page 357