Packs

Packs are placeholder structures that serve to contain either Actions or plugins to enhance the functionality of your system. Packs have a predefined folder structure.

A Pack that contains Actions is an Action Pack. An Action Pack can contain one or more Actions. You can create your own Action Packs (custom Action packs) or you can download Packs from our marketplace, provided you have a valid CA/Broadcom account.

For more information, see Actions.

Folder Structure

A Pack consists of the following folders:

<PACKAGE_NAME>

Top-level folder containing all Action Pack content
ACTIONS

Actions contained in the Pack.
CONFIG

Static VARA objects, PromptSet objects and any other objects that are 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

Script objects where external, interpreted scripts are stored
SOURCE

Internals for each Action such as sub-workflows, Jobs, Script objects, VARA objects, and so on.
TEMPLATES

Template Workflows, which are registered in the UC_OBJECT_TEMPLATE. Actions from other Packs on which the current Pack depends can also be incorporated into this Folder.

Categories of Packs

Packs and Action Packs are classified in categories to help you identify their purpose. You use the Category field to filter for Packs in the marketplace. You see the category of a Pack in the Packs view of the Administration perspective.

When you create your own Pack (custom Packs, you can assign it a category in its METADATA VARA object.