...

If a user clicks submit and any of the controls listed above fails validation, the controls will be highlighted with an orange color indicating that the form cannot be submitted. See above for other methods to notify users when forms are invalid.

Patterns

Patterns imposes impose additional validation on what users enter in a particular control. See Designing Forms with Patterns for information on setting a pattern on any control in your form. Patterns are XML schema regular expressions.

...

• Set the pattern to: ([0-9]{1,3},([0-9]{3},)*[0-9]{3}|[0-9]+)(\.[0-9][0-9])?

...

Numbers with Decimal Places

...

This pattern allows you to specify the number of decimal places for Number Controls. Change the number 6 in the pattern to the desired number of decimal places. Note there is a period before the second slash.

\d+(.\d{1,6})

A customized error message displays if the user enters more than the allowed number of decimal places and the control becomes invalid.

Image Added

EMail pattern

Apply this pattern to an EMail control to create a customized Email validation.

1. Drag an EMail control into your form/flow. Click on the EMail control

2. Copy this pattern into the Pattern property

   Code Block
   [a-zA-Z0-9\-_][a-zA-Z0-9\-\+_]*(\.[a-zA-Z0-9\-\+_]+)*@<your email domain>

3. Change <your email domain> in the pattern to your email domain
4. You can customize the error message that displays in the Error Message property and add a placeholder to guide your users
5. Save and Test the form/flow.
6. If users enter an email address that does not have the correct email domain, the customized Error Message displays.

If you use  In-house (downloaded and installed on your computer), you can change ' built-in patterns for the Email control by editing the ''types.xsd'' file included in the <frevvo installdir>/tomcat/webapps/frevvo.war file. This file includes the email type definition shown below, and you can edit its pattern value. See the example in the phone pattern section below for instructions to modify the types.xsd file.

...

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.

...

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

...

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

...

Modify the types.xsd file

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

...