Document download

RE: Document download

Mike Schmitt — Thu, 22 Sep 2022 13:59:03 GMT

[quote userid="2318" url="~/discussions/f/user-interface/13022/document-download/101632#101632"]Is there any other way to set a different external file name while using download document link functionality?[/quote]

Nope. Such behavior will 100% require 2 clicks by the user, at least.

The implementation you describe is pretty much already what I'd suggest anyway - copy the document to a temporary copy with a new name, and expose that as the document download link. The user would need to click once to initiate the initial copy/rename, then after that's done, they can click again to download the document.

To confirm, the Document Download Link component does not have any way of doing anything "before" the download - literally all it does is provide a direct download link.

RE: Document download

ujjwalr0002 — Thu, 22 Sep 2022 05:55:59 GMT

We have a smart service for that to update the document properties.

https://docs.appian.com/suite/help/21.1/Edit_Document_Properties_Smart_Service.html

RE: Document download

shalini — Thu, 22 Sep 2022 04:28:28 GMT

Use the a!documentDownloadLink field. The following code will be useful for you.

a!linkField(
links: a!documentDownloadLink(
label: "Download Health certificate Part II",
document: todocument(
rule!ASM_QE_GetAnimalHealthReports(
animalId: ri!animalId,
mediaCategoryId: 193,
mediaNote: "Animal Health Report part II"
)
)
),
showWhen: a!isNotNullOrEmpty(
rule!ASM_QE_GetAnimalHealthReports(
animalId: ri!animalId,
mediaCategoryId: 193,
mediaNote: "Animal Health Report part II"
)
)
)

RE: Document download

Thenmozhi Mohanakrishnan — Thu, 22 Sep 2022 03:50:22 GMT

We have a requirement to allow all users to download a particular document, but whenever they download, the document name should be appended with a dynamic text. Currently we are using copy document node to achieve this. Is there any other way to set a different external file name while using download document link functionality?

RE: Document download

Mike Schmitt — Tue, 21 Jun 2022 15:00:32 GMT

AFAIK there have been no recent changes that would add any new capabilities with respect to the number of clicks required to do this sort of thing.

RE: Document download

robertso0001 — Tue, 21 Jun 2022 14:47:12 GMT

yes you are very correct

RE: Document download

robertso0001 — Tue, 21 Jun 2022 14:43:59 GMT

yes

RE: Document download

Venkatesh Suram — Tue, 21 Jun 2022 13:19:28 GMT

Hi Team,

Can we able to download the document from ECM in one click in the Appian 22.1 version OR is it still same limitation.

Thanks!!

RE: Document download

Mike Schmitt — Thu, 18 Mar 2021 15:23:27 GMT

Your scenario is a 2-step process so inherently it will require 2 clicks. Unless you can shorten the process to 1 logical step, the best you're going to be able to do is 2 clicks, IMHO.

RE: Document download

guiomarp0001 — Thu, 18 Mar 2021 15:07:17 GMT

Hi Mike

Thanks for your response.

We're looking at the details to explore that option of preload into Appian, but we will have some 2 clicks required - which is not ideal.

Regards

RE: Document download

Mike Schmitt — Thu, 18 Mar 2021 15:00:03 GMT

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.

RE: Document download

Robert Shankin — Thu, 18 Mar 2021 14:25:38 GMT

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.

RE: Document download

guiomarp0001 — Thu, 18 Mar 2021 14:04:05 GMT

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

RE: Document download

Robert Shankin — Thu, 18 Mar 2021 13:48:17 GMT

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.

RE: Document download

guiomarp0001 — Thu, 18 Mar 2021 12:12:46 GMT

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).

RE: Document download

manjunathb58 — Mon, 06 Aug 2018 16:37:40 GMT

Thanks All.
It makes sense to provide link to document on ECM (read only). But in our usecase access to ECM system can't be provided for security reasons.

So I was looking for any option that makes UI experience seamless.

RE: Document download

Robert Shankin — Mon, 06 Aug 2018 16:31:22 GMT

Adding to what manisht209 mentioned here -
Some ECM tools include integration links for exactly this purpose. For example, OnBase has "doc POP" links which can be included in an Appian interface to retrieve content directly from the ECM tool without ever putting the document in Appian.

This scales especially well when the 3rd party tool links take a token value that you can reference from available data on your (record, report, or task) interface.

RE: Document download

manisht209 — Wed, 01 Aug 2018 06:07:31 GMT

Hi manjunathb58 ,

Do you actually need to download the content on Appian ?
Considering you already have the document in ECM, you might just use the link to the get service to download the document as a response.

RE: Document download

ganeshp — Wed, 01 Aug 2018 01:06:48 GMT

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.

RE: Document download

Mathieu Drouin — Tue, 31 Jul 2018 23:50:40 GMT

I don't think this is possible at the moment.

If the Appian and ECM instance are both protected using the same SAML SSO solution, you could simply directly link to the ECM file from within Appian and it should work seamlessly.

docs.appian.com/.../SAML_for_Single_Sign-On.html