Outcome. Child custom object records created without a link to their parent get flagged immediately, instead of orphaned records piling up that nobody can trace back to where they belong.
Workflow map
Enrollment, branches and actions at a glance
data-quality-035
flowchart TD
A[Asset record created] --> B[Custom code: read Location associations]
B --> C{Location linked?}
C -->|no| D[Flag Missing parent Location, add to list, create task]
C -->|yes| E[Status: Linked]

When to use it, when not to
- UseUse it whenever a child custom object only makes sense in the context of its parent, an asset belongs to a location, a subscription belongs to an account, and the object can technically be created without that link.
- UseUse it when the child object is created through more than one path, manual entry, import, a form, or an integration, so a single UI guardrail cannot guarantee the association.
- SkipDo not use it if your custom object schema already enforces the association through a required default association at creation time in Settings > Objects. Check that first; a workflow-based check is a backstop, not a replacement.
- SkipDo not use it to automatically pick a default parent for an unlinked record. Picking the wrong parent silently is worse than a flagged gap a human resolves.
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.5 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.5 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, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
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.





