Formulas and validation
Computed fields and the rules that keep card data correct.
Two features keep card data trustworthy: formula fields compute values, validation rules reject bad ones.
Formula fields
A formula field is computed from other fields using a template with built-in functions and field references. Dependencies are checked when you save the field: a circular reference is rejected at definition time, so a pipe can never wedge itself at runtime.
Field-level validation
Every field type carries constraints — text length, number ranges, date bounds, attachment count / size / MIME type, allowed select options. Invalid input is rejected on the card.
Cross-field rules
Beyond single fields, a pipe can enforce relationships:
- require one of — at least one of a set must be filled
- require exactly one of — mutually exclusive fields
- date comparison — e.g. end date must be after start date
- conditional required — field B is required when field A has a value
- composite uniqueness — a combination of fields must be unique across the pipe
Rules are evaluated before a card can move on, so problems are caught at the point of entry instead of three phases later.