A validation form is where you first enter codes or values that will be used throughout some functional area in Banner. Any time you reference one of these codes on another form, Banner will "validate" it, or check that the code is active and able to be used.

Validation forms are generally the first types of forms that get set up in your system, because so many other forms use the values defined on them. Since the codes on these forms are referenced from many other forms, validation forms are updated infrequently. For example, your institution may need to create a new type of employee code only once a year or so.

Validation forms are the backbone of "LOVs," or lists of values (those little windows that display values that you can select when you're using a related form). For instance, blue fields on the forms you use generally allow you to double-click in that field, and then display a little window that has values you can choose for that field. Those values were originally entered on a corresponding validation form.

Wait, wait, wait! Before you change a code or create a new one, think about how that change will impact all the forms and functions that currently use it. A seemingly insignificant change can sometimes manifest itself in unforeseen ways in your Banner system.

Havin' trouble creating a new code? That's because validation forms are often protected from updates according to the Banner security at your institution. You might not have the necessary authorization to create a new code. Banner's kind of like the FBI that way.

Find out more about naming conventions for forms.

Learn more about lists of values (LOVs).