Documents upload and delete

RE: Documents upload and delete

Mike Schmitt — Tue, 04 Feb 2020 15:18:35 GMT

If it's the user that decides an incorrect file was uploaded, that's fine (and a normal use case) -- you would then need to build in the capability in your interface for the user to "delete" the file (i suggest for record-keeping purposes, you not actually delete files except for ones used very temporarily, but instead, move them to a special designated location within Appian's folder structure for "deleted" files, and have a flag in the database table for each document to also indicate its "deleted" status).

The recipe Stewart posted in his earlier reply would only need a small addition to accomplish this - add an extra column at the end of the grid, and configure it to contain a "delete" link (either text, or icon, etc), which could then submit the form, mark that document as "deleted" in the database and move it to the "deleted" folder location (or actually delete it if you are required to), then loop back to the same form again.

RE: Documents upload and delete

srilakshmit — Tue, 04 Feb 2020 15:09:25 GMT

Hi Mike,

Thanks for clarifying.

What if user upload an incorrect file and submit which gets stored in database. So he needs to upload the file again and delete the older document.

RE: Documents upload and delete

Stewart Burchell — Tue, 04 Feb 2020 14:40:44 GMT

So...it's a little unclear in places what you're asking for but I can try to cover all the bases...so:

in your interface you can use the https://docs.appian.com/suite/help/19.3/File_Upload_Component.html to upload files. This comes with the ability to remove the file within the same component BEFORE you submit the form to the process. That might address your requirement to remove documents accidentally uploaded, but only BEFORE you submit the form.
once the form has been submitted the document objects are now available to your application and you can, for example, render them in an interface and could run a deletion process from that point if you need to delete AFTER the original upload form has been submitted.
A typical pattern is that a database table is used to hold metadata about the document, including the document's objectId (as a 'pointer' to the document). You can then use this database table as the source for a user interface table, and then you can run deletion activity from this interface (again, there are a variety of patterns available to you)
Here's one recipe that might help you get started: https://docs.appian.com/suite/help/19.3/recipe-display-multiple-files-in-a-grid-for-editing.html (there are plenty of other examples you can draw upon to help you achieve your objectives)

RE: Documents upload and delete

Mike Schmitt — Tue, 04 Feb 2020 14:30:08 GMT

I'm a little confused by what your requirement / desired process flow is here?

[quote userid="43346" url="~/discussions/f/user-interface/18265/documents-upload-and-delete"]a user should upload multiple documents[/quote]

(simple enough...)

[quote userid="43346" url="~/discussions/f/user-interface/18265/documents-upload-and-delete"]and delete any accidentally uploaded documents[/quote]

what/who is determining which document(s) are considered as "accidentally uploaded"?

[quote userid="43346" url="~/discussions/f/user-interface/18265/documents-upload-and-delete"]the process model would kick start where the documents details get stored in database.[/quote]

(this sounds fine also. should be straightforward to implement.)

[quote userid="43346" url="~/discussions/f/user-interface/18265/documents-upload-and-delete"]Also,we need to delete the documents[/quote]

Why would you delete the documents just after uploading? Am I missing something?

[quote userid="43346" url="~/discussions/f/user-interface/18265/documents-upload-and-delete"]

After file upload , Need to get the link to download.

[/quote]

FYI there isn't really any "link" to get, really - all you need is the Appian Document ID for each uploaded document (which you get automatically after submitting the original form the document(s) were uploaded on), and a!documentDownloadLink() on an interface. So just make sure your database row for a document includes its Appian Document ID.