Cisco Cisco Process Orchestrator 3.1 User Guide

Page of 786
 
13-61
Cisco Process Orchestrator 3.1 User Guide
 
Appendix 13      Using Adapters
  Core Adapter
  –
Comparison—Selected operator used to evaluate the expression
  –
Expression—Expression associated with the selected operator
Defining the Create Automation Summary Activity
An automation summary is a record of process execution. The automation summary includes 
information about the events that trigger processes, activities that were executed, and the data retrieved 
by the executed activities.
Use the Create Automation Summary activity to specify the activities in the process for which an 
automation summary should be generated. To generate the data output, select the activity and then 
specify the section in the automation summary in which to output the data.
The share path specified in the Core Functions Adapter properties will be used when viewing the 
automation summary reports.
If the automation summary is set to not be shared, then only local users on the Process Orchestrator 
server computer will have access to the automation summary report. The automation summary will not 
display for users with remote access, such as those accessing Process Orchestrator from the Web Console 
or the remote client, unless a UNC share or IIS Virtual directory sharing options have been selected.
Step 1
In the Process Editor Toolbox, choose Core Activities > Create Automation Summary, then drag and 
drop the activity onto the Workflow pane.
Step 2
Click the General tab and enter the required information.
Step 3
Click the Automation Summary tab to define the properties specific to the activity, including:
  •
Automation summary style sheet—Select the type of template to be used for the automation 
summary. 
  –
Table of Configuration Properties
  –
Situation Analysis Report (default)
  •
Include the following items—Select the activity or trigger/event, since events and triggers can be 
included into the automation summary as well, and specify the section of the automation summary 
to include the reporting details and whether the activity is the root cause of any issues that are 
detected.
  –
Name—Name of the activities that are included in the process
  –
Section—Name of the section of the automation summary where the data will be stored
  –
Root cause—Yes indicates the Is the root cause check box is checked
  •
Section—Specify the section of the automation summary template in which to export the data:
  –
SituationAnalysis—After a situation that requires action is identified, the state and diagnostic 
information is displayed in the Situation Analysis section of the automation summary.
  –
ContextAnalysis—After a situation is analyzed in context with other situations, the symptom 
and cause is displayed in the Context Analysis section of the automation summary.
  •
Is the root cause—List the activity or event at the top of the automation summary, or identified as 
the root cause of the problem.
  •
Last instance information only—Indicate that the automation summary must include only 
information for the latest execution of the activity instance.