Gravity Perks Preview Submission

Your preview also shows what you hid in the form

You design an order form with a hidden field: a campaign code, an internal reference, a starting price. You add a final screen so the customer can review their data before submitting. If that screen shows everything submitted, the hidden field appears in front of the customer, who was never meant to see it.

A preview that summarizes "all fields" includes the hidden ones, so what you hide in the form has to be excluded on purpose from the review screen.

GP Preview Submission is a Gravity Wiz perk for Gravity Forms that adds a review step to a form. It is built with an HTML field and a merge tag, and that tag has two versions: one shows all the data, hidden fields included, and the other leaves them out. Choosing the right one is the perk's central decision.

How the review screen is put together

The perk does not bring a new field with its own look. It uses pieces that already exist in Gravity Forms:

• An HTML field on the last page: its content is filled with an entry-based merge tag.
• {all_fields}: shows all submitted data, hidden fields included.
• {all_fields:nohidden}: shows the data without the hidden fields.
• Default values: the same tags work in a field's default value, to carry data from earlier pages to later pages.

To populate fields on the same page, or to use merge tags in field labels, there is Populate Anything. Gravity Forms Conditional Shortcode lets you show conditional content inside HTML fields when used with this perk.

There are developer filters that modify the entry or the content before and after merge tags are replaced, and code snippets for specific cases, such as copying what the preview shows into a hidden field or refreshing a field when another one changes.

An idea of use: reviewing an order with a hidden field

Create a two-page form. On the first, the customer picks options and you add a hidden field with an internal reference. On the second, an HTML field with the {all_fields:nohidden} tag.

The review shows what was chosen and leaves out the internal reference; with {all_fields} that reference would appear. Take it as a starting point and adapt it to your form.

Limitations and requirements

Previews do not work with Page Transitions when Soft Validation is enabled. If you use Page Transitions, leave Soft Validation off on forms with a preview.

The review needs a final page: if the form has a single page, you must add a Page field and move the HTML field to the last one. Among its functions there is no way to edit the data from the preview itself; to correct something, the customer goes back to the previous page.

Adding the review to your form

Before you start you need Gravity Forms with at least one form created. Then:

1. Install and activate the perk with the WordPress plugin installer.
2. Open the form in the editor and check that it has several pages; if not, add a Page field.
3. Add an HTML field on the last page.
4. Click the merge tag icon next to the field's content and choose All Submitted Fields.
5. If you have hidden fields, change the tag to {all_fields:nohidden}.

Perks for multi-page forms

To improve the path through the form's pages, see GP Multi-page Navigation and GP Page Transitions. To save progress and resume later, there is GP Advanced Save and Continue. And to fill fields with data from other sources, you can review GP Populate Anything.

Answers about GP Preview Submission

Can I leave hidden fields out of the review?

Yes. Use the {all_fields:nohidden} tag instead of {all_fields}.

Does it work in a single-page form?

You need a final page for the HTML field, so add a Page field first.

Can I carry data from one page to another?

Yes. Entry-based merge tags also work in a field's default value.

Does it work with Page Transitions?

Not when Soft Validation is enabled: in that case previews do not work.