Skip to main content

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

Archiving resolved emails for an email bot (Pega Cloud Services)

Updated on February 10, 2023

Archive resolved emails for triage cases in Pega Email Bot™ that are older than a specified number of days in Pega Cloud Services installations of Pega Platform. Since the email triage data in tables can grow quickly for an email bot that is available in Pega Cloud Services, archiving resolved emails improves the overall performance of your system by reducing primary storage consumption and cost.

Emails from email triage cases that are resolved and archived are no longer actively used by the email bot, and are placed in secondary storage.

When the email bot receives an email that is related to an archived, resolved email triage case, the system then also displays the archived triage case in the context of the new triage case for reference purposes, for example, in the Email Manager portal.

You use the Data-Retention-Policy rule for the Work-Channel-Triage-Email class to control which cases your application moves from primary storage to secondary storage. The system runs the archive process for this policy in the background using system agents and job schedulers. For more information, see Improving performance by archiving cases.

  1. In the navigation pane of App Studio, click Channels.
  2. In the Current channel interfaces section, click the icon that represents your existing Email channel.
  3. On the Email channel configuration page, click the Behavior tab.
  4. In the Options section, select the Archive emails checkbox.
  5. In the Archive resolved emails older than field, enter the number of days after which the system will archive resolved triage cases.
    By default, the system archives emails that are older than 365 days.
  6. 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us