Skip to main content

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

Storing robotic automation packages in Pega Robot Manager

Updated on December 20, 2022

Make your robotic solution fully compatible with your data storage policy by configuring Pega Robot Manager to use a repository for package binary files.

Using a repository for automation deployment files (packages) eliminates the need to maintain a local Pega Package Server.

When you publish a package from Pega Robot Studio, Pega Robot Studio sends the package and its associated metadata to Robot Manager, which then forwards the package files to the repository of your choice. The repository can be local or cloud-based. When Pega Robot Runtime starts, makes a call to Robot Manager to discover which package files to retrieve, and then Pega Robot Runtime retrieves the appropriate package files from the repository.

Important: You can delete a package from Robot Manager. If you carry out that operation, then this also removes the package from the target repository. For more information, see Deleting a package.

What to do next: Configure a repository for package data files, and discover more about the repository structure by reviewing the following articles:
  1. Configuring a repository for package data

    Comply with your data storage policy by configuring Pega Robot Manager to run a repository for package binary data files.

  2. Package repository data model

    Learn more about the topology of the package repository that is controlled by Pega Robot Manager. That repository provides an intuitive folder tree for browsing and managing your package data.

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