2022.2

misinterpretation. If the original file name is needed, it can be found in the original attrib-
ute 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.
Caution: 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 attach-
ment. 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 inform-
ation 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 selec-
tions; see "Variable task properties" on page289.
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".
l
Send immediate response to client: Do not wait for the process to finish and send a static
HTML or Text file back to the client instead. This prevents any timeout from occurring.
l
Response file: Select which file to return. Note that the file name doesn't have to be static.
You can use any combination of text, variables and data selections; see "Variable task
properties" on page289.
l
Use custom HTTP server response code: When the process ends and a response is sent to
the requesting client, a custom response code can be specified depending on how the process
goes; for example: "200 OK", "404 Not Found" or "401 Unauthorized".
Choose a response code between 100 and 599. (See: List of HTTP status codes on Wikipedia.) If
the response isn't currently handled by any HTTP response code, you may use an unused code
Page 332