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
Input
The HTTPServer Input task does not, by itself, capture any files. Neither does it directly wait
for requests to be received. Actually, it is the HTTPservice that receives the requests and
places them in a specific location on the drive. When a request is received, the HTTPServer
Input polls that location and finds the requests and all attachments. It will always pick up the
"oldest"request received.
The request can contain one or more files, one being an XMLfile containing the request
information as well as any GETor POSTvariables that were received within this request. Other
files are POSTattachments.
Note
By default, the request XMLalso contains a CDATAsection which contains the raw input
data, effectively doubling the size of the incoming file. Due to technical restrictions, the
incoming XMLfile cannot be more than 400MB, which because of CDATA is reduced to
around 200MB. To help in this situation, you may elect to omit CDATA from the
attachment, which can be changed in HTTP Server Input User Options. Please note that
incoming binary files (sent through file upload in a form) can never be larger than 400MB.
Processing
Depending on the options chosen in the HTTPServer Input task properties, the task may
choose to ignore some of the files. For example, using the "Do not include
XMLenvelope"means that only the POSTattachments will be used in the process, the
XMLfile 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
First, the output inside the process itself is, depending on the selected options, an XMLrequest
files, POSTAttachments files, either one or both.
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
Page 229