Question
Coforge Limited
IN
Last activity: 17 May 2017 10:07 EDT
Upload Document Service is failing because of white spaces occuring by "pySaveFileContent" Pega OOTB activity in the DOCUMENT-CONTENT field (typically get from "pyAttachStream" field from Data-WorkAttach-File)
In our Connect-HTTP Upload document service, we have a field called DOCUMENT-CONTENT, which takes document content streame in Base64 encoded format. We need to pass the attach document stream to the DOCUMENT-CONTENT field to store the document.
For that we are using "pySaveFileContent" Pega OOTB activity to capture the content of the document and passing it to service. But the problem is with the Pega OOTB activity from which we get the document content stream in property of "pyAttachStream" with white spaces/invalid form and truncated Document stream. Due to invalid content and white spaces the Upload Document service is getting failed.
Can someone please assist?
Coforge Limited
IN
My service was not failing because of issue described in this article; actually this was not an issue at all. It was failing because of other reasons which I had solved. The document contents appear to be truncated in the clipboard and tracer (might be because of large document length) but this field gets resolved perfectly fine when sending the doc-content to the external service.
Pegasystems Inc.
US
Thanks for the clarification. I believe there is a limit for pyAttachStream for displaying on the clipboard (that would bloat the clipboard if there was none, leading potential OOM etc).