This plug-in is deprecated, unmaintained and no longer recommended for use. Refactor applications utilizing the functionality of this component to use alternatives. The functionality is available in Appian (without a plug-in) using the Integration Object.
Allows use of REST web services that return documents as Base64 strings.
Custom Smart Services included:
The main difference between the “Http Json MultiDocument WS” smart service and the “(Encoded Keystore) Http Json MultiDocument WS” smart service is that the latter stores the keystore and truststore as base64 encoded text. The latter does not store the keystore/truststore on the file system.
The Base64 JsonDoc contains the same functionality as the Http Json MultiDocument WS smart services for extracting base64 documents into binary documents. However, the designer is expected to retrieve the web service response using the HTTP File Download Smart Service. Therefore, the inputs related to connecting to the Web Service are replaced with a document as input. The document should be a text document containing the web service response.
Thanks for the suggestion @pavans82. The ability to send base64 inline with JSON or XML is supported with Integrations objects in 18.3.
docs.appian.com/.../Integration_Object.html
@vikrantb You should use the 18.3 integration object to send documents. If that's not available you should use ###<docid>### in the request. For example, if the document id is 123 use ###123###. The ability to send a document is deprecated in the latest version of the plugin. If you still need to send documents, stay with the older version of the plugin.
@sanjays754. There shouldn't be a limit on the size of the document. What type of error do you see when you attempt to upload the document. Are you able to use the 18.3 integration object?