Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


The first step to solving this issue is to understand which control(s) are causing this issue.There are two ways to find the invalid controls:

Method 1

  1. Install the Firebug tool, in the Firefox browser. This your browser's developer tool. This tool is a great way to find hidden controls which are invalid or required and empty.
  2. Test your form and enable the firebug developer tool.
  3. Open firebugthe developer tool's HTML tab and search for all instances of s-invalid using the search box in the tool's top-right corner. This will take you to the HTML of each control in the invalid state. The control's name can be found in that HTML.
  4. Now you can edit your form in the designer, find that control and fix the issue.


If a required control is inside a hidden section, then that section will also be invalid and you will also see s-invalid in the section control's HTML. This s-invalid is not the root cause of your bug. You will have to continue searching with firebug developer tools further to get to the actual control inside the section control that is the root cause.

Method 2

  1. Install the Firebug tool, in the Firefox browser.Install your browser's developer tool. 
  2. Test your form and enable the firebug developer tool.
  3. Click on the Console tab.
  4. Execute this JavaScript function   _frevvo.api.forms.controls.getControlErrors(); Calling this function returns a collection of objects that describe any invalid controls including the control id, control label and the error description. In the image, you can see the reported errors for an Email, Money and Date field that contain invalid data. The controls are inside of a hidden section and are not visible to the user who is trying to Submit/Continue the form/flow.


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 repository. The submission repository has an error indicator on any submission that had an issue. See Submission Errors.

When you are done testing and are ready to roll out your form, mark it public or public in tenant via the  icon and make it available by sharing it.