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
Input
The current job file.
Processing
The current job file is converted from XML to JSON or from JSON to XML. When converting
from JSON to XML, the encoding of the resulting XML file is always set to UTF-8 (which is the
default format for JSON).
The converted job file gets the appropriate extension (.JSON or .XML).
If the current job file isn't JSON or XML (depending on the type of conversion requested), or if
the conversion fails for any reason, the task raises an error and the current job file and
metadata remain unchanged.
JSON to XML conversion
When a JSON source file contains a single JSON object, that object's key will be used as the
root node name in the resulting XML file, and the root node will be populated with the data
inside of the JSON object. In all other cases, a root node named 'root' will be added to the XML.
It has the property "OL" with the value "RootObject" to define it as an array container. This
property will be ignored when converting from XML to JSON.
Note
In addition to being valid, the JSON should follow naming rules for XML elements. For example,
"adress_line_1:" is a valid key name in JSON, but it cannot be converted to a valid element name in
XML because the colon is reserved for namespaces. For XML naming rules and best naming
practices, see: XML elements on W3Schools.
Output
The output is the modified job file, which replaces the input job file. The metadata are reset.
Page 380