Question : Third Party Integration in Appian

Question

Can someone tell me what all options are correct for this question? 
 
 Which two use-cases would require a third party integration? 
 
 A customer needs to be able to share document with other Appian users 
 A customer needs to be able to retain and store an extensive number of large, historical documents over a 7 year period 
 A customer needs to collaborate on documents with non-Appian users in real time 
 A customer needs to email copies of documents to non-appian users

Richard Michaelis · Answer

the second calls for a file storage solution. so systems which are made for that. Appian can deal with documents, but is not especially made to deal with a huge amount of (big) files, which is indicated by " an extensive number of large [...] documents over 7 years" The third - appian means collaboration within appian, especially not real time wise. (workflow oriented, step by step)

juergeng0002 · Answer

Hi Gaurav, the second topic needs configuration (if on premise) to avoid storing the documents on the Appian Server. A dedicated File server will do the job. If on a Cloud Instance - this would be better a third party integration The third topic: Collaborate on documents in real time. This is possible with a third party integration (Microsoft Online Server or Collabora) and the App from the App-Market ( https://community.appian.com/b/appmarket/posts/online-office-integration) . Again - only possible with an on-premise installation.

Harsha Sharma · Answer

In Appian applications, you can send emails to non-appian users and mail ids using Send Email node in process. You dont need to setup any integration for this. This makes statement 4 incorrect. 
 For Option 2, as already answered earlier here, large number of historical documents affect the memory and performance of Appian servers. Its better to use S3, Sharepoint etc external systems to store these documents and use integration for documents to be accessible to users. 
 Hope it clarifies!