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

When sending attachments by REST meta data is not populated



User has implemented the SnapStart URL concept in PRPC for external Users and reported that they are facing issue forming different session on click of the URL.

User is explicitly setting values for optional parameters such as pyAttachFileNames and pyAttachTypes in pyResponseAttachmentsPage but those parameters are not taking effect in generated response.

Even though above parameters are set, Content-Disposition: filename defaults to pyAttachNames and not pyAttachFileNames and for Content-Type gets always application/octet-stream, ignoring set pyAttachTypes.

Error Messages

Not Applicable

Steps to Reproduce

1. Create four new argument constructor in to include attachFileName.
2. Perform a change in to retrieve pyAttachFileNames and set attachFileName in ClipboardAttachment.
3. Perform a change in to take pyAttachFileNames and set as attachFileName in attachmeninfo stringbuffer.
4. Perform a change in to retrieve attachFileName if present and pass to FilePart. Also, in case attachType has value, pass that to FilePart constructor.

Root Cause

A defect in Pegasystems’ code or rules;
There was no support for optional parameters in case of multipart attachments.


Apply HFix-36865.

Published March 23, 2018 - 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