The "next generation" workflow module has been under development as Workflow-ng for Drupal 5.x and is our current module of choice for providing store administrators with web based order workflow configurations. Integration with Workflow-ng means we will be defining different events which can trigger actions assuming any specified conditions have been met. Confusing? Don't let it be. Here's a use case...
Let's say you've set the credit card module to automatically process payment at checkout. When sales come in, you don't always want to have to go manually review the orders to make sure payment was processed fine. A completed checkout has been defined as an event, so you can setup a configuration to process when it occurs. It is possible to update an order's status with this event using the action we've defined, so you can have it automatically move orders to Payment received. Simple enough.
But wait! What if you also let people pay by check? You don't want their orders to move to Payment received right after checkout, because, well, you haven't received the customer's payment. In this case you need to apply some conditions to the configuration. The simplest thing to do will be to check the payment method. You can add a condition that only performs the actions if the payment method is Credit card. This isn't foolproof if you start accepting payment through other methods like PayPal, so why not use a condition that checks the order balance instead? You can set it up so that it only performs the actions if the balance is zero and never think about it again. 
Pretty simple, eh? I'd like to think so, and I'll be working with the module's developer to iron out some kinks in the user interface. For now just use the 1.0 version and you shouldn't have any trouble. I'll let you know when some improvements have been worked into the module.
This thread will be used to track the various integration points of Ubercart with Workflow-ng. Lyle and I will both post comments on here that we will keep updated with the latest events, conditions, and actions we're integrating, and we're open to discussion of these and future ideas in the thread as well. Workflow-ng will make it into the documentation... well, when it makes it. 
Any clue where to find out more info?
