2019.1
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 2019.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
- 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
- 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 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
- 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
- Knowledge Base
- Legal Notices and Acknowledgements
Note
When the data mapping configuration provides multiple records, the preview
is created based on the first record.
Note
The Create Preview PDF plugin cannot parse Workflow automation variables.
Instead it uses the default values set up in the Preprocessor of the data mapping
configuration.
To work around this issue you could either convert the posted data file into JSON,
add the variables and use the JSON string option in the Create Preview PDF
plugin, or you could add the variables to the data file and let the data mapping
configuration extract them.
Another alternative would be to use the "All In One" on page524 task.
l
JSON string sets the data source to a JSON string (see "Using JSON" on the next page).
A text area is shown allowing the user to enter the JSON string.
The JSON string may contain local and global variables, Job Infos and data selections
(see "JSON string samples" on the next page).
A single variable can be used, assuming that the respective variable contains a JSON
string.
In case the JSON string is not a valid JSON object, the plugin will error out with an explicit
message.
Note
This option requires that keys in the JSON string have matching field names in the
data model of the template. When they have, the JSON values are passed to the
template and the personalization scripts of the template will have access to the
values through the record's data fields. (See the Designer help: Adding Variable
Data).
Page 543