Object rules are exclusive to generic surveys. They can be written for one or more questions and include a certain condition, which may result in true or false. If the condition is true, one or more actions defined in the rule will be automatically executed in the object associated with the survey. It is through these rules that it is possible to provide or update values provided for business component or asset properties and attributes.
A rule has the following logical structure:
|
If (the condition created is true)
Then (execute a specific action) |
Thus, each object rule contains a logical condition, which can be true or false depending on the responses provided by the interviewee to the questions associated with the rule. Each rule also includes one or more actions. Each action, in turn, is associated with one or more properties or attributes of the business component or asset for which the survey will be sent. When the condition for an object rule is true, the system automatically updates the properties or attributes of the object.
To check whether there are inconsistencies within a rule, you can validate object rules before publishing a survey. If any rules are inconsistent, validation messages will appear indicating possible errors. Note that rules with errors can be saved, but the surveys cannot be published until they have been corrected.
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 object 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.