Process Hub · Business scenarios to work through
Business example: allocate orders to delivery vehicles
Plan a dispatch load, save assignments and handle a reasoned vehicle change.
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.
- Deploy a standalone demo Order process and Vehicle Register with unique stable order/vehicle keys. Prepare two orders and two vehicles.
Sample records
On smaller screens, scroll the table sideways to see all columns.
| Setting | How to use it |
|---|---|
| SO-1001 | Demo order A → VAN-01 |
| SO-1002 | Demo order B → VAN-01, later VAN-02 |
| VAN-01 / VAN-02 | Two reusable Vehicle Register records with unique keys. |
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Create an Allocation / Mapping process named Dispatch Allocation. Choose Allocation cards, Orders as source and Vehicle Register as destination.
- Set order_number and vehicle_code as identity keys and readable labels. Choose useful columns such as customer reference and requested delivery date.
- Configure many-to-one so several orders may share one vehicle while each order has one current destination. Enable reassignment/release only with the intended permissions/reasons.

Choose the workspace layout and relationship rule to match the business scenario before configuring sources and destinations. - Save, publish and deploy. Grant the planner access to the allocation process and both underlying sources. Prepare SO-1001, SO-1002, VAN-01 and VAN-02.
- As planner, allocate both orders to VAN-01 and choose Save allocations. Reopen the workspace and confirm both saved relationships.
- Move SO-1002 to VAN-02 with the training reason “Vehicle capacity changed”, save and verify SO-1001 remains on VAN-01. Test release only if the configured rules allow it.
- Optionally follow the advanced load guide to print a saved picking list or finish a load into a separate deployed Header + lines document. Review that document before using its release flow.
- Test an ineligible order and a user without source access. Confirm the denied operation does not leave an assumed partial assignment.
Expected change
After reassignment, VAN-01 has SO-1001 and VAN-02 has SO-1002. Inspect actual saved relationships and any configured lifecycle event evidence. This example does not reserve physical vehicle capacity or book an external carrier automatically.
What you should see
The planner sees persisted current vehicle assignments and can trace permitted changes without duplicating orders.
If something goes wrong
The same order cannot be kept on both vehicles
One source has one current destination. Reassignment changes that current relationship.
The printout omits a drag/drop move
Save allocations first. Printing uses persisted relationships.
The vehicle label matches but it is treated as a different destination
Check the stable key, case and spaces. Display labels are not identity keys.