Cisco Cisco Process Orchestrator 3.0 Guida Utente

Some use case details include:

Task Assignment—A new user installs and runs the SAP Automation Packs. Automation Pack 
processes create Alerts and Incidents. The user needs to assign the alerts and incidents to individuals 
who own that specific area of SAP. It is difficult to anticipate every way the customer may have 
broken up their SAP management responsibilities within the team. Virtually every customer who 
uses Process Orchestrator for SAP customizes the product for assignments. The user can go to a list 
of Task Rules and create a rule to make the assignment. In this list, they can see what other 
assignments have been made.

Task Notification—Beyond notifications, when an owner is assigned, often the same or separate 
people must be notified in response to incidents. For example, if a job fails that is a financial job, 
perhaps both the technical owner of SAP job management and someone in the financial team should 
be notified; ownership of the incident should not be assigned just to the financial team. Note that 
Cisco’s implementation task rules set a “people to notify” property on the task. The Task Rule 
identifies who to notify and a process would send the actual email.

Change Alert or Incident Severity—Cisco’s SAP automation pack assigns the severity of each 
detected condition when it creates the alerts and incidents. However, customer environments and 
requirements are unpredictable. It is very common for customers to change the severity of their 
alerts and incidents to match the business importance of that issue relative to others in their systems.

Add a Custom Category to a Task—If a user needs to see a certain type of review, alert, or incident 
within a restricted view, categories are a natural way to group these alerts. Default alert categories 
are established in the automation pack, but users might want to add their customized categories to 
Tasks generated by automation packs.

Process Orchestrator allows users to define variables. There are several types.

Global variables span processes. All processes can reference or update them. Process Orchestrator 
often stores data such as performance thresholds in global variables so that customers can edit them 
easily without modifying process definitions, and automation packs can then update processes 
without affecting customer settings. 

Process variables are created from within a process and can be used as a reference value to store or 
pass a value between executions of a process or between steps within a single process. Process 
variables can also be used to collect input parameters from the user or parent process. These 
variables are only available from within the defined process and cannot be accessed or referenced 
by objects outside of the process. 

There are several types of process variables:

Definition variables are created in the process definition and only that process can reference them. 
The value is persistent and shared across instances of that process.

Input variables are also created in the process definition. They specify data (parameters) which can 
be passed into the process. Input variables can optionally be marked as required.

Output variables are also created in the process definition. They specify data which the process can 
return to its caller. 

Local variables are also created in the process definition and only that process can reference them. 
However, a new instance of the variable is established for each process instance, so that one 
instance’s interaction with the variable cannot affect another instance of the process.