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

Unable to read an incoming multipart response

SA-67307

Summary



Unable to read an incoming multipart response.


Error Messages



Not Applicable


Steps to Reproduce



Unknown


Root Cause



This behavior is as per Pega product design.


Resolution



Here’s the explanation for the reported behavior:

To map the multipart response to pyAttachmentPage, configure the response in the activity which invokes the REST connector.

For example, consider the below activity,



  1. Clear any existing information on pyRequestAttachmentPage.

    Set Method to Page-Remove



     
  2. Create a new pyRequestAttachmentPage.

    Configure When to Page-New


     
  3. Create the new AttachmentFile page.



     
  4. Set property names to map the incoming multipart response to Pega properties. The values vary depending on the EndPoint format.


     
  5. This is the first instance of the pyRequestAttachmentPage. Use this instance to set the first part (text). The values depend on the service.


     
  6. This is the second instance of the pyRequestAttachmentPage. Use this instance to set the second part (binary). The value for the pyAttachTypes(2) depends on the service.


     
  7. Call the REST connector.

Suggest Edit

Published March 23, 2019 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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