Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
We want user to download files that are present in ECM system with a single click from Appian user interface.
We don't want to download and keep files on Appian server till user explicitly click on link to download file. How can we achieve file download (REST API call) and document link together on single button click?
Discussion posts and replies are publicly visible
It must have to be stored in Appian post which you can have sub processes that can one write to the external ECM system based on the doc id to the specific folder in the external system and removal from appian data entites.
Is there a solution for this matter? At the minute in order to acheive this, we are making the user click 2 times (one downloads the doc to appian, the other one downloads to the user computer).
Please refer to my previous response. If you want the end user to acquire the document directly from the 3rd party tool, identify that tool's api for building direct download links. Put those links in the Appian interface.
Hi Robert,
Thanks, we will try, but we might be causing a security breach. We're using sharepoint with Oauth per Application, users don't have direct access.
Are there other options?
Thanks
There may be other options, but none that I'm aware of. In order for a document link to be presented to an end user, the document needs to be in Appian.
Do you have some way of pre-loading certain documents into Appian, before being specifically requested by a user? This would be the only way I can think of to prevent the 2-click method. Though given your use case, it seems like 2 clicks both within Appian is a pretty good solution overall.