Cisco Cisco Process Orchestrator 3.0 Guida Utente

Process Orchestrator Automation Package files include processes and other objects for Process 
Orchestrator. The defined automation packs included with the product are located in the install directory 
on the machine where the product was installed. Individual-created automation packs can be exported 
and reimported on an as-needed basis. 

Each exportable object in Process Orchestrator supports at least two customization settings; you can tune 
these settings to control what customers can edit (see 

No—The object is not customizable.

Limited—Some object properties can be customized. The extent to which properties are 
customizable varies by object type; the controls for any non-customizable (immutable) property will 
be read-only. Most objects default to Limited.

Processes have three customization settings:

No—Users have no process editing capabilities.

Limited—This is the default setting, under which users can make the following changes:

Change the execution and archival option.

Change the default target and default runtime user.

Change the process input variable value. Users cannot add or create process variables (input or 
output), only the value of the input variables.

Add new triggers to the process.

Enable/disable existing triggers. Users cannot remove triggers from the process.

Add category (assuming the category customization setting is set to limited).

Remove category that is added by users (assuming the category customization setting is set to 
limited).

Workflow—Users have near full control to edit processes with this setting. Under the Workflow 
setting, in addition to the above, users can make the following changes:

Edit the process workflow. If the process shipped with some workflow, defined users can delete 
the existing workflow (activities).

Create process local or definition variables.

Delete process variables they have created.

Users cannot:

Delete the process

Change the input or output variables. Input and output variables are the API or the contract 
between parent and child process.

Change the name, description, target type, or runtime user that the process can run against.

The best practice for authors, then, is to plan extension points. Most processes that an author ships in an 
automation pack would be locked down. Authors design specific points of extension, and embed calls to 
processes with workflow customization enabled for these extension points. The workflow for these 
extension point processes would be empty.