Nested Wizard Forms
Last updated
Was this helpful?
Last updated
Was this helpful?
This workflow demonstrates how to display the Nested Wizard's pages as a sub-navigation within the Parent Wizard, allowing users to seamlessly navigate between sections. By integrating a Nested Wizard, users can interact with multi-step forms within a larger parent form structure. This approach enhances user experience by organizing complex workflows into manageable steps while maintaining a clear and structured navigation flow.
At times, you may want to add a Nested Wizard page to a Parent Wizard form to add more granular control over user navigation between sections. Here is an example Wizard Form that will be used as a Nested Form inside a Parent Wizard.
When a Nested Wizard form is introduced into a Parent Wizard form, the Nested Wizard pages will be added to the Parent Wizard navigation bar.
In most cases, this interface is not ideal, as users typically prefer the Nested Wizard navigation pages to be separate, functioning as a sub-UI within the Parent Wizard page, as shown below.
Create a Wizard form that will be included in the Parent Wizard.
Navigate to a Project and create a new Form.
Click the Display as Form and select Wizard.
Create Wizard Pages by clicking the +Page button
Add fields to the Wizard pages
A parent form will be needed to house the Nested Wizard pages.
Create a new Form
Click the Display as Form and select Wizard.
Create Wizard Pages by clicking the +Page button
Add a Container component to the page of the Parent Wizard a Nested Wizard should be added to.
Add the Nested Form inside the Container component
Click the Form dropdown and select the Child Form
Save the Form
Use the Form to confirm the UI is working as expected.
Data within a Container component is stored as an object inside the parent form’s submission.
This example will showcase how to utilize a component to improve the wizard page navigation UI.
Wizard button labels (Cancel, Previous, Next) and functionality can be customized to enhance the user experience.
If Wizard navigation is not needed, consider using the component as an alternative.