Installation
FlowOn BPM is deployed as a managed solution to your Microsoft Dynamics 365 CE environment. It supports both cloud and on-premises deployments, giving you flexibility in how you run your business processes.
FlowOn BPM depends on FlowOn Logic. The Logic runtime must be installed before BPM, as BPM leverages Logic constructs for automation, branching decisions, expressions, and configuration values.
Step 1: Acquire a License
Before installing FlowOn BPM, you must obtain a license from the Microsoft Marketplace.
License Portal: https://marketplace.microsoft.com/en-us/product/saas/flowon.flowon_public_initial
Contact the FlowOn team through the marketplace listing for licensing inquiries, pricing information, and trial options.
Step 2: Import Solutions
FlowOn BPM consists of multiple managed solutions that must be imported in the correct order. Because BPM depends on Logic, you must install the complete Logic stack before installing BPM.
Solution Architecture
| Solution | Description |
|---|---|
| FlowOn Base | Foundation - prerequisite for all FlowOn products |
| FlowOn Logic | Runtime engine for Logic Blocks, Flows, and expressions |
| FlowOn Logic Tools | Design interface for creating logic artifacts |
| FlowOn BPM | Core runtime for process execution |
| FlowOn BPM Tools | Visual designer for modeling processes |
FlowOn Base (Foundation)
FlowOn Base is the prerequisite solution that must be installed first. It provides foundational components used across all FlowOn products.
| Component | Description |
|---|---|
| FlowOn Project Entity | The container for organizing FlowOn artifacts |
| Related Artifacts | Shared entities, web resources, and configurations |
| License Management | License validation and activation |
FlowOn Logic (Required for BPM)
FlowOn Logic must be installed before FlowOn BPM. BPM relies on Logic for:
| Integration Point | How BPM Uses Logic |
|---|---|
| On Entering/Exiting | Call Logic Flows when entering or exiting stages |
| Transition Branching | Use Logic Blocks (Decision Tables, Decision Trees) to determine which path to follow |
| Expression Builder | Use FlowOn expressions in all configurable fields |
| Configuration Values | Reference Configuration variables for dynamic values |
| Localized Resources | Display multi-language text in process interfaces |
FlowOn BPM (Runtime)
FlowOn BPM is the core runtime solution containing everything needed to execute business processes.
| Component | Description |
|---|---|
| Plugins | Server-side logic for process execution |
| Entities | Process definitions, instances, stages, traces |
| Forms | Runtime forms for process interaction |
| Workflows | Background automation components |
The FlowOn BPM runtime solution must be installed in every environment where processes will execute—development, test, and production.
FlowOn BPM Tools (Designer)
FlowOn BPM Tools provides the visual designer interface for modeling and configuring business processes.
| Component | Description |
|---|---|
| Process Designer | Visual canvas for designing process flows |
| Stage Configuration | Tools for configuring stage behavior |
| Transition Builder | Interface for defining routing logic |
In production environments, you typically only need the runtime solutions. The Tools/Designer solutions are not required for execution and can be omitted to reduce the solution footprint.
| Environment | FlowOn Base | FlowOn Logic | FlowOn Logic Tools | FlowOn BPM | FlowOn BPM Tools |
|---|---|---|---|---|---|
| Development | ✅ Required | ✅ Required | ✅ Required | ✅ Required | ✅ Required |
| Test/UAT | ✅ Required | ✅ Required | ⚠️ Optional | ✅ Required | ⚠️ Optional |
| Production | ✅ Required | ✅ Required | ❌ Not Required | ✅ Required | ❌ Not Required |
Import Order
Import the solutions as managed solutions in this exact sequence:
| Step | Solution | Required | Depends On |
|---|---|---|---|
| 1 | FlowOn Base | Yes | None |
| 2 | FlowOn Logic | Yes | FlowOn Base |
| 2a | FlowOn Logic Tools | Design environments only | FlowOn Base, FlowOn Logic |
| 3 | FlowOn BPM | Yes | FlowOn Base, FlowOn Logic |
| 4 | FlowOn BPM Tools | Design environments only | FlowOn Base, FlowOn Logic, FlowOn BPM |
Step 3: Configure Security
After importing the solutions, configure user access to FlowOn BPM.
Process Designer Security Role
Upon installation, FlowOn BPM creates a security role called Process Designer. Users who need to create and configure business processes must be assigned this role.
| Role | Capabilities |
|---|---|
| Process Designer | Create, edit, publish, and activate business processes |
Assigning the Role
To assign the Process Designer role:
- Navigate to Settings → Security → Users
- Select the user who needs design access
- Click Manage Roles
- Select Process Designer
- Click OK to save
Only users who need to design and configure processes should be assigned the Process Designer role. Runtime users who only participate in processes (completing tasks, approvals, etc.) do not need this role.
Deployment Options
FlowOn BPM supports both cloud and on-premises Dynamics 365 CE deployments:
| Deployment | Supported | Notes |
|---|---|---|
| Dynamics 365 CE Online | ✅ Yes | Cloud deployment via Microsoft Dataverse |
| Dynamics 365 CE On-Premises | ✅ Yes | On-premises deployment for organizations with specific data residency or compliance requirements |
Post-Installation Checklist
After completing the installation:
- License acquired from Microsoft Marketplace
- FlowOn Base solution imported
- FlowOn Logic solution imported
- FlowOn BPM solution imported
- FlowOn BPM Tools solution imported (if needed)
- Process Designer role assigned to appropriate users
- Verify access to FlowOn BPM in the application