Process Hub · Design your first process
Plan a process before opening Builder
Turn a business task into records, stages, responsibilities and a testable first version.
On this page
Before you start
- Use a training profile with synthetic data. Have the process owner, one person doing the work and one reviewer agree the outcome.
Choose the right mechanism
On smaller screens, scroll the table sideways to see all columns.
| Setting | How to use it |
|---|---|
| Fields and views | Capture data and control its presentation. |
| Business lifecycle | Manage states, actions, field access and handoffs on one record. |
| Approvals | Review a submitted record through configured approval stages. |
| Workflow chains | Create or update dependent records across processes. |
| Notifications | Send supported event messages to resolved recipients. |
| Schedule Plans | Create recurring work using a recurrence or operating calendar. |
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Write the trigger and completion in one sentence: for example, “A customer reports a damaged item; the case ends when the agreed resolution is recorded.”
- Decide what one record represents. Keep one customer case in one Forms record; put an order with product rows in Header Line. Use the process-type guides when the work needs routes, document matching or allocation.
- List the information captured at the start and at each later stage. Mark required evidence and decide which values come from lookups or calculations. Use stable field keys that will still make sense next year.
- Draw the states of this record and who may act in each state. Separately list any downstream processes, submitted-record approvals, reminder events and recurring work.
- Agree profile roles, records people may open, who can build/release, and what should appear in navigation. Ask the administrator to prepare the approved runtime connection and dependent data.
- Build the smallest useful process, deploy it to the training profile, then test a happy path, a missing-value path, a reassignment and an unauthorised user. Record the expected outcome before inviting real users.

Choose the process type and placement deliberately. Configure the draft before publishing or deploying it.
Worked design: a damaged-product case
At the fictional NovaNest Living warehouse, customer care logs a damaged bottle. Care captures the customer reference and evidence; Quality reviews the issue; Care records a resolution. This can start as one Forms process with lifecycle stages. Add a separate corrective-action process only when the business needs independent follow-up.
What you should see
You have a one-page design and a clear choice of process type, with dependencies and acceptance checks ready for the build.
If something goes wrong
The diagram has every task in one form
Use lifecycle for the same record. Split into linked processes only when the next task needs its own record, fields, ownership or history.
The team wants reminders before defining due dates
Decide what work becomes due, which event should fire, and who owns it. Queue colouring alone does not schedule a reminder.