Preview Limitations

Early Access / Preview: dbflowlabs/filament-pro 0.1.0-alpha.20 is for evaluation and developer-assisted authoring — not turnkey production workflow administration.

This page lists known maturity limits. It is not a complete issue tracker; package release notes remain authoritative.

Release status

Fact	Implication
Package version `0.1.0-alpha.20`	Semver and APIs may break between alpha tags
Early Access / Preview	No stability or long-term support commitment yet
Pro license gating	Production canvas use may require entitlement validation through DBFlow HQ

What works today (alpha)

LogicFlow canvas rendering via ProCanvasField
Graph parsing (WorkflowGraphJsonParser) and compilation (ProGraphBlueprintCompiler) with package test coverage
Standard WorkflowResource integration through ProCanvasWorkflowDefinitionEditorResolver
dbflow-demo sandbox at /admin/pro-canvas-sandbox with refund / procurement fixtures

What is not ready

Treat the following as roadmap or incomplete — not production promises:

Area	Status
Dedicated standalone builder route	May be deferred; editing often flows through `WorkflowResource`
Full visual condition builder	Conditions still compile to `transitions[].condition` expressions — review in code
Template marketplace / gallery	Not shipped
Non-technical business-user editing	Not supported — developers must review compiled output
One-click production publishing	May require Standard publish steps + validation
Deadlines, escalation, delegation UX	Roadmap items — not Core/Pro alpha scope today

Developer responsibilities

Pro output is only as safe as your review process:

Validate every compiled definition with WorkflowDefinitionValidator::validateOrFail().
Test branches and reject paths in PHPUnit — see Testing Workflows.
Review condition expressions — routing authority is transitions[].condition; see Conditions.
Restrict editor access through PermissionChecker and host policies — see Permissions.
Version definitions in Git when possible; treat canvas saves as drafts until reviewed.

Non-technical stakeholders may view graphs for alignment, but published definitions should only change after developer review and tests.

Relationship to Core and Standard

Mistake	Reality
"Pro runs workflows"	Core runs workflows; Pro edits definitions
"Canvas replaces tests"	Tests remain mandatory during alpha
"Publishing from canvas skips validation"	Validation and publish rules still apply
"Pro changes approve semantics"	`DBFlow::approve()` / `DBFlow::reject()` are unchanged

Recommended adoption path

Ship workflows with Core + Standard and code-defined JSON (or providers/seeders).
Enable Pro on local or staging panels first.
Use dbflow-demo sandbox fixtures to compare canvas vs known-good definitions.
Add CI validation for any graph compiled in admin.
Roll out Pro editing to production only after your team owns the review pipeline.

Licensing note

Pro licensing, domain seats, and checkout timing are documented in Pricing. This page does not describe sales terms.

What's next

Pro Visual Builder → — scope and architecture
Standard Integration → — resolver and compiler wiring
Installation → — Composer and asset setup