You can control where case and Pulse attachments are stored and sourced for your application. There are different types of content storage types that you can use. The storage type is based on the content storage vendor that your business uses, your expected file size, and the number of concurrent uploads/downloads.
The following types of content storage are supported:
- Content Management Interoperability Services (CMIS) systems
- External systems that use the CMIS standard, such as Alfresco, Microsoft SharePoint, and OpenText, to which you connect by using a CMIS connect rule. CMIS systems support storing and sourcing content. For more information, see About Connect CMIS rules.
- Web storage
- Storage to which you connect by using an account and credentials from a web storage provider, such as Box or SharePoint Online. Online repositories support storing and sourcing content. In addition, you can use web storage APIs to interact with the online repository outside of case and Pulse attachments. For more information, see Adding case attachments from external content locations.
- Storage to which you connect by using a repository rule and relevant role. This
category includes the Pega Cloud file repository, which is the
default location for Pega Cloud applications. Repositories are the
only supported content storage type that supports streaming and that have no risk of
running out of memory. In addition, repositories have an API that lets you interact
with the repository outside of case and Pulse attachments. The supported repository
- JFrog Artifactory
- Amazon S3
- File system
- Microsoft Azure
- Custom repositories
- Repositories support storing and sourcing content. For more information, see Creating a repository.
- The Pega Platform database
- The default location for on-premises applications. The Pega Platform database supports storing content only.
The following table shows the features supported by each storage type.
|Pega Platform database||X|
Differences between web storage and repositories
Web storage and repositories differ in the following ways:
- Only repositories support streaming. If your application processes large files or multiple concurrent files, use a repository.
- Custom repositories can be used for file interactions in different scenarios, such as with file listeners or the Deployment Manager.