Setup and Installation
Solution Components
Logic Composer is delivered as Dataverse managed solutions. To use Logic Composer, you need to import the following solutions into your environment:
Solution Dependencies
┌─────────────────────────────────────────────────────────────────────────┐
│ SOLUTION DEPENDENCIES │
├─────────────────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────────────────┐ │
│ │ Flowon Base │ │
│ │ (Required First) │ │
│ └──────────┬──────────┘ │
│ │ │
│ ┌────────────────┴────────────────┐ │
│ │ │ │
│ ▼ ▼ │
│ ┌─────────────────────┐ ┌─────────────────────┐ │
│ │ Logic Composer │ │ Logic Composer Tools │ │
│ │ (Core Runtime) │ │ (Design Interface) │ │
│ └─────────────────────┘ └─────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────────────┘
Solution Details
| Solution | Description | Dependency |
|---|---|---|
| Flowon Base | Core platform components shared across all Flowon products. Contains foundational entities, plugins, and infrastructure. | None (install first) |
| Logic Composer | The Logic runtime engine. Contains entities for Logic Blocks, Flows, Recipes, Events, Schedules, and all execution infrastructure. | Flowon Base |
| Logic Composer Tools | The design-time interface. Contains the visual designers, editors, and tools for creating and managing Logic artifacts. | Flowon Base, Logic Composer |
Installation Order
Solutions must be imported in the correct order due to dependencies:
- Flowon Base - Import first (no dependencies)
- Logic Composer - Import second (depends on Flowon Base)
- Logic Composer Tools - Import third (depends on Flowon Base and Logic Composer)
Security Configuration
Flowon Customizer Security Role
When you import the Logic Composer solutions, a security role called Flowon Customizer is automatically created. This role grants the permissions necessary to design and manage Logic Composer artifacts.
Role Permissions
The Flowon Customizer role provides:
| Permission Area | Access Level | Description |
|---|---|---|
| Projects | Full | Create, read, update, delete projects |
| Logic Blocks | Full | Create and manage Formulas, Decision Tables, Decision Trees, Validations, Validation Sets |
| Logic Flows | Full | Create and manage Logic Flows and Flow Steps |
| Business Processes | Full | Create and manage Business Process definitions |
| Recipes | Full | Create and manage entity event handlers |
| Configurations | Full | Create and manage global configuration variables |
| Localized Resources | Full | Create and manage multi-language strings |
| Schedules | Full | Create and manage scheduled executions |
| Service Connections | Full | Create and manage external API connections |
| Events | Full | Create and manage Event Definitions and Handlers |
| APIs | Full | Create and manage exposed API endpoints |
| Instances | Read | View execution history and instance data |
Assigning the Role
To enable users to work with Logic Composer:
- Navigate to Settings → Security → Users
- Select the user(s) who will design and manage logic
- Click Manage Roles
- Select Flowon Customizer
- Click OK
Role Considerations
| User Type | Recommended Role | Notes |
|---|---|---|
| Logic Designers | Flowon Customizer | Full access to create and modify all logic artifacts |
| Administrators | Flowon Customizer + System Administrator | Full access plus solution management |
| End Users | No Flowon role needed | Logic executes automatically; users interact with Dataverse normally |
| Read-Only Reviewers | Custom role with Read access | Create a custom role if you need users who can view but not modify logic |
Licensing
Logic Composer requires a valid license to operate. License details:
| Aspect | Description |
|---|---|
| License Type | Per-environment subscription |
| Activation | License key configured in Flowon Base settings |
| Scope | Covers all Logic Composer functionality in the licensed environment |
| Validation | License validated at runtime; expired licenses prevent execution |
License Configuration
After importing the solutions:
- Navigate to Flowon → Administration → License
- Enter your license key
- Click Activate
- Verify activation status shows as Active
License Features
Your license may include different feature sets depending on your subscription level:
| Feature | Description |
|---|---|
| Logic Blocks | Formulas, Decision Tables, Decision Trees, Validations |
| Logic Flows | Flow design and execution |
| Recipes | Entity event handling |
| Schedules | Time-based execution |
| Events | Publish-subscribe pattern |
| Service Connections | External API integration |
| APIs | Exposed endpoints (requires API Builder license) |
| Business Processes | Multi-stage processes (requires Process Orchestrator license) |
Post-Installation Checklist
After installing Logic Composer, complete the following steps:
| Step | Action | Verification |
|---|---|---|
| 1 | Import Flowon Base solution | Solution appears in Solutions list |
| 2 | Import Logic Composer solution | Solution appears in Solutions list |
| 3 | Import Logic Composer Tools solution | Solution appears in Solutions list |
| 4 | Configure license key | License status shows Active |
| 5 | Assign Flowon Customizer role | Users can access Flowon menu |
| 6 | Create first Project | Project record created successfully |
| 7 | Test with simple Logic Block | Formula evaluates correctly |
Environment Considerations
Development vs. Production
| Environment | Recommendation |
|---|---|
| Development | Full Logic Composer Tools for design work |
| Test/UAT | Full Logic Composer Tools for testing and validation |
| Production | Logic Composer (runtime) required; Logic Composer Tools optional |
Solution Layering
Flowon solutions are managed solutions. Your customizations (Projects, Logic Blocks, Flows, etc.) are stored as data records, not solution components. This means:
- Flowon solutions can be upgraded without affecting your logic artifacts
- Your logic artifacts are exported via FLoP files, not CRM solution export
- Multiple Flowon versions can coexist during upgrade testing