Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Attachments are not sent through emails if added via Doc Req FW

SA-9561

Summary



Emails sent with Attachment added through Document Requirement Framework (FSIF) are sent out without attachments. Even though the email attached to the WO shows the attachment. When the same attachment is uploaded using Paper Clip icon, it is sent out fine. 
When FSIF is uploading the document, it is setting the class of the attachment as Data-WorkAttach-ProcessRequirements. Also the property storing the Binary stream is called pyReqStream as opposed to pyAttachStream (for File attachment class).  

Error Messages



Not Applicable

Steps to Reproduce



Install PEGA document Reuqirement Framework.
Upload Documents through upload doc screen
Send an email with the specified attachment categories
Check if emails are sent through


Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules. Standard SendCorr agent looks for pyAttachStream and pxAttachName as the properties to get attachment data. These were not set. Hfix-22107 was created for this, but developers went for local change instead (along similar lines) as they had already customised OOTB rules.


Resolution



Provided Hfix-22107. Due to customization at user end, user moved the section where attachment was created to Data-WorkAttach-File class and updating missing properties (pyAttachStream and pxAttachName).

Published May 11, 2015 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us