We have a requirement to consume the inputs and file attachments(base64Binary) as inbound service request message to a SOAP service. To accommodate this request, we have used pyRequestAttachmentPage as the top level page of class 'Data-ServiceMessage' in the Service activity which will directly parse the multiple file attachments (from the client) and store it in a value list under the top level page pyRequestAttachmentPage. Post this implementation a request with multiple file attachments has been trigerred via SOAP UI and observed that all the attachment content are being parsed and merged in to a single 'pyAttachValues(1) ' under the Page pyRequestAttachmentPage. The pyAttachTypes type has also been observed as : FileType multipart/mixed; boundary="----=_
How to directly Parse all the file content in to different value list values ?
Once you pass the request from SOAP UI with attachments all the attachments will be stacked on 'pyRequestAttachmentPage' in pagelist 'pyAttachValues' on different indexes like 'pyAttachValues(1), pyAttachValues(2), ....etc' depending on number of attachments you are sending via request. You can probably write a 'For-each' step to get the details of each file by iterating though 'pyAttachValues' page list and copy to value list however I am not sure of the PRPC version you are working with since in higher versions page list would be recommended to handle it.
Many Thanks Habeeb and Prasad for your replies. We are currently using the Pega PRPC version 6.2 SP2 and we see that multiple attachments are being marged in to a single attachment content under the property 'pyAttachValues(1)'... I am aware that expectation of pyRequestAttachmentPage as the top level page of class 'Data-ServiceMessage' to Parse the files in to multiples value lists but which is not happening in 6.2 SP2. I will check with Pega support as well on this.