8.5
Table Of Contents
- Table of Contents
- Welcome to PlanetPress Workflow 8.5
- System Requirements
- 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
- Variable Properties
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
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 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.
Metadata Fields Management
The Metadata Fields Management task can be used to add new fields into your metadata, either for every
element or through conditions.
Note
This task will automatically "loop" through the metadata and repeat its action for each of your
metadata's datapage. This task should not be placed after a Metadata Sequencer.
Input
Any data file with accompanying metadata.
Processing
Fields are added, removed, modified, etc, according to the actions defined in the task properties. If the field
is present in a level that repeats (for example, the data page level), this task loops so that the action may
take place on each of the occurrence of that level.