Outcome. New custom object records missing a required field get flagged and routed to a task immediately, instead of an incomplete record sitting unnoticed until someone downstream tries to use it.
flowchart TD
A[Vendor record created or edited] --> B{Vendor name or Payment terms missing?}
B -->|yes| C[Status: Incomplete, add to list, create task]
B -->|no| D[Status: Complete]

When to use it, when not to
- UseUse it on any custom object where a small set of fields must be filled in for the record to be usable, an approval, a report, an integration export.
- UseUse it when the custom object is created through more than one path (manual entry, import, an integration) so a single form cannot guarantee the fields are filled in.
- SkipDo not use it as a substitute for making the property required at the form or record-creation level if your object supports that. Workflow-based enforcement is a safety net for paths that bypass the form, not the first line of defense.
- SkipDo not use it if the object has no meaningful required-field concept to flag. A purely descriptive object with no downstream dependency on completeness does not need this.
or the data quality pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





