Hi all, I would like to ask you a question on the cmis integration: May I please

Only one at a time.

The CMIS connector returns a writer object. I don't see a way to upload more than 1 at a time.

@Eduardo Thanks Eduardo. Earlier my understanding is that the user needs to send each and every file to Alfresco if we want to proceed with using connector functions and I hope my understanding is correct.

@shyamb Correct, I am well versed with the return type of the object that any connector functions return but my question is around sending more than file at a time.

Affirmative. Per definition of the CMIS connector, it takes 1 document at a time. My stress is on the return "writer" object. It basically means not just 1 at a time but, 1 per user click.

You can call a!save() multiple times from one user action. With that in mind, you should be able to copy more than one document at a time. Something like this:

saveInto: {
a!save(local!cmiCopyDocumentFromAppianWriter, appianDoc1),
a!save(local!cmiCopyDocumentFromAppianWriter, appianDoc2)
}

(where appianDoc1 and appianDoc2 are Appian Documents you've already stored)

Let me know if that works out for you.

@shyamb Yep, thanks and I know that but as of now I feel that it's not related as I am looking for a different scenario.

@rawichp Are you suggesting to make use of looping functions? I think obviously you aren't suggesting me to hard code the calls to a!save(). It would be grateful if you could elaborate it.

If you can use looping function with a!save, that would actually address your need. But a!save does not support partial function evaluation, which is required when using with looping function such as apply().

So, you can upload more than one file, if you know at design time, how many files you're going to upload :)

I actually gave up on these cmi Connector functions, because there is nothing we can do to detect an error condition, if the file didn't get uploaded.

Even if you create a custom Writer function, the best you can do is to get an error reported to end-users, no option to gracefully handle exceptions. So I chose to create Smart Service plug-in instead.

@rawichp True, wanted to know if you or other practitioners have devised any approach. Neither a!save (because of the support not offered to partial function evaluation) nor the number of documents (because of the unknown count until run time) are a great options to me.

Thank you all for your feedback. Looks like what I'm looking to do cannot be done easily. I think we are going to try the approach of using the Advanced Call Web Service plugin.