| Section | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Note that controls that are optional do not cause the submit button to be disabled unless the value entered is invalid. As the figure above shows, there are no values in the optional Email Address and Phone fields but the form may be submitted. However, if the user enters an invalid value in one of the fields (required or not), the submit button will again be disabled by Live Forms .
And here is a form missing values in required fields. Therefore again the submit button in disabled.
...
If the user changes his/her mind and removes the value from the Street field, will recalculate the validity of the form and infer that the Address section is no longer invalid since it is optional. The generated XML instance document will also not contain an address element. Once again, Live Forms is automatically ensuring that it is not possible to submit a form that is in an invalid state and that would generate an invalid document.
...
Form fields added from ' control pallet have built-in validation rules. The table below details the default validation for each control type in Live Formsin ' s palette. Patterns added to a control change the defaults.
...
| Note |
|---|
Do no use the typical leading ^ and trailing $ characters in your patterns. These two characters represent the beginning and end of line markers and do not apply to Live Forms to form field values. |
| Tip |
|---|
It is important to use a text control for most patterns. For example a zip code requires a '-' character. If a '-' is used in a quanty control the pattern will fail, as a quantity control does not allow non-numeric characters. |
...
Lets say you would like to change the phone control validation from the Live Formsthe ' s current built-in pattern to: ##-####-#### or ####-###-###
...