Weave Code
Flowable Bundle Laravel Package
dmstr/flowable-bundle
Symfony bundle that exposes a remote Flowable BPMN engine as Doctrine-less API Platform pass-through resources, plus a per-request HTTP client and flowable:* CLI commands. Connection details resolve per request from an ApiConfiguration, so no database tables are needed.
Flowable BPMN engine pass-through resources, HTTP client and CLI for API Platform / Symfony.
Frequently asked questions about Flowable Bundle
- Is dmstr/flowable-bundle a Laravel package?
- No. It is a Symfony 7 bundle for API Platform 4 that exposes a remote Flowable BPMN engine as Doctrine-less pass-through resources. It has no Laravel service provider, facade, config/flowable.php, or Illuminate dependency, so it will not boot in a Laravel application. Any assessment that treats it as a Laravel dependency is measuring the wrong artifact.
- Can I use dmstr/flowable-bundle with Laravel?
- Not as a working Laravel integration. Dropped into a Laravel application it does not boot, and its symfony/* and api-platform/* constraints plus PHP >= 8.4 can collide with a typical Laravel lockfile. At best it survives as a Composer-adjacent library, not a Laravel package. Use a Symfony 7 and API Platform 4 application, or build a separate Laravel HTTP client integration.
- What does dmstr/flowable-bundle actually do?
- It exposes a remote Flowable REST engine as Doctrine-less API Platform pass-through resources under /api/flowable/*. It also provides a per-request HTTP client and matching flowable:* CLI commands. The application owns no workflow tables because Flowable remains the system of record and resources read or write the remote engine at request time.
- What are the requirements and installation steps for dmstr/flowable-bundle?
- It requires PHP >= 8.4, Symfony 7, API Platform 4, and a reachable Flowable REST engine. Install with composer require dmstr/flowable-bundle. If no Symfony Flex recipe registers it, add Dmstr\Flowable\FlowableBundle::class => ['all' => true] to config/bundles.php. The bundle is self-wiring and ships its own service definitions, so it needs no entry in services.yaml.
- How do I configure the Flowable connection and authentication?
- Create an ApiConfiguration of type flowable through dmstr/api-configuration-bundle. Its configJson is validated against schema.json and must include base_url plus auth_type. Use basic with username and password, or bearer with token. Connection details resolve per request rather than as boot-time singletons, which is suitable for multi-tenant use.
- Which Flowable API resources and endpoints does dmstr/flowable-bundle expose?
- All resources are served under /api/flowable/*. They include FlowDeployment for deployments, FlowProcessDefinition for process definitions with start and input_schema operations, FlowProcessInstance for process instances, and FlowTask for tasks including complete. Operations map to remote Flowable REST calls made at request time rather than local database queries.
- What is the external worker model in dmstr/flowable-bundle?
- Using flowable:type="external-worker" inverts the integration so the engine enqueues a job on a topic and waits while your worker authenticates outbound. This avoids an inbound route from the engine into your network and avoids embedding credentials in .bar artifacts. A throwing handler becomes fail so Flowable owns retry, backoff, and dead-lettering, while a topic with no registered handler is unacquired rather than failed.
- Is dmstr/flowable-bundle production ready or stable?
- It is pre-1.0 beta, currently 0.9.0-beta2, and does not promise API stability. Maturity signals are weak: 0 stars, 0 dependents, one vendor, and a small bus factor. Minor bumps may break resource shapes, form-schema conventions, or worker command signatures. Pin the version and be prepared to fork or vendor it if you depend on it.
- What are alternatives to dmstr/flowable-bundle for a Laravel app?
- There is no Laravel-native version of this bundle described in the provided context. Practical alternatives are a dedicated Symfony 7 and API Platform 4 service using this bundle, a custom Laravel HTTP client around Flowable REST, or a Laravel workflow or BPMN package if one fits your requirements. None of those alternatives are evaluated in the provided material, so compare them against your own integration, auth, and maintenance needs.
- How should I test or evaluate dmstr/flowable-bundle before adopting it?
- There is no package-specific testing guidance in the provided documentation, so spike it in a Symfony 7 plus API Platform 4 application against a test Flowable REST engine. Mock or sandbox the Flowable API and validate ApiConfiguration against schema.json. Exercise basic and bearer auth, the CLI external worker, and the failure and unacquired-topic policies before relying on it. Also verify the release tag against the code you actually intend to pin.
Weaver
How can I help you explore Laravel packages today?