RE: Appending text in base64 - Integration Call

arjunv489 — Mon, 05 Aug 2019 12:12:52 GMT

Steven Miccile Thanks a lot. That helped.

RE: Appending text in base64 - Integration Call

Steven Miccile — Fri, 02 Aug 2019 15:27:14 GMT

I have observed the same behavior with the Integration Object such that the document/base64 string must be the entire value for that JSON key. Can the web service be updated? I would hate for you to miss out on the features of the Integration Object and build/use something custom and difficult to maintain. Previous plugins that turn documents into base64 strings have all been removed because they can lead to memory issues if used incorrectly. I highly recommend against that approach. That is why the Integration Object does the conversion inside the web service call for you: no memory concerns and the designer never has to deal with the base64 string.

Workaround: We used to have a plugin node that did exactly this for web service calls but it was deprecated once the Integration Object could handle this. The plugin is still in the AppMarket, but that specific node is hidden from the pallette since it is deprecated. I can provide you a process model with that node and based on my testing, it should accomplish your goal.

1) import this: community.appian.com/.../base64-request-to-rest-web-service
2) import application zip file I attached
3) copy node from sample process model in application zip to your process model
4) set up your node. follow request string syntax in the example node (document id's wrapped in #s, for example #6745#)

community.appian.com/.../Send-Base64.zip