Process Hub · Design your first process
Test and release a complete Process Hub solution
Check structure, access, automation and everyday use before handing a process to a new team.
On this page
Before you start
- Have a training profile, representative users and a written expected result. Prepare the approved connection and deployed lookup/source dependencies.
A useful acceptance record
On smaller screens, scroll the table sideways to see all columns.
| Setting | How to use it |
|---|---|
| Who tested | Builder, ordinary member, assignee, approver and restricted user. |
| What version | Deployed structural version plus published automation/chain/schedule versions. |
| What passed | Known data, expected calculations, stage/work transitions and actual channel delivery. |
| What failed safely | Missing required evidence, denied access, stale record and unavailable dependency. |
| Who maintains it | Business owner, source-list owner and operational support contact inside the organisation. |
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Review the design against the process-type guide. Save and validate the structural draft, resolve errors, publish an immutable process version and deploy it to the intended profile.
- Grant process/record access and configure navigation for real member roles. Confirm a member can find the process, open it and perform only the permitted actions.
- Test record capture, draft reopen, validation, attachments, calculations and each relevant process-type operation. Use known sample values and compare expected totals/evidence.

Review every publication check and fix validation errors before publishing. Deployment is a separate step. - Test lifecycle entry, each transition, claims/handoffs, terminal behaviour and stage field access. Include missing evidence and a user without ownership.
- Save, validate and release the corresponding approval/rule/notification/chain changes. Publish schedules/calendars through their own controls; deploying structure alone does not activate every automation.
- Run the complete business example as the actual users. Inspect Automation activity, Schedule activity and Notification delivery, and check the recipient can open resulting work.

Use activity to verify which released automation ran and what it did. Check resulting records and assignments as well. - For mobile users, verify supported online/offline paths and synchronisation separately. Record the deployed process version, active automation release, roles, test results and any environment dependencies.
- Agree the go-live owner and the guide links to give new users. For later changes, assess existing records and dependencies before deployment; preserve stable keys and test compatibility.
What you should see
The process is usable by its intended audience and its structure, automation and delivery behaviour have separately verified results.
If something goes wrong
Builder Preview works but the member flow fails
Preview does not prove deployed connections, record access, workers or providers. Reproduce with the member role against the deployed version.
A structure update breaks existing work
Inspect deployed dependencies and live record states before changing/removing keys. Republishing does not migrate every existing lifecycle record or repair all automation references.