Skip to main content


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

Adding a file system

Updated on November 23, 2022

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

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.
  1. In the header of Dev Studio, click CreateSysAdminRepository.
  2. Enter a short description of the repository and the repository name and click Create and open.
  3. In the Definition tab, click Select and select the repository type.
  4. In the Resource path field, enter the path under which artifacts are stored on a file system.
    Note: Each node's operating system must detect the resource path in order to import and export artifacts.
  5. Click Test connectivity to verify whether your credentials are valid.
  6. Click Validate repository to test the connection to the Repository APIs and review the results in the Test Repository Connectivity window. The results include the total time to complete the test, the Repository APIs tested, and the status of the connection.
  7. Click Save.

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