2022.1

Processing
Depending on the options chosen in the HTTP 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.
Output
At 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
HTTP Server Input task: The last output generated by PReS Workflow is sent back to the
initial input, which is returned back to the client (see "Request/process/response cycle" on
page283).
Even if the process ends with a "Delete" on page609 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, which is especially useful for images,
CSS and JavaScript files. See "HTTP Server Input plugin preferences 2" on page803.
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:8080/MakePDF . This is also what your HTML Form's action should be.
l
MIME Type: Select the MIME type of the file that will be returned by the plugin.
Page 680