Integration Architecture
Flowon products are designed to work together seamlessly, creating a unified platform for no-code development.
Architecture Overview
Integration Points
| From | To | Integration |
|---|---|---|
| Process Orchestrator | Logic | Stages use Logic Flows for automation |
| Process Orchestrator | Logic | Transitions use Logic Blocks for guards |
| API | Logic | Actions use Logic Blocks for validation |
| API | Process Orchestrator | Process Actions trigger Process Orchestrator operations |
| Logic | External | Service Connections call external APIs |
| All | Events | Custom events for cross-component communication |
Product Interactions
Logic ↔ Process Orchestrator
Process Orchestrator leverages Logic Composer extensively:
Business Process Stage
├── On Entering
│ └── Run Logic Flow: "InitializeStage"
├── Assignment
│ └── Run Decision Table: "DetermineAssignee"
├── Validation
│ └── Run Validation Set: "StageValidations"
├── On Exiting
│ └── Run Logic Flow: "FinalizeStage"
└── Transitions
└── Guard: Run Logic Block: "CanTransition"
Logic ↔ API
API Builder uses Logic for business rules:
API Action: CreateOrder
├── Pre-Validation
│ └── Run Validation Set: "OrderValidations"
├── Pre-Processing
│ └── Run Logic Flow: "PrepareOrder"
├── Execute (CRUD operation)
└── Post-Processing
└── Run Logic Flow: "ProcessOrderCreated"
Process Orchestrator ↔ API
API exposes Process Orchestrator operations:
POST /api/orders/{id}/actions/submit
└── Triggers Process Orchestrator Transition: "Submit for Approval"
POST /api/orders/{id}/actions/approve
└── Triggers Process Orchestrator Transition: "Approve"
GET /api/orders/{id}/process-status
└── Returns current stage, history, available actions
Event-Driven Integration
Flowon's event system enables loose coupling between products. Instead of direct calls, components emit named events that any number of handlers can subscribe to - including Logic Flows, Process Orchestrator triggers, and external integrations. This allows the platform to react to business activity without hard-wiring dependencies between products.
Solution Dependencies
Flowon products are packaged as separate Dataverse solutions and must be installed in dependency order. Flowon Base is the shared foundation required by all products. Logic Composer extends Base with the declarative engine, and Process Orchestrator requires Logic to be present. API Builder depends only on Base and can be deployed independently.
Data Flow
Every request entering the platform passes through a consistent processing pipeline. API Builder acts as the entry point, delegating to Logic for business rules and Dataverse for persistence. Process Orchestrator processes run asynchronously alongside this pipeline, reacting to events emitted at each stage.
Next Steps
- Deployment and Licensing - Installation and licensing