Main Tab

This setting lets you take the form offline, preventing Form Tools from accepting any more submissions from the form. Generally speaking, using this feature is discouraged for any reason other than programmatically preventing any new submissions being added to the database. For forms with temporary shelf lives (e.g. registrations for an event), you should take the form itself offline to prevent people wasting their time filling it in, only to find out the submission isn't going to be processed! However, if you do want to keep the form up but don't want the users to see the Form Tools "303" error, add the following hidden field to your form: <input type="hidden" name="form_tools_inactive_form_redirect_url" value="http://yoururl.com" /> That will automatically redirect all users to a custom URL if and only if the form is set to inactive/offline.

The form name is used in a various places throughout the program to uniquely identify your form. Try to give it as descriptive a name as possible!

This lets you choose between the External and Internal form types. For more information about the meanings of these, see this documentation page.

This tracks whether your form data is being submitted directly to the process.php script, or via the API.

Whether or not the form is actually a multi-page form.

This lets you keep track of the form URL(s). Generally it's mostly used in the Add Form process, but it can also be used later for re-Smart Filling multi-select field option groups. It's a good idea to always keep it up to date.

This determines the client permissions for this form: who can view and (potentially) edit the form submissions. For more information on this setting, see the Form Permissions (who sees what?) page.

This should be pretty self-explanatory. If you form contains file upload fields, you'll want to decide whether or not files associated with submissions should be deleted along with the submission. The default setting is yes, but you're free to change it here.

This is included for security purposes to prevent XSS attacks and the like. This setting, again, is enabled by default. What it does is strip out the contents of any tag - regardless of the tag type - from the incoming form submission data. Now, depending on your form contents this may not be desirable. If your form accepts HTML via a WYSIWYG field, for instance, you'll need to disable this. This only affects incoming form submissions. Once the data is in Form Tools you can add whatever content you want via the Form Tools UI and not worry about it being removed.

This setting lets you control the page title and heading on the administrator's and client's Edit Submission page. See the icon at the right of the input field? That means that this field allows for dynamic content. Click the icon to see a dialog window containing the available placeholders. Here's what's available:

• you can enter language placeholders (so that the title will change depending on the user account's language). Browse your language file (/global/lang) to see the available language strings. They should be entered in Smarty syntax, like {$LANG.phrase_edit_submission}.
• you can specify form field values, e.g. "First Name" and "Last Name" from your form, so that the title will be different for each submission that you are looking at. This can be a nice clear way to visualize the information better.

By default this setting is set to the string: "Edit Submission".

Like the previous setting, this field allows for dynamic placeholders. It controls the label for the Add Submission button, which appears on the Submission Listing page and (as of 2.1.0) on the Edit Submission page as well.