Installation
Process Orchestrator is deployed as a managed solution to your Microsoft Dataverse environment. It supports both cloud and on-premises deployments, giving you flexibility in how you run your business processes.
Process Orchestrator depends on Logic Composer. The Logic runtime must be installed before Process Orchestrator, as Process Orchestrator leverages Logic constructs for automation, branching decisions, expressions, and configuration values.
Step 1: Acquire a License
Before installing Process Orchestrator, 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
Process Orchestrator consists of multiple managed solutions that must be imported in the correct order. Because Process Orchestrator depends on Logic, you must install the complete Logic stack before installing Process Orchestrator.
Solution Architecture
| Solution | Description |
|---|---|
| Flowon Base | Foundation - prerequisite for all Flowon products |
| Logic Composer | Runtime engine for Logic Blocks, Flows, and expressions |
| Logic Composer Tools | Design interface for creating logic artifacts |
| Process Orchestrator | Core runtime for process execution |
| Process Orchestrator 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 |
Logic Composer (Required for Process Orchestrator)
Logic Composer must be installed before Process Orchestrator. Process Orchestrator relies on Logic for:
| Integration Point | How Process Orchestrator 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 |
Process Orchestrator (Runtime)
Process Orchestrator 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 Process Orchestrator runtime solution must be installed in every environment where processes will execute - development, test, and production.
Process Orchestrator Tools (Designer)
Process Orchestrator 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 | Logic Composer | Logic Composer Tools | Process Orchestrator | Process Orchestrator 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 | Logic Composer | Yes | Flowon Base |
| 2a | Logic Composer Tools | Design environments only | Flowon Base, Logic Composer |
| 3 | Process Orchestrator | Yes | Flowon Base, Logic Composer |
| 4 | Process Orchestrator Tools | Design environments only | Flowon Base, Logic Composer, Process Orchestrator |
Step 3: Configure Security
After importing the solutions, configure user access to Process Orchestrator.
Process Designer Security Role
Upon installation, Process Orchestrator 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
Process Orchestrator supports both cloud and on-premises Dataverse deployments:
| Deployment | Supported | Notes |
|---|---|---|
| Dataverse Online | ✅ Yes | Cloud deployment via Microsoft Dataverse |
| Dataverse 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
- Logic Composer solution imported
- Process Orchestrator solution imported
- Process Orchestrator Tools solution imported (if needed)
- Process Designer role assigned to appropriate users
- Verify access to Process Orchestrator in the application