The Workflow Library

Library / Data quality / data-quality-032

Custom object required-field enforcement on creation

Data qualityCustomData Hub EnterpriseIntermediate~25 min to buildFull spec

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.

Workflow map Enrollment, branches and actions at a glance data-quality-032
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]
action or delay branch public on every spec, paid or not

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.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.6 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.4 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

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.