Each Transition has: a From State (where the record currently is), a To State (where the record will go), a Transition Name (the button label users see), and optional configuration for Field Mandates, Before Actions, and After Actions.
You can also restrict who can execute a specific transition. For example, only a manager can execute the “Approve Discount” transition, while any sales rep can execute the “Send Proposal” transition.
A state can have multiple transitions leading to different next states. For example, from “Proposal Sent” a rep might have three transitions: “Won”, “Lost”, and “Deferred”. The rep chooses the appropriate transition based on the outcome. This branching logic allows a single Blueprint to model complex real-world processes.
A Blueprint Transition is the mechanism by which a user moves a CRM record from one Blueprint State to another. It appears as a button on the record, and clicking it initiates the transition – potentially requiring field fills, running automated actions, and moving the record to the configured next state.
Yes. Each transition can be configured so that only specific users, roles, or profiles can execute it. For example, a ‘Final Approval’ transition might be restricted to users with the Manager role.
Aaxonix is a certified Zoho implementation partner based in Pune. Architecture-first, no surprises.