8.4
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 8.4.1
- 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
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
is closed with the OKbutton, and are displayed in The Task Comments Pane.
Input SOAP
The Input SOAP task is used to answer calls from a remote SOAPclient and to return a response to that
request. It is similar in functionality to the "HTTP Server Input" on page 176 task.
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