8.4
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 8.4.1
- Basics
- Features
- The Nature of PlanetPress Workflow
- About Branches and Conditions
- Configuration Components
- Connect Resources
- About Data
- About Documents
- Debugging and Error Handling
- The Plug-in Bar
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Task Properties
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
l Store the message in variable:Select in which jobinfo, local or global variable you want to store the
message content.
l ID:Enter an error ID. This IDwill be visible in the Windows Event Viewer. However, the IDis not
visible in the PlanetPress Suite Workflow Tools' log file.
l Store the IDin variable:Select in which jobinfo, local or global variable you want to store the error ID.
l Reset to defaults:Resets all options in this tab to their default values.
If storing the message or ID, if they are store in a jobinfo they will be available in any error handling process
where errors are being forwarded. In all cases, if your process continues after the error, the contents of the
variables selected in this window will be available for the rest of your process, or whenever they are
overwritten.
Common Errors
Though some error messages are specific to a task in particular, others may apply to any and all tasks
because they are related more to the system than to PlanetPress itself. Some examples would be W3813,
W3830, W3991, W4005. These correspond to issues such as not having any space to write files, permission
errors on folders or files, etc.
Comments Tab
The Comments tab, added in PlanetPress Suite 7.5, is common to all tasks. It contains a single text area
(Task comments)that lets you write comments about the task. These comments are saved when the dialog
is closed with the OKbutton, and are displayed in The Task Comments Pane.
NewWild Card
For a given Metadata Field Management action, all nodes of a given level mightbe updated with a new
Field Value.To accommodate this,metadata/data selection functions have beenmodified to accept a wild
card parameter "?", indicating the function operates on allnodes (not just one) of a given level.For example,
in a PDF emulation, the format of a selected region is:
region(?,0.59375,2.21875,1.85416,2.51041,KeepCase,NoTrim)
where “?” represents the current physical data page processed by the task.
Limitations
l The name of the metadata field to add must adhere to these syntax rules: start with a letter, followed by
zero or more letters, numbers, underscore or dash. The name is not case-sensitive.