Collaboration & Workflow

Template Variables

Last Updated: Jul 04, 2017 10:15AM PDT


Note: This article is about variables used in template workflows and calculated fields. For variables used in recipe workflowssee here.

GoFormz supports variables that represent various properties of a form that are not known until the form is filled out. This includes the form’s field values, as well as various form metadata like the form’s name, completion date, etc. Variables allow you to set up dynamic rules for your forms. For example:

Let’s go over the two types of variables -- metadata variables and field variables.

Metadata variables

Form metadata variables provide information about the form itself. GoFormz supports the following metadata variables:

  • [FORMNAME]: The name of the form.

  • [COMPLETEDDATE]: The date on which this form was completed. (If the form was completed multiple times, this will be the date of the latest completion.)

  • [USERNAME]: The first and last name of the user who completed the form.

  • [EMAILADDRESS]: The email address of the user who completed the form.

  • [OWNER_NAME]: The first and last name of the user who owns this form.

  • [OWNER_EMAILADDRESS]: The email address of the user who owns this form.

Field variables

In addition to the metadata variables, GoFormz supports field variables. These variables represent the value contained in a form field, and are represented by the form field name in square brackets. So if, for instance, your form has a field called “Customer Name” -- then [Customer Name] is the variable representing that field’s value. Field variables can be used within a form in calculated fields and auto-filled fields. They can also be used in form workflows -- for instance, you may want to use the email address in your form’s “Customer Email” field to send your customer a PDF of the completed form.
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found