Base data
A switch for whether the form is active and reachable, and a name. The name is an internal one - it appears in lists and in the history, not in the storefront.
From an empty form to the first submission. Every step happens in the administration; the four deep dives below go into detail.
None of them leads into the source code.
Four cards, and none of them touches a field.
A switch for whether the form is active and reachable, and a name. The name is an internal one - it appears in lists and in the history, not in the storefront.
What the sender sees after submitting: free text with HTML or one of the four message kinds. Without your own message the text from the snippets applies.
A switch and a recipient address, per form. It does not replace the history, it comes in addition.
The tree. Everything else happens here - and only here is it decided what the form actually asks.
A form carries no sales channel and no technical name. A form is global; which channel it was filled in is only recorded by the submission.
Everything else is elements, structure included. This is what the demo form "Request product advice" looks like in the administration.
Elements
| # | Name | Type | Width |
|---|---|---|---|
| 1 | Product advice | Group, Structure element | — |
| 1.1 | Customer type row | Row, Structure element | — |
| 1.1.1 | Customer type | Dropdown (select), Input element | 1/2 |
| 1.1.2 | Advice topic | Radio (radio), Input element | 1/2 |
| 1.2 | Company data row | Row, Structure element | — |
| 1.2.1 | Company | Text (text), Input element | 1/2 |
| 1.2.2 | VAT ID | Text (text), Input element | 1/2 |
| 1.3 | Project row | Row, Structure element | — |
| 1.3.1 | Quantity | Number (number), Input element | 1/3 |
| 1.3.2 | Urgency | Slider (range), Input element | 1/3 |
| 1.3.3 | Preferred date | Date (date), Input element | 1/3 |
| 1.4 | Rush notice | Warning message, Content element | 1/1 |
The number in the first column is the outline, not the sort order: 1.2.1 sits in row 1.2, which in turn sits in group 1.
Two questions remain, and both have a page of their own.
Shopping experiences, product page, customer account. At the latter two an assignment with a priority decides which form a product or an order gets.
A history with form, context, customer, sales channel and date, plus filters and a CSV export. The export reads the stored submissions, not the current form.
Groups, rows and the twelve-column grid.
All 23 field types and what they do.
Mandatory fields, limits, CAPTCHA.
Twelve operators and the OR rule.