Ask: form

When you need to elicit more than one piece of information you can use the ask form node type. It is designed for web front-ends. One form can have multiple input fields.

The fields to elicit can be configured as part of the node. In this example we configured three fields of type "Custom". They are required (so can't be skipped, see the little asterisk sign). The other fields (without the asterisk) are optional.

he following parameters can be configured for a form field:

Property	Description	Explanation
Title	The label for the field
Type	The type of the field determines how the field is validated and stored.
Required	Toggle when the field is required and cannot be skipped.
Remember in user.<var>	Toggle when you want to remember the field in the user object	Only use when the value identifies this user.
Assign to	Fill in with a name of a variable to store the value in	Use primarily when the expected value doesn't identify this user. Like when you are asking for some one elses phone number.

Field types

The following types are supported:

Field type	Description	Where it is stored
First name	The first name of a user	user.first_name
Last name	The last name of a user	user.last_name
Email	The email address (needs to be a valid email format)	user.email
Phone	The phone number (needs to be a valid phone number)	user.phone
Custom	See custom fields

Custom fields

Custom fields can be used for any type of information. It needs more properties to be configured since its behaviour isn't fixed by its type.

At the time of writing their is a non-blocking issue that text fields in embedded fields show as red while they are perfectly fine. It is a known issue and will be fixed.

Property	Description	Explanation
Title	The label for the field
Type	Custom
Required	Toggle when the field is required and cannot be skipped.
Remember	To store the variable in the user object
Assign to	The name of the variable to store it in
Text area	Wether to render a multiline text area or just a single line
Default value