Your system's answer before a back-office document is submitted
The customer asks: A purchase order blocked by data our ERP holds; a goods receipt checked against the supplier's terms
- Verdict: Not yet
- Door: Request · area: Documents and print › Numbering and checks on save
- Recipe: A back-office check that blocks a document (check by workflow)
- Sample: none yet
- Request: P-DOCCHECK · ask for an extension point
- Checked: carried 2026-10-16 · not re-run
What you build
Not yet as its own extension point. Today: a workflow step only your service can take, after its check passes (the recipe), or a Desk action a user presses.
Limits
- Today, with a workflow: the user waits a few seconds, and your service must be up for back-office submits.
- Today, an outside app finds a problem only after the save.
Tell the customer
A back-office document can be held for your system's check today through a workflow step; a direct check is coming.
What next
- Ask for it: the extension-point request for P-DOCCHECK (members only; how requests work).
- Until then, today: with a workflow: the user waits a few seconds, and your service must be up for back-office submits. an outside app finds a problem only after the save.
- Today's way round it: A back-office check that blocks a document (check by workflow).
Related needs
- Check a limit (an item's maximum discount, say) against the ceiling only when someone sets or changes it, not on every edit of the record — Ready, with limits (3)
- A code must follow our pattern — Ready, with limits (1)
- Documents numbered our way — Ready
- A field filled in from other fields when the record is saved — Ready, with limits (2)
Start a project shortlist with this need · Put it in your blueprint · Every need