Consumer validation
ConceptintermediateValidation contributed by each consumer for the time data it is about to receive, checked against that consumer's own preconditions.
What people get wrong
The confusions are the difficulty. Each one is a belief that sounds right and is not.
- That project and payroll validations run on save by default. Absence validations do; those two do not unless configured.
Recall it
Which delivered consumer validations run when a worker saves a time card, and which wait until submit?
The delivered absence validations always start. The delivered project and payroll validations do not, unless Validate on Time Card Actions is set to include save.
Memory hook: Absence runs on save. Project and payroll wait for submit.
Rests on OTL-ACTION-061.
Taught in
- Time Card Actions and What Validates WhenWhich buttons exist on a time card, which validations run on each, and the defaults that decide whether a worker hears about a problem before payroll does.
- Time Consumer SetsHow Time and Labor decides which downstream systems receive time, which validations they contribute, and why the set locks once a profile uses it.
Related
- Terminology glossary — what a term means, and what people get wrong when they use it