https://i0.wp.com/springboardmodulesfork2.com/wp-content/uploads/2019/04/themesmain-1.png?w=1220&ssl=1

Wizard Module

Overview

When it comes to inputting data, the two most common patterns used on the web and in applications are forms and wizards.

The electronic form is a direct descendant of the paper form: a page with empty fields that the user needs to fill in. The wizard is a mini-application that takes the user through a sequence of forms.

This modules is intended to provide the mechanism to implement wizards within K2 without the need to have to manage all the complexity of the rules of moving the user forward or backwards through the different pages.

Benefits

Business

Users can sometimes become overwhelmed by the number of fields on a form and often abort form completion.

By splitting up a complex task into a sequence of chunks, you can effectively simplify the task.

The wizard is especially good when users lack the necessary domain knowledge. Completing a task gets easier: the user can just follow a preplanned, step-by-step path to accomplish his goal:“Don’t make me think, just tell me what to do next.”

For more information and UX design patters see
https://uxplanet.org/wizard-design-pattern-8c86e14f2a38

Technical

Implementing wizard can be very time consuming and laborious and often results in a solution that can be difficult to maintain due to the rules of moving a user from one page to the other. This module aims to provide a mechanism to implement a wizard as easy as possible so the time is spent on the contents of the wizard and not the wizard itself.

Components

View Components

SBM4K2.Wizards.ViewComponents.Pager

Responsibility

This component is responsible for the hiding and showing of K2 view on a page to create the effect of a wizard based input.

  • The hiding and showing of K2 views on the page to create the effect of a wizard based input.
  • The next and back buttons and the viability of these buttons when at the start or end of the wizard index.
  • The number of pages and where the user currently is in the index.

 

Input

This component is parameter driven:

Parameter Name Description Example
listOfViewsDelimitered List of view instance names that will fall part of the wizard. View1,view2,view3
delimiter The delimiter the views are seporated by. The default is ‘,’ ;

Output

Output
Type
Name Description
Control [Public] – TotalPages Data Label Output the number of pages in the wizard

Outcome

The views that are passed in are all set to invisible and the first view is displayed.

The Next button will be visible and ready for the users to step through the wizard.

 

 

 

Published by

Igor Jericevich

Off the charts lunatic with technology

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.