In my opinion, I think this is mandatory to be able to use rules on attachments controls. For example : minimum 2 attachments if contract type is "Invoice", 1 otherwise

Will this have rule based logic for validations of string or number as well?

Well, this is a show stopper now for the new Applicant Tracking System I just wrote using Nintex Forms and Workflows.

Please don't forget to add File Name Validation option to the Attachment control, it will be best if the validation auto follows what's allow in SharePoint. Just experienced first hand what happens if the user attach a file with invalid file name to the form, and it's not nice.

this needs to be done into the product

I agree that this is a defect, not an enhancement. Users are not informed that they have attached a file with "invalid" characters in the file name and are not given a chance to correct the situation. Then the workflow fails and all functions included in that workflow are never executed.

I know it's a Nintex charter to try and get rid of JavaScript helps like this - please add the attachment validation soon...

Please, validate unsupported characters within the filename on attachment in Nintex Forms. (& " : * ? <> # {} % ~ / \, I would also add comma "," and plus "+" to the list as non-recommended) and sequences like ".."

If there is an attachment added to the form in a Workflow task form the user receives an error and the tast never completes. Even worse: te workflow task is locked and the workflow is STUCK...

May be this could help:

http://www.vadimtabakman.com/nintex-forms-attachment-required.aspx

Im encountering same problem too, hope someone helps. I am thinking about cutting file name due to attachment with very long file name is much worse when you have email notification with attachment. thanks for the help.

I agree with Barry that this is a Nintex bug. The Nintex form should parse the attachment file name and report the error (invalid character) to the user immediately and require that it be corrected before submitting/exiting the form.

Currently it just waits for SharePoint to report the error after the form has been submitted, at which point it is to late for the user to fix (even if they understand what just happened).

I also agree with Eric - don't change the file name out from under the user. Better that they change the file name and re-attempt the attachment.

any updates?

Adding the validations for minimum and max are helpful, but to have complete control on the dynamic validations, we will need NAMED CONTROLS added to the list of references.

We have several forms in our environment that generate user errors from the attempted attachment of file names with illegal characters. Would really like to see a built validation for these.

Any update on the Planned release? We still cannot use rules or use Named Controls within the reference. If we can use named controls then we can dynamically set the number of minimum by using a value in the named control

Please add support to conditionally require an attachment.

Nintex Forms breaks the standard SharePoint attachment name validation.

Within SharePoint standard forms characters such as ampersands are highlighted and users are prompted to correct any issues before submission. However, when using Nintex Forms there is no validation and any file name can be submitted by users.

This results in an exception when list items are created and renders Nintex forms useless for anything which relies on attachments.

In my book the fact that using Nintex forms breaks standard Sharepoint functionality makes this a bug.

Not being able to confidently attach documents within a SharePoint form is ludicrous. At a minimum attaching a document should provide the same feedback that standard SharePoint forms offer.

Validation of unsupported characters needs to be provided in Nintex Forms. It's a huge hole in attachment validation and leaves some serious gaps in attachment functionality.

Please, validate unsupported characters within the filename on attachment in Nintex Forms.
This is becoming a major headache with our customers.

Customer submitted 3 attachments and one of the attachment contain special characters in the filename. Nintex Form will insert the two valid attachments into the List item and prompt a nasty error back to the user. Error occurred during submission. The worst part, it will kick off the workflow with two attachments.

Nintex Forms should validate the special characters within the attachment filenames and warn the user about this issue instead of inserting the record into the List Item

(& " : * ? <> # {} % ~ / \, I would also add comma "," and plus "+" to the list as non-recommended) and sequences like ".." (see http://support.microsoft.com/kb/905231)