This document describes the creation and usage of Automation Summaries in Cisco Process Orchestrator (CPO).
Cisco recommends that you have knowledge of general process authoring in CPO.
The information in this document is based on Cisco Process Orchestrator version 3.0 or later.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
What are Automation Summaries?
Automation Summaries are XML-based documents which CPO can produce and share that hold information about the output of activities in a process that has run. These Automation Summries can be shared through UNC share or Virtual Directory. By default they are kept in the system for 30 days before they are removed, but that time limit can be configured to be longer or shorter.
Automation Summary Use
Automation Summaries should be used to send the output of processes to a large audience or to save the output of a process, particularly when the process instances and activity instances are not archived. They can also be the vital report attached to a ITIL incident or alert.
How to Create an Automation Summary
Complete these steps:
Either drag and drop a Create Automation Summary, Create Incident, or Create Alert activity into your process.
If you use the Create Automation Sumary, then skip to step 4. If you used the others, go to step 3.
After you drop a Create Incident or Create Alert, go to the automation summary tab and choose to create one.
On the Automation Summary configuration tab, you should choose the activities in the box that you wish to report on and for each one with the new analysis styles you want. You can also choose for only one activity to be the root cause.
If you choose an activitiy to be the root cause, then it is copied to the top of the automation summary.
Upon running the process, the automation summary is created and stored in the share setup that was configured. Normally it is good practice to email this link out as part of the process or give the end user someway to know of its existance.