Feature Request: Phone Field Validation

  • Profile Image
    asimfarhan
    Asked on March 14, 2013 at 12:59 PM

    Hi there, 

    There's a problem in the phone filed where the user can keep inputting alphabets and numerical values ( as many as they want) in the area code field as well. 

     

    Is there a way where the user starts inputting in the area field and after the area code automatically jump to the phone number field?

     

    Many thanks!

     

    Asim

  • Profile Image
    jefreylandicho
    Answered on March 14, 2013 at 01:12 PM

    The phone field works that way by default as it does not validate the user input. You may however use a standard field text  instead and set it to accept numerica data only. To do this, first click and drag the standard text field in your form builder then click the Validation Icon and select the Numeric Option.


    If you need further assistance please contact us again.

  • Profile Image
    asimfarhan
    Answered on March 14, 2013 at 02:54 PM

    Ok thanks. I tried that but then again, with thestandard field, you cant put dashes or spaces in even if the alpha numeric option is selected from validate. 

     

    I think maybe the highly used phone filed needs to be re-thought. 

     

    thanks.

  • Profile Image
    jefreylandicho
    Answered on March 14, 2013 at 04:32 PM

    Thank you for your comment. I have forwarded your request to our developers for consideration.

  • Profile Image
    kenneth
    Answered on March 16, 2013 at 09:40 PM

    I'm able to replicate this bug. Our developers will now look onto it. Please stay put.

    Thanks,
    Kenneth 

  • Profile Image
    kenneth
    Answered on March 25, 2013 at 06:05 AM

    Hi,

    We have added a new feature into the Phone Question, we called it the Phone masking, the validation of phonenumber input is now depends on how the form owner put the masking.

    For example. the default masking is ####-#####, the # symbols represent the numbers to be entered. Try it and let me know your comments. Please try to clean your browser cache to get the latest updates.

    Thank you,
    Kenneth