This section lists the terms and their definitions for the Wizard application.

TermDefinition

Banner Statement

A message at the top of the wizard displayed to the end-user in place of the wizard design name.

Field Class

The response type expected for a predefined input. Response type can be either Wizard Input Field or Object Field.

Input

A wizard component that is part of a step, comprising a question or instruction provided to end-users of the wizard at runtime. Values received from end-users are stored as Inputs.

Input Group Option

A wizard step setting that allows designers to choose how inputs are displayed to the end-user.

Step

A wizard component that acts as a container for an Input. Steps also contain rules that designate the navigation flow, and the object and submission actions, which are determined and executed based on the end-user responses at runtime.

Step Input Rules

These rules allow you to configure rules and expressions for your Inputs at Wizard runtime. Input rule types can be configured to enable/disable or show/hide Inputs, or to conditionally determine the focus object of the Wizard (e.g., Agreement) or conditionally determine the record type for the focus object's record to be created (e.g., SOW, NDA, MSA, etc.), or to set the value of one input based on the value of other inputs.

Wizard

A runtime instance of a wizard design that allows users to create object records following a series of steps and other guidance.

Wizard Component Library

A repository for storing Wizard components that may see reuse across various wizard designs.

Wizard Design

The framework for an object creation wizard. Contains the structure, steps, controls, and logic for all steps in a single customer-facing wizard.

Wizard Step Rules

These rules control the flow of Wizard steps at runtime. You can create GoTo rules for your steps which determine step order in the Wizard based on runtime user responses. The rules you create can be assigned as default for individual steps and can be made conditional based on expressions you create for each rule, using values from Inputs to determine whether rules are fired for any given step.