Process Hub · Build by process type
Build a Register or List process
Create a structured collection of records that users can browse, maintain and review.
On this page
Before you start
- Decide what one row represents and who maintains it. Prepare a small sample list and stable reference values. Have edit/deployment authority or an authorised publisher.
Example field plan
On smaller screens, scroll the table sideways to see all columns.
| Setting | How to use it |
|---|---|
| asset_code / Text | Required business reference, for example EQ-0100. |
| site / Lookup or Choice | Consistent location. |
| custodian / User | Actual responsible profile user. |
| next_service / Date | A date people can filter and review. |
| condition / Choice | Controlled labels such as In service or Needs inspection. |
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Open Builder → New process → Register. Choose the appropriate Register or List subtype, set its name and create the draft.
- Open Register setup and define identity, numbering and the intended record capabilities. Keep a reference such as asset code as Text when leading zeroes matter.

Choose the register template and configure the record fields and behaviour before publishing and deploying. - Add the record fields: for example asset code, description, site, responsible user, service date and condition. Configure required values and lookup/user sources.
- Configure the list/detail views with the columns and filters users need. Choose useful labels and avoid showing every long field in the first table.
- Where supported and required, configure lifecycle actions for controlled record stages; do not assume typing a status label creates approval or work assignment.
- Save, preview, validate, publish and deploy. Grant member access and create two representative records. Open, edit and review history using the intended role.

Find equipment by its stable asset code. Open the record to make a permitted change and inspect its history. - If using import/export, test a small file first with the deployed structure. Verify archive and restricted-user behaviour before importing a real register.
Try a complete business example
What you should see
The team has a usable register/list with consistent records, practical views and controlled maintenance access.
If something goes wrong
A code lost its leading zeroes
Use a Text reference field and review import data types. Numeric fields treat codes as quantities.
A status change was expected to create an approval
A displayed status value is not a configured approval or lifecycle handoff. Add the appropriate workflow feature explicitly.
An import works differently from manual entry
Check the import mapping, field keys/types, required values and deployed version with a small sample.