Skip to main content


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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Creating a repository

Updated on April 5, 2022

Create connections between Pega Platform and repositories to provide centralized storage, versioning, and metadata support for file storage and knowledge management, for example, to store and source file attachments in cases, or for use in DevOps.

Pega Cloud Services environments do not support adding local file system repositories. Instead, client applications running in Pega Cloud Services environments use a default S3 repository that is preconfigured and optimized for Pega Cloud environments. This repository appears as pegacloudfilestorage in your list of repositories in RecordsSysAdminRepository in Dev Studio. For details, see Pega Cloud Services File Storage.

Note: To create a repository, your access group must have the PegaRULES:RepositoryAdministrator role. To use a repository, your access group must have the PegaRULES:RepositoryUser role.

The information you enter when you create the connection determines the file specification, also referred to as a file spec. A file spec is an alias, that is, a way to reference file locations that is independent of the physical file storage. A file spec is resolved based on configured file storage, such as a repository.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us