https://legacy.forums.gravityhelp.com/topic/feature-suggestion-help-icon-on-form-settings Gravity Support Forums Topic: Feature suggestion: Help Icon on Form Settings en-US Sun, 19 Apr 2026 19:59:29 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/feature-suggestion-help-icon-on-form-settings#post-32437 Fri, 12 Aug 2011 17:38:13 +0000 sirspacey 32437@https://legacy.forums.gravityhelp.com/ <p>just suggesting that when you write the documentation (<a href="http://www.gravityhelp.com/forums/topic/gravity-forms-url-redirection-query-string-price#post-32391" rel="nofollow">http://www.gravityhelp.com/forums/topic/gravity-forms-url-redirection-query-string-price#post-32391</a>) you put it there.</p> <p>I realize now it was actually a workflow issue:</p> <p>1. I add a field and save.<br /> 2. I go over to "Form Settings" the field isn't listed in the "Insert field" drop down<br /> 3. I click "Edit Forms" on the WP left side-bar<br /> 4. I click "Edit" under my form.<br /> 5. I go over to "Form Settings" and the field is listed in the "Insert field" drop down </p> https://legacy.forums.gravityhelp.com/topic/feature-suggestion-help-icon-on-form-settings#post-32415 Fri, 12 Aug 2011 14:56:24 +0000 Carl Hancock 32415@https://legacy.forums.gravityhelp.com/ <p>{Phone:1} is a field merge tag. If you insert a merge tag using the insert form field drop down, it outputs a merge tag for that field. The merge tag is replaced with the field value when the form is submitted and processed. They are placeholders for that field value and are form specific. </p> https://legacy.forums.gravityhelp.com/topic/feature-suggestion-help-icon-on-form-settings#post-32381 Fri, 12 Aug 2011 09:59:51 +0000 sirspacey 32381@https://legacy.forums.gravityhelp.com/ <p>The "Help" icon for the Form Settings on the Confirmation tab points you to a wikipedia page. I know what a query is, what I don't know is the syntax you expect. The example provided is vague, what does {Phone:1} mean. Maybe have this point to the appropriate documentation instead? </p>