Glossary
Business process flow (BPF)
By Emil Björk · Microsoft business apps consultant, Gothenburg
The staged progress-bar guidance pattern in Dynamics 365 model-driven apps — guides users through multi-step processes.
A business process flow (BPF) is the staged top-of-form progress bar in Dynamics 365 model-driven apps that guides users through a multi-step process — qualifying a lead through stages from Qualify → Develop → Propose → Close, for example. A BPF defines an ordered list of stages, each with steps (fields the user must complete before moving on). Required steps block stage transitions; optional steps prompt without blocking. BPFs can span multiple tables (lead → opportunity → quote, following the record as it converts from one to the next), branch based on field values (a high-value deal routes through an extra approval stage a low-value one skips), and trigger automations on stage transitions through Power Automate.
In practice, a BPF's value is less about the fields it collects — those could live on the form anyway — and more about the sequence it enforces. A salesperson opening a record sees exactly where it sits in the process and exactly what's needed to advance it, without needing to remember the company's sales methodology or hunt through a form for the relevant fields. This makes BPFs a training and consistency tool as much as a data-entry one: a new hire follows the same staged flow a veteran does, and management gets a clean "what stage is everything at" pipeline view for free. The best practice that keeps this working is restraint — three to seven stages, three to six steps each, with branching only where the underlying business process genuinely diverges; a BPF with fifteen stages and forty steps stops guiding and starts obstructing.
Where confusion shows up: BPFs are sometimes mistaken for a workflow or approval engine, but they don't themselves do anything — they're a visual and structural guide over data the user still enters manually, with automation (if any) delegated to Power Automate flows triggered on the stage-change event. A record can also sit at any stage indefinitely; a BPF has no SLA-style timer or escalation of its own. For time-based enforcement, pair a BPF with an SLA or a Power Automate flow watching for stale stages, rather than expecting the BPF to police duration on its own.