General guidelines for validation

You should be aware of some guidelines when performing validation on forms. Typically, you associate forms with data models. That lets you trigger validation as part of binding an input user interface control to a field of the data model. You can also perform some of the following actions:

  • If possible, assign validators to all the individual user-interface controls of the form. You can use a validator even if all that you want to do is to ensure that the user entered a value.

  • Assign validators to multiple fields when necessary. For example, use the CreditCardValidator or the DateValidator with multiple fields.

  • If you have any required fields, ensure that you explicitly call the validate() method on the validator. For more information, see Validating required fields.

  • Define a Submit button to invoke any validators before submitting data to a server. Typically, you use the click event of the Button control to invoke validators programmatically, and then submit the data if all validation succeeds.

The following example uses many of these guidelines to validate a form made up of several TextInput controls:

<?xml version="1.0"?>
<!-- validators\FullApp.mxml -->
<s:Application xmlns:fx="" 


            private var vResult:ValidationResultEvent;

            // Function to validate data and submit it to the server. 
            private function validateAndSubmit():void           {
                // Validate the required fields. 
                vResult = fNameV.validate();
                if (vResult.type==ValidationResultEvent.INVALID) 
                vResult = lNameV.validate();
                if (vResult.type==ValidationResultEvent.INVALID) 

                // Since the date requires 3 fields, perform the validation 
                // when the Submit button is clicked. 
                vResult = dayV.validate();
                if (vResult.type==ValidationResultEvent.INVALID) 
                // Invoke any other validators or validation logic to make
                // an additional check before submitting the data.

                // Submit data to server.

        <!-- Define the data model. -->
        <fx:Model id="formInfo">
        <!-- Define the validators. -->
        <mx:StringValidator id="fNameV" 
        <mx:StringValidator id="lNameV" 
        <mx:PhoneNumberValidator id="pnV"

        <!-- Invoke the DataValidator programmatically. -->
        <mx:DateValidator id="dayV" 
            daySource="{dayInput}" dayProperty="text" 
            monthSource="{monthInput}" monthProperty="text" 
            yearSource="{yearInput}" yearProperty="text"/>

    <!-- Define the form to populate the model. -->
        <mx:FormItem label="Month">
            <s:TextInput id="monthInput"/>
        <mx:FormItem label="Day">
            <s:TextInput id="dayInput"/>
        <mx:FormItem label="Year">
            <s:TextInput id="yearInput"/>
        <mx:FormItem label="First name">
            <s:TextInput id="fNameInput"/>
        <mx:FormItem label="Last name">
            <s:TextInput id="lNameInput"/>
        <mx:FormItem label="Phone">
            <s:TextInput id="phoneInput"/>

    <!-- Define the button to trigger validation. -->
    <s:Button label="Submit"

The executing SWF file for the previous example is shown below:

In this example the following actions occur:

  • The associated validator executes whenever the TextInput control dispatches a valueCommit event.

  • The click event for the Button control invokes the validateAndSubmit() function to perform final validation before submitting data to the server.

  • The validateAndSubmit() function invokes the validators for all required fields.

  • The validateAndSubmit() function invokes the DateValidator because it requires three different input fields.

  • Upon detecting the first validation error, the validateAndSubmit() function returns but does not submit the data.

  • When all validations succeed, the validateAndSubmit() function submits the data to the server.