Processes (Blueprint): govern an object’s state transitions
A Blueprint turns a select field (stage, status) into a state machine: you declare which transitions are allowed and, for each one, the conditions, required fields, automatic actions and whether approval is needed. It is opt-in per object and per field, with no code.
In Settings → Processes (Blueprint) you design an object’s process: pick a select field (for example Status or Stage) and declare the allowed transitions between that field’s values. When someone changes that field on a record, the Blueprint validates the transition before saving. It is an opt-in layer: until you create a Blueprint for an object nothing changes (Opportunity pipelines and gates stay the same).
Create a process
- Pick the Object and the State field (only select fields appear, and their values are the states).
- Set the Mode: Strict (only declared transitions are allowed) or Open (undeclared transitions are free; declared ones still validate).
- Add the From → To transitions. Leave "From" as "Any state" to apply from any origin.
- For each transition, set conditions, required fields, actions and whether it needs approval.
- Save. Mark the process as Active for it to take effect.
Conditions and required fields
Conditions use the same engine as Field rules: pick a field, an operator and a value, and choose whether all (AND) or any (OR) must be true. Required fields list the fields that must be filled for the transition to happen. If a condition fails or a required field is missing, the change is blocked with a clear message.
Post-transition actions
- Set field: writes a value into another field of the record in the same save.
- Create activity: opens a task linked to the record (with an optional due in days).
- Notify: sends an in-app notification to the record owner.
- Webhook: registers the intent of an external dispatch for the transition.
Approval
Check "Require approval" on a transition so it only completes once approved. The request uses the CRM’s Approvals engine: if a matching approval policy exists, the transition is blocked until decided; if no policy is configured, the transition proceeds and the intent is registered.