Skip to main content


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

Migrating case attachments to a repository

Updated on November 22, 2021

Reduce the size of your Pega database and improve performance by migrating your application's case attachments from Pega database storage to a repository.

Before you begin: Ensure that the pzAttachmentMigrationProcessor queue processor is running. In Admin Studio, click ResourcesQueue processors, and then click Start in the State field for pzAttachmentMigrationProcessor.
  1. In the header of Dev Studio, click ConfigureSystemReleaseUpgradeAttachment Migration.
  2. In the Repository field, select the repository to which you want to migrate case attachments.
  3. Click Browse, navigate to the folder on your repository that you want to use for case attachments, and click Select.
  4. Click Start Migration.
  5. Click Refresh to update the display.
Result: When the migration is finished, the results include how many files migrated. For the files that were not migrated, the work object ID is displayed along with a description of the error that you can use for troubleshooting.
What to do next: Ensure that the repository that the files were migrated to is the same as the repository being used for new attachment storage. For more information, see Configuring external storage options for attachments.
  • Previous topic Requirements and restrictions for case attachments in a file storage repository
  • Next topic Managing work across your team

Related articles

Storing case attachments using external storage

Tags

Pega Platform 8.5 Case Management

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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