8.8
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 8.8
- System Requirements
- Basics
- Features
- The Nature of PlanetPress Workflow
- About Branches and Conditions
- Configuration Components
- Connect Resources
- About Data
- Data Repository
- About Documents
- Debugging and Error Handling
- The Plug-in Bar
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Working With Variables
- About Configurations
- About related programs and services
- The Interface
- Customizing the Workspace
- PlanetPress Workflow Button
- The Configuration Components Pane
- Components Area Sections
- Processes and Subprocesses
- Manipulate Global Variables
- Connect Resources
- PPS/PSM Documents
- Associate Documents and PlanetPress Printer Queues
- Using the Clipboard and Drag & Drop
- Rename Objects in the Configuration Components Pane
- Reorder Objects in the Configuration Components Pane
- Grouping Configuration Components
- Expand and Collapse Categories and Groups in the Configuration Components Pane
- 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
- PlanetPress Fax plugin preferences
- FTP Output Service preferences
- PlanetPress Image preferences
- LPR Output preferences
- PrintShop Web Connect Service preferences
- Editor Options
- The Process Area
- Zoom In or Out within Process Area
- Adding Tasks
- Adding Branches
- Edit a Task
- Replacing Tasks, Conditions or Branches
- Remove Tasks or Branches
- Task Properties Dialog
- Cutting, Copying and Pasting Tasks and Branches
- Moving a Task or Branch Using Drag-and-Drop
- Ignoring Tasks and Branches
- Resize Rows and Columns of the Process Area
- Selecting Documents in Tasks Links
- Highlight a Task or Branch
- Undo a Command
- Redo a Command
- The Quick Access Toolbar
- The PlanetPress Workflow Ribbon
- The Task Comments Pane
- Additional Information
- Copyright Information
- Legal Notices and Acknowledgements
l
Character per inch (CPI): The number of individual characters per inch on a line of
text.
l
Line per inch (LPI): The number of lines of text per inch.
XML/JSON Conversion
The XML/JSON Action task converts an XML job file to JSON or a JSON job file to XML.
This task makes parsing XML/JSON files much simpler in a JavaScript environment and also
allows processes to natively send JSON to a Connect template or data mapping configuration.
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 ':' is forbidden in XML element names.
Page 365