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
Omit attachments as CData node in the XML envelope: By default, the request XML
has a CDATA node that contains the raw input data, effectively doubling the size of the
incoming XML file, which due to technical restrictions cannot be larger than 400 MB. This
option allows for much larger (non-binary) attachments by removing them from the XML
data file. Generally attachments are both saved on disk and included as a CDATA node
within the XML envelope. This option removes them from the envelope, but they remain
accessible through their direct path.
Note
Incoming binary files (sent through file upload in a form) can never be larger than
400 MB.
PHP arrays example
This example shows how incoming HTML is converted to XML with the two different PHP-like
Arrays options.
Incoming HTML
<input type="hidden" name="user_account" value="email@example.com">
<input type="text" name="name" value="Peter Parker">
<input type="text" name="company" value="Objectif Lune">
<input type="number" name="pinElm1[pin_0][left]" value="122">
<input type="text" name="pinElm1[pin_0][top]" value="253">
<input type="text" name="pinElm1[pin_0][type]" value="dent">
<input type="text" name="pinElm1[pin_1][left]" value="361">
<input type="text" name="pinElm1[pin_1][top]" value="341">
<input type="text" name="pinElm1[pin_1][type]" value="dent">
Resulting XML Structure with PHP-like arrays
<values count="4">
<user_account>email@example.com</user_account>
<name>Peter Parker</name>
<company>Objectif Lune</company>
<pinElm1>
<pin_0>
<left>122</left>
Page 659