Cisco Cisco Process Orchestrator 3.0 Guida Utente

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. 

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. 

For example, the global variable customization level is set to Limited. Users change the variable 
value. However, in the updated automation pack, the author no longer allows users to change the 
variable value, because the automation pack must have a particular value. Therefore, the 
customization level is now set to No. 

The object customization level is unchanged, but the schema of the object is changed. The old object 
is now obsolete and needs to be replaced.

To change the customization of an object:

Choose Administration > Automation Pack, highlight the appropriate automation pack, right-click and 
choose Properties.

Click the Objects tab, highlight the appropriate object, then click Settings.

In the Settings dialog box, click the Customizable drop-down list and choose the appropriate option, 
then click OK. 

Use the Circular Dependency Check command to perform an automation pack circular dependency 
check on the selected automation pack.

You can only run this test if you are the “author”.

This command relies on the automation pack dependencies and their dependent automation packs 
dependencies (recursively) to be accurate. The command will not continue if it detects the 
automation pack or its dependent automation pack is not up to date. 

To run this check, choose Administration > Automation Packs, highlight the appropriate automation 
pack (you must be the author), and choose Circular Dependency Check.