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 User Defined (displayed when User Defined is selected in the Condition Type box)
l MIB OID number: Enter the Management Information Base Object Identifier corresponding to the
object you want to test. Vendors of SNMP compliant devices sometimes list MIB OIDs in their
documentation.
l Test: Click to test communication with the device and the MIB OID number.
l Operator: Select the operator used to test the condition.
l Value: Enter a specific object status. Vendors of SNMP compliant devices sometimes list
possible object states in their documentation.
l Invert condition result: Select to toggle the result of the whole SNMP condition (true becomes
false and vice versa).
Management Information Base Object Identifiers
A Management Information Base (MIB) is a database of Object Identifiers (OIDs) that can be used to monitor
device objects using SNMP. An MIB OID can point be a printer tray, cartridge or hard disk, or to modem
mode. Using an SNMP condition, PlanetPress Workflow can communicate with a device located at a given
IP address and request the status of the object identified by a given MIB OID number. Object Identifiers are
typically assigned and registered by device manufacturers. They are based on a standard known as
Abstract Syntax Notation One (often referred to as the ASN.1 standard).
On Error Tab
The On Error Tab is common to all tasks. Details can be found on " Task Properties Dialog" on page 587.
By default, any action task, branch, splitter or condition that generates an error will simply be ignored, and
the task just under it (not within a branch)will be given control of the job file without any modification. Any
initial input task that generates an error will stop the process from running as a whole, and output tasks will
not generate output. The On Error tab can be used to overwrite the default behaviors.
l Send to Process: Check this option to send the job file to an error management process.
l Error Process drop-down:Enabled only when the Send to Process option is checked. Lists any
process of which the initial input task is the Input Error Bin task.
l Action Group:This group is disabled in the initial input tasks and defaults to Stop Process. In all
other tasks where the On Error tab is present, the following options are available:
l Ignore:The task is ignored as if it did not exist, and the job file is passed on to the next task in
the process.
l Stop Branch:If the task is in a branch of the process, the branch is stopped and the job file is
returned to the process after the branch. The branch will not produce any output.