2018.1
Table Of Contents
- Table of Contents
- Welcome to PReS Workflow 2018.1
- Installation and setup
- Basics
- Features
- About Workflow Configurations
- Workflow Configuration resource files
- About data
- Data Repository
- Debugging and error handling
- About printing
- OL Connect print jobs
- PlanetPress Suite print jobs
- PReS Workflow printer queues
- Shared printer queue properties
- Windows Output printer queue
- LPR Output Printer Queue
- FTP Output Printer Queue
- Send to Folder printer queue
- Triggers
- Load balancing
- Objectif Lune Printer Driver (PS)
- Associating PlanetPress Design documents and PReS printer queues
- About processes and subprocesses
- Using Scripts
- Special workflow types
- About Tasks
- About variables
- Workflow add-ons
- About related programs and services
- The Interface
- Customizing the Workspace
- PReS Workflow Button
- Configuration Components pane
- Components Area Sections
- Process properties
- PlanetPress Design document properties
- 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
- PReS Fax plugin preferences
- FTP Output Service preferences
- PReS Image preferences
- LPR Output preferences
- PrintShop Web Connect Service preferences
- Editor Options
- The Process area
- Zoom in or out within Process Area
- Adding Branches
- Replacing tasks, conditions or branches
- Removing tasks or branches
- Task Properties dialog
- Cutting, copying and pasting tasks and branches
- Moving a task or branch using drag-and-drop
- Disabling tasks and branches
- Resize rows and columns of the Process Area
- Selecting a resource file in task properties
- Highlight a task or branch
- Undo a command
- Redo a command
- The Quick Access Toolbar
- The PReS Workflow Ribbon
- The Task Comments Pane
- Additional Information
- Copyright Information
- Legal Notices and Acknowledgments
Job Information definitions
l
%1 - URL address: Contains the full URL that was requested by the task. This includes
any GET variables in the URL.
On Error Tab
For a description of the options on the On Error tab see "Using the On Error tab" on page82.
Comments Tab
The Comments tab is common to all tasks. It contains a 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.
Check the option Use as step description to display the text next to the icon of the plugin in
the Process area.
HTTP Server Input
HTTP Server Input tasks are used to receive HTTP requests made via GET or POST
commands and to send replies to the servers from which the requests were made. The HTTP
server supports both HTTP and HTTPS. For HTTPS Support information, see HTTP Server
Input User Options.
Note
While you can insert the HTTP Server Input task anywhere in your process as a
secondary input task, in reality the HTTP Server Input task will only function when used
as the initial input, as it is triggered when PReS Workflow HTTP Server receives a
request and passes it on to the correct task.
Note
Athough Workflow can serve both static and dynamic resources to a web browser, it is not meant to
be used as a fully featured web server as it is not built for responsiveness nor guaranteed uptime. It
is recommended to use a common web server (for example, IIS or Apache) to serve your contents
Page 223