Skip to main content

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

Automation packages

Updated on January 31, 2022

After you build an automation, you can publish automation packages to a Package Server and then to Pega Robot Manager, which displays all the available packages that developers can publish.

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, a package can contain updates to customer service tasks, which you can test and then deploy those changes to contact center agents who respond to calls from customers.

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

  • Package versions

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

  • Modifying package details

    You can modify the name and description of a package.

  • Viewing package versions

    You can view information about versions of a package, such as when a package was published and by whom, that are on Pega Platform.

  • Deleting package versions

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

  • Deleting a package

    You can delete a package from Pega Robot Manager.

  • 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 its 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.

  • Removing assignments

    You can remove an assignment, for example, if a case worker was inadvertently assigned to use the Development deployment level and package.

  • Viewing assignments

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

  • Enabling and disabling assignments

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

  • Package configurations

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

  • Promoting a package to another deployment level

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

  • Removing a package from a deployment level

    You can remove a deployed package from a deployment level.

  • Restoring a package on a deployment level

    You can restore a previously deployed version of a package deployment on a 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