Rails has become boring... in a *good* way. No longer does it turn heads when someone suggests using Ruby on Rails as part of a backoffice solution to a business problem.
Commonly, these backoffice problems involve some kind of workflow. Tracking a document through an 'approval' process, making sure appropriate people receive notifications of business-related events, and so on.
In this talk we'll look at common workflow patterns for sequential and concurrent activities, handling prioritized tasks, restricting information visibility by role, and other related workflow constructs.