- DATE:
- AUTHOR:
- The Fountain team
Format Rules for Worker Attributes
Admins can add a format rule to a custom worker attribute, so values people type in are checked before they are saved.
A custom worker attribute checked the data type but not the shape of the value. A phone number, routing number or national ID could be saved in any format, and errors surfaced later when a downstream system rejected the value.
What's new
One rule per attribute — in the Add or Edit attribute window in worker attribute settings, choose a validator that fits the attribute's data type, configure it and test a sample value before saving.
Validators for text, numbers and dates — text attributes support email, phone, bank account, US bank routing number, IBAN, national or tax ID, passport, postal code, restricted characters, length and pattern rules. Number attributes support a minimum and maximum, and date attributes support past only or future only.
Checked at entry — on the Worker Profile and in Onboard data collection tasks, an invalid value is refused with a message under the field until it matches the rule.
Integrations keep running — values written through the API, imports, automations and integrations are never blocked. An invalid value is saved as sent and marked invalid.
Applies going forward — a new or changed rule checks new and updated values. Existing values are checked the next time they are written.
Why it matters
The person who can fix a bad value sees the problem while typing it, instead of an integration failing days later, and one rule on the attribute applies everywhere the value is entered.
What to expect
Validation is optional and set per attribute; an attribute without a rule behaves as before. Error messages are shown in English.
Availability
Available to all customers.