Cisco Cisco Process Orchestrator 3.0 User Guide

Triggers are events and conditions in the system that can fire off processes. The attributes of the trigger 
that fires off a process instance can be referenced in the process workflow. Processes often use this data 
to control execution. 

Process Orchestrator supports two types of rule-based triggers: 

Events—The Process Orchestrator can monitor for events from the environment, and you can 
specify triggers that initiate processes when the subscribed event occurs. For example, an event 
might be an incoming SNMP trap or a fault on a UCS system.events and schedules.

Schedules—Schedules allow triggering processes at some time by leveraging calendars that define 
which days something can occur. Calendars can be selected days or sequences of dates such as 
weekly or monthly, they can represent dates like fiscal quarter end, or they can be combined 
hierarchically. Schedules then associate a time with a calendar. When the day is in the calendar, the 
time is evaluated. Times can be explicit or repeating (for example, hourly).

The following sections provide information about working with triggers and events:

The following table summarizes some of the more commonly-used types of triggers and when to use 
them. For a complete list of trigger types, see the Adapter Integration and Automation Packs Guide.

AMQP (Advanced Message 
Queuing Protocol)

Use AMQP to create Process Orchestrator triggers for events that occur 
out on the IT landscape for which Cisco does not have adapters, but that 
can generate AMQP messages.