Posted: 27 May 2018 22:13 EDT Last activity: 30 May 2018 7:06 EDT
HTTP Connect - Attachment not in pyResponseAttachmentPage
I have defined a HTTP Connect that accesses a URL endpoint (which is a URL to a pdf document). I created an activity that calls the HTTP Connect. When I run the activity and trace it, the tracer shows that the step Method Connect-HTTP has a pyHTTPResponseCode of 200. However, when I look at the Clipboard, the pyResponseAttachmentPage does not contain any pyAttachValues. Am I missing something?
According to the Pega documentation:
To process attachments that have been received as part of a connector response message, configure your connector activity to look for a top-level clipboard page named pyResponseAttachmentPage of type Data-ServiceMessage after the connector has been invoked. If the page exists, any attachments that were received appear as Base64-encoded values in the pyAttachValues value list property on the page. The typical use case is to iterate over the list of attachments and associate them with a work object.
The implication here is that the content received by Pega was not in the format that causes the attachments page to be populated. Does the endpoint return a Multipart message? If not, you should be mapping the response to the clipboard or a parse file, using the Connector UI.
Thanks for the response. The endpoint is just a resource URL returning a PDF.
The documentation doesn't state that the pyResponsAttachmentPage is only intended for multipart messages, so I assumed our resource request would also be supported. Mapping to the clipboard is solution we looked at as a fallback, but I guess it's the primary solution. Thanks for confirming.