Most sets can be processed using one of the standard logic types, with your changes. However, imagine what would happen if a new printing or generation of a form caused it to look different enough to require a new form definition in FORMS. If several generations of a form were in use at the same time, it would be inconvenient to sort them by hand before processing.
To solve this problem, FORMS has a function called Alias.
|
Form structure |
Level |
From |
To |
Seq |
Break |
|
Questionnaire 1A |
1 |
1 |
999 |
1 |
Page=1 |
|
Questionnaire 1B |
= |
|
|
|
|
|
Questionnaire 1C |
= |
|
|
|
|
In the above example, there are different generations of the same form, but they are handled identically. That is, three form definitions are processed as if they were one, indicated by the equal sign (=), which we call the alias sign here, under Level.
Another way to solve the problem of forms with slight variations is to use flexible forms functionality.