| Table of Contents |
|---|
There are two ways you can test your forms.
...
When the 
save and test is clicked, the form is saved in the background, and the Test frevvo Test popup window displays reflecting the newly saved version of your form. The form will behave exactly as it will when users access it. To test the form, just complete it as your users would and click Submit
...
Each time you supply a value in a control, sends frevvo sends an asynchronous request to the server to validate the data. This means users will get immediate feedback while they are using your form. They do not have to wait until they click the form's submit button for example to discover that a zip code is missing a digit or that they neglected to fill in a required phone number field. Try to type letters in a number control, for example, and you’ll immediately see an error message.You'll want to test your form to make sure that you are using the correct control based on the validation you want. For example if you used a Text control for a phone number field, you'll won't see the correct error occur if you enter an incorrect phone number. Go back and edit your form to change the control type for that field from Text to Phone.
...
- Test your form and enable the developer tool.
- Open the developer tool's HTML tab and search for all instances of s-invalid in the elements tab. One way to search is to click in the Elements tab and use the Ctrl-F search shortcut. This will take you to the HTML of each control in the invalid state. The control's name can be found in that HTML, indicated by cname. Each browser may be slightly different, but here is an example in the Chrome browser:
- Now you can edit your form in the designer, find that control and fix the issue.
...
Test your form to verify that the final form and doc actions are working as expected. Make sure your final submissions are reaching their desired end point. For example, if your form Doc Action is configured to send an email or post to another system or to save to Google Drive or Sheets, you'll want to verify that this is working. Submissions errors have many possible causes. Maybe your forms is configured to send an email and you used a control template in the email wizard To field. If the email address control was filled with an bad email it will cause the submission to fail. Errors can also occur if you are posting to a web service and the web service fails. One way to debug submission errors is to set your Error Actions to {_frevvo_root_cause_msg}. A second way to debug submission errors is to use the submission frevvo submission repository. The submission repository has an error indicator on any submission that had an issue. See Submission Errors.
...
Forms can be translated to multiple languages using the internationalization feature which enables you to easily localize your forms for target audiences that vary in culture, region and language. supports frevvo supports localization from the browser's locale setting.
You can test the translation files you create and upload into by frevvo by clicking the test icon on the Internationalization screen or you can use the &locale URL parameter to initialize the form with other languages. See Multi Language Support for details on creating translations and testing locale translations .
...