Process Hub · Design your first process
How to create and configure a process draft
Create a draft and design its data and runtime screens.
On this page
Before you start
- Process Hub must be enabled. You need Edit solutions access; publishing/deployment requires additional authority. Plan a simple non-production example first.
Follow the guide for your process type
The six process families have different setup and runtime controls. Choose the matching guide before adding advanced features.
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Select the intended profile → Settings → Process Hub → Builder and select New process.
- Choose a blank/custom process or an appropriate Solution starter. Set Placement, Name, Process type and any subtype. For Embedded child, choose the owning parent process.

Choose the process type and placement deliberately. Configure the draft before publishing or deploying it. - Create the draft, then open it in Builder. Configure Process setup, numbering and the type-specific header/lines/pages/entities needed by the business task.
- Add fields with clear labels and suitable types. Set required/read-only/default rules deliberately and give users helpful instructions. Configure lookup/calculation sources only after their data is ready.

Use the outline to select a section, the canvas to arrange questions, and Question settings to configure the selected field. - Configure the record views and runtime screens members will use. Check multi-page flow, hidden/conditional fields, validation messages and attachments in Preview.
- Save the draft before leaving. Use Validate & publish to inspect publish checks when the design is ready; publication and deployment are separate follow-on tasks.
What you should see
A saved process draft is ready for review and validation. It does not replace the deployed process until the required publication/deployment steps succeed.
If something goes wrong
A draft cannot be published
Read the field/entity-specific publish checks and fix the identified configuration. Incomplete drafts can be saved for later.
You changed a field used by automation/integration
Review dependency and compatibility impacts before deployment. Do not remove/rename production dependencies casually.