Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Automation packages

Updated on December 20, 2022

After you build an automation, you first publish automation packages to a Package Server and then to Pega Robot Manager.

You can use Pega Robotic Automation Importer to enable easier development for attended (RDA) implementations. For more information on the Importer, see Pega Robotic Automation Importer component.

Once the package appears in Pega Robot Manager, you can then deploy the automation package to a robotic work group, department of users, or individual users in your organization. For example, if a package contains updates to customer service tasks, you can test the changes, and then deploy the changes to contact center agents who respond to calls from customers.

When a robot logs in to Pega Platform, the robot registers with its assigned work group, retrieves the automation package that is assigned to that work group, loads the package, and then begins requesting automation assignments.

  • Package versions

    Packages can have one or more versions, and you can deploy any new or updated version of a package.

  • Modifying package details

    You can modify the name and description of a package to make it easier to find the package in Pega Robot Manager.

  • Viewing package versions

    You can view information about a version of a package. In this way, you can find out, for example, when a package was published, and who published the package.

  • Deleting package versions

    You can delete a version of a package from Pega Robot Manager.

  • Deleting a package

    You can delete a package from the system if the package is no longer necessary for the deployment process.

  • Removing package assignments

    You can remove a package assignment. For example, if a package in Development deployment level was accidentally assigned to a case worker instead of a package in Production deployment level being assigned to that case worker, then you can remove the package.

  • Removing package deployments from a deployment level

    You can remove a deployed package from a deployment level.

  • Deployment levels

    You deploy a package to a level and assign the deployment level to departments, users, and robotic work groups in that level so that the appropriate resources can develop, test, and use the package.

  • Deploying a package

    You deploy a package into a deployment level, and then assign the deployment level (and therefore its associated package) to the appropriate robotic work group, department, or user.

  • Assigning deployment levels and packages

    You assign a deployment level (and the package that is deployed in it) to a robotic work group, department of users, or individual users.

  • Viewing assignments

    You can view all the packages that are assigned to either departments or individual users.

  • Enabling and disabling assignments

    You can enable or disable packages that are assigned to either departments or users.

  • Package configurations

    Configurations act as variables into which different information can be substituted as needed. A package can contain one configuration, or multiple configurations, and configurations are defined for an automation by the Pega Robot Studio developer.

  • Promoting a package to another deployment level

    After a package has been deployed to a given deployment level, you can promote the package to another level in the pipeline.

  • Restoring a package on a deployment level

    You can restore a promoted version of a package deployment back to the previous deployment level.

  • Viewing package deployment history

    You can view details about a package deployment, such as which version of a package was deployed and when it was deployed.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us