States and Transitions

In the previous chapter, we introduced the idea that a business process can be implemented as a finite state machine. In this chapter, we take a closer look at its two main building blocks: states and transitions.

States

A state represents a situation in which a business process is waiting. While the process is in a state, no work is being performed. The process simply remains there until something happens.

An important property of states is that their duration is unknown. We cannot predict when a state will begin or how long it will last.

Consider the process of ordering a pizza. After the order is placed, the process enters a state that could be called “Waiting for pizza to arrive”.

We do not know in advance when this waiting period starts or ends. The delivery time may vary depending on traffic, weather, or how the order was placed. Because of this uncertainty, a state cannot be defined by time.

Instead, states are defined by meaning. Each state is given a unique name that describes what the process is waiting for.

A state is a named waiting condition of a business process.

Transitions

Transitions represent short periods of activity that move a process from one state to another. They are the moments when work is actually performed.

Unlike states, transitions are well defined. They describe what actions must be performed and what rules determine the outcome.

A transition usually includes:

Transitions may take milliseconds or much longer, but they always represent execution rather than waiting.

Yes, it’s called a state machine — but the real action lives in transitions. States describe where a process is waiting; transitions describe what actually happens.

Configuring a Finite State Machine

When we say that a business process is a programmed finite state machine, we mean that its behavior is defined by a set of transitions.

Each transition specifies:

The state machine itself does not contain business logic. It simply executes transitions according to their definitions.

This separation makes business processes easier to understand, test, and change.

Table of Content Introduction into Business Process Previous: Finite State Machine Next: Business Logic