Skip to main content

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

Updating the email bot to the 8.7.1 version

Updated on September 19, 2023

Take advantage of Pega Email Bot™ performance improvements that are available in Pega Platform version 8.7.1. As a result, you enhance how the system references email triage information, helping customers to interact with the email bot in a timely manner.

Pega Platform version 8.7.1 introduces performance improvements that help reduce the clipboard page size by not storing email body, attachments, and NLP outcome data in this page. The following data pages are now available so that you can obtain the relevant email body for an email triage or interaction case that was previously referenced in the clipboard page:

  • D_pxFirstInboundEmail[ETCaseId: "ET-100"].pyBody
  • D_pxLatestInboundEmail[ETCaseId: "ET-100"].pyBody
  • D_pxAllInboundEmails[ETCaseId: "ET-100"].pxResults(1).pyBody

For compatibility purposes, if you update to Pega Platform 8.7.1 or higher:

  1. Identify rules in your Pega Platform application that refer to properties where the email body for an email triage case is referenced in the pyWorkPage clipboard page.
    For example: Your rule contains pyWorkPage.pyHistory(1).pyBody and pyWorkPage.pyInboundEmail.pyBody email body references for an email triage case.
  2. Replace the references in these rules with the email body references by using one of the three new data pages.
    For example: Replace the pyWorkPage email body references from the previous step with D_pxAllInboundEmails[ETCaseId: "ET-100"].pxResults(1).pyBody and D_pxLatestInboundEmail[ETCaseId: "ET-100"].pyBody.
  • Previous topic Troubleshooting other email bot issues
  • Next topic Updating to the threading mechanism available in the 8.6 version

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