Cisco Cisco Process Orchestrator 3.0 Guía Del Usuario
11-4
Cisco Process Orchestrator User Guide
OL-30196-01
Chapter 11 Authoring Custom Automation Packs
Creating an Automation Pack
Note
You cannot export a process from an automation pack you do not own. Therefore, instead of creating
your extension in the extension point itself, call a child process where you code the logic. In other words,
the contents of an extension point should simply be an invocation of child processes, not activities within
the extension point workflow. In this way, you can ship an automation pack with your extension.
However, the call to this process must be coded into the extension point in each development, test, and
production system.
your extension in the extension point itself, call a child process where you code the logic. In other words,
the contents of an extension point should simply be an invocation of child processes, not activities within
the extension point workflow. In this way, you can ship an automation pack with your extension.
However, the call to this process must be coded into the extension point in each development, test, and
production system.
Recommendations
•
The functionality authored to extend the solution should be defined in terms of child processes, not
activities within the workflow of the extension point.
activities within the workflow of the extension point.
•
It should be exported separately from solution-packaged automation packs
•
The functionality authored to extend the solution should be imported separately from
solution-packaged content and stitched into the solution extension points.
solution-packaged content and stitched into the solution extension points.
•
By passing target objects rather than specific parameters in to extension points, your automation
becomes more extensible from a data perspective as well. For example, someone can come along
and add more properties to some target type, and if the target is passed through to the extension
point, this data is available.
becomes more extensible from a data perspective as well. For example, someone can come along
and add more properties to some target type, and if the target is passed through to the extension
point, this data is available.
•
If XML is passed into a process request, it is a good idea to make this XML available to extension
points as well, so that they are open to extension. Moreover, the child processes in the extension
point can modify the target properties.
points as well, so that they are open to extension. Moreover, the child processes in the extension
point can modify the target properties.
Before You Begin
You must have Process Orchestrator Administrator privileges to create an automation pack.
To create an automation pack:
Step 1
Choose Administration > Automation Pack, right-click and choose New > Automation Pack.
Step 2
In the New Automation Pack Properties property sheet, click the General tab, then enter the required
information.
information.
Note
For information about the field parameters for this dialog, see the online help.
Step 3
If the automation pack file is a community automation pack, click the About tab, then check
Community Automation Pack. This lets anyone modify and export this automation pack.
Community Automation Pack. This lets anyone modify and export this automation pack.
Note
The Community Automation Pack checkbox is available only during automation pack creation,
and cannot be turned on or off later. Use this feature with caution; it is mostly suitable if the
author has no plans for maintaining and releasing new versions, and wants to post this
automation pack as an “open source”.
and cannot be turned on or off later. Use this feature with caution; it is mostly suitable if the
author has no plans for maintaining and releasing new versions, and wants to post this
automation pack as an “open source”.
Step 4
Click the Objects tab to add objects to the automation pack.