Table of Contents

Using Submit Rules

Sarto Jama Updated by Sarto Jama

What are Submit Rules?

Submit rules determine where the user is redirected after they submit a form successfully. This is often a crucial piece of setting up workflow, as you can redirect a user from one form to another - or to any other page in your app which your user can access.

Build Submit Rules

Submit rules can be accessed in the Settings menu for your form. Select the Rules option under the Form Menu and Submit Rules on the following menu:

Add a Submit Rule

Each form will include one submit rule by default. This rule cannot be removed. You can add additional submit rules by clicking the Add Rule button below your default submit rule:

Edit an Existing Submit Rule

The criteria for your submit rule can be edited directly in the settings screen. You can also rearrange the order of your submit rules by clicking the ‘move’ icon for that rule and dragging it above or below your existing rules:

Copy a Submit Rule

You can copy existing submit rules by selecting the copy icon in the top right corner of the rule.

Submit Actions

There are 5 actions that you can choose for your submit rule. The action that is chosen is what determines what occurs once your form is submitted.

Show a confirmation message

After submission, the form will fade out and the confirmation text will appear. 

There are two additional options here: 

  • Show a link to reload a form 
  • Automatically reload the form

Below is an example of a form that displayed a confirmation message and a link to reload the form once the form was submitted:

Redirect to an existing page

After submission, the user will be redirected to an existing page in your app that you have specified. Submit rules can redirect the user to existing parent/top-level pages and any child page that shared the same data source as the form.

Redirect to the parent page

After submission, the user will be redirected to a parent page. This is perfect if your form adds a child record, and you want to send your users back to a page showing all parent records.

Examples

  • After a user creates a record, send him/her back to the parent page with a table showing all records for that object
  • Upon form submission, redirect the user to a page with a rich text view which serves as a "thank you" page.

Redirect to another website's URL

After submission, the user will be redirected to any URL of your choosing. For example, upon form submission, send the user to an existing "thank you" page at the end of their workflow.

Redirect to a new child page

Create a new child page to which to direct the user.

You can add any views you wish to this page, and it will automatically work with the form's record. This means you can have a user insert a new record and immediately be redirected to that records relevant views (a details view, for instance).

When

This is the condition(s) that triggers the submit rule:

You can add multiple conditions for each rule based on field values by clicking on the green ‘+’ button next to your rule. Please note that if you do add multiple conditions here, all conditions must be true in order for your submit rule to trigger.

Please note that you will not be able to add conditions to your first, or default, submit rule.

Notes & Troubleshooting

  • If a submit rule does not seem to be working, make sure you don’t have a second one with the same trigger, as the second one will take precedence over the first.
  • You will not be able to add ‘When’ conditions to your first, or default, submit rule. Your default submit rule will trigger with every form submission that doesn't match another submit rule.

How did we do?

Calendars

Menus

Contact