Core Concepts and Architecture
The architecture of Process Builder is based on a model-driven principle: everything — logic, layout, navigation, and user interaction — is described as metadata rather than code.
These definitions are stored in the P4 database and dynamically interpreted by the platform engine. This makes applications instantly deployable, version-controlled, and evolvable without recompilation or downtime.
At a high level, the Process Builder is composed of five interconnected layers, each responsible for a different aspect of application definition. Together, they form a complete no-code ecosystem.
1. Flow Builder – Process Logic Layer
The Flow Builder defines the logical behavior of the system — how data are loaded, processed, and stored.
It allows users to build process flows as visual graphs composed of nodes such as Start, Load Object, Condition, or End. Each node performs a specific operation, and the result of one becomes the input for the next.
Flows can represent anything from a simple data load to a multi-step transactional workflow. They execute in memory to ensure consistency and reliability before any data are written to the database.
2. Widgets – UI Logic Layer
Widgets describe what happens in the user interface — actions, reactions, and interactive behavior.
A widget can, for example, define that clicking a button opens a dialog or triggers a flow. It is the connective tissue between the visual layer and the logical layer, allowing data and processes to communicate seamlessly.
Widgets are reusable and parameterized, supporting visibility rules, triggers, and data bindings.
3. Layouts – Page Composition Layer
A Layout defines how visual and logical elements are arranged on a page.
It acts as a template that determines the structure of dashboards, forms, or detail pages. Layouts contain widgets, components, and references to flows, defining both appearance and behavior.
Because layouts are reusable, a single design can serve multiple application pages or modules.
4. Application Structure – Module Hierarchy Layer
The Application Structure describes how pages and modules are organized in the system.
It defines the navigation hierarchy — which modules exist, what pages they contain, and how users move between them. This structure provides the foundation for routing, permissions, and contextual navigation.
5. Components – UI Building Blocks
Components are the smallest reusable visual elements: input fields, buttons, tables, charts, lists, and so on.
They ensure consistent design and behavior across all applications built in Process Builder. Components are referenced inside layouts and widgets and are maintained in a central library.
Interconnection of Layers
Each layer is metadata-linked to the others:
A Widget may invoke a Flow.
A Layout may contain multiple Widgets.
An Application Structure references Layouts to build navigation.
This interconnected model allows the platform to interpret the entire application tree dynamically, maintaining logical integrity between data, UI, and user actions.
Execution Model
When a user interacts with the system — for example, by clicking a button — the platform resolves which widget, flow, and layout definitions are involved. It executes the process in memory, applies data bindings, and updates the interface instantly.
This runtime interpretation is what makes P4 a living application rather than a static one.