2020.2

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.
l
Do not include XML envelope: Only active when the previous Loop option is
checked. When checked, the XML file containing the request data will not be
available. Only the attachment itself is sent as a data file.
l
Respond on error: Enter a message to be sent to the client as the output file if the
process encounters an error and is unable to send a reply that includes the actual output
file. The information can be in any desired format such as HTML or plain text. However, if
it must be displayed in a browser, the format should match the selected MIME type.
This is a variable property box. You can use any combination of text, variables and data
selections; see "Variable task properties" on page304.
Note
This option requires every plugin in the process to be explicitly set to "On Error:
Stop process" (see ), even if the process itself is set to "On Error: Stop process".
Page 359