I've got a form with an email address field (using the standard Designer custom object) that is set to "User Entered - Required".
When I tested an early version of the form, this worked as expected. If the field was left blank, the required-field-empty error message appeared and the triggering event was prevented.
At some point, something I did broke the standard operation. While the field still appears with a red border to indicate that it's required, there's no message about the field being empty and the triggering event proceeds as though there's no problem. In this case, I get an email with my attached PDF and a recipient address of "null".
I haven't added any code to the Designer email field or removed any of the standard code.
Since I can't figure out what could possibly be causing this problem, my workaround is for my triggering event (a button click) to test the email field's value and provide an app.alert message if the email field is empty. The email with attached PDF still starts, though; this requires the user to pay attention to the app.alert, cancel their email, and go back to fill in the address. Not optimal.
Has anyone got an idea what could prevent a field marked Required from operating properly? Thanks.
SLDC
Thom Parker
The source for PDF Scripting Info
www.pdfscripting.com
Very Important - How to Debug Your Script