2019.1

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741 and "Resulting XML structure with
Enhanced PHP-like arrays" on page742.
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.
If the Send Immediate Response to client option is selected, the response file is sent back
right away and the involvement of the input task ends then.
However, if this option is not checked, it means there is a second output that comes out of the
NodeJS Server Input task: the last output generated by PReS Workflow is sent back to the
initial input, by which it is returned to the client.
Even if the process ends with a Delete task, it is still returned to the client; deleting the job file
only means you are not doing anything with it locally.
Note
You can serve static resources through PReS Workflow, which is especially useful for
images, CSS and JavaScript files. See "NodeJS Server Input plugin preferences 2" on
page747.
Task properties
General Tab
l
HTTP action: Enter the name of the action requested of PReS Workflow by the client.
This name corresponds to the URL that the client will be accessing. For example, if you
enter "MakePDF" here, you could trigger the process by accessing
http://127.0.0.1:9090/MakePDF . This is also what your HTML Form's action should be.
Page 333