Cisco Cisco Process Orchestrator 3.1 User Guide
1-20
Cisco Process Orchestrator 3.1 User Guide
Chapter 1 Introduction
Process Orchestrator System Elements
4.
The Remedy automation pack can synchronize data between the systems and when the incident
reaches a terminating state in the Remedy system, the incident in Process Orchestrator is then
automatically synchronized.
reaches a terminating state in the Remedy system, the incident in Process Orchestrator is then
automatically synchronized.
5.
When the incident in Process Orchestrator is closed, if the process in the network best practice
automation pack blocked, it can continue. For example, the process might go on to prove that the
problem that generated the incident in fact no longer manifests, closing the loop to prove that the
remediation did in fact fix the problem.
automation pack blocked, it can continue. For example, the process might go on to prove that the
problem that generated the incident in fact no longer manifests, closing the loop to prove that the
remediation did in fact fix the problem.
With this abstraction, the network best practice automation pack does not need to be dependent on the
specifics of which service desk is involved, and no dependency exists between the automation packs.
specifics of which service desk is involved, and no dependency exists between the automation packs.
Human Interactions
Human interaction tasks are steps in a workflow where a human needs to take action. They include the
following types of tasks:
following types of tasks:
•
Approval tasks consist of steps where the workflow needs someone’s indication of what route to
take. They may be simple yes or no questions, or they might give any arbitrary set of choices.
take. They may be simple yes or no questions, or they might give any arbitrary set of choices.
•
Guided Operation tasks consist of steps in a workflow that someone must perform manually. For
example, a step in a network automation workflow might be to replace a cable. While this step
cannot be automated, it might be a small part of an overall workflow that can be automated.
example, a step in a network automation workflow might be to replace a cable. While this step
cannot be automated, it might be a small part of an overall workflow that can be automated.
•
Review tasks allow the assignment of a document or automation summary review. When someone
indicates the review is complete, the workflow can continue. Moreover, the person who indicated
they completed the review is recorded in auditing. Many systems might send a notification to let
someone know that they need to, for example, look at a report, but do not close the loop to see that
the review actually occurred. Process Orchestrator allows closing the loop.
indicates the review is complete, the workflow can continue. Moreover, the person who indicated
they completed the review is recorded in auditing. Many systems might send a notification to let
someone know that they need to, for example, look at a report, but do not close the loop to see that
the review actually occurred. Process Orchestrator allows closing the loop.
•
Input Request tasks allow gathering data as the workflow executes.
Task Rules
Task rules provide a list of rules that act on new tasks or task changes to handle cases such as
assignments, changing alert or incident severities, or setting customer-specific categories on tasks. By
defining a task rule, you can tune the content you receive to your specific company without having to
edit processes in the automation pack. By performing these actions by rule, one change can affect tasks
created by multiple processes. For example, you can assign all SAP Incidents to a single person with a
single rule.
assignments, changing alert or incident severities, or setting customer-specific categories on tasks. By
defining a task rule, you can tune the content you receive to your specific company without having to
edit processes in the automation pack. By performing these actions by rule, one change can affect tasks
created by multiple processes. For example, you can assign all SAP Incidents to a single person with a
single rule.