POCO DataSet as Transition Context Container

Introduction

Most enterprise applications move information between architectural layers using a mixture of DTOs, view models, service contracts, and persistence entities. Each layer often introduces its own representation of data, and the meaning of that data must be reconstructed repeatedly.

Business Process Unit Architecture (BPUA) approaches the problem differently. Instead of translating data between many incompatible structures, BPUA uses a single structured container to exchange information between components involved in transition execution.

In BPUA-based systems, POCO DataSet is used as the container that transports the data and metadata required to execute a business process transition.

Transition Context

When a trigger initiates a business process transition, the system prepares a set of information describing the situation in which the transition must execute. This information is called the Transition Context.

The Transition Context typically includes:

• Business data required for the transition
• Metadata describing the request
• Identifiers used for routing (such as BPUI)
• Additional information required by the transition handler

The Transition Context is delivered to the transition handler, which validates the context and performs the transition.

POCO DataSet as Context Container

In BPUA-based systems, the Transition Context is represented using a POCO DataSet instance.

POCO DataSet provides a convenient structured container capable of holding:

• Multiple related tables of data
• Schema and metadata information
• Row state tracking
• Original and current values
• Merge behavior for refresh and reload scenarios

Because POCO DataSet supports rich structured data, it serves as a practical container for exchanging Transition Context between BPUA components.

How Transition Context Flows Through the System

During transition execution, the Transition Context flows through several architectural components:

• A Trigger prepares the Transition Context.
• The Application Runtime forwards the context to the router.
• The Router reads BPUI information from the dataset and selects the appropriate handler.
• The Transition Handler validates the context and performs the transition.

The handler may update the dataset or produce additional data, which then becomes part of the resulting Transition Context.

Relationship to Business Process State

A business process state is a conceptual element of the process model defined by the finite state machine describing the process.

POCO DataSet does not represent the business process state itself. Instead, it contains the information required to execute transitions between states.

Relationship to Model Context Protocol (MCP)

In systems that integrate reasoning engines, information contained in the Transition Context may also be used to construct structured context provided to the AI layer using the Model Context Protocol (MCP).

In this scenario, the dataset remains the internal container used by BPUA components, while MCP provides a standardized way to deliver selected information to reasoning engines.

Summary

POCO DataSet is not a business process protocol and does not define business process semantics.

Instead, it serves as a structured container used by BPUA-based systems to transport Transition Context between architectural components.

Triggers prepare the context, routers deliver it to the appropriate handlers, and transition handlers interpret and validate the data contained in the dataset when executing business process transitions.

 

Table of Content Business Process Unit Architecture