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
l If, however, the file is found, then it is loaded with the "Load External File" on page294
task, and then deleted (for the same reasons).
HTTP Brochure Request
This workflow builds on the knowledge acquired in "HTTP PDF Invoice Request" on page180
and uses a single process, but in this case it also uses a PlanetPress Design document which
merges the data received from a browser form with the document to generate a PDF brochure,
which is sent via email.
Resources
l HTTPBrochureRequest.zip (PReS Workflow Configuration)
l InformationBrochure.zip (PlanetPress Design Document)
Installation
l Download both files and unzip them.
l
Open InformationBrochure.pp7 and send it to PReS Workflow.
l
Open HTTPBrochureRequest.pw7 and send the configuration to your local PReS
Workflow service.
l Open your browser to http://localhost:8080/generatebrochure
Task Breakdown
l
The HTTP Server Input receives the initial request from the browser.
l Because this is a demonstration, a backup is made of the XML request. It's not suggested
to do this every time, especially on servers receiving a large number of requests, as these
files do take some amount of space for each request.
l A condition checks whether the form has been submitted, by verifying that one of the
required fields is empty. If it is, it means this is the initial request, so the condition
becomes true.
l If this is the initial request, an HTML page is created which contains a form asking
the client for a required full name and email, and optional company name. A
checkmark also offers to subscribe to a newsletter (it is unchecked by default!). The
Page 182