I'm evaluating the possibility of using the Base64 Utilities plugin to conve

I'm evaluating the possibility of using the Base64 Utilities plugin to convert base64 document encodings (sent by an external system) into Appian documents.
Each xml request sent by the external system can contain the encodings of about 3/5 documents, with the size of 8MB (at most) per document. In step 1 of my project, the expectation is to receive at most 2 xml requests per day (so let's say about 10 documents per day). In next steps, the number of requests per day will increase (expected amount to be evaluated).

According to the plugin pre-requisite, Convert Base64 String to Document is not recommended for use in large volume on production sites. Can you tell me if the Base64 plugin can be used in my project or suggest me alternatives?

Thanks!

OriginalPostID-140218

OriginalPostID-140218

  Discussion posts and replies are publicly visible

Parents
  • AFAIK if you ensure that the involved processes are deleted directly after completion to free up memory this should be no problem. Check best practices for memory efficient process models. And you should do a analysis of memory usage as described in documentation to find out how much memory is really used. I think this will cause trouble only if there are a lot of ( lets say > 10 ) incoming documents at the same time.
Reply
  • AFAIK if you ensure that the involved processes are deleted directly after completion to free up memory this should be no problem. Check best practices for memory efficient process models. And you should do a analysis of memory usage as described in documentation to find out how much memory is really used. I think this will cause trouble only if there are a lot of ( lets say > 10 ) incoming documents at the same time.
Children
No Data