Custom Form Validation in Workflow Solution

Good video Chris. Keep up the good work.

Very nice.
With your help, Chris, I built a similar validation in a form, but since I am use the Date/Time picker (instead of just the Date picker), I don't have the option of customizing validation inside of the component. To accomplish my validation, I have done the following:

1. Create a box somewhere in your form
2. Doubleclick on the box you just created
3. Click on the Functionality tab
4. In the Output Paths: field, find the button that you want to use to trigger the validation, then put the black dot in the circle next to Optional for that button
5. Set the Visible: field to "False"
6. Check the Use Custom Validation: box, then follow Chris's instructionsfor creating the Custom Validation Model

Does anyone know the EXACT logic (regular expression) behind the "Internet e-mail address" validation ?   All the comments and examples that reference this validation use x@y.com as the "valid format".  This isn't correct ... there really are TLDs other than dot.com !   What about x@y.net, x@y.us, x@y.co.uk, and so on throughout the world ?  All valid addresses.

My description above was too simple when I mentioned x@y.com.  With a little reverse engineering, it appears that the Find Common Pattern component is filtering against this expression:

x@y.z

Where x, y and z can be any string.  z can be a string with a dot in it as well, for example co.uk.  I tested with your examples and they all worked, but any variation from x@y.z did not work (for example x@y).

If you want to make sure that someone puts in a TRULY valid email address, i.e. one that actually exists instead of just matching a pattern, there are web services that you can call (via the Web Service Caller Generator) to validate an email address.  I'm not sure if there are any free ones, though...there may be a subscription fee for such a service.

Good luck.

Good response, Chris. I discovered this article on the subject... It can be quite complex.
http://www.regular-expressions.info/email.html

And you're right, it's getting more and more complex each year with the addition of new top-level domains. 

Also I haven't worked with it in some time, but I believe you can use the FindMultipleMatchesComponent to put in your own Regex expression(s), if you want to have more control over the exact validation.  Last I checked this component did a good job of telling you whether there was a match or not, and what the index (first position) of the match was, but it didn't give you a length or an easy way to get the actual "matched object" into its own variable.  But for the purpose of validating a field to determine whether there is a match or not, this component should give you more flexibility to do that if the built-in expressions aren't perfect for your needs.