Use the Automation Orchestrator Client to create, export, and import packages. Packages can be used to export workflow objects for use on other Automation Orchestrator instances.

Packages can contain workflows, actions, policies, configuration elements, or resources elements.

When you add an element to a package, Automation Orchestrator checks for dependencies and adds any dependent elements to the package. For example, if you add a workflow that uses actions or other workflows, Automation Orchestrator adds those actions and workflows to the package.

Note: Automation Orchestrator dependencies added to a package can also include commented out code. For example, a workflow can include a line of code referencing an action that is commented out. In such a scenario, the action is added to the package regardless. The addition of commented out code in the package is expected behavior.

When you import a package, the server compares the versions of the different elements of its contents to matching local elements. The comparison shows the differences in versions between the local and imported elements. The user can decide whether to import the package, or can select specific elements to import.

For most objects created in the Automation Orchestrator Client, aside from resource elements, packages are the only way to export and import these objects.

Packages use digital rights management to control how the receiving server can use the contents of the package. Automation Orchestrator signs packages and encrypts the packages for data protection. Packages can track which users export and redistribute elements by using X509 certificates.