Cisco Cisco Process Orchestrator 3.1 用户指南
1-21
Cisco Process Orchestrator 3.1 User Guide
Chapter 1 Introduction
Process Orchestrator System Elements
You can view default assignments, notifications, and properties to be updated according to the following
defined rule types:
defined rule types:
Whenever a task is created, Process Orchestrator goes through the settings and conditions of each task
rule that is listed and enabled. If the conditions and settings in the rule are satisfied, the task rule is
executed.
rule that is listed and enabled. If the conditions and settings in the rule are satisfied, the task rule is
executed.
Note
Task rules are executed according to the order in which they are displayed in the list.
When Task Rules Execute
Task rules can not be manually run by the user. Task rules can only execute when a task is created within
Process Orchestrator processes and rule conditions are met. If the task-created trigger (for any task type)
and rule conditions are met, the action of the task rule is executed in the order in which it is listed in the
Definitions > Task Rules view.
Process Orchestrator processes and rule conditions are met. If the task-created trigger (for any task type)
and rule conditions are met, the action of the task rule is executed in the order in which it is listed in the
Definitions > Task Rules view.
Any processes that are triggered based on a Task Created trigger will only execute after the appropriate
task rules have executed.
task rules have executed.
Task Rules
Example
Assign a task
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.
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.
Send a 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.
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
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.
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
task
If you need 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.
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.