Transition Execution Pipeline
In the previous chapters, we examined how business processes are modeled and how different types of logic participate in executing a transition. In this chapter, we focus on the execution structure itself.
A transition is not executed by a single component. Instead, it flows through a fixed pipeline of logical stages.
A transition execution pipeline defines the order in which logic layers are invoked when a business process transition is executed.
The pipeline represents a stable execution path. Each stage in the pipeline corresponds to a specific type of logic:
The order of these stages does not change. What may change is whether a particular stage performs work for a given transition.
Not every transition requires all logic types. For example, a transition may:
In such cases, the corresponding pipeline stages remain present but perform no work. Control simply passes through them.
This design keeps execution predictable and consistent, regardless of which logic types are involved.
When a transition requires a particular type of logic, the corresponding stage becomes active and performs its responsibility.
After a stage completes its work, control is passed to the next stage in the pipeline.
A fixed execution pipeline provides several important benefits:
The pipeline does not add new behavior to the business process. It simply defines how existing logic types are orchestrated during transition execution.
A transition execution pipeline is a structural mechanism. It ensures that all transitions follow the same execution path, even when some logic stages perform no work.
By separating execution structure from business behavior, the pipeline keeps business process implementations clean, consistent, and extensible.
Table of Content Introduction into Business Process Previous: Business Process Activities Next: From Business Processes to Software Product