2018.2
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 2018.2
- 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
- PlanetPress Workflow printer queues
- Shared printer queue properties
- Windows Output printer queue
- LPR Output Printer Queue
- FTP Output Printer Queue
- Send to Folder printer queue
- Load balancing
- Associating PlanetPress Design documents and PlanetPress printer queues
- Triggers
- Objectif Lune Printer Driver (PS)
- About processes and subprocesses
- Using Scripts
- Special workflow types
- About Tasks
- About variables
- Special workflow types
- About related programs and services
- The user interface
- Customizing the Workspace
- PlanetPress Workflow Button
- Configuration Components pane
- Components Area Sections
- Process properties
- PlanetPress Design document properties
- Moving and copying configuration components
- 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...
- Deleting something from the Configuration Components pane
- 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 plugin preferences 1
- HTTP Server Input plugin preferences 2
- LPD Input plugin preferences
- NodeJS Server Input plugin preferences 1
- NodeJS Server Input plugin preferences 2
- NodeJS Server Input plugin preferences 3
- 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
- Cutting, copying and pasting tasks and branches
- Highlight a task or branch
- Disabling tasks and branches
- Moving a task or branch using drag-and-drop
- Redo a command
- Removing tasks or branches
- Replacing tasks, conditions or branches
- Resizing the rows and columns of the Process area
- Undo a command
- Zoom in or out within Process Area
- The Quick Access Toolbar
- The PlanetPress Workflow Ribbon
- The Task Comments Pane
- Additional Information
- Copyright Information
- Legal Notices and Acknowledgements
replicating process polls its source once, determines the number of files to process, then
replicates itself up to the maximum allowed and treats the files simultaneously. The initial
process runs again once it has completed itself and replicates again as necessary, until all files
have been processed.
You can either create a regular process that is set to be self-replicating from the start (see
"Creating a process" on the next page) or change a regular process into a self-replicating
process and vice versa (see "Process properties" on page668).
Processes in a configuration (except startup processes) will always run concurrently. You can
schedule processes to run only at certain times or intervals via their properties (see "Process
properties" on page668).
Regular and startup processes can be set to be Active (process runs normally) or Inactive
(process will not run at all); see "Activating or deactivating a process" on page119.
Startup processes
Startup processes run only once before every other process in a given configuration. They can
be used to perform operations that need to be completed once before the configuration can
actually be run, such as to map network drives.
The order in which the Startup processes are arranged in the Configuration Components pane
determines, from top to bottom, the order in which the Startup processes are executed when the
Workflow Service launches. To learn how to reorder processes see: "Reordering objects in the
Configuration Components pane" on page644.
Startup processes always run sequentially.
To learn how to create a startup process see: "Adding a startup process" on the facing page.
Subprocesses
Subprocesses are special processes that can be called by any other process. Subprocesses
act exactly as subroutines in programming languages, allowing users to reuse existing
processes by sharing them to the whole configuration file. They can thus be used to perform
redundant operations that may need to be executed numerous times; for instance, archiving a
copy of a zipped file received as the input job file, then decompressing it before sending the
unzipped version of it back to the calling process.
To learn how to create a subprocess see: "Adding a subprocess" on the facing page.
Page 114