Question rules are created if you want to control which questions will be visible or hidden from interviewees. By default, all questions are visible. However, some questions may not make sense depending on answers provided to other questions. If an interviewee says there are no security guards in the building, it does not make sense to show the next question, which asks if the security guards are also on duty on weekends. This second question can be hidden by creating a rule in which the first question will influence the second dependent question. Note that question rules that influence the visibility of other questions can only be written for List of Options questions, while any type of question can be dependent.
In addition to rules that control the visibility of questions, rules can also be created so that any comment or attachment fields that were enabled will become required fields.
A rule has the following logical structure:
|
If (the condition created is true)
Then (execute a specific action) |
Thus, if the condition of a rule created for a question is true, the actions defined will be executed.
Keep in mind that the system supports up to 300 rules per survey without suffering any performance loss. This number includes all rules – control, object, or question, depending on the survey – created for a single survey. Therefore, when creating new question rules, it is important to note whether there are other rule types so this limit is not exceeded. If the limit is not respected, the system performance will be compromised when managing surveys in the Knowledge module, but will not be affected when answering the interviews generated from these surveys.