Automation package basics
Automation packages contain automations and instructions for robots to execute. The robotic developer creates and deploys automations in Pega Robot Studio and includes instructions about which application the robots should access and what information to retrieve and update within the application. The automation package typically contains several automations that an organization requires to achieve a specific business objective.
To access the packages, in the navigation pane of Pega Robot Manager, click Packages, as shown in the following figure:
The Packages landing page displays information about available versions, assignments, and active configuration, as shown in the following figure:
Publication and use of automation packages
When the robotic developer deploys the project, Robot Studio publishes the automation package to a Package Repository or a Package Server. At the same time, the system posts the metadata to Robot Manager, providing information about available package versions. After publication, the Robot Manager administrator can assign the package to an individual user, a group of users, or a workgroup of robots. Based on the package assignment, Robot Runtime downloads the corresponding package to the workstation of the user.
The following figure presents an example of the package deployment and usage process:
Note: When you build automations with Robot Studio version 19.1, you deploy your package to a Package Server or Package Repository. As a best practice, deploy your package to a Package Repository for automations built with Pega Robot Studio version 22.1.
Automation package versions
Deployment versions of automation packages provide consistent labeling so that you can track the project versions used by your robots. When a developer deploys the project in Robot Studio, the system assigns the version number to the deployed package file. The version number consists of the major and minor versions.
Package assignment group
The package assignment group points to a specific automation package version and is used to associate users or robots with the automations included in the package. The package assignment group contains information about the runtime version used to create the package. If the robotic developer included environment overrides in the package, they are displayed in the package assignment group details. The first time the robotic developer deploys the package, Robot Manager creates a Default package assignment group. You can rename the default package assignment group or create a new one from the package details page by clicking Actions > Manage Package assignment groups, as shown in the following figure:
For more information about creating a package assignment, see Selecting package versions.
You can create and maintain one or more package assignment groups for a single package version.
Package association
The package association links the package assignment group with robots, departments, or individual users. You can automatically assign the packages to multiple users by defining your organization's hierarchy. For more information, see Organizational structure and hierarchy.
In the following image, click the + icons to learn more about package assignment groups and associations:
Check your knowledge with the following interaction:
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?