Outcome. Test and sandbox deals get tagged and pulled into a dedicated list, so every other hygiene workflow and dashboard in this category can exclude them cleanly instead of every fiche re-inventing its own exclusion logic.
Workflow map
Enrollment, branches and actions at a glance
deal-hygiene-038
flowchart TD
A[Deal marked Is Test Deal true, or in sandbox pipeline] --> B[Add to Excluded from hygiene reporting list]
B --> C{Deal later marked not test and not in sandbox pipeline?}
C -->|yes| D[Remove from list, exit]
C -->|no| E[Stay on list, exit]
When to use it, when not to
- UseUse it before activating any other deal-hygiene workflow in a portal that has training pipelines, QA deals, or demo data mixed in with real pipeline.
- UseUse it as the shared foundation other fiches in this category reference (deal-hygiene-001, deal-hygiene-014, deal-hygiene-015, deal-hygiene-025, and others point back to this exclusion pattern) (check in your portal: several earlier fiches in this pack reference "deal-hygiene-037" for this sandbox-exclusion pattern rather than deal-hygiene-038, this is a numbering inconsistency in the pack, deal-hygiene-037 is the multi-threading fiche, this fiche, deal-hygiene-038, is the actual sandbox-exclusion build, cross-check the reference before relying on it).
- SkipDo not use it if test deals already live in a completely separate pipeline that every report and workflow already filters out by pipeline ID, in that case this fiche adds nothing.
- SkipDo not use it as a substitute for actually deleting genuinely obsolete test records, a flag keeps them out of reports, it does not clean up the CRM.
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.3 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.5 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 deal hygiene 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.
