8.5
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 8.5
- System Requirements
- Basics
- Features
- The Nature of PlanetPress Workflow
- About Branches and Conditions
- Configuration Components
- Connect Resources
- About Data
- About Documents
- Debugging and Error Handling
- The Plug-in Bar
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Task Properties
- Variable Properties
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
If the Send Immediate Response to clientoption 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 HTTPServer Input task:The last output generated by PlanetPress
Workflow is sent back to the initial input, which is returned back to the client.
Note
Starting in version 7.2 of PlanetPress Workflow, you can now serve static resources through
PlanetPress, which is especially useful for images, CSSand JavaScript files. See "HTTPServer Input
2 User Options" on page645.
HTTP Server input task properties are as follows:
l
HTTP action: Enter the name of the action requested of PlanetPress Workflow by the client. This
name corresponds to the URLthat 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 HTMLForm's action should be.
l
MIME Type: Select the MIME type that best suits the files PlanetPress Workflow will be receiving as
input.
l
Loop each attachment as a data file: When receiving attachments through a POSTrequest
(HTMLForm), this option will make the HTTPServer Input task loop through each attachment. Each
data file is an XMLwith the accompanied file.
l Do not include XMLenvelope:Only active when the previous Loop option is checked. When
checked, the XMLfile 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 HTMLor plain text, but most browsers will interpret it as plain text.
l
Send immediate response to client:Do not wait for the process to finish and send a static HTMLor
Text file back to the client instead. This prevents any timeout from occurring. When checking this
option, the field under the option is used to select which file to return.
l Use custom HTTPserver 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.
While in previous versions the "200 OK"code was always used, this option overrides it to, for