Storing case attachments using external storage
You can configure your application to store case and Pulse attachments outside the Pega Platform database. By using external resources, you can upload large files without causing out-of-memory errors.
- In the header of Dev Studio, click the name of the application, and then click Definition.
- On the Application form, click the Integration & security tab.
- In the Content storage section, select and configure a
storage type.
For more information about supported storage types, see File and content storage.
- Store in Pega database – Pega database is the default option for on-premises deployments.
- Store in CMIS system: In the Connector name field, press the Down Arrow key, and then select a Connect CMIS rule that defines connections to CMIS repositories.
- Store in web storage provider
- In the Provider list, select an installed storage provider.
- In the Authentication profile field, press the Down Arrow key, and then select an authentication profile of type OAuth 2.0 that authenticates the connection to the provider that you use.
- Click Browse, and then select the folder that stores the case and Pulse attachments.
- If you are connecting to your web storage provider account from this application for the first time, follow the prompts to authenticate and authorize the connection with your web storage provider.
- Store in repository
- In the Repository list, select a data repository.
- Click Browse, and then select the folder that stores the case and Pulse attachments.
- Optional: To prompt users to decide whether an attachment is removed from the external content management system when they remove it from a case, select the Prompt users for confirmation before deleting content check box.
- Click Save.
- Requirements and restrictions for case attachments in a file storage repository
You can configure your application to store case attachments in a repository. When you use a repository, Pega Platform appends the case ID and time stamp to the attachment name. For example, an attachment called loanapplication.pdf becomes loanapplication_19691231T115959999_CASE-1234.pdf.
- Migrating case attachments to a repository
Reduce the size of your Pega database and improve performance by migrating your application's case attachments from Pega database storage to a repository.
Previous topic Managing a case attachment stored in a CMIS system Next topic Requirements and restrictions for case attachments in a file storage repository