We configured Pega NLP to analyse, routing and attaching email attachments to case, it’s working for one level but our requirement is if attached email has attachments, Pega has to extract and attach to case, this is not happening now.
Is there any configuration or way to achieve this?
Attached requirement diagram for reference.
Ex. Email has PDF1 and .EML attachments, when Pega processed case C-01 has PDF1 and .EML attachments but not PDF2 and PDF3.
To address the challenge of extracting and attaching nested email content in Pega, you’ll want to extend the out-of-the-box email listener functionality. Currently, Pega handles attachments at one level, so you would need to:
Create a Custom Service: Implement a service that processes incoming emails, specifically looking for .EML attachments.
Parse Nested Attachments: Develop a Java step within the service activity that parses .EML files to identify and extract additional attachments.
Use Pega APIs: Programmatically attach the extracted files to the case using Pega’s APIs, such as Link-Attachment or pxAddAttachment.
Remember to test thoroughly to handle various attachment scenarios. This approach requires custom coding, but it ensures that all attachments are captured, meeting your multi-level extraction needs.
