Skip to main content


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

Creating a repository

Updated on April 6, 2022

Create connections between Pega Platform and repositories to provide centralized storage, versioning, and metadata support for file storage in your Pega application. For example, you can store and source file and case attachments, or for use in a DevOps pipeline configuration.

Note: Ensure that you review the restrictions of adding a repository for case attachments in Requirements and restrictions for case attachments in a file storage repository. If you fail to observe restrictions while you implement a repository, you can experience system failures.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. Pega Cloud clients can use Pega Cloud File Storage as the default repository for case and Pulse attachments. For details, see Pega Cloud Services File Storage.

Pega Cloud supports the use a of client file repository instead of Pega Cloud File storage as well. Configure a file repository using an option below to use that repository throughout Pega Platform.

Restriction: Pega Cloud does not support local file systems as external repositories. Do not select defaultstore when you select a file repository.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.

On-premises and client-managed cloud systems can store case and Pulse attachments in a file repository after you create the respective repository. Configure a file repository using an option below to use that repository throughout Pega Platform.

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.

  • Adding an S3 repository

    Add an S3 repository to provide centralized storage resource. Your application can then use the S3 repository to store and source file attachments.

  • Adding a Microsoft Azure repository

    Add an Azure repository to provide centralized storage, versioning, and metadata support for file storage and knowledge management, for example, to store and source file attachments in cases.

  • Adding a JFrog repository

    Add a JFrog repository to provide centralized storage, versioning, and metadata support for file storage and knowledge management, for example, to store and source file attachments in cases.

  • Adding an on-premises file system (legacy)

    Add a file system repository instance to use a local file system storage in your application.

  • Creating a custom repository

    Use a repository API to create a custom repository for repository types that are not provided with Pega Platform. For example, you can build a Google Drive custom repository type. Custom repository types appear in the Pega Platform user interface.

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