Process Hub · Business scenarios to work through
Business example: maintain a warehouse equipment register
Give the team a reliable list of equipment, custodians and service dates.
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 field plan
On smaller screens, scroll the table sideways to see all columns.
| Setting | How to use it |
|---|---|
| asset_code / Text | EQ-0100; preserve identity as text. |
| description / Text | Packing scale |
| site / Choice or Lookup | Warehouse A |
| custodian / User | Authorised demo Warehouse member |
| next_service / Date | An agreed training date |
| condition / Choice | In service, Needs inspection, Out of service |
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 Register/List process named Warehouse Equipment. Add asset_code, description, site, custodian, next_service and condition using the field plan below.
- Make asset_code and description required. Use controlled site/condition values and a real single-select User field for custodian; choose the appropriate record-maintenance permissions.
- Configure a practical list view showing code, description, site, custodian, service date and condition. Add useful supported filters and a detail view for longer notes/evidence.
- Save, publish and deploy. Grant Warehouse members the intended view/edit rights and verify the process appears in their navigation.
- As an authorised member, add EQ-0100 “Packing scale” at Warehouse A and EQ-0101 “Label printer” at Warehouse A. Assign a demo custodian and future training service dates.

Find equipment by its stable asset code. Open the record to make a permitted change and inspect its history. - Reopen EQ-0100 and change condition to Needs inspection with a note/evidence if configured. Check record history, then filter the register to the relevant site/condition.
- Export the permitted list if required. Test a small import only after checking the deployed field mapping; verify leading zeroes and user values are preserved.
- As a read-only member, confirm viewing works while editing is denied. Test archive with an authorised user and document how the team finds archived records.
Extend it deliberately
A separate Equipment Inspection form can capture repeat inspections and evidence. Add a workflow/schedule only when its trigger, assignee and result are agreed. The register itself does not run external maintenance bookings.
What you should see
Warehouse staff can find equipment, identify its custodian and review service/condition information with controlled maintenance rights.
If something goes wrong
A service date did not create a task
A stored date is not automatically a recurring schedule. Configure a supported Schedule Plan/automation separately if service work must be created.
A custodian name is visible but cannot be assigned work
Use a real User field for identity. A typed display name in Text is not a profile-user assignment.