Integration Architecture
Logic Fabric products are designed to work together seamlessly, creating a unified platform for no-code development.
Architecture Overview
Integration Points
| From | To | Integration |
|---|---|---|
| Logic Process Orchestrator | Logic | Stages use Logic Flows for automation |
| Logic Process Orchestrator | Logic | Transitions use Logic Blocks for guards |
| API | Logic | Actions use Logic Blocks for validation |
| API | Logic Process Orchestrator | Process Actions trigger Logic Process Orchestrator operations |
| Logic | External | Service Connections call external APIs |
| All | Events | Custom events for cross-component communication |
Product Interactions
Logic ↔ Logic Process Orchestrator
Logic 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
Logic API 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"
Logic Process Orchestrator ↔ API
API exposes Logic Process Orchestrator operations:
POST /api/orders/{id}/actions/submit
└── Triggers Logic Process Orchestrator Transition: "Submit for Approval"
POST /api/orders/{id}/actions/approve
└── Triggers Logic Process Orchestrator Transition: "Approve"
GET /api/orders/{id}/process-status
└── Returns current stage, history, available actions
Event-Driven Integration
Logic Fabric'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, Logic Process Orchestrator triggers, and external integrations. This allows the platform to react to business activity without hard-wiring dependencies between products.
Solution Dependencies
Logic Fabric 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 Logic Process Orchestrator requires Logic to be present. Logic API depends only on Base and can be deployed independently.
Data Flow
Every request entering the platform passes through a consistent processing pipeline. Logic API acts as the entry point, delegating to Logic for business rules and Dataverse for persistence. Logic Process Orchestrator processes run asynchronously alongside this pipeline, reacting to events emitted at each stage.
Next Steps
- Deployment and Licensing - Installation and licensing