To learn how to design a Blueprint, let’s consider a scenario. Zylker Inc is a software company sells cloud applications.
A Blueprint is designed by creating a sequential order of these stages in a process. In CRM lingo, the primary building blocks of a Blueprint are - States and Transitions.
In a Blueprint, a "State" is the particular condition that something is in at a specific time.
For example, a deal in CRM goes through different stages until Follow-up - Qualification, Negotiation and Discount approval. Each of these stages will be called a “State”.
States must be dragged and dropped in the Blueprint Editor to design the process flow.
A Transition is a link between two States in a process. It prescribes the conditions required for a record to move from one State to another. For example, the conditions and actions required for a record to move from Qualification to Negotiation are prescribed in the “Transition” block called "Negotiate".