8.8
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 8.8
- System Requirements
- Basics
- Features
- The Nature of PlanetPress Workflow
- About Branches and Conditions
- Configuration Components
- Connect Resources
- About Data
- Data Repository
- About Documents
- Debugging and Error Handling
- The Plug-in Bar
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Working With Variables
- About Configurations
- About related programs and services
- The Interface
- Customizing the Workspace
- PlanetPress Workflow Button
- The Configuration Components Pane
- Components Area Sections
- Processes and Subprocesses
- Manipulate Global Variables
- Connect Resources
- PPS/PSM Documents
- Associate Documents and PlanetPress Printer Queues
- Using the Clipboard and Drag & Drop
- Rename Objects in the Configuration Components Pane
- Reorder Objects in the Configuration Components Pane
- Grouping Configuration Components
- Expand and Collapse Categories and Groups in the Configuration Components Pane
- Delete Objects and Groups from the Configuration Components Pane
- Other Dialogs
- The Debug Information Pane
- The Message Area Pane
- The Object Inspector Pane
- The Plug-in Bar
- Preferences
- Other Preferences and Settings
- General appearance preferences
- Object Inspector appearance preferences
- Configuration Components Pane appearance preferences
- Default Configuration behavior preferences
- Notification Messages behavior preferences
- Sample Data behavior preferences
- Network behavior preferences
- PlanetPress Capture preferences
- OL Connect preferences
- PDF Text Extraction Tolerance Factors
- General and logging preferences
- Messenger plugin preferences
- HTTP Server Input 1 plugin preferences
- HTTP Server Input 2 plugin preferences
- LPD Input plugin preferences
- Serial Input plugin preferences
- Telnet Input plugin preferences
- PlanetPress Fax plugin preferences
- FTP Output Service preferences
- PlanetPress Image preferences
- LPR Output preferences
- PrintShop Web Connect Service preferences
- Editor Options
- The Process Area
- Zoom In or Out within Process Area
- Adding Tasks
- Adding Branches
- Edit a Task
- Replacing Tasks, Conditions or Branches
- Remove Tasks or Branches
- Task Properties Dialog
- Cutting, Copying and Pasting Tasks and Branches
- Moving a Task or Branch Using Drag-and-Drop
- Ignoring Tasks and Branches
- Resize Rows and Columns of the Process Area
- Selecting Documents in Tasks Links
- Highlight a Task or Branch
- Undo a Command
- Redo a Command
- The Quick Access Toolbar
- The PlanetPress Workflow Ribbon
- The Task Comments Pane
- Additional Information
- Copyright Information
- Legal Notices and Acknowledgements
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 plugin preferences" on page756.
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 of the file that will be returned by the plugin.
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 example, "404 Not Found"or "401 Unauthorized".
l Variable containing the response code:The contents of the job information or
local variable selected in this drop-down, presumed to be a valid response code,
Page 230