One of frevvo's most powerful and useful features is its ability to automatically ensure that any submitted form generates a set of XML documents that are valid with respect to their corresponding XML schemas. frevvo does this by:
...
- Apply patterns to a control - Like other control properties, the pattern property will not need to be redone when you upgrade frevvo.
- 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 frevvo upgrade or apply a frevvo patch.
...
If you are using frevvo Online, you will not have access to types.xsd. Both Cloud and On Premise 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.
| Tip |
|---|
The Pattern property will not need to be redone when you upgrade frevvo. |
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 frevvo. The built-in values are shown in the image below:
...
- Rules, Document Actions, or Form actions are being executed
- A schema-bound / Doc URI table is populated
- A table is populated from a Google sheet
- A table/repeat control is scaled from few to many or many to few rows through rules
- A large amount of data is populated in the dropdown through query
- A ComboBox searches for a typed-in value
- PDF generation takes a long time upon form submit
One case where you will not see this indicator is when a rule/loop runs at form load and delays the opening of the landing page.
...
Assume that the user adds the element customer to the form's types. All three elements (firstname, lastname, and fullname) are required by the type. But, the form designer is not obligated to add all three controls to the form. Let's say the designer adds controls for firstname and lastname but omits fullname. The form will have two invalid controls when initially loaded.
When the user enters values in both fields, the form can be submitted.
However, this would generate an invalid XML document with respect to the schema since the schema specifies that a customer must also have a fullname. frevvo manages this automatically by creating an empty fullname element in the document. The generated document looks like this:
...