About Packs

A Pack is an optional set of functionality for a specific topic to be used on top of the Automation Platform. It ranges from modifying windows services up to complex workflow templates for deployments of enterprise applications. Some Packs even include their own user interface within the AWI:

Depending on the functionality provided by a package, a combination of the following artifacts is contained in the package:

Implementation source
Configuration settings and configuration files
Templates
Actions
Variable objects
Documentation
Binaries needed to execute the actions (libraries)
Custom types
Roll-back capability
Snapshot capability for the environment or application server the package is designed for

Actions Packs

What are Action Packs?

Action Packs are outbound integrations with third-party products such as Amazon S3, Docker and Tomcat for automation purposes. They group actions that are related to each other (for example, Windows File System Actions).

Packs Folder Structure

<PACKAGE_NAME>
Top-level folder containing all Action Pack content.
ACTIONS

An Action contains workflows for the Pack that has been created (or a link to the referenced workflow).
CONFIG

Contains static VARA objects or other objects used to store the configuration.
DOCUMENTATION

Documentation objects containing license and pack documentation.
RESOURCES

Pack resources that are used across multiple Actions.
INTERPRETERS

Storage object containing binaries of external interpreters.
LIBS
Storage object containing binaries such as Java jar files or compiled libraries.
SCRIPTS
Storage objects containing external, interpreted scripts.
SOURCE
Contains the internals for each Action such as sub-workflows, jobs, scripts objects, VARA objects and so on.
TEMPLATES
Contains template workflows, which are registered in the UC_OBJECT_TEMPLATE. Actions from other Packs the current Pack is dependent on can also be incorporated into this Folder.