Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

220
Views
 Terence Yuen (TerenceY0215) Bank of Nova Scotia Senior Pega Solutions Architect
Bank of Nova Scotia
CA
TerenceY0215 Member since 2016 44 posts
Bank of Nova Scotia
Posted: December 2, 2019
Last activity: December 2, 2019
Posted: 2 Dec 2019 8:55 EST
Last activity: 2 Dec 2019 8:55 EST
Closed

Using Attachments in Connect REST - other than Base64 Encoded string

Report

https://community.pega.com/sites/default/files/help_v83/procomhelpmain.htm#rule-/rule-connect-/AttachmentsSOAPdotNetHttp.htm

According to help pages, in order to send an outbound message with attachments via Connect-REST, the binary data has to be encoded as a Base64 string.

Now in version 7.4 and above, with Repository API, the D_pxNewFile datapage will by default use Inputstream as opposed to Base64 encoded string. However, if the Custom Repository in turn calls a Connect REST rule that uses attachments, does it mean the Inputstream has to be encoded to Base64 still? Is there any other properties on the pyRequestAttachmentPage that support Inputstream instead?

Data Integration

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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