The Business Rules chapter compared a business rule to a car's dashboard warning light — an instant reaction to one condition. A Business Process Flow (BPF) is the opposite kind of tool: a guided, multi-step path that walks a user through an entire process from start to finish, one stage at a time.

Quick facts
  • A BPF is a numbered, stage-by-stage checklist shown across the top of a form
  • Built from stages (checkpoints) and steps (usually required fields)
  • One BPF can span several related tables, not just one
  • BPFs can branch to a different next stage based on a condition
  • Which BPF a user sees is controlled by security roles, not the flow itself

The checklist on a driving test

Think of the numbered checklist an examiner uses during a driving test: check mirrors, signal, check blind spot, merge — each step happens in order before the next, and the examiner sees exactly which step the candidate is on. A BPF puts that same checklist across the top of a form, showing a user which stage of a larger process they're in and what comes next.

Stages and steps

A BPF is built from stages — big checkpoints like "Qualify" or "Develop" — and each stage contains steps, usually specific fields the user fills in before that stage counts as complete. A required step blocks the flow from advancing until it's filled in.

This is the same Lead-to-Opportunity-to-Quote-to-Order progression covered in the Core Modules course's Sales Process chapter — a BPF is very often the visual stepper that guides a rep through those stages on screen.

Example A "Qualify" stage on an Opportunity BPF might require Estimated Revenue and Close Date before letting the rep move to "Develop" — keeping pipeline data consistent without a separate business rule for each field.

One flow, multiple tables

Unlike a form, which belongs to one table, a single BPF can span several related tables. A Lead-to-Opportunity flow can carry the same stepper across the Lead record and continue onto the Opportunity created when that Lead is qualified. That's a genuinely different capability from anything else in this course: process guidance that follows the work across record boundaries.

Branching, briefly

BPFs can also branch — showing a different next stage depending on a condition, similar in spirit to a business rule's if-this-then-that logic, but applied to which stage comes next. Worth knowing it exists; not something a beginner needs to design on day one.

Who gets to use which flow

An environment can have several BPFs active on the same table. Which one a user sees — or is allowed to use — is controlled through security roles, the same mechanism covered in the Security & Access course. Building the flow is a customization concern; controlling who can use it is a security one.

Key takeaway: A Business Process Flow is a guided, stage-by-stage checklist that walks a user through a multi-step process — potentially across several related tables — the same way a driving examiner's checklist guides a candidate through a test in order. It's a different tool from a Business Rule: rules react instantly to one condition, BPFs guide an entire process from start to finish.