/
edit_form_main_tab.html
166 lines (147 loc) · 7.56 KB
/
edit_form_main_tab.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
---
layout: default
navPage: docs
heading: Main Tab
breadcrumbs:
- User Documentation,/userdoc/
- Form Management,/userdoc/form_management/
- Main Tab
prev: Editing Forms,/userdoc/form_management/editing_forms/
next: Fields Tab,/userdoc/form_management/edit_form_fields_tab/
categories: userdoc
tags: permissions
---
{% include open_section.html nav='nav_userdoc_form_management.html' selected='edit_form_main_tab' nav_width=4 %}
<p>
{% include screenshot.html item="i219.jpg" %}
The main tab contains the main settings for your form. Each setting is explained
individually below. Note, some settings (such as the entire Extended Form Info section)
only appear depending on how your form is configured. This was done to hide away
all the settings you don't need to see.
</p>
<p>
One thing you should know: Form Tools is very lenient in the way it receives and accepts
the data. So even though you may configure a form to be set up as a multi-page API form,
you can actually create 10 other forms that submit to the same form ID, only containing
a subset of the fields. Sometimes scenarios like this arise and it's good to know Form
Tools will let you do it.
</p>
<br clear="all">
<h3>Main Settings</h3>
<div class="row">
<div class="col-lg-2"><code>Status</code></div>
<div class="col-lg-10">
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:
{% codemirror html %}
<input type="hidden" name="form_tools_inactive_form_redirect_url" value="http://yoururl.com" />
{% endcodemirror %}
That will automatically redirect all users to a custom URL if and only if the form
is set to inactive/offline.
</div>
</div>
<div class="row">
<div class="col-lg-2"><code>Form Name</code></div>
<div class="col-lg-10">
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!
</div>
</div>
<div class="row">
<div class="col-lg-2"><code>Form Type</code></div>
<div class="col-lg-10">
This lets you choose between the External and Internal form types. For more information
about the meanings of these, see <a href="../form_types">this documentation page</a>.
</div>
</div>
<h3>External Form Info</h3>
<p>
If you chose "External" for your form type, a new section shows up with the following settings. Precisely what
settings appear in this section depend on the values you select, but here are ALL settings.
</p>
<div class="row">
<div class="col-lg-3"><code>Submission Type</code></div>
<div class="col-lg-9">
This tracks whether your form data is being submitted directly to the process.php
script, or via the API.
</div>
</div>
<div class="row">
<div class="col-lg-3"><code>Is Multi-page form</code></div>
<div class="col-lg-9">
Whether or not the form is actually a multi-page form.
</div>
</div>
<div class="row">
<div class="col-lg-3"><code>Form URL</code></div>
<div class="col-lg-9">
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.
</div>
</div>
<h3>Permissions / Other Settings</h3>
<div class="row">
<div class="col-lg-3"><code>Access</code></div>
<div class="col-lg-9">
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
<a href="../form_permissions">Form Permissions (who sees what?)</a> page.
</div>
</div>
<div class="row">
<div class="col-lg-3"><code>Delete associated files when deleting submission</code></div>
<div class="col-lg-9">
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 <b>yes</b>, but you're free to change
it here.
</div>
</div>
<div class="row">
<div class="col-lg-3"><code>Strip tags in form submissions</code></div>
<div class="col-lg-9">
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 <b>incoming</b> 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.
</div>
</div>
<div class="row">
<div class="col-lg-3"><code>Edit Submission Page Label</code></div>
<div class="col-lg-9">
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 <i>dynamic content</i>. Click the icon to see a dialog
window containing the available placeholders. Here's what's available:
<ul>
<li>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
<b>{$LANG.phrase_edit_submission}</b>.</li>
<li>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.
</li>
</ul>
By default this setting is set to the string: "Edit Submission".
</div>
</div>
<div class="row">
<div class="col-lg-3"><code>Add Submission Button</code></div>
<div class="col-lg-9">
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.
</div>
</div>
{% include close_section.html %}