- How do I install orlyapps/nova-workflow in a Laravel Nova application?
- Install it with Composer, run the package migrations, and publish any config or assets the README lists, then wire the workflow traits and Nova fields/actions into the resource you want to manage. Because there has been no tagged release since April 2022, do the install on a throwaway branch against your exact Nova version first. Confirm migrations run cleanly and the workflow UI loads before connecting it to a real model.
- Which Laravel, Nova, and PHP versions does nova-workflow support?
- The package does not publish a clear compatibility matrix, and the last release was April 2022, so Nova 4 support is likely while Nova 5 and Laravel 11 support are unproven. Because it targets Laravel Nova, its PHP and Laravel requirements will track whatever Nova required at that time, roughly PHP 8.0 or 8.1. Build your own version matrix by testing a fresh install and an upgrade on a non-production branch before committing.
- Is nova-workflow a real state machine or just a Nova UI for status fields?
- It provides workflow definitions, states, transitions, transition buttons, guards, and activity history, but the behavior is tightly coupled to Nova UI conventions. That makes it a good fit for small back-office admin processes, not high-volume or complex orchestration. Treat it as an admin workflow layer and enforce transition rules in your own domain service so other code paths cannot bypass them.
- How do I define states and transitions for a Nova resource with nova-workflow?
- You typically define states and transitions in configuration or model-level definitions, then add the package traits plus the Nova field and actions to your resource to show current status and transition buttons. Exact syntax depends on the installed version and its README, so validate it on one low-risk model first. Keep workflow definitions in version control next to your migrations so changes are reviewable.
- Does nova-workflow support guards, transition validation, and atomic updates?
- Guards and transition buttons are part of the package, but it does not document clear concurrency semantics or row-level locking for transitions. Two simultaneous transitions could therefore leave a record in an inconsistent state unless you add your own protection. Wrap transitions in a service method that re-checks the current state inside a database transaction with an explicit lock.
- Is nova-workflow still maintained, and is it safe to use in production?
- Adoption is low, around 22 GitHub stars, and there has been no release since April 2022, so treat the package as likely stale. It can work for a small internal admin tool if you assign a named owner and budget for forking and patching it. It is a risky choice for audited, customer-facing, or high-volume processes where upgrades and fixes must be timely.
- Can nova-workflow handle authorization, multi-tenancy, and audit logs?
- Nova resource policies and authorization apply to the UI, but multi-tenancy and API-level authorization are not documented, so you must verify them yourself. The built-in activity history may not satisfy compliance-grade audit requirements. Add domain-level authorization checks and, if you need durable audit trails, write your own transition event table alongside the package.
- What are the best alternatives if nova-workflow is abandoned or breaks on a Nova upgrade?
- A common replacement is a maintained PHP state-machine library such as symfony/workflow combined with a custom Nova resource, field, and actions for the UI. That gives you explicit guards, atomic transitions, and a supported upgrade path. If you keep nova-workflow, fork it and pin the version so a Nova major release cannot silently break your admin workflows.
- How should I test workflows and upgrade paths when using nova-workflow?
- Test transitions in feature tests at the domain level instead of clicking buttons in Nova, and add a time-boxed compatibility spike against your exact Nova, Laravel, and PHP versions. Verify migrations, rollbacks, and one full transition path end to end. Test upgrade scenarios as well as fresh installs, since Nova major versions are the most likely breakage point.
- Can nova-workflow transitions be triggered from an API instead of the Nova UI?
- The package is designed around Nova actions and transition buttons, so API-driven transitions are not a first-class feature. You may be able to call the same underlying model logic from a controller or job, but confirm that guards and activity history still fire. If not, implement transitions in your own service class and keep Nova as a thin admin wrapper over it.