...

When a form has sections or tabs, the submit button may be disabled due to invalid controls that are not currently visible. For example, a section that is collapsed or a tab that is not currently selected may have an invalid control. This is indicated in the header section and tab label color changing to red.

Image RemovedImage Added

Optional Sections

Optional sections can cause the validity of a form to change dynamically. For example, consider the following form:

Image RemovedImage Added

The only required field in the form is Name and since it contains a valid value, the Submit button is enabled and the form may be submitted. The entire Address section is optional. However, if the user chooses to enter an address, then the entire address is required. If the user enters a value in the Street field, the City, State and Zip fields will become invalid and the Submit button will be disabled until valid values are entered in the three newly required fields.

Image RemovedImage Added

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,  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.

You can find information about the section Required property here.

Input Validation

Form fields added from ' control palette have built-in validation rules.  The table below details the default validation for each control type in ' palette. Patterns added to a control change the defaults.

...

([1-9]|[1-3][0-9]|4[0-2])

Patterns i.e. regular expressions take into consideration each character that is entered instead of the whole value that is entered. Here is the explanation for the pattern shown above:

• [1-9] – means any number between one and nine will satisfy the pattern. So this covers the range of numbers between 0 and 9.
• | - OR operator   
• [1-3][0-9] – means first digit can be between 1 and 3 and second digit can be between 0 and 8 to satisfy the pattern. So this covers the range of numbers between 10 and 39.
• | - OR operator
• 4[0-2] – means first digit can be 4 and second digit can be 0 or 1 or 2 to satisfy this pattern. So this covers the range of numbers between 40 to 42

Numbers with commas

' default number control supports digits followed by an optional decimal point and multiple decimal places. Suppose instead you want to allow numbers containing commas and optionally starting with a '$' and only up to 2 decimal places. For example: $1,000.50 2,500. But also to allow numbers without the comma such as $1000. To do this:

...

<xsd:simpleType name="emailType">       
          <xsd:restriction base="xsd:string">        
                  <xsd:pattern value="[a-zA-Z0-9\-_][a-zA-Z0-9\-\+_]*(\.[a-zA-Z0-9\-\+_]+)*@([a-zA-Z0-9\-_]+\.)+[a-zA-Z]{2,6}"/>         
          </xsd:restriction>    
</xsd:simpleType>

Phone pattern

Lets say you would like to change the phone control validation from the ' current built-in pattern. Cloud customers must apply Patterns to a text control while in-house customers have two options

1. Apply patterns to a control - Like other control properties, the pattern property will not need to be redone when you upgrade .
2. Modify the built-in values in the types.xsd file. Be aware that if you modify the types.xsd file, you will have to make this change each time you perform a  upgrade or apply a  patch.

Apply a Pattern to a Control for a Phone Number

If you are using  Online, you will not have access to types.xsd. Both cloud and in-house customers, can override the pattern in the phone control by setting its pattern property. You can only restrict a built-in pattern (such as the phone control) but not change the pattern via the pattern property. For example you can add the pattern 203-\d{3}-\d{4}.  Now all phone numbers must start with area code 203.

A pattern such as ##-####-#### or ####-###-### is not a simple restriction. To impose validation against this pattern you must start with a Text control rather than a Phone control

1. Drag a Text control to your form
2. Add your pattern to the Text control's pattern property: \d{2}-\d{4}-\d{4} or \d{4}-\d{3}-\d{3}
3. Change the error message and help properties to assist the user in understanding the required pattern

Modify the types.xsd file

frevvo OEM partners may choose this method when customizing . The built-in values are shown in the image below:

Image Added

Follow these steps to change the current buit-in pattern to  ##-####-#### or ####-###-###.

If you are using  In-house (downloaded and installed on your computer), you can change ' built-in patterns for the Phone control by:

1. Stop  if it is running. 
2. Unpack the frevvo.war file to a temporary location of your choice: e.g. c:\tmp\frevvo-war.
3. Edit c:\tmp\frevvo-war\WEB-INF\data\users\types.xsd,
4. Change the element phoneType as shown in the code block below: Save the changes to the types.xsd file. 

5. Rezip all the files in the c:\tmp\frevvo-war directory, even the ones you did not edit.

6. Zip will often give your zipfile a .zip extension. Make sure you change this to a .war extension. 

7. Copy the updated frevvo.war file to <frevvo installdir>/tomcat/webapps.
8. Restart your  form server. Now all your phone controls will validate against this pattern.
   
   

<xsd:simpleType name="phoneType">     
    <xsd:restriction base="xsd:string">         
        <xsd:pattern value="\d{2}-\d{4}-\d{4}"/>         
        <xsd:pattern value="\d{4}-\d{3}-\d{3}"/>
    </xsd:restriction> 
</xsd:simpleType>

If you are using  Online, you will not have access to types.xsd. You can override the pattern in the phone control by setting its pattern property. You can only restrict a built-in pattern (such as the phone control) but not change the pattern via the pattern property. For example you can add the pattern 203-\d{3}-\d{4}.  Now all phone numbers must start with area code 203.

A pattern such as ##-####-#### or ####-###-### is not a simple restriction. To impose validation against this pattern you must start with a Text control rather than a Phone control

1. Drag a Text control to your form
2. Add your pattern to the Text control's pattern property: \d{2}-\d{4}-\d{4}|\d{4}-\d{3}-\d{3}
3. Change the error message and help properties to assist the user in understanding the required pattern

...