Thread:Talk:Flow Portal/Warning levels detection/reply (12)

Well, what I am seeing is the term "workflow" to describe multiple things, and it is not actually being used correctly. Workflows have rigid ordering of steps that must be done in a specific order or the end result is not correct. Much of what we do on our projects that is being described as a workflow isn't really. For example, when we block a user, we complete the block form, we may or may not leave a notice on the page (either personally written or using a template), we may or may not revert edits, we may or may not ask for revision deletion or suppression, and none of these has to be done in a specific order, or within a specific timeframe. Yet, this would be described as a workflow. There is no sequence, the only step that is mandatory is the actual completion of the block form (whose fields can be completed in any order), and the end result is the same whether or not any of the non-mandatory steps are taken.