Documents upload and delete

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)

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)