I have a requirement to send an email upon case submission with all attachments.
Currently, attachments are stored in a custom Page List: pyWorkPage.CaseRelatedFiles (Service-Work class), populated via a custom upload implementation.
I tried using the OOTB activity: SendEmailWithAllAttachments but the email is sent without any attachments.
It appears this activity only picks up attachments from: pyWorkPage.pyAttachments()
Questions:
Does SendEmailWithAllAttachments support custom Page Lists, or only pyAttachments()?
What is the recommended OOTB approach to send attachments stored in a custom Page List?
Should these be converted to Data-WorkAttach-* instances or mapped to pyAttachments() before sending?
Hi @MaleeshaW Does SendEmailWithAllAttachments support custom Page Lists, or only pyAttachments()?
No - The OOTB activity SendEmailWithAllAttachments only processes attachments stored in the standard work attachment structure.
pyWorkPage.pyAttachments() → Data-WorkAttach-* instances
It does not support or recognize -Custom Page Lists, Custom attachment-like structures and Pages populated outside the OOTB attachment framework. This behavior is intentional and consistent across Pega versions, including 25.1.1.
What is the recommended OOTB approach to send attachments stored in a custom Page List?
Use the standard Work Attachment framework. Storing case attachments as Data-0WorkAttach* instances. Allow Pega to manage - Persistence, Security, Lifecycle and Email integration.
Once attachments are stored as work attachments, all standard features—including SendEmailWithAllAttachments—work automatically.
Should these be converted to Data-WorkAttach-* instances or mapped to pyAttachments() before sending?
Yes — map them into pyAttachments as Data-WorkAttach- instances*