Cisco Cisco Process Orchestrator 3.1 사용자 가이드

다운로드
페이지 786
 
3-11
Cisco Process Orchestrator 3.1 User Guide
 
Chapter 3      Managing Automation Packs
  Controlling the Customization of Automation Pack Elements
  •
Raising the quality of packaged automation and automation created by Cisco Services, delivery 
partners, or customers.
  •
Tuning preferred checks per automation pack. Style checkers can be turned on or off based on need. 
For example, automation packs developed for in-house use might want to turn off some style 
checkers (such as target, or users included in automation pack).
  •
Embedded help for identified issues. Help topics notify users why a style check is added, and what 
the consequences might be if the warning is not resolved.
To run a style checker against an automation pack:
Step 1
Choose Administration > Automation Pack, highlight the appropriate automation pack, right-click and 
choose Properties.
Step 2
Click the Style Checker Selection tab to select the rules you want to validate against an automation pack 
(see 
Step 3
To start the validation process, you can either:
  •
Right-click on the automation pack and choose Validate from the context menu. 
  •
On the Process Editor, choose File > Validate to display the Style Checkers Selection dialog box.
Note that:
  •
The automation pack validation action can be run on-demand or at export.
  •
This menu item is disabled if you click an automation pack that you did not create.
  •
Validation of an automation pack could take several minutes. 
Step 4
Click OK. The process validator will start processing the selected validation rules against the current 
process. 
Controlling the Customization of Automation Pack Elements
Use the Settings dialog box to define the customization settings for the objects included in an automation 
pack. These settings can only be modified by the automation pack author. 
Note
This functionality (the Settings dialog box and Customization settings) is not available on “Community” 
automation packs; anyone can modify objects in those types of automation packs. For more information, 
see 
When the automation pack author imports a newer version of the automation pack, the objects in the 
automation pack will replace the objects in the database.
When a third-party user imports a newer version of the automation pack, the customization setting of an 
object will determine whether user-customized values will be preserved.
The following are instances where an object customization will be lost:
  •
The author of the object no longer allows users to customize the object. Any customization of the 
object will be lost on upgrade.