Skip to main content

Introduction

Similar to tabs, you may want to use a multistep wizard to reduce the number of components that are visible at once. These are especially useful if your form has a definite chronological order, in which you want each step to be validated as the user progresses.
We have different setup instructions if you’re looking to add a wizard to the creation process inside a panel resource or an action modal. Following that documentation will ensure that the ability to submit the form is only available on the last step of the wizard.

Rendering a submit button on the last step

You may use the submitAction() method to render submit button HTML or a view at the end of the wizard, on the last step. This provides a clearer UX than displaying a submit button below the wizard at all times:
Alternatively, you can use the built-in Filament button Blade component:
You could extract this component to a separate Blade view if you prefer.

Setting a step icon

Steps may have an icon, which you can set using the icon() method:

Customizing the icon for completed steps

You may customize the icon of a completed step using the completedIcon() method:

Adding descriptions to steps

You may add a short description after the title of each step using the description() method:

Setting the default active step

You may use the startOnStep() method to load a specific step in the wizard:

Allowing steps to be skipped

If you’d like to allow free navigation, so all steps are skippable, use the skippable() method:
Optionally, the skippable() method accepts a boolean value to control if the steps are skippable or not:

Persisting the current step in the URL’s query string

By default, the current step is not persisted in the URL’s query string. You can change this behavior using the persistStepInQueryString() method:
When enabled, the current step is persisted in the URL’s query string using the step key. You can change this key by passing it to the persistStepInQueryString() method:

Step lifecycle hooks

You may use the afterValidation() and beforeValidation() methods to run code before and after validation occurs on the step:

Preventing the next step from being loaded

Inside afterValidation() or beforeValidation(), you may throw Filament\Support\Exceptions\Halt, which will prevent the wizard from loading the next step:

Using grid columns within a step

You may use the columns() method to customize the grid within the step:

Customizing the wizard action objects

This component uses action objects for easy customization of buttons within it. You can customize these buttons by passing a function to an action registration method. The function has access to the $action object, which you can use to customize it. The following methods are available to customize the actions:
  • nextAction()
  • previousAction()
Here is an example of how you might customize an action: