Process Hub · Business scenarios to work through
Business example: request a supplier purchase order
Build a header-and-lines document with tested totals and a sequential authorisation flow.
On this page
Before you start
- Use a training profile and synthetic data. NovaNest Living is a fictional home-goods business; names, records and amounts below are examples, not installed customer configuration.
- Ask your administrator to prepare the approved runtime connection and member roles. Use the linked build guide before this walkthrough; only authorised people should publish/deploy.
Example structure
On smaller screens, scroll the table sideways to see all columns.
| Setting | How to use it |
|---|---|
| Header | supplier_reference (Text/Lookup), request_date (Date), requested_by (User), total (Calculation). |
| Lines | product_code (Lookup/Choice), quantity (Number), unit_cost (Number/Currency), line_total (Calculation). |
| Review evidence | Compatible Text fields for any configured approver inputs; optional completion flag after final approval. |
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Create a standalone Header Line process named Purchase Request with Header + lines subtype. Add the header and repeated line fields below; do not choose Transaction batch for this example.
- Configure product selection from a prepared demo lookup or controlled choices. Set quantity and unit_cost as numeric inputs and line_total as ROUND([quantity] * [unit_cost], 2).
- Add header total as SUM([Lines.line_total]) using the actual entity/key names. Set supplier and required line inputs; decide which fields become read-only after submission.
- Save, publish and deploy. Grant Purchasing, requester and Finance the appropriate access. In Workflows → Approvals add Purchasing review followed by Finance authorisation, then validate/release that configuration.
- As the requester create PR-1001 for supplier SUP-DEMO-01. Enter 10 refill packs at 25 and 4 gift boxes at 60. Save/reopen and confirm line totals 250 and 240, header total 490.

The example has line totals of 250 and 240 and a document total of 490. Save and reopen to verify persistence before final submission. - Submit the request. As Purchasing, verify supplier/quantities and approve online. Confirm Finance receives the next stage; as Finance review the amount and approve.
- Inspect approval history and completion fields. Create a separate test request and Request changes with a reason; verify it returns to the submitter as draft work.
- Test one incomplete line and an unauthorised reviewer. Confirm validation/access blocks the operation and no external supplier order is assumed sent.
Known totals and business boundary
The sample total is 490 before any tax/freight calculation you deliberately add. Approval records authorisation; it does not send a purchase order, update accounting or pay a supplier without a separate supported configuration.
What you should see
The request keeps its lines and totals together and records the intended sequential review before the business acts on it.
If something goes wrong
The total is 0 or includes only one line
Review stable keys, numeric inputs and the repeated Lines context. Compare the two known line totals before investigating approval.
A closed batch blocks edits
This example requires Header + lines. Batch close is a different permanent-lock operation.