• Replies 7 replies
  • Subscribers 14 subscribers
  • Views 8850 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Best Practices

Wizard Form vs Chained User Input Tasks for a user form flow

Larry Nguyen

What is the preferred way to build out a user form flow (complete screen one to fill out general info, complete screen two to fill out detailed info, screen three is confirmation / submission)?  When would you choose a wizard form (one sail interface that controls the flow and saves all the values) vs a process model that calls multiple user input tasks as the user progresses in the form flow?

  Discussion posts and replies are publicly visible

Parents
  • The advantage of the wizard is it gives you greater flexibility to redesign the interfaces without having to manipulate the process models and you have fewer process model paths to create, manage, and test (Save, Save & Exit, Back, Next, etc) so your process models become simpler. However, as stated earlier, you do lose the process history so you need to decide how important is the process history vs the flexibility to redesign interfaces.
Reply
  • The advantage of the wizard is it gives you greater flexibility to redesign the interfaces without having to manipulate the process models and you have fewer process model paths to create, manage, and test (Save, Save & Exit, Back, Next, etc) so your process models become simpler. However, as stated earlier, you do lose the process history so you need to decide how important is the process history vs the flexibility to redesign interfaces.
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.