The Workflow Library

Library / Sales ops / sales-ops-041

Notify a manager when an AE manually edits an auto-generated commission record

Sales opsCustomSales Hub EnterpriseAdvanced~50 min to buildFull spec

Outcome. Finance finds out the same day a commission record's amount was changed after it was already calculated and moved past the initial stage, instead of discovering it at payroll reconciliation.

Workflow map Enrollment, branches and actions at a glance sales-ops-041
flowchart TD
    A[Commission amount changes while status is Approved, Paid, or Disputed] --> B[Set Commission manual edit flagged]
    B --> C[Notify finance manager of the change]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it together with sales-ops-020 (commission calculation), once auto-generated commission records exist and are editable by AEs or managers.
  • UseUse it as an audit trail signal, not a hard block; this fiche notifies, it does not prevent, undo, or require approval for the edit.
  • SkipDo not use it if commission records are locked down with permissions so only finance can edit them; in that case the edit is already controlled at the permission level and this notification is redundant.
  • SkipDo not use it if legitimate corrections are expected to be common in your process (for example, if reps routinely fix data-entry mistakes); frequent notifications for expected behavior will get ignored.
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.2 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.2 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 sales ops 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.