2018.1
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 2018.1
- Installation and Setup
- Basics
- Features
- The Nature of PlanetPress Workflow
- About data
- Data Repository
- Debugging and Error Handling
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Working With Variables
- About Workflow Configurations
- Workflow Configuration resource files
- About related programs and services
- The Interface
- Customizing the Workspace
- PlanetPress Workflow Button
- Configuration Components pane
- Components Area Sections
- Process properties
- Manipulate Global Variables
- Connect resources
- PPS/PSM Documents
- Associate Documents and PlanetPress Printer Queues
- Using the Clipboard and Drag & Drop
- Renaming objects in the Configuration Components Pane
- Reordering objects in the Configuration Components pane
- Grouping Configuration Components
- Expanding and collapsing categories and groups in the Configuration Component...
- 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
another SMTPserver. In order for this task to receive files, the SMTPServer (also called
"Outgoing Email Server")in the email client must point to PlanetPress Workflow server's IPor
hostname.
Warning
Emails received through this task will not reach their intended destination if the process
does not end with a Send Email Output Task, or contain the PlanetPress Connect
"Create Email Content" on page458 task.
Input
The SMTPInput task does not, by itself, capture any files. Neither does it directly wait for
requests to be received. Actually, it is the SMTPServer service that receives the requests and
places them in a specific location on the drive. When a request is received, the SMTP Input
polls that location and finds the requests and all attachments. It will always pick up the
"oldest"request received.
Warning
In its initial implementation, the SMTPInput task will NOTreceive the BCCaddresses
from most emails sent to it. This is due to a technical limitation that will be resolved in a
future version.
Processing
The task reads the incoming SMTPrequest and provides the data within its body.
Output
Depending on the Data Location option, the output is different:
l Envelope: The request file in XMLformat, including all email fields (from, to, cc, bcc,
subject, body) as well as additional header fields (email client information, attachments,
etc). The message body and attachments are available through specific XMLattributes.
These files do not have the full path, but you can use the %t%O variable to get the current
temporary folder where they are located.
Page 245