Skip to main content


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

Configuring default repository storage for Pega Cloud deployments

Updated on May 30, 2022

This content applies only to Pega Cloud environments

For Pega Cloud deployments, you can enable and configure the default repository storage.

  1. In Dev Studio, configure the following dynamic system settings:
    • MarketingImageAssets/IsRepositoryStorageEnabled - Set to true.
    • Optional: MarketingImageAssets/Folder - Enter the name of the folder where Pega Customer Decision Hub will store the image assets. This folder will be located inside the root folder defined in the repository rule. If you do not define a folder for the images, they will be stored directly in the repository root folder.
    • Optional: MarketingImageAssets/BaseURL - Enter the URL of the Content Delivery Network which you configured, and update the MKTDefaultSecured content security policy rule to include BaseURL under the Image-Source category in the Allowed Websites column. If you leave this setting blank, the images will be rendered directly from the Pega Web Service.
  2. Optional: To modify the maximum file size allowed for images, edit the MarketingImageAssets/AllowedFileSize Dynamic System Setting.
  3. Optional: To allow image types other than .png, .jpg, .jpeg, .tiff, and .heif, save the data transform AllowedImageTypes to your application ruleset and add new types as required.
  4. Run the D_RepositorySettings data page with flush mode on, or clear the cache.
    Flushing the DSS settings is required to apply the changes made to the settings.
What to do next: If you replace an image in the repository with a new version, the cached image on the Content Delivery Network is invalidated and replaced with the new version of the image. Cache invalidation is automatic in the Pega Cloud repository. The request to invalidate the cache is made immediately, but may take some minutes to fully refresh the image cache.
    • Previous topic Configuring custom repository storage
    • Next topic Optional: Integrating Pega Customer Decision Hub with Adobe Experience Manager

    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