Deep dive: modeling real approval workflows with the Process Designer
Vulo Team · Product · July 8, 2026 · 8 min read
A purchase request is not just a record. It is a journey. Draft, submitted, under review, approved or rejected, ordered, received. At each step, different people act, different fields matter, and different rules apply. This is what the Process Designer models.
States and transitions on a canvas
Open the Process Designer on any table and convert it to a process table. Add states, draw transitions between them, and assign colors and icons so every listing communicates status at a glance. The canvas is the documentation. Anyone can read the process by looking at it.
State-specific fields and permissions
The real power is in the details. Fields can appear, become required, or lock per state: a rejection reason only exists in the rejected state; the approved amount locks after approval. Combined with policies, you control exactly who can move a record between states and what they must fill in to do it.
Bulk state changes handle high-volume operations: approve fifty requests in one action, with every transition validated and logged.