Multi part payload REST call question
https://docs-previous.pega.com/data-management-and-integration/86/file-attachment-configuration-rest-and-soap-integrations Indicates that Pega does multi part payload transfer files in REST/SOAP calls if pyRequestAttachmentPage page present on the clipboard. We need to find out if this applies to Pega 8.3.0 ? If so, what is the payload size for each part?
Public Safety
CA
@Abhilash_K Thanks Abhilash for your response. A follow up question is how the payload size is determined for each part of the multipart file transfer. For example, I have a 1 GB size binary file, loaded up to Pega server as 1.5 GB (as in Base64 format) on pyRequestAttachmentPage. Do Pega automatically takes care of dividing these file into multiple parts for REST/SOAP transfer? If so, what is the size of each payload? how the size is configured? If not, do the developers need to take care of the division of the file into multiple parts?
I haven't written a POC to figure this out yet? If you have any documentation or point to me any clue, that will be much appreciated. Thanks much in advance.
Albert
Infomatics Corp
US
@AlbertQ7 How are this files uploaded to the Pega Server. If the Upload is from UI there are DSS settings where you can set the file size limit for each upload. And coming to the part sending the files as part of the request - Pega doesn't split or divide this files. If there are multiples files need to be send then in the pyRequestAttachmentPage you populate the fileds like below. There are other ValueList properties which needs to be populated.
pyRequestAttachmentPage.pyAttachValues(1)
pyRequestAttachmentPage.pyAttachValues(2)
pyRequestAttachmentPage.pyAttachValues(3)