Normally a document is included in base64 encoding. If you mapping points to a filedocument specialization Mendix does the hard work for you and creates a filedocument. Be sure to assign a name with a correct extension like '.pdf'.
It is possible that your webservice calls results in a link to ftp, webservice or a different way to get the document. It that case you must create some logic to get that document.
Hi Chris,
The message content in response I got is:
<e:Envelope xmlns:d="http://www.w3.org/2001/XMLSchema" xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns:fn35="http://www.filenet.com/ns/fnce/2005/02/ws/schema" xmlns:fn40m="http://www.filenet.com/ns/fnce/2006/11/ws/MTOM/schema" xmlns:fn40="http://www.filenet.com/ns/fnce/2006/11/ws/schema" xmlns:xop="http://www.w3.org/2004/08/xop/include" xmlns:e="http://www.w3.org/2003/05/soap-envelope">
<e:Body>
<GetContentResponse xmlns="http://www.filenet.com/ns/fnce/2006/11/ws/schema">
<ContentResponse i:type="fn40:ContentElementResponse" retrievalName="WVL12352USEN.PDF" totalSize="717387">
<SourceSpecification i:type="fn40:ObjectReference" classId="Document" objectId="{C404669C-524D-419C-B3A5-ED4B4F91E079}" objectStore="{A5E3D405-E66C-4B26-9093-650CBAC577ED}"/>
<ElementSpecification elementSequenceNumber="0"/>
<Content i:type="fn40:InlineContent">
<Binary>
<xop:Include href="cid:v1-9f7c8e655b0991cf-1493720352b@mtom.p8ce.filenet.com"/>
</Binary>
</Content>
</ContentResponse>
</GetContentResponse>
</e:Body>
</e:Envelope>
And an attachment.
Ik can see the name of the document and see a Href., but is this a ftp link?
Regards,
Peter