Cisco Cisco Process Orchestrator 3.0 Guida Utente

Process Event

Process events allow one process to pass an event to other processes. For 
example:

A Raise Process Event activity can post a process event, and a 
trigger can monitor for a specific event. 

A Correlate Process Events activity allows monitoring for an event 
within a process workflow. 

Process events include elements of the Process Orchestrator functional 
model so that they are aware of internal schema elements. For example, 
you can include a target type in your subscription criteria.

Process events are exposed in the northbound web service, so an external 
system can programmatically submit an event to Process Orchestrator. 
However, the use cases for process events generally center more around 
Process Orchestrator-internal use cases; Advanced Message Queuing 
Protocol (AMQP) is preferred for external message passing.

For internal use cases, process events have the advantage because they 
are native and lightweight within Process Orchestrator. It is easy to 
create message driven architectures within Process Orchestrator using 
process events. Since these events are not persisted to the database, they 
are very lightweight. Process events have the advantage that they do not 
require external setup and installation, as would be the case with AMQP.

Started by Parent Process 

Indicates that a process can be used by a parent process. If this trigger is 
not set in the child process, the parent process will fail.

The information used to start the child process can also be included in 
the automation summary. 

Started by User 

Indicates that the process can be started manually by a user. This trigger 
is added by default to a process, but can be removed. 

If a user attempts to manually start a process that does not have the 
ad-hoc trigger (or the user is restricted from starting the process in the 
ad-hoc trigger), an error message will be displayed and the process will 
not be launched.

This trigger will expose all the typical trigger properties, as well as some 
additional properties that allow you to determine exactly how the 
process was manually started.

Started by Web Service

Indicates that the process can be started using the Northbound Web 
Services. For more information, see the Cisco Process Orchestrator 
Northbound Web Services Guide.

Task Event

All task events are monitored by the Process Orchestrator environment. 
A user can create a trigger that can watch for any task event (task 
created, task deleted, task updated) that matches the user-specified 
criteria. 

For more information about tasks, see