8.8

Table Of Contents
make the condition False whenever a critical alert is detected, regardless of its type.
Select Non-critical alert to choose a specific non-critical alert in the Detected error
box. Select Critical alert to choose a specific critical alert in the Detected error box.
Select Do not test if you only want to test the printer status (above).
l
Detected error: Select a specific non-critical or critical alert. Note that this box is
only displayed if you selected either Non-critical alert or Critical alert in the Alert
Status box.
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 in the" Task Properties Dialog"
on page777.
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.
Page 417