Hi All,
We have a requirement where client wants to store the restricted client documents in Filenet instead of in Appian cloud env. which are uploaded during the application workflow.
Could any one tell me how to achieve this. There is Filenet service existing which might need to be modified as required for Appian. Also I have below questions :
1) What are the pre-requisites for the Filenet Service
2) How to send the document info. from Appian to Filenet service, is it through link or any predefined functions or smart services available
3) How to fetch the documents from Filenet.
Please suggest how to achieve this requirement. I am very much new to Integrations and any suggestion or code sharing would be very much helpful. Thanks in advance.
Discussion posts and replies are publicly visible
Hi Bhanu -
A good place to start would be to explore what Web API's FileNet has available for these operations.Also take a look at if FileNet exposes links that you could put into Appian to allow Appian users to download documents directly from FileNet.
Review our docs on Appian Integrations (for calling 3rd party web api's):https://docs.appian.com/suite/help/19.2/Integration_Object.html
And Web API's (for receiving calls from 3rd party web service calls):https://docs.appian.com/suite/help/19.2/Web_APIs.html
Technically - you will only be able to leverage Appian's document related functions on Appian documents. For example, Appian's document browser will only work on documents stored in Appian.
What I would encourage you to consider is that the documents should stay in Appian for any in-process work, or any recently completed work. This way users can interact with the full functionality that Appian has to offer. Then, for older work, you can transport documents from Appian to FileNet for long term archival and storage. If your application relies heavily on documents that are already going to be in FileNet, it might make sense to integrate for in process work. Otherwise, if the docs are originally being uploaded to Appian, or being generated in Appian - it's usually most efficient to work with the docs in Appian until you're ready to Archive.