Step Field
Purpose
The Step field type is a multistep divider: it does not collect input. It splits the form into steps when Multistep is enabled on the parent Form. Each step can have Prev/Next button text, an icon, and optional step title and description. The form shows one step at a time.
When to use
- Long forms that you want to break into logical sections (e.g. details → address → payment).
- When the Form module has Multistep enabled and you want to define step boundaries.
Key settings
- Field — Field Type: step.
- Step — Step Prev Text, Step Next Text, Step Icon, Step Title, Step Description.
Top features to configure
- Step Prev/Next text — Rename buttons to match your flow (for example, “Back” and “Continue”).
- Step title and description — Give users context at each stage.
- Step icon — Add a visual cue for each stage in longer multistep forms.
- Step order — Arrange step markers to keep progression clear and predictable.
Validation behavior
- Step fields do not collect data; they control navigation and grouping.
- Required fields in a step must pass validation before users can continue.
- Step ordering affects form flow, so marker placement is critical.
Common mistakes
- Adding Step fields without enabling Multistep on the parent Form.
- Placing fields in the wrong step order, causing confusing navigation.
- Using vague step titles that make progress unclear.
Verify it works
- Move through each step using Prev/Next and confirm progression works.
- Test required fields in each step and ensure users cannot proceed when invalid.
- Submit a full multistep flow and verify final entry data includes all step values.
What's Next
- Configure Multistep form for full step behavior options.
- Use HTML content to add instructional blocks between steps.
- Check FAQ if step navigation breaks or skips validation.