Pro Known Limitations
DBFlow Pro (dbflowlabs/filament-pro, 1.0 stable) is a commercial visual workflow builder. This page lists scope boundaries — not a complete issue tracker. Package release notes remain authoritative.
Release status
| Fact |
Implication |
| 1.0 stable line |
Install with composer require dbflowlabs/filament-pro:^1.0 |
First stable tag 1.0.0 |
Semver applies from 1.0 onward; read release notes before upgrading |
| Commercial license |
One production domain registration is handled through DBFlow HQ; license expiration does not disable installed deployments |
| Private Composer distribution |
Install via packages.dbflow.dev with Portal credentials |
What works today
- LogicFlow canvas rendering via
ProCanvasField
- Graph parsing (
WorkflowGraphJsonParser) and compilation (ProGraphBlueprintCompiler) with package test coverage
- Draft save —
ProCanvasDraftSaveAdapter dehydrates canvas state to Standard definition_json
- Standard
WorkflowResource integration through ProCanvasWorkflowDefinitionEditorResolver
- dbflow-demo sandbox at
/admin/pro-canvas-sandbox with refund / procurement fixtures
Current scope boundaries
These items are not part of the current DBFlow Pro 1.0 product surface:
| Area |
Status |
| Dedicated standalone builder route |
Deferred; editing flows through WorkflowResource is supported |
| Full visual condition builder |
Conditions still compile to transitions[].condition expressions — review in code |
| Template marketplace / gallery |
Not shipped |
| Billing / licensing inside the package |
Handled by DBFlow HQ, not the Pro Composer package |
| Symfony ExpressionLanguage condition evaluation in canvas |
Deferred |
Operational expectations
- Pro designs definitions; Core executes them
- Compiled graphs should pass the same validation as code-defined workflows
- Run
php artisan filament:assets after every Pro install or upgrade
- Replace default permission checkers before shared Filament environments
- Confirm
DBFlowFilamentProServiceProvider is loaded after install; register it manually in bootstrap/providers.php when Composer auto-discovery does not pick it up — see Installation → Pro service provider
- Call
DBFlowFilamentPanel::register($panel) inside panel(), not boot() — see Installation → Filament
- Set
workflow_resource_class explicitly in config/dbflow-filament.php when Pro (or a host subclass) should replace Standard
Troubleshooting
| Symptom |
Likely cause |
What to check |
| Pro canvas never appears |
Pro provider not booted |
DBFlowFilamentProServiceProvider in loaded providers; manual bootstrap/providers.php entry |
Still on Standard WorkflowResource |
workflow_resource_class not updated |
Set Pro or host subclass in published config/dbflow-filament.php |
RouteNotFoundException on workflow list/edit links |
Panel registered from boot() or page $resource mismatch |
Register in panel(); provide List/Create/Edit page subclasses — Filament UI |
vendor:publish for Pro config empty |
Publish tags unavailable in dist build |
Copy vendor/dbflowlabs/filament-pro/config/dbflow-filament-pro.php |
| Canvas loads but save/publish fails |
Draft missing or validation |
Workflow::hasDraft(); run dbflow:validate --strict on compiled output |
Related