Web service to support SOAP attachments


Is there a way by which we can create web services in PRPC, which accepts SOAP attachments?

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.


Keep up to date on this post and subscribe to comments

April 27, 2010 - 9:15am

Typically you use SOAP services (Rule-Service-SOAP), created by the Service Accelerator. Do you have special requirements that can't be met by SOAP services?

See http://pdn.pega.com/ProductSupport/Products/PegaRULESProcessCommander/documents/PRPC/Help_V55/rule-/rule-service-/rule-service-soap/main.asp

April 27, 2010 - 9:43am

Support for SOAP services with MIME attachments will be available in PRPC 6.1. Until then, you will need to contain all data in the SOAP envelope, which means Base-64 encoding any binary data.

August 19, 2015 - 7:45am

SOAP, HTTP, REST, SAP and dotNet connectors and services use a common approach for handling attachments.


Sending attachments from your application


When building the outbound message content for a SOAP, SAP, dotNet, or HTTP connector, PRPC looks for a top-level clipboard page named pyRequestAttachmentPage of type Data-ServiceMessage. If it finds the page in the clipboard, it adds attachments to the outgoing message for every string value found in the pyAttachValues Value List property on the page. Each string is assumed to be a Base64-encoded representation of a binary data value. This page must be created and populated prior to invoking the connector.


The same general model applies for REST, SOAP, SAP, dotNet, and HTTP services; but the top-level page is named pyResponseAttachmentPage since the attachments are added to the outgoing service response message.


Receiving and processing attachments


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 pyResponseAttachmentPageof 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 same general model applies for REST, SOAP, SAP, dotNet, and HTTP services; but the top-level page is named pyRequestAttachmentPage since the attachments are received as part of the inbound service request message.


You may want to have a look at this PDN article that has information on both incoming attachments as well as outgoing attachments