A button on a record that asks your system
The customer asks: A button on a record that rechecks stock in our ERP or assigns a pick route
- Verdict: Ready, with limits (1)
- Door: Desk action · area: Documents and print › Your own records, fields and buttons
- Recipe: A button on a Desk record (a Desk action)
- Sample: S16 — Assign pick route (pp_pck): a Desk action
- Checked: carried 2026-10-16 · not re-run
What you build
A Desk action: a button on the form, or for the ticked rows of a list, answered by your service.
Limits
- A user presses it: nothing runs on its own when the record is saved.
Tell the customer
Users press a button on the record and your system answers in Desk.
What next
- Tell the customer the 1 limit above, and write it into the proposal.
- Follow the recipe: A button on a Desk record (a Desk action).
- Copy the sample: S16 — Assign pick route (pp_pck): a Desk action, and change it.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
- Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.
Related needs
- The approver must give a reason when rejecting a purchase order, and it is kept on the document — Ready, with limits (4)
- Extra fields on a purchase order and its lines, a goods receipt, a stock transfer, an expense or the till close — Ready, with limits (1)
- Keep each customer's prescriptions in iVendNext — Ready
- Keep our own records, such as a warranty register, in iVendNext with their own screens and print formats — Ready, with limits (1)
Start a project shortlist with this need · Put it in your blueprint · Every need