8.7
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 8.7.1
- 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
- Task Properties
- Variable Properties
- 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
- PlanetPressFax 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
This task does not poll any location by itself. It sits there waiting for requests coming in through
WSDL(SOAPcommunication)and, when it receives a request, runs the process and returns
the last output generated by the process to the client.
Processing
No processing is done. The request that is received by this task is XML and it is maintained as
such.
Output
As with the HTTPServer Input, this task has a dual-output purpose. First, when the initial input
task is run, the XMLrequest is output onto the process. Then, when the process is finished, the
last job file generated by the process is returned to the requesting client.
Technical
SOAPcommunication is non-trivial and requires a certain understanding of XMLand the
SOAPprotocol. Using the SOAPtasks pre-supposes this knowledge and this
documentation does not attempt to provide it.
The Input SOAP Task only responds to a single SOAPaction by the client:SubmitJob. Within
this request however, a secondary action (SubmitSOAPActionName)can be specified - this is
what the SOAPAction corresponds to in this task's properties.
General Tab
l
SOAP Action: The SOAP action is used with the SubmitJob action. It’s the equivalent of
the process name. The difference is that more than one processes can share the same
SOAP action. That way more than 1 CPU can be used to process all the incoming
requests however this means that all process sharing the same SOAP action must be
identical because there is no way to decide the execution order of all the process.
Page 229