Best Online Examples of Workflow Patterns?

g8orade writes "In his bestselling book, The World is Flat, Thomas Friedman lists workflow management software in the top 5 Flatteners. During my work for a shipping startup, I have analyzed our software's many UI weaknesses, particularly related to workflow management, and am currently searching for the best online examples of various UI application patterns / widgets that address managing transaction flows. What are the best examples you know of that are commonly viewable on the web?"

"Our software UI is Oracle (9i) Forms compiled to run with Java, through the web. We're using RT for our internal ticket tracking and it has many of the features listed. Also, we're evaluating several commercial document management systems as bolt-ons or companions to our in-house application. Here are some patterns we'd like to improve:

• Queue with count beside it. Example: 'Unshipped orders (5)'
• Screen for UI building of a search and ability to save the search as a queue
• List of queues showing all transaction counts and their various states
• Transaction list / table screen (should have an many possible features as a standard spreadsheet: pick your columns, column order, sort order, clickable column headings, export to various formats, print view, etc.)
• Detail view screen (one transaction, may include too many fields to display at once, requiring tabs, scrolling up and down, left to right, etc., should have a good printable view)
• Contact database built-in or connection to one from another system
• Auto messaging of various statuses to contacts and lists of contacts, above
• Full web accessibility and security model to allow our suppliers and clients access to their own queues for 'pull queries', in addition to what we email them.
• Ability to create a list of values for a field, then incorporate that into the query for a queue.
• Journal of a transaction
• Screen showing progression of a transaction
• Screen showing Parent / child parts of a transaction"

Why don't you DO YOUR JOB?

[Anonymous Coward]

It sounds like you are getting paid to solve this problem. Why should we solve it for you for free? Jerk.

Re:Why patterns?

[Anonymous Coward]

Agreed. It sounds like they want their own unique and very customized software solution. There is no such thing as a generic pattern for every different business application. Banks operate differently from clothing stores, which operate differently from auto shops. If there was such a piece of software, that you could buy shrink-wrapped off the shelf, push a few buttons (say about 10 buttons max), then be able to give it to some high school graduate to use on a daily basis, and have your small business up and running on that software platform in just a few days.... that would be an incredible feat and you would be a billionaire if you could invent such a thing. In fact, the closest thing to this is Google, which is basically a Universal Answer Machine. You ask it a Question (phrased in the form of a search query) and it gives you the Answer(s) in response. I would argue that only very few pieces of software have nearly universal applicability to businesses, and the Google Search Engine is one of them. Some people have likened Google's massive repository of knowledge to Artificial Intelligence, and I would agree. It is the closest thing we humans have created so far to Artificial Intelligence.

Re:Why don't you DO YOUR JOB?

[Tsar]

Afraid I have to agree with the AC, g8orade. You haven't even posted on /. since May '02 [slashdot.org] (and haven't answered anyone else's "Ask Slashdot" question, like, ever) and you're expecting everyone here to do your googling for you? Again? [slashdot.org]

I, for one, do not welcome our lazy, buck-passing overlords.

Re:Why patterns?

[JoshRoss]

I personally find patterns one-step away from being useless. They are almost by design so generic as to be applicable to everything that they are appropriate for nothing.

Friedman Says "workflow" But Means "Web Apps"

[Anonymous Coward]

Thomas Friedman lists workflow management software in the top 5 Flatteners

Read the book, AssHat! Friedman is NOT a developer and not even software savvy, so when he titles something "workflow", you have to read what he says, and what he says is "web apps".

Bad news is that every "Web 2.0" marketer is going to interpret Friedman's words in the most convenient way. Like the Far Side cartoon with two bears at the cave door fighting off humans: "Seems like there's more and more of these each year!"

Re:Why don't you DO YOUR JOB?

[sonamchauhan]

Because it makes for an interesting discussion.

Re:Why don't you DO YOUR JOB?

[WasterDave]

Nah, I disagree man. I'd like to know more about what the UI problems with workflows are ... I'm a really big project-management-software hater and am intrigued to see if there are any experiments with alternative UI's.

It happens to be (about to be) my job too, so you can accuse me of self interest too. But hey - interesting discussion. Better than some halfarsed regurgitated press release, eh?

Dave

Re:Why patterns?

[rossifer]

They are almost by design so generic [...] that they are appropriate for nothing

I find them useful for communication. If my design is similar to a pattern (most patterns are only part of any solution) then I can use the name of the pattern to describe my design more quickly. Often, because a pattern will include several distinct elements, I am able to convey several nuances of a particular design with only one or two words.

Explaining a design in terms of patterns is also a cool way of mentoring junior developers. You can back them out of the details of "this problem" and take a look at the more general situation, what the pattern suggests, and then go back to "this problem" and see how it fits in. Often you'll be able to elicit multiple "a-ha!'s" from the junior.

Back to your point, I find that the best pattern authors understand that they must strike a useful balance between generality and specificity. You still have to design the solution, but the top-level "how the heck do I get started here" is what's described by the pattern. Fowler tends to be better than the GoF at this particular skill.

Of course, getting the most utility out of patterns absolutely requires that you are an experienced designer (or are working with one). This means applying all of the classic design skills, including patterns, as appropriate to solve the problem (and that may mean no use of patterns for a particular problem).

Regards,
Ross

Re:YAWL

[BarryNorton]

Have a look at the YAWL project of the Business Process Modelling Group at the Queensland University of Technology.

Despite the title, he doesn't seem to really be talking about workflow patterns, but about common UI idioms that fit into a workflow-driven app (though some of these may be associated with data/resource patterns).