Setting

Definition

Wizard to which step belongs

Identifies which wizard the step belongs to.

Step #

Defines the order in which steps will be processed.  The lowest numbered step will be processed first.  For best results, steps should be sequentially numbered starting at 1.

Step Description

A description of the purpose of the step.  The description is available for display on the various wizard screens as a general tag - {%V2%}

Min access required

This is the minimum access required in order to run this step.  An access of 0 means that the user does not have to be logged in to run the step.  This is useful in designing wizards that allow users to create their own accounts on the system.  Generally, if a step requires an access greater than 0, then the wizard must supply one step to allow the user to login.  All steps that require an access level will be sequenced after the login step.  If a wizard is left on a step that requires login, and then picked up again after the site times out and logs the user out, the wizard engine will backtrack to the last step that does not require access and that will be the first step presented to the user.  Generally, the last step that does not require access is the login step.

Run under the following MIE form

Each wizard step may be run under the control of any given form on the MIE.  The form controls what displays in the top, left, right, and bottom regions of the screen, as well as which color scheme is used.  The default form to use is the Wizard form, which will not display any menu options while the wizard is running.  The is the only form to be used when a wizard has been marked as requiring completion (otherwise the user, if presented menu options, can simply exit the wizard and begin using MIE functions by clicking on one of the menu options).

Save data using schema

The wizard engine uses the same parsing and data storage logic as the rest of the edit screens on the MIE.  Data presented on one wizard screen may be from several related tables.  Generally, a schema does not need to be specified as the parsing/saving logic is smart enough to figure out the relationship of the data fields/tables presented on the wizard screen. NOTE:  the wizard can only handle a parent table and any number of related children - as long as there is only one level of children below the parent.  

Steps to execute before

List of commands to execute before the screen is displayed.

SQL to apply before

(Not implemented)

HTML used to render screen

The actual HTML, with general and merge tags, that will be used to display the screen.

HTML used to render help screen

(Not implemented)

Steps to execute after

List of commands to execute after the data from this screen is posted back and saved.

SQL to execute after

(Not implemented)