Weave Code
Ui Process Bundle Laravel Package
cleverage/ui-process-bundle
CleverAge/UiProcessBundle adds a simple EasyAdmin-based UX to the CleverAge ProcessBundle for Symfony, giving you a ready-made interface to view and manage your process workflows.
UI for cleverage/process-bundle
Frequently asked questions about Ui Process Bundle
- Is cleverage/ui-process-bundle compatible with Laravel?
- It is primarily a Symfony bundle that provides an EasyAdmin UI on top of CleverAge ProcessBundle. Laravel integration is possible through Symfony components and Laravel's Symfony bridge, but it is not a native Laravel package. Confirm that your app already uses or can support cleverage/process-bundle and the required Symfony versions before adopting it.
- How do I install cleverage/ui-process-bundle in a Laravel app?
- Install it with Composer, for example composer require cleverage/ui-process-bundle:^2.3, and make sure cleverage/process-bundle is installed at a compatible version. Publish the configuration with php artisan vendor:publish for the bundle config tag, then run php artisan migrate if schema changes are included. Register the bundle service provider if your Laravel setup does not discover it automatically.
- Which PHP and Laravel versions work with cleverage/ui-process-bundle?
- The package requires PHP 8.1 or newer and is evaluated with Symfony 7.3, with PHP 8.2 or 8.3 recommended for stability. Laravel 10 and newer are the safest fit because they support Symfony 7.x more fully. Laravel 9.x may need a Symfony 6.x compatibility layer, so test your exact PHP and Laravel combination.
- Does cleverage/ui-process-bundle require cleverage/process-bundle?
- Yes, the UI bundle is part of the CleverAge ProcessBundle project and layers an EasyAdmin UX over process management. If cleverage/process-bundle is not already present, install and configure a compatible version such as v2.x. The UI layer alone is usually not enough for full process execution.
- How do I configure cleverage/ui-process-bundle after installation?
- Publish and update the bundle configuration, typically config/ui_process.php, to match your process and user-management setup. Ensure the Cleverage UiProcessBundle service provider is registered if Laravel does not auto-discover it. Use Laravel configuration and feature flags to control routes and bundle behavior in different environments.
- What database schema or migrations does cleverage/ui-process-bundle need?
- The bundle assumes database tables for process and user management, so check whether the package version ships migrations or requires documented schema setup. Run php artisan migrate after publishing if schema changes are provided. Test against MySQL, PostgreSQL, or SQLite before relying on it in production.
- How do I create a UI Process user with Artisan?
- Use the cleverage:ui-process:user-create Artisan command with the username and password arguments. The newer CLI arguments are additive, so existing command usage remains backward-compatible. Align stored credentials with Laravel's authentication approach, such as hashing passwords with Hash::make().
- Can I use existing Symfony Process or Workflow integrations with this bundle?
- Yes, the bundle is designed around CleverAge ProcessBundle and Symfony process-management concepts, so existing Symfony Process or Workflow usage can reduce boilerplate. Verify that symfony/process and related constraints satisfy the package requirements, such as Symfony 6.4 or newer in the integration path. Reuse your existing service wiring where possible and test the UI routes against real process data.
- How should I test cleverage/ui-process-bundle in a Laravel application?
- Use unit tests to mock Process and Workflow components, then add integration tests for Artisan commands and UI routes. Include end-to-end tests that validate a complete process flow against a test database. Run staging tests on your target PHP and Symfony versions before production rollout.
- What are Laravel-friendly alternatives if I do not want a Symfony bundle?
- If you need native Laravel workflow management, evaluate Laravel queues with Horizon, custom state machines, or Laravel-oriented workflow packages. CleverAge UI Process Bundle makes the most sense when you already use CleverAge ProcessBundle and want its EasyAdmin interface. Otherwise the Symfony and EasyAdmin layer may add more integration overhead than a Laravel-native solution.
Weaver
How can I help you explore Laravel packages today?