Make your robotic solution fully compatible with your data storage policy by
configuring Pega Robot Manager to use a repository for package binary
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 the associated metadata to Pega Robot Manager, which forwards the package files to the repository of
your choice. That repository can be local or cloud-based. When Pega Robot Runtime starts, it receives the package files from the
repository by calling Pega Robot Manager.
Important: You can delete a package from Pega Robot Manager. That operation 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 and discover more
about the repository structure by accessing the following articles:
- Configuring a repository for package data
Comply with your data storage policy by configuring Pega Robot Manager to run a repository for package binary files.
- 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.