Cisco Cisco Process Orchestrator 3.1 User Guide
1-22
Cisco Process Orchestrator 3.1 User Guide
Chapter 1 Introduction
Process Orchestrator System Elements
Notifications
In addition to notifications that occur when a user is assigned, often the same or other people must be
notified in response to a task. The task rule notification identifies which person or group to notify and a
process emails the notice.
notified in response to a task. The task rule notification identifies which person or group to notify and a
process emails the notice.
Each task contains a list of notification recipients in addition to task assignees. The notification task rule
adds to this list of notification recipients. A process can react to a task create event or task change event
and then appropriately notify the notification recipients by email or any other mechanism.
adds to this list of notification recipients. A process can react to a task create event or task change event
and then appropriately notify the notification recipients by email or any other mechanism.
Automation Pack Rule Management
Task rules can be included in automation packs to easily transfer default task rules from one system to
another, such as transferring task rules from a development system into a test or production system.
another, such as transferring task rules from a development system into a test or production system.
Some Cisco automation packs include not only processes that generate tasks, but also separate processes
that handle notifications. You can create task rules to manage these objects without editing the process
or task so that your customization to the tasks occurs before these notification processes run.
that handle notifications. You can create task rules to manage these objects without editing the process
or task so that your customization to the tasks occurs before these notification processes run.
Triggers
Process instances can come into existence in the following ways:
•
A process can be invoked manually.
•
A process can be invoked by another process.
•
A trigger can fire, which initiates the process.
•
A process can be invoked using the northbound web service.
Triggers are events and conditions in the system that determine how or when the process will be
executed. Multiple triggers can be added that can be initiated when certain conditions are met.
executed. Multiple triggers can be added that can be initiated when certain conditions are met.
Process Orchestrator supports two types of rule-based triggers: events and schedules.
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 stop
trap or a fault on a UCS system.
initiate processes when the subscribed event occurs. For example, an event might be an incoming stop
trap or a fault on a UCS system.
Schedules
Schedules allow triggering processes at some time by leveraging another object called a calendar.
Calendars 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).
Calendars 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).