A wizard specification document details all wizard requirements by determining the following information for each step (page) of the wizard:
•Object for which the wizard and any associated templates must be created.
•System and custom fields, or blocks of fields, which capture the appropriate information that needs to be gathered.
•Required fields as specified in the object definition, such as:
oThe parent project field.
oFields whose values are used in the unique ID or name patterns.
oFields that are required by the rules created for the selected object on the Create trigger--create rules are not triggered until the user reaches the end of the wizard, which is when the record is created.
oRequired custom fields to be included in the object view, and so on.
For more details on required fields, see Required Fields.
•Additional fields necessary only in the wizard. For example, parameter fields might require the user to enter a Yes, No, or Unknown value to determine the next wizard page. Such fields are not saved or displayed in the resulting record. For details, see Defining Parameters.
•Default values for certain fields.
•Additional rules to ensure the needed values are entered through the wizard.
For example, if a user selects Yes in response to a wizard question, the user must make at least one selection from a set of later-displayed check-boxes. This requirement might be accomplished using a custom block or by creating a page transition rule that directs the user to an end page.
•Error messages displayed for the user if a page transition rule is triggered.
•Prompts to help the user enter information for the fields in the record.
•The field order on each page.
•Page transitions, including dependencies on the input from the user.
The following table provides an example of a wizard requirements specification document for an insurance claim.
Wizard Design Specification Document Example
# |
Wizard question |
Field type |
Field label |
Display in record |
Wizard page component |
Comments |
1 |
What is the caller's first name and last name? |
Text |
None |
No |
Parameter |
If the caller is a third party, an action must be written to add the names to the involved party record. |
2 |
What is the caller's phone number? |
Text |
None |
No |
Parameter |
If the caller is a third party, an action must be written to add the number to the new contact record. |
3 |
Is the caller insured or third party? |
Radio Button |
None |
No |
Parameter |
Insured or third-party values •If Insured, go to #4 •If third party, go to #16 |
4 |
What is the insured's policy number? |
Search Module |
Policy Number |
Yes |
System Field |
This is the name or number of the policy. |
5 |
When did the accident occur? |
Date & Time |
Date of Loss |
Yes |
Custom Field |
This is the date of the accident. |
6 |
Where did the accident occur? 1 Location 2 State |
3 Text field 4 List |
5 Accident Location 6 Location State |
7 Yes 8 Yes |
9 Custom Field 10 Custom Field |
This is the physical location (for example, intersection of 5th and Main St.) Use State List lookup table |
7 |
Did the accident involve an intersection? |
Radio Button |
None |
No |
Parameter |
Yes or No Value •If Yes, go to #8 •If No, skip to #9 |
8 |
What Type of Intersection was involved? |
List |
Intersection Type |
Yes |
Custom Field |
Default to No. |
9 |
Did the accident involve traffic controls or signage? |
Radio Button |
None |
No |
Parameter |
Yes or No Value •If Yes, go to #10 •If No, skip to #11 |
10 |
What Type of Traffic Control was involved? |
List |
Traffic Control |
Yes |
Custom Field |
Default to No. |
11 |
Please describe the accident. |
Memo Text |
Description of Loss |
Yes |
Custom Field |
For example, the insured vehicle failed to yield right of way and made a left turn in front of claimant vehicle. |
12 |
Are there any Area Risk Factors that apply to this accident? |
Radio Button |
None |
No |
Parameter |
Yes or No Value •If Yes, go to #13 •If No, skip to #14 |
13 |
Indicate the Area Risk Factors that apply to this accident. |
Check-Boxes |
Multiple - Area Risk block |
Yes |
Block |
A rule must be added to require at least one selection. |
14 |
Additional required information |
|||||
