Document Viewer

Hi, check this link

https://docs.appian.com/suite/help/24.1/Document_Viewer_Component.html

And remember that when you upload files into Appian with fileUpload Component, the document won't be available until you call submitUploadedFiles() ...

But keep in mind that the function submitUploadedFiles() is ONLY to be used in Appian portals. Process start forms and user input task forms will automatically upload files once submitted.

Yes, but you can use it also in interfaces on a site for example, if no process is started...

Stefan Helzle said:

ONLY to be used in Appian portals

(and sites, as of the past ~2 versions)

I hope this section in the documentation helps to limit any confusion: https://docs.appian.com/suite/help/24.1/fnc_system_a_submituploadedfiles.html#usage-considerations

Thank You for your response. I check this out. 

I have a problem to solve before I get here. I have an interface for user to upload files. I want to store these files in new folders with their unique uploadID. So i use the following code in SaveInto:

a!createFolder(
name: ri!DR_Filings['recordType!{7e936f34-1fd3-4278-8e04-aa1289d866dd}DR Filings.fields.{b10b56fd-3534-4386-a523-e76a45f88f15}companyName'],
parentFolder: cons!DR_UPLOADED_FILES_PARENT,
onSuccess: a!save(target: local!newFolder, value: fv!folder)
),

but the local variable is not getting populated with the new folder name, which i want to use in my file upload function:

a!fileUploadField(
label: "Upload Type3 Document",
labelPosition: "ABOVE",
target: local!newFolder,
value: ri!DR_Filings['recordType!{7e936f34-1fd3-4278-8e04-aa1289d866dd}DR Filings.fields.{ba570aec-da87-4369-939e-5387d9a3bea4}docId3'],
saveInto: {
ri!DR_Filings['recordType!{7e936f34-1fd3-4278-8e04-aa1289d866dd}DR Filings.fields.{ba570aec-da87-4369-939e-5387d9a3bea4}docId3']
},

Can you help me figure out where I am going wrong?

hi swapnae0002  could try this with smart service from process model

Appian does not work this way. It is not made to just do everything inside code snippets in the UI.

I suggest to just upload the files in a process start form. Then, in process, create that new folder and move the document into it.

When the client is being created,

1. create a folder and save the ID of the folder, tagged with the client ID, in the table.
2. Now use a a!fileUploadField and in the target, pass the correct folder ID.
3. Add the interface in a process model as a task and when you submit the interface, your document will be uploaded. 

As David mentioned, you can use the documentViewerField to show the PDF documents on dashboards. 

Stefan Helzle said:

I suggest to just upload the files in a process start form. Then, in process, create that new folder and move the document into it.

To tag onto that, this approach (while solid) requires something else that might catch some newer folks off-guard.  The file upload field still requires a folder target (else throwing an error).  Some people might be tempted to use the "Temporary Documents" folder in the Default KC, but I strongly recommend to create a "temp files" folder in your own organizational folder structure instead of using the default one.

The main issue there is that the default one still has an "Expiration" time set, and files uploaded into a folder / knowledge center with an Expiration time will keep that expiration time even after they're moved to a completely different target location - and there is not any easy way to tell until they suddenly disappear after 6 months or whatever the timer is.