Concept: File upload form control

Looks great ‌!!

One question though; would there be a minimum number of attachments or is that implied with "required"?  What if we wanted a minimum of 3 and a maximum of 5?

Looks good Guy and very intuitive.  I'm assuming the "pdf, docx etc" accepted message is auto generated based on what extensions the designer allows.  I'm also assuming there's some other text if we accept any file extension.

looks sharp guys, well done and thanks for listening to our feedback

Some thoughts of mine are:

In the inital state, could the file types sit under the file size, just to keep all the requirements grouped together for the end user, currently the file types sit next to the select button. This can include other requirements as well eg required field, maximum numbers of attachments.

Highlight the drag functionality, over the select file button. Currently the select file is more prominent.

I wouldn't want to see the ability to have unlimited file size attachments, make this required always to eliminate human errors, this could even effect Nintex servers and performance if they were large gigabit files.

By default, can they block executable files (or other high risk attachments that have viruses), even before they are submitted.

When a attachment is being uploaded, disable the submit form button until the upload is completed.

This is a great starting point and as always feedback and continuous improvement will occur once we can use it in real world scenarios.

Anthony  

What if we want to allow ANY file attachment type EXCEPT particular types?

In most cases it will be a certain amount to allow but I am sure we will run into the opposite.

As an aside, it's an often requested feature to be able to attach metadata to a file upload. So for example, a dropdown / free text next to each attachment to say which it is. Is there any way to add this here? Or is that a far-down-the-road thing.

Last comment is that it would be nice to see a preview of the file - whether it's by mousing over, or a thumbnail just shown as the file attachment. Sometimes people can't recall the names of each thing (or they don't follow good naming conventions ... so many people don't... bleh!) so that'd be awesome.

Looks great, so happy to see this is getting added so quickly!

rhia

Everything has been said

Looking forward to test it

Hi Chris,

Thanks for the feedback.

1. Yes - I had thought that the "file's accepted text in the form would be created automatically.
2. I had thought that the form designer could just leave the file type section blank to accept all file types.  Considering Rhia's comment below, I think I need to look at some sort of qualifier/drop down for this like "<Accept/reject> file types". 

Cheers,

Guy

Hi Anthony,

Appreciate your time in writing this.  I definitely want to style this control a little more.

1. File types layout: I take your point.  
2. "Drag files here" prominence:  Fair point again.
3. File size limit:  I think this bit eager on my behalf :-)  Will need work out what the maximum is technically and then either perhaps say " (empty is 100mb)" OR give a drop down with common sizes.  Which works better for you?
4. Reject file types:   I agree.  I think (with Rhia's point) that I need to move a <Accept / reject> file types UI.  In this way you could specify to either accept all file types except for .exe OR reject all file except for .pdf (just an example).'
5. Submit button disabled:  That's a good idea. Will need to see if this can be done

Cheers,

Guy

:-)

Hi Rhia,

Thanks for your feedback.

1. File attachments:  Great point.  Does moving to a sort of <accept / reject> toggle with file types work?  In this way you could toggle "Accept just these file types" OR "Reject these file types but accept everything else"

2.Metadata:  Interesting.  Is your requirement that the person completing the form needs to select a file descriptor from a dropdown from a specified list or that they are able to add a description in a text field?  Or both ?  :-)

3. Image preview:  This does indeed sound awesome. In the concept I uploaded, the file name is a link so that the user can select in order to download in order to review in some way. It may be possible to give a thumbnail preview of an image (way more useful) but not sure about document thumbnails.  Will look into this.

Thanks again,

Guy

Hi Cassy,

Thanks.  :-)

Good point.  I had thought that that setting the element to Required would mean at least one attachment was required.

It's interesting thinking about a range of attachments required - can you think of an example use case?

I guess the simple option is to have a min and a max field.... hmmm.... 

:-)  Thanks!

Guy

erm ok what if a visitor request and you asked for upload of photocopy of driving license and an upload of sponsor form?

or job application and you want a CV and copy of degree certificate?

bad examples but just off the top of my head...

I have an example of an expense process: you declare each payment you've done and must add one attachment per payment declared and only one.

I think this looks pretty straight forward. I think adding in a Min would be nice so then you can let users know, how many files you are looking for. Pretty much I second everything else that has been covered above. This is a nice update to the forms.

Woot! This is perfect!

I am looking to replicate an external process that we have now and this gets me one step closer to it!

Most questions/comments have been made already (and I assume it will be this easy), but will we be able to move/store the file(s) using the existing actions within NWC? I ask because right now I have to do a lot of base64 conversions to shuffle files around and am hoping I can get out of that

Overall, looks good!

Nice!

Hi ‌, in short - the file attached will be referenceable in the workflow. Hence you will be able to move/store the file(s) using the existing actions within NWC.

Interested in hearing more about the base64 conversions. Is there a custom endpoint you're sending these files to that accept it in Base64 hence you have to convert them?

Cheers,

Josh

Yes we created a custom service to convert a document to base64 so that we can leverage workflow to move documents to and from document libraries and list items.

We have an external facing form that requires attachments to be submitted with the form and we pass them through to our on-prem SharePoint environment. The attachment goes into a document library and the form data goes into a list. I am also tagging the file and list item with a GUID so that I can match the file to the list item and add it as an attachment within the workflow.

For us, it is still a process that is being fine tuned, but I want to see what other options we have and if they would make our lives easier!