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 Idea of a Pipeline

The pipeline represents a stable execution path. Each stage in the pipeline corresponds to a specific type of logic:

• State logic
• Business logic
• Data processing logic
• Data access logic

The order of these stages does not change. What may change is whether a particular stage performs work for a given transition.

Optional Stages

Not every transition requires all logic types. For example, a transition may:

• Use business logic without accessing data
• Access data without performing complex data processing
• Simply move from one state to another

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.

Active Stages

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.

Why a Pipeline Matters

A fixed execution pipeline provides several important benefits:

• Each logic type remains independent and focused on its responsibility
• Transitions execute in a predictable order
• Logic layers can be added, removed, or replaced without breaking the flow
• The execution model remains easy to reason about and test

The pipeline does not add new behavior to the business process. It simply defines how existing logic types are orchestrated during transition execution.

Summary

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

 

---

Business Process Programming in .Net
© 2004–2026 Laskarzhevsky Software Inc.
Unless otherwise noted, the content of this website is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0).
Code examples are provided under the MIT License.
You are free to share and adapt the material provided that appropriate credit is given and any modifications are clearly indicated.
The information provided on this website is for educational purposes only.
The author and publisher make no warranties regarding the completeness or suitability of the information and are not responsible for any damages resulting from its use.