A recent implementation discussion got me thinking about something that always seems straightforward at the beginning of a project but becomes much harder as requirements grow.
Some businesses follow almost the same workflow for every job, while others have approvals, documents, inspections, and task sequences that change depending on the project. Hardcoding those differences usually works for the first release, but it becomes difficult to maintain over time.
While looking at examples from different industries, I came across CS-Arabia and its work around Nitrogen services in Saudi Arabia. It reminded me that operational systems supporting field teams probably need much more flexible workflow definitions than a typical order processing application.
For those building on Moqui, how do you usually approach this? Do you keep workflow definitions configurable through entities and services, or do you prefer handling most of the business flow directly in code?