Can someone tell me what all options are correct for this question?
Which two use-cases would require a third party integration?
Discussion posts and replies are publicly visible
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)
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 integrationThe 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.
Dear all, I also have the same question. So we are saying that two use-cases that require a third party integration are 2 and 3? Because without this helpufl thread I would have answered 3 and 4. Can you please tell me in which documentation I can retrive this information? I need to study this for the Appian Certification analyst. Thanks a lot for your availability
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!