Formulas and validation
Computed fields and the rules that keep card data correct.
Formula fields compute values and validation rules reject bad ones. Between them they keep card data trustworthy.
Formula fields
A formula field is computed from other fields using a template with built-in functions and field references. Track40 checks dependencies when you save the field, so a circular reference fails at definition time instead of at runtime.
Field-level validation
Every field type carries its own constraints, from text length and number ranges to date bounds, attachment count, size and MIME type, and the options a select is allowed to offer. The card rejects anything that breaks them.
Cross-field rules
Beyond single fields, a pipe can enforce relationships:
- Require one of. At least one field in the set must be filled.
- Require exactly one of. The fields are mutually exclusive.
- Date comparison. An end date that must fall after a start date, for example.
- Conditional required. One field becomes required once another has a value.
- Composite uniqueness. A combination of fields must be unique across the pipe.
Rules run before a card can move on, so problems surface at the point of entry instead of three phases later.