Validator Types

This section documents each validator type available in the DAQS rule editor — what it checks, how it works, and what it will not catch.

Each validator only evaluates what the filter returned. If the filter does not provide the correct structure or value, the validator will produce misleading results.

---

Pages in this section

Validation Name

How to write a clear, actionable validation name. The name is shown directly in the Revit plugin — it must communicate the problem without context.

Value to Validate

How to point the validator at the correct field in the filter output. The bridge between filter and validator.

Boolean Validators

Checks for true or false. Includes the Revit tri-state pitfall: Unset is not False.

Float Validators

Comparisons for decimal values: equal, not equal, greater than, less than.

Integer Validators

Same comparison logic as float, but for whole numbers only.

List Validators

Membership checks against a fixed list of allowed or forbidden values. Includes keyword-based matching.

Null Validators

Existence checks: should be null (must not be set) and should not be null (must be set).

Property Validators

Structural checks on the filter output: whether a property key exists or should be absent.

String Validators

Text comparisons: equal, contains, empty, matches regex. The most commonly used and most commonly misused validator type.