Overview
The wizard allows completion of a long or unfamiliar task by dividing it into steps and guiding people through it.
Look and feel
When to Use
Recommended
- Create an entity which has a complex structure or many attributes related to it.
- Create an entity which attributes are dependent on previous choices (branching paths).
- Guide a person through long or unfamiliar task.
Not Recommended
- Avoid creating an entity in two steps or less. Consider using a dialog instead.
- Avoid creating an entity in nine steps or more. Consider simplifying or automating parts of the flow itself.
- Avoid editing of entities. Use a dialog or in-place editing instead.
Anatomy
Modal Dialog
In technology products, wizards are displayed inside of modal dialogs. As wizards typically take time to complete, they should block the UI until a task is complete or canceled. A modal dialog allows blocking of the interface without using page context. Dialogs have the benefits of being called from any part of the product, making the wizard highly reusable. In addition, dialogs allow for easy and fast negative path navigation since they close as soon as a person cancels the wizard.
When setting up the dialog for displaying wizards consider the following properties and their recommended values. Adjust the values if needed to best fit your scenario.
See also:
Dynamic Page
To make the wizard consistent with the Fiori floorplan, a dynamic page layout is placed inside the dialog. The dynamic page is used to provide a consistent and standards-compliant look. In addition, it also provides the title and footer to ensure proper wizard function.
When setting up a dynamic page for displaying wizards consider the following properties and their recommended values. Adjust the values if needed to best fit your scenario.
See also:
Wizard
The wizard is the bread and butter of this floorplan. It will contain the content of your guided procedure or complex task. When constructing it consider the flow you are creating and follow the rules below to achieve proper navigation and actions.
Wizard Actions
The footer contains the wizard actions which allow people to navigate it. The following table describes their usage.
Wizard Steps
When constructing the wizard steps consider the content and make sure the steps contain logical pieces of information.
Recommended
- Have a clear title for each step. If possible make sure that step titles are present in the application UI.
- Use Forms for creating logical groups of inputs. Use multiple forms sparingly as it affects performance.
- Favor vertical form layout over horizontal form layout.
- Use appropriate input controls for the data type you are working with.
Not Recommended
- Avoid using lists and tables in wizards unless they are needed for selection.
- Avoid master-detail patterns. If possible use branching paths instead or simplify the flow.
- Avoid nested dialogs or wizards. If possible use popups.
Writing Wizard Steps
When using the wizard floorplan, formulate the texts for each step as follows:
- Use a noun for the name of the step (for example, “Authentication”).