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

Issue with OOTB corrattach activity



After correspondence gets generated and attached to the work object, the content(body) of the email is blank in the attachment section ,but the email gets generated properly to the receiver . 

Error Messages

Unable to see the content of the mail

Steps to Reproduce

1)Cretate a case and send mail correspondance.(use property-set-corr, sendEmailNotification,corrAttach)
2)Open the WO by doing a search with WO id , check the attachment section of the WO.
3)The mail icon with subject name will appear as a hyper link in the attachment section .Click on it, another IE window will open as the mail.

To, from subject etc is fine, body/content of the email will be seen as blank.

Root Cause

An issue in the custom application code or rules  The parameters .pyBody,.pyReply is not set to the proper value on the pyCorrPage .


Perform the following local-change: 

We need to explicitly set the parameters .pyBody , .pyTo , .pyToString to the appropriate values as shown below .

Perform the Obj-Save of pyCorrPage, to ensure that values we have set are commited .

sendEmailNotification only sends the email to appropriate id, it wont attach it to the work object . Hence need to call CorrAttach, to make sure that the generated correspondence gets attached to the WO properly .


Published January 31, 2016 - Updated October 8, 2020

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