Lab orders kept as records, with a workflow
The customer asks: Optical lab orders tracked in iVendNext and sent to the lab
- Verdict: Ready, with limits (1)
- Door: Manifest · area: Documents and print › Your own records, fields and buttons
- Recipe: Shipping your own data in a manifest
- Sample: none yet
- Checked: carried 2026-10-15 · not re-run
What you build
Lab orders as your manifest's own record type with a workflow; your outside app sends them to the lab.
Limits
- Who may edit a record in a workflow state is checked in the browser only: follow the four safeguards in chapter 13a.
Tell the customer
Each lab order is tracked through its steps and sent to the lab.
What next
- Tell the customer the 1 limit above, and write it into the proposal.
- Follow the recipe: Shipping your own data in a manifest.
- 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.
Install it on your sandbox the way the shop's administrator will; the checker refuses a manifest that declares code.
Related needs
- A prescription number is required before a prescription item is paid for — Ready, with limits (1)
- 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