Using attachments with SOAP, SAP, dotNet, and HTTP connectors and services
|
|
REST, SOAP, SAP, dotNet, and HTTP connectors and services use a common approach for handling attachments.
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.
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 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.