Automation package basics
To successfully automate a task, a robot must first load an automation package that contains the instructions necessary to run the automation.These instructions could include a list of applications to access, how to proceed through a user interface, or which information to retrieve or update.
A single package typically contains the related automations that are needed to complete a specific business objective, for example, looking up a financial history, updating user contact information, and so on.
Each automation package can have multiple versions that correspond to development updates or bug fixes.
For more information, see Automation packages.
Deployment levels are groupings of packages that are related to how mature an automaton package is. In Pega Robot Manager, you can associate an automation package (or its specific version) with one of the three default deployment levels:
- UAT (user acceptance training)
For more information, see Deployment levels.
Package assignment links a deployment level of an automation package to a specific department, user, or robotic work group. For example, you can assign a package version in the UAT deployment level to a specific group of users for testing purposes.
Assignments can be inherited through your organization hierarchy. For example, users in a subdepartment inherit a package assignment that was deployed at the parent department level.
For more information, see Assigning deployment levels and packages.
The following example provides a summary of automation package deployment and consumption in Robot Manager.
When a developer creates an automation in Pega Robot Studio, they publish their work to the automation package repository (Pega Package Server or a repository controlled by Robot Manager).
Simultaneously, the package metadata is published to Robot Manager. This way, Robot Manager is aware of all the automation packages and versions that are available for consumption. When a package version and the associated metadata are published, the robot administrator can then log in to Robot Manager and assign the automation package version to a user or a group of users.
When a customer service representative (CSR) logs in to their workstation, the instance of Pega Robot Runtime that resides on that workstation requests the package assignment that is associated with the CSR. Based on the package assignment, Pega Robot Runtime then downloads and loads the corresponding package from the package repository, and the CSR is ready to work.
The following figure shows a graphic representation of the package deployment and consumption process:
Previous topic Pega Robot Manager as part of the Robotic Process Automation suite of applications Next topic Installing Pega Robot Manager