Rules are parametric, which means that you can control their behaviour by setting the parameter values. This makes the system extremely flexible; rules can be configured to check, for example, project specific issues.
User interface of a parameter depends on the type of the parameter. It is also possible to have totally customized user interface (typically for rules with multiple parameters). Rules can have following types of parameters:
-
Enumeration Parameter: Used to select a value from a predefined list, usually represented by Drop-down list in user interface.
-
Numeric Parameter: Typically used to specify numeric value for the parameter, usually represented by text box in user interface.
-
Boolean Parameter: Used to set some the value on or off, usually represented by Checkbox in user interface.
-
Table Parameter:
Used for list of accepted values, list of conditions, checking of space schedule, etc. A table parameter can contain multiple rows and columns. Column types depends on the rule. It is also possible, that a value in table cell has an own editor, like a combo box (list of predefined values), or totally custom editor.
It also possible to read values from Excel to table parameter. Typically, the user interface contains these UI components listed from top to bottom. But some rules have totally customized user interface.
To set value for a rule parameter:
-
Go to the Parameters view.
-
Modify the necessary parameter values. If you modify values in a table parameter, press Enter in the table to commit the changes you made.
To restore the parameter values:
Important
After you select another rule, changes to parameter values are submitted and they cannot be canceled anymore.
-
-
Severity Parameters: The main purpose of introducing 'Severity Parameters' is to override the severity of the issues that occurs when the rule is checked. They can be used to set the severity of a particular parameter either Critical or Low.
In order to understand 'Severity Parameters', we take an example Rule, for example, 'Free Area in Front of Components'. In the following snapshot, we get issues with Critical Severity.
Now, we want that a Column having 'Length' as 2.85 m should have Low Severity Issues. So, we configure this in the Severity Parameters.
So, we set a Column having Length = 2.85 m, in the Low Severity Filter because we want that if there is an issue with Critical Severity about a Column having Length = 2.85 m, it should be changed with Low Severity issue, after passing through this filter, as shown below.
You can see that the second expanded issue turns to Low Severity issue from Critical Severity issue, because it contains a Column with 2.85 m.