Skip to content

Commit 96aecc3

Browse files
committed
core doc update
1 parent 09e2ea2 commit 96aecc3

File tree

1 file changed

+25
-12
lines changed

1 file changed

+25
-12
lines changed

userdoc/views/main_tab.html

Lines changed: 25 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -83,20 +83,33 @@ <h3>Main Tab</h3>
8383
<div class="row">
8484
<div class="col-lg-3"><code>Default Values for New Submissions</code></div>
8585
<div class="col-lg-9">
86-
If "Can add submissions" is set to "yes", a new section will appear at the bottom of
87-
the page. This was added in 2.1.0 to allow you to specify default values for submissions
88-
added via the Form Tools interface. All you need to do is add those fields that you would
89-
like to contain default values, and specify exactly what values you want them to have.
86+
This section appears when "Can add submissions" is set to "yes". It lets you to specify default values for
87+
submission fields when added through the Form Tools interface. All you need to do is add those fields that you
88+
would like to contain default values, and specify exactly what values you want them to have.
89+
90+
This section is very important if your View has <a href="">filters</a>. Filters limit what submissions appear
91+
in the View. So unless your submission contains values that match the criteria you entered immediately after
92+
the submission is created, it may appear that creating a submission does nothing - since you can never view the
93+
submission in your View.
94+
95+
<p>
96+
Since version 3.0.13 of the Core, you can also enter the following placeholders. These work for any Form
97+
Tools user account (admin or client) and will have their values replaced with their content.
98+
</p>
99+
90100
<ul>
91-
<li>Tip: a big reason this was added was to reconcile an issue that arose when adding
92-
View Filters. Filters let you limit the results that appear in a View (e.g. only
93-
show people from Vancouver, BC). When you added a submission in that View, even though
94-
the submission was created, it wouldn't get listed in the View - because the value
95-
of the "City" field wasn't "Vancouver". So, the <i>Default Values for New Submissions</i>
96-
resolves this issue: it lets new submissions added to Views with standard filters
97-
automatically contain the appropriate values to be listed in the View. Keep this in mind!
98-
</li>
101+
<li><b>{% raw %}{$ACCOUNT_ID}{% endraw %}</b></li>
102+
<li><b>{% raw %}{$USERNAME}{% endraw %}</b></li>
103+
<li><b>{% raw %}{$EMAIL}{% endraw %}</b></li>
104+
<li><b>{% raw %}{$FIRST_NAME}{% endraw %}</b></li>
105+
<li><b>{% raw %}{$LAST_NAME}{% endraw %}</b></li>
99106
</ul>
107+
108+
<p>
109+
You may also use placeholders from the <a href="{{site.baseurl}}/modules/extended_client_fields/">Extended
110+
Client Fields</a> module here to add values from those fields. That module (version 2.1.0 and later) lists
111+
the available placeholders.
112+
</p>
100113
</div>
101114
</div>
102115
<div class="row">

0 commit comments

Comments
 (0)