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
Common Errors
Though some error messages are specific to a task in particular, others may apply to any and all tasks
because they are related more to the system than to PlanetPress itself. Some examples would be W3813,
W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission
errors on folders or files, etc.
Comments Tab
The Comments tab is common to all tasks. It contains a single text area (Task comments)that lets you
write comments about the task. These comments are saved when the dialog 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 page202 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