Process Hub · Design your first process
Understanding Process Hub process types
Choose an appropriate starting point and recognise why screens differ.
On this page
Before you start
- Agree the business outcome, record structure, ownership and approval needs before building.
Available type families
On smaller screens, scroll the table sideways to see all columns.
| Type | Typical structure |
|---|---|
| Forms | One set of answers, or a survey with pages/questions. |
| Header Line | One header with repeated line items, or a permanently closable transaction batch. |
| Register | A maintained collection/list of structured records. |
| Route | Calculated planning, driver assignment and ordered stop execution. |
| Document Chain | Read-only/non-owning matching of business documents across ordered steps. |
| Allocation / Mapping | Saved current relationships between supported source and destination records. |
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Identify the data structure: one set of answers, a header with lines, a reusable register, a route, a linked document flow or an allocation/mapping workspace.
- Use the type-family reference in this guide. Follow the dedicated build guide and business example for the type you choose; a Solution starter is an editable starting point, not an approved complete workflow.

Choose the process type and placement deliberately. Configure the draft before publishing or deploying it. - Choose Standalone for a process opened independently. Use Embedded child when records must be created/opened under their owning parent record.
- Plan fields, labels, lifecycle actions, assignments and required evidence before publication. A process’s configured labels are the ones members should follow.
- Create a draft in Builder, preview its actual runtime and test with representative users/data before publishing and deploying.
What you should see
You have a process design that fits the business task and can be explained to the people using it.
If something goes wrong
You need every screen to look like a form
Registers, routes and other operational types intentionally use different runtime views.
The business flow spans processes
Plan workflow chains and dependency/access rules separately from the structural process type.